Since I’m working with ConfigMgr there was always the question of the staging team or end users if the staging of a device has really completed. Many years ago, I created a script which solved this question. Now I got again a few requests of customer and also discussions at
One and a half year ago I posted an article about a problem which every OSD Enginer should know. Some Windows Updates make multiple reboots and this behaviour breaks a ConfigMgr Task Sequence as described in KB2894518. Until now we had to use some workarounds to block these updates from
Often I see the following issue, updates are installed during a Task Sequence, then the Task Sequence doesn’t continue after a reboot. In the smsts.log are errors like these: !sVolumeID.empty(), HRESULT=80004005 !sTSMDataPath.empty(), HRESULT=80070002 TS::Utility::GetTSMDataPath( sDataDir ), HRESULT=80070002 Failed to set log directory. Some execution history may be lost. The system
Copyright © 2023 Workplace Ninja’s. All Rights Reserved. – Code of Conduct, Webpage Terms of use and Webpage Privacy Policy