Category: TaskSequence

Best Practice
Thomas Kurth

Best Practice: Complete Naming Convention for ConfigMgr CB

A few weeks ago I posted and updated poster for the collection structure and naming conventions. because of the great feedback I got I have now added a new poster for objects like Task sequences, applications, packages and WIM files in the ConfigMgr Console. Additionally I have moved all posters

Read More »

Update: Multireboot issue with Windows Updates is solved

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

Read More »

Windows Update Issue which every SCCM OSD/OSI Engineer should know! (KB2894518)

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

Read More »