While running an OSD task sequence you can use powershell to check the TS Environment variables.
I added a ‘Pause’ step using this guide. If, like me, you are using an x64 PE image, you need use the ‘serviceui.exe’ from either the Program Files location on the machine with MDT installed, or a MDT package :
Recently I had an issue with a Windows 7 deployment, the winsxs folder was very large. I wasn’t able to look into whether this was a problem with our wim, or the updates process. But this is how I gained 7GB of space back…
This is how much space Windows folder was taking up before the cleanup process :
Troubleshooting OSD remotely can be difficult if the person initiating the build does not know how to get the logs from a failed machine.
This is a useful status message query to show all messages from the OSD process. It requires a Deployment ID, which is from the deployment of the task sequence you have a problem with.
left join SMS_StatMsgInsStrings
on SMS_StatMsgInsStrings.RecordID = SMS_StatusMessage.RecordID
left join SMS_StatMsgAttributes
on SMS_StatMsgAttributes.RecordID = SMS_StatusMessage.RecordID
where SMS_StatMsgAttributes.AttributeID = 401 and SMS_StatMsgAttributes.AttributeValue = "!!DEPLOYMENTID!!"
and SMS_StatMsgAttributes.AttributeTime >= ##PRM:SMS_StatMsgAttributes.AttributeTime## order by SMS_StatMsgAttributes.AttributeTime DESC
Replace !!DEPLOYMENTID!! with the deployment ID of the TS.