Hello, My ConfigMgr site system consists of only a central site running in native mode. I'm trying to perform a push installation on two servers (One is running Windows 2008 Datacenter x64 and the other is a Windows 2003 R2 Datacenter x64 Service Pack 2.) with no success. DOM-DEV02 is the name of the 2008 server and DOM-SAV04 is the name of the 2003 server. I have checked the ccm.log and get the following messages: Received request: "VIQUCEMD" for machine name: "DOM-SAV04" on queue: "Incoming". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.542 2011 Central Standard Time><thread=3004 (0xBBC)> Stored request "VIQUCEMD", machine name "DOM-SAV04", in queue "Processing". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.542 2011 Central Standard Time><thread=3004 (0xBBC)> ======>Begin Processing request: "VIQUCEMD", machine name: "DOM-SAV04" $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.542 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.542 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Attempting to connect to administrative share '\\DOM-SAV04.bocpc.maddioc\admin$' using account 'BOCPC\Rintaro.Arakane'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.542 2011 Central Standard Time><thread=2216 (0x8A8)> ---> The 'best-shot' account has now succeeded 4 times and failed 2 times. $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.636 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Connected to administrative share on machine DOM-SAV04.bocpc.maddioc using account 'BOCPC\Rintaro.Arakane'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.636 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Attempting to make IPC connection to share <\\DOM-SAV04.bocpc.maddioc\IPC$> ~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.636 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Searching for SMSClientInstall.* under '\\DOM-SAV04.bocpc.maddioc\admin$\'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.636 2011 Central Standard Time><thread=2216 (0x8A8)> ---> System OS version string "5.2.3790" converted to 5.20 $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.870 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Service Pack version from machine "DOM-SAV04" is 2 $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:06.870 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Mobile client on the target machine has the same version, and 'forced' flag is not turned on. Not processing this CCR~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:07.042 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Deleting SMS Client Install Lock File '\\DOM-SAV04.bocpc.maddioc\admin$\SMSClientInstall.DOM'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:07.058 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Completed request "VIQUCEMD", machine name "DOM-SAV04". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:07.058 2011 Central Standard Time><thread=2216 (0x8A8)> Deleted request "VIQUCEMD", machine name "DOM-SAV04" $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:07.058 2011 Central Standard Time><thread=2216 (0x8A8)> <======End request: "VIQUCEMD", machine name: "DOM-SAV04". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:44:07.058 2011 Central Standard Time><thread=2216 (0x8A8)> Received request: "DOM-DEV02_BOCPC_MADDIOC" for machine name: "DOM-DEV02" on queue: "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.010 2011 Central Standard Time><thread=3008 (0xBC0)> Stored request "DOM-DEV02_BOCPC_MADDIOC", machine name "DOM-DEV02", in queue "Processing". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.010 2011 Central Standard Time><thread=3008 (0xBC0)> ======>Begin Processing request: "DOM-DEV02_BOCPC_MADDIOC", machine name: "DOM-DEV02" $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.010 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.010 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Attempting to connect to administrative share '\\DOM-DEV02.bocpc.maddioc\admin$' using account 'BOCPC\Rintaro.Arakane'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.010 2011 Central Standard Time><thread=2216 (0x8A8)> ---> The 'best-shot' account has now succeeded 3 times and failed 0 times. $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.088 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Connected to administrative share on machine DOM-DEV02.bocpc.maddioc using account 'BOCPC\Rintaro.Arakane'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.088 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Attempting to make IPC connection to share <\\DOM-DEV02.bocpc.maddioc\IPC$> ~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.088 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Searching for SMSClientInstall.* under '\\DOM-DEV02.bocpc.maddioc\admin$\'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.088 2011 Central Standard Time><thread=2216 (0x8A8)> ---> System OS version string "6.1.7600" converted to 6.10 $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.369 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Mobile client on the target machine has the same version, and 'forced' flag is not turned on. Not processing this CCR~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.416 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Deleting SMS Client Install Lock File '\\DOM-DEV02.bocpc.maddioc\admin$\SMSClientInstall.DOM'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.416 2011 Central Standard Time><thread=2216 (0x8A8)> ---> Completed request "DOM-DEV02_BOCPC_MADDIOC", machine name "DOM-DEV02". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.432 2011 Central Standard Time><thread=2216 (0x8A8)> Deleted request "DOM-DEV02_BOCPC_MADDIOC", machine name "DOM-DEV02" $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.432 2011 Central Standard Time><thread=2216 (0x8A8)> <======End request: "DOM-DEV02_BOCPC_MADDIOC", machine name: "DOM-DEV02". $$<SMS_CLIENT_CONFIG_MANAGER><Tue Feb 22 09:39:31.432 2011 Central Standard Time><thread=2216 (0x8A8)> I checked both servers and there is no sign that ConfigMgr client on them. Can someone please help me find out what's wrong? Thanks!

How are you checking for the ConfigMgr client? There will be nothing in Add/Remove programs. Checking for the SMS Agent service is an easy way.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I was checking in Add/Remove programs. I had no idea that's not where I had to check, my bad. Do I have to check it in services.msc? I already did and the SMS Agent Host service is running, is this the ConfigMgr Client? The two servers don't show up as clients in the ConfigMgr console. By the way, I haven't extend the AD schema. How can I check if the Management point is being publish to client computer through DNS?

Hi, The configuration manager client will appear in the Control Panel. Open the Icon properties and select the Actions tab. If you only have two actions then the site assignment has failed (meaning that the client will not be controlled by any site). about site assignment - http://technet.microsoft.com/en-us/library/bb681005.aspx Site assignment flowchart - http://technet.microsoft.com/en-us/library/bb932178.aspxKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Thanks. I checked the Configuration Manager Client's Action tab and it only has two options. So I guess the site assignment failed. When I performed the push installation I specified the SMSSITECODE, but it doesn't show in the Configuration Manager Client. I've tried setting the site code manually in the Configuration Manager Client's Advanced tab but I get the following message "Failed to update site assignment". I've also configured the DNS suffix of the management point in the Config Manager Client's Advanced tab. Is there something that I'm missing?

start by checking the clientidstartupmanager.log file and the clientlocation.log file both found on the client .\ccm\logsKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

This must be a really dumb question, but where on the client do I find the \ccm\logs? I looked everywhere and can only find the ccmsetup folder in C:\Windows\ccmsetup

C:\Windows\System32\CCM or C:\Windows\SYSWOW64\CCMKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

I checked the clientlocation.log and found this messages: <![LOG[Assigning client to site 'DOM']LOG]!><time="13:31:16.625+360" date="02-22-2011" component="ClientLocation" context="" type="1" thread="664" file="smsclientclass.cpp:485"> <![LOG[Unable to verify the sitecode 'DOM', AD schema is not extended or SLP is not present. Cannot continue site assignment.]LOG]!><time="13:31:16.640+360" date="02-22-2011" component="ClientLocation" context="" type="3" thread="664" file="smsclientclass.cpp:544"> <![LOG[Autodiscover Site]LOG]!><time="13:31:18.797+360" date="02-22-2011" component="ClientLocation" context="" type="1" thread="664" file="smsclientclass.cpp:1310"> I do not have my Ad schema extended but I do have Server Locator point install in my ConfigMgr Central site. This is what I got in the clientidstartupmanager.log: <![LOG[Error initializing client registration (0x80040222).]LOG]!><time="13:27:48.546+360" date="02-22-2011" component="ClientIDManagerStartup" context="" type="3" thread="2648" file="regtask.cpp:787"> <![LOG[The 'Certificate Store' is empty in the registry, using default store name 'MY'.]LOG]!><time="13:29:48.561+360" date="02-22-2011" component="ClientIDManagerStartup" context="" type="1" thread="2520" file="ccmcert.cpp:204"> <![LOG[RegTask: Failed to refresh site code. Error: 0x80004005]LOG]!><time="13:29:48.796+360" date="02-22-2011" component="ClientIDManagerStartup" context="" type="3" thread="2520" file="regtask.cpp:172 What do I need to do? Thanks

did you use the SMSSLP=SLPServer when you installed the client?Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

I did a push installation...Where do I have input that command?

Without AD extended, clients must use an SLP to find their management point and verify the version of the site. The only ways for a client to find the SLP is via WINS or if you manually input the SLP at the command-line. The best thing for you to do is to publish your SLP via WINS: http://technet.microsoft.com/en-us/library/bb632435.aspx http://technet.microsoft.com/en-us/library/bb632567.aspxJason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I don't have WINS available in my current windows server environment. So the only way to to publish SLP would be during installation. I want to specify installation properties during push install. I know have to input the commands in the Client tab of the Client Push Installation Properties dialog box. This may be a dumb question, but I don' know if have to separate the commands with a comma, semicolon or nothing at all. What's the correct way to input the commands? These are the following properties I want to specify: DNSSUFFIX, SMSSLP, SMSMP, CCMFIRSTCER, SMSSITECODE, FSP Thanks.

Nothing at all is the correct answer. These are actually public MSI properties passed to client.msi during installation. Thus is will look something like this: SMSSITECODE=XYZ SMSSLP=myslp.mydomain.com SMSMP=mydp.mydomain.com FSP=myfsp.mydomain.com CCMFIRSTCERT=1 DNSSUFFIX=mydomain.comJason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Thanks! I will specify these properties the next time I do a push installation. But now, how can I specify them in the clients that already have Configuration Manager Client install on them? I already tried changing the settings in the Advanced tab of the Configuration Manager Client dialog box. But the clients still don't get assign to the Central Site let alone find their MP.