I was having null certficate value problem associated with kb974571 I downloaded and installed hotfix 977203 on the server and added the patch command line specification to the client when it deploys. Problem is I use a migration task sequence to migrate clients from xp to windows 7. On these clients I run a ccmcertfix.exe utility as the first part of the task sequence. When the state store is requested, the task sequence fails. If I the ts again, it works. I have tried to change the task sequence to allow more time for ccmcertfix to run. This does not seem to be the issue. I don't know why, but ccmcertfix.exe seems to work randomly at best. I know this has been in the forums before: http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/f83b7577-1d52-4ccb-87c0-352c4b767697/ but there was no solution to it. I just wanted to bring it up again, so I could hopefully solve the problem and get my migrations under way. Thanks for any replies in advance.

yeah, we're experiencing the same thing on our end. lot of osd failures and so far no reliable way to fix. I'ved tried deploying 977203 patch and running ccmcertfix before we ever start the OSD task sequence, and it still is failing at the request state store. migh have to open a ticket with MS and see if we can get any help, cause this makes the whole OSD process pretty unreliable. so far on one machine that I had time to really play with, the only real fix was to uninstall and reinstall the SCCM client.

After you have applied the hotfix to your SCCM server make sure that you also perform the following steps: 1. In the SCCM Console, under Software Distribution, locate the package created by applying the KB977203 hotfix. Make sure that you have deployed it to your desired DPs. 2. Also under Software Distribution, locate your ConfigMgr Client Install Package. UPDATE the DPs to which the package has been previously deployed. Also note the Package ID for the client install. 3. Create a package and program for CCMCERTFIX utility. (see KB977203 for full details) (DEPLOY TO DP!) 4. Under Operating System Deployment/Task Sequences, right click on your selected task sequence and choose Properties. a. Click on the Advanced Tab b. Select (check) the "Run another program first" box c. Select the CCMCERTFIX Package and program that you created in step 3. d. Close properties of task sequence. 5. Right Click on task sequence and select EDIT. 6. Locate Setup windows and ConfigMgr task sequence step, ensure that you have the following under the "Installation Properties" section: PATCH="%_SMSTSMDataPath%\OSD\<Package_ID of ConfigMgr client install package>\i386\hotfix\KB977203\SCCM2007AC-SP2-KB977203-x86.msp" 7. Test deployment again... I have been fairly successful following the steps outlined in KB 977203. Others that I have assisted included the CCMCERTFIX program in the task sequence, as opposed to in the properties of the task sequence. NOTES: Please make sure that you pay very close attention to steps 1 through 3! At my client sites, this is where I see most of the causes of failures in this process...

so I have double checked that everytghing is ok with 1-3. we've even gotten to the point that we run the ccmcertfix and trigger a reinstall of the client , well before we start the builds. but we're still seeing about 20-30% failure rate at the request store task. and of the few I've been able to play with, only uninstall and reinstall fo the client seems to help. the only thing I've not implemented from teh KB is teh step 6 item, as that seems to affect the remaining steps of the task sequence, and not the request state store during the capture part, where we're still seeing success... we're basically at 100% success when we get past that cert issue...all the rest of the sequence, including restoring the user's usmt data. we just have the occasional failure still that I need to basicaly eliminate.

... only uninstall and reinstall fo the client seems to help. I am seeing this too. Clients just do not want to communicate with the MP. They receive their site assignment but then sit there... Doing nothing. I have forced them to update their policies and reboot and done all the usual troubleshooting tips but nothing. Just sit there. Nothing logged either... Remove and reinstall the client and it works again... Immediate policy evaluation... Any other tips?

I am having this issue as well.. Also, when I run the ccmcertfix manually I get 0 out of 2 certificates were fixed.. Seems the ccmcerfix does not even corret the issue when run manually.. Has anyone gotten around this?

Half a year later ccmcertfix does not work on Windows 7 SP1 and I'm still having this problem. What's going on?