There are a handful of workarounds that have been floating around the Internet for some time but those of you who prefer a workaround that doesn’t involve implementing the MDT database or robust scripting languages like Powershell or VBS will be disappointed I’m afraid.
That’s why I developed a simple batch script to solve this problem. Before I get into how it works, please note the list of Prerequisites you must fulfill before adding this script to your Task Sequence. Also, I know the video is a bit rushed so I will put together a more detailed video at a later time that goes a bit more in depth.
If you have any issues please contact me @ firstname.lastname@example.org
A) In the Rules tab or CustomSettings.ini, Set OSDComputerName value to the first machine in the sequence(SalesPC01, MarketingPC01, etc..)
B) Create a shared folder that each machine can access. Create a shared folder that each machine can access
C) Add a “Run From Command Line” step to the Task Sequence and place it in the State Restore phase right above “Recover From Domain”
Editing The Script
There are two changes you will have to make to the script that I didn’t mention in the video and that is the username and password of an account that can authenticate to the network share.
Add Admin Creds
1) Find the :CreateLog step in the script,
2) Read my comments
3) Enter the your user credentials where applicable.
Click here to get MDTSequential code!
Have fun and enjoy!! 🙂