LimeProselyte Posted July 3, 2014 Report post Posted July 3, 2014 The agency I work for is using SCCM 2012 R2 and is currently using static IP addresses for all of our machines. Because of this I have created a customized powershell script that is ran as a "pre-start package" for my OSD task sequence. This script asks the user for the machine name and IP address then sets the OSD Task Sequence variables and network adapter properly. I have the preferred Deployment ID hard coded into the variables. Everything works fine and I couldn't be happier. Currently, I am running the Task Sequence in an unattended mode. If something should go wrong with attempting to initialize the task sequence from the SCCM DP's, it just reboots with no indication of what happened (other than the obvious). With that in mind, I'm looking to try and improve the process by having some sort of warning pop up if there was a problem with the possibility of bringing the powershell script back up and/or fire off the proper commands to try and connect to the DP's again. Is this even possible? If so, what commands are ran to fire off the Task Sequence? I've seen the TSBootShell.exe and TSBootStrap.exe programs being called in the very beginning to start things off (located in the winpeshl.ini and TSBootShell.ini files), but I am not certain if I'm on the right path or not. Any help would be greatly appreciated. Thanks! Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted July 4, 2014 Report post Posted July 4, 2014 If you want to re-start the Task Sequence, issue the following command x:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:x:\sms\data Quote Share this post Link to post Share on other sites More sharing options...
LimeProselyte Posted July 7, 2014 Report post Posted July 7, 2014 Thanks a million, anyweb! : ) Quote Share this post Link to post Share on other sites More sharing options...
