We've now had several instances where the user state store on the State Migration Point was deleted prematurely. Our SMP is configured to maintain data for 7 days. However, in these specific cases the data was deleted approximately 36 hours after it was captured. (In all cases it was more than 36 hours but less than 37 hours.) The consistency of the duration leads me to believe that it is being caused by an automatic process (perhaps a cleanup script/stored procedure) but I don't know for sure. I've been looking for patterns where this occured but it has been difficult to do so. Let me give some examples of scenarios where we've seen this: Task Sequence is interrupted before completion but after user state is successfully captured. In this case the TS reports that it is still running when in fact it is not. Task Sequence fails at a step after successful state capture. In this case the TS reports successful completion (MDT-based TS template with error handling) but failed at or prior to applying OS. Task Sequence mistakenly restarted after successful completion and terminated prior to formatting system disk to avoid rerun. Computer with failed TS is PXE booted to same TS. Treats as Bare Metal deployment so no new state capture is performed. Bare Metal deployment also fails. Note that each of these may have further permutations such as failing at different tasks or the TS being restarted one or more times. The commonality seems to be that a successful state capture is executed but the TS never reaches completion. When examining the computer associations in the SCCM console, all of the associations still exist. They have a Date State Saved value and a State Delete On value but they do not have a Migration Date value or a State Location path. Given that the migration date is not populated, the store shouldn't have been flagged for deletion. Even if it had been flagged for deletion, it shouldn't have been deleted for 7 days. Why is SCCM deleting these state stores after 36 hours? What can I do to prevent this from happening?

WHat version (service pack level) of ConfigMgr are you running?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

do you have any other cleanup processes/scripts that could be deleting this data ?, what do your SMP logs say ? My step by step SCCM Guides I'm on Twitter > ncbrady

System Center Configuration Manager R2 w/ SP2 Help indicates version 4.00.6487.2000

To my knowledge, no custom cleanup processes or scripts have been defined--only what runs out of the box. I'm afraid you'd have to point me at the specific log and/or what I might be looking for to tell you what's in the logs. I've reviewed smpmgr.log and smpmsi.log and don't see anything that appears relavent to what we're seeing.