Number Your Task Sequence Steps

Profile picture for user PaulW

On several occasions at the local user group and at MMS, I have heard the discussion about wanting to have numbers in the task sequence steps that corresponds to the execution steps reported in the smsts.log file and those reported back to the ConfigMgr database (these are both the same numbering of course).  There is also a user voice that exists for this very item and has been there for quite some time.

An animation of a sample TS getting numbered

OSD Gather.vbs Script - Help Replace MDT!

Profile picture for user PaulW

Its seems that getting away from Microsoft Deployment Toolkit (MDT) has been all the buzz lately.  And really, for many of us, there is good reason to leave it behind.  Garytown recently posted a great article about getting off of MDT, and the goods and bads of having it.

Here is my own version of a custom Gather script to handle this payload in VBScript.

Architecture = X64
IsOnBattery = True
Model = Surface Book 2
Vendor = Microsoft Corporation
Make = Microsoft Corporation
IsVM = False
VMPlatform = 
Memory = 16308
Product = Surface Book 2
SerialNumber = 002123456789
BIOSVersion = 389.2370.769
..................and more..................

Post Upgrade Task Sequence Payload to User

Profile picture for user PaulW

For part of our upgrade process, we decided that we wanted to give users the opportunity to complete a survey to give us their feedback on the upgrade process.  We thought of an email but, figured that would be just as well ignored as any other bulk email.  So, I thought we could just dump something in the run once, or startup for the user that initiated the upgrade.  So, the first thing I needed to do was capture the user to a task sequence variable.  Sounds easy but, remember, the task sequence runs as system.