OSD issue: ConfigMgr client not cleaning up properly

[jkurtz]

Hi all,

 

First time post. Let me say this has been a fantastic resource and that I've learned much from searching existing posts. That said, I've finally come across an issue I don't see others experiencing.

 

I've installed SCCM 2007 R3 and have my Windows 7 x64 OSD TS nailed (or so I thought...), with much help from reading this site. I'm moving on to the next step of installing software through collections and noticed software wasn't installing until I rebooted the OS. Digging further, I noticed the "Setup windows and ConfigMgr" portion of the task sequence is setting the "PendingFileRenameOperations" (http://technet.microsoft.com/en-us/library/cc960241.aspx) key in the registry, and my package is failing to install because of that key. Rebooting the OS or manually deleting the key allows software to install normally.

 

Next, I thought I would simply add a "Restart Computer" to the TS and call it good. That didn't work - in fact, I can see that part of the TS go by but the machine doesn't reboot. As a work around, I could write a script to kill the PendingFileRenameOperations key, but it seems to me something isn't completing properly. I'd rather not work around something that may be a side-effect of a deeper issue.

 

For what it's worth, I have my SCCM client package set up using the pre-configured template "package from definition," and in the Setup windows and ConfigMgr step I have the following for Installation properties - note the R3 patch for the client:

 

SMSSLP=jkurtzw2k8r2dev.jkurtz-test.local
SMSMP=jkurtzw2k8r2dev.jkurtz-test.local
FSP=jkurtzw2k8r2dev.jkurtz-test.local
PATCH="C:\_SMSTaskSequence\OSD\LAB0000B\i386\hotfix\KB977384\SCCM2007AC-SP2-KB977384-x86-enu.msp"

 

I'm attaching my exported TS as well as the smsts.log file captured from the deployed OS. As you can see from the smsts.log file, it looks like the TS is indeed having some issues cleaning up, but it otherwise exits without an error. I'll be trying to figure out what's wrong but would be grateful to anyone that may have some insight.

 

Thanks,

Jeremy

OSD-TS.xml

smsts.log

[jkurtz]

Update: I firmly believe this is a bug in SCCM. PendingFileRenameOperations gets set at the end of the OSD TS no matter what I try, and I'm able to replicate it every time in various environments.

 

Rather than waste any more time, I will be modifying our MSI packages to ignore this flag. More details for anyone interested here: http://msdn.microsoft.com/en-us/library/aa370492(v=VS.85).aspx. I'm likely more affected than others due to using Installshield to repackage our applications, which sets this MSI LaunchCondition by default.

 

Thanks,

Jeremy