Hi I have a query regarding what files / registry keys / (?) SCCM uses to keep track of state information. I’ve been reading through some old threads on this issue however have been unable to implement a successful solution, so hoping someone had some ideas regarding what I’m missing! We have Deep Freeze installed on machines that are required to run 24 x 7. SCCM is to be used to send updates to these machines. Given the machines are required to be up 24 x 7, scheduling a specific maintenance period is not ideal. Rather we want to use BITS to download updates in the background and then apply as per a given schedule (preferably at logout). However I’m having trouble getting SCCM to play nicely with Deep Freeze. After reading through http://social.technet.microsoft.com/Forums/en/configmgrsetup/thread/0e9b6cb9-181b-420f-89f1-d7714c7ac7a9 I implemented the steps outlined by Ross. Effectively: Start = no ccm client installed Thawspace created on T: drive Made use of the instructions in the above link to ensure: windows\system32\wbem\repository is first removed, and then is linked with the thawspace (via junction.exe) windows\temp is linked with the thawspace (via combination of unlocker and junction.exe) windows\system32\sccm is linked with the thawspace (via junction.exe) ccm client is installed I confirmed that all junction points were successfully created. I can confirm that, whilst Deep Freeze is “frozen” changes made to the linked “C” folders are also applied to the “T” folder and are retained after a reboot. For example, any changes made to the sccm cache or windows temp directory are still present after reboot, so junctioning appears to have been correctly implemented. The problem I’m seeing is that, if I push an advertisement to the client, initiate a “run” from the client and view the “last run time” everything looks fine. Upon reboot, the “last run time” gets reset to before the last advertisement .. Sccm cache, “last updated” dates for files in the repository, etc all appear to have been retained. Yet the last run time is reset and the client believes it needs to run the advertisement again. (Note that from tests, it appears the client doesn’t re-download the files – just runs the advertisement again). So, is there another location (folder? Registry key?) that SCCM uses to keep track of the “last run time” / ‘last advertisement run’ type information? (From my reading I thought that this information was in WMI but maybe that’s not the case ...) Thanks!!

Hi, I've just realised i've been looking in the wrong place ... found the registry key at: HKLM/Software/Microsoft/SMS/Mobile Client/Software Distribution/Execution History/

What did you do to Thaw that particular key? Thanks, Ross

What did you do to Thaw that particular key? Thanks, Ross Hello - What are you looking for? The details of key ? HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\Software Distribution\Execution History then read the keys and you see info such as: ProgramID Run start time State successorfailurecode SuccessorfailureReasonAnoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

When using Deep Freeze the registry gets reset everytime the computer reboots. yeahyeahnah pointed out that this key and values under it get reset when the computer reboots, causing the advert to run again. I am wondering how he made this key "thawed" in Deep Freeze similar to the steps I outlined for the WMI in the link he included. Thanks, Ross