Here's an interesting issue I saw the other day that I thought I'd mention here just in case you run into it. I'm sure you're already familiar with all the client installation properties that can be specified when installing the ConfigMgr client but here's a gotcha you may encounter if the syntax of some of those properties aren't exactly right:
Issue: When you install a Configuration Manager client on a target machine, it may fail to register and as a result it's unable to pull the machine policies. You may also notice errors similar to the following in the ClientIDManagerStartup.log:
Error initializing client registration (0x80040222). ClientIDManagerStartup 1/8/2009 1:12:10 PM 1896 (0x0768) RegTask: Failed to refresh site code. Error: 0x80004005 ClientIDManagerStartup 1/8/2009 12:51:41 PM 1896 (0x0768)
Cause: This can happen due to incorrectly specified client installation properties. For example, let's say you defined the client installation properties as:
ConfigMgr does not validate the site code to verify that it should be limited to only 3-4 characters so since there's a comma but no space, anything specified after SMSSITECODE= is considered to be the site code. As a result, the installation command line becomes something like the following:
MSI PROPERTIES are REINSTALL=ALL REINSTALLMODE=vmaus INSTALL="ALL" SMSSITECODE="ABC,SMSCACHESIZE=1000" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="0" SMSPUBLICROOTKEY=<...key...>
Note that the SMSSITECODE is considered as "ABC,SMSCACHESIZE=1000" and the installation will actually proceed without any errors. However, this incorrect value is also stored in the registry and as a result the client is never able to successfully register.
Resolution: To resolve this issue we changed the client installation properties and removed the comma as follows:
After re-pushing the client, it showed the command line MSI Properties as follows:
MSI PROPERTIES are REINSTALL=ALL REINSTALLMODE=vmaus INSTALL="ALL" SMSSITECODE="ABC" SMSCACHESIZE="1000" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="0" SMSPUBLICROOTKEY=<...key...>
After doing this the client was successfully installed, it successfully registered and was able to pull the policies from the Site Server.
Hopefully this will help you either ID the problem or keep you from seeing the issue in the first place, and a big thanks to Vinay Pamnani for his work on writing this up.
J.C. Hornbeck | Manageability Knowledge Engineer
Just an FYI that I posted a note about how incorrect client install properties can cause ConfigMgr 2007
ConfigMgr 2007: Client registration fails and Clients cannot pull any policies Feed: The Configuration
please take the intelligence of the readers serious!