Thursday, January 10, 2013 4:30 AM
Part way through testing our deployment for Windows 8 and I'm looking at automating the image creation with MDT (as is the best practice). I'm trying to use LITSuspend in the task sequence to install a couple of apps that need special attention while we test.
I was under the impression that you LTISuspend will pause the task sequence indefinitely until the script is run again from the desktop, I am starting to find that this is not the case. What I need to do is paus, install an application, do several restarts and then continue with the task sequence. At the moment it will pause no problem, but when I restart, it continues with the 'Applying WinPE' and sysprep stages.
Is this the expected behaviour or is something going wrong?
Thursday, January 10, 2013 6:36 AM
First, I'd ask why you aren't scripting or automating your "special attention" application? Pretty much anyone on these forums is going to ask the same question and point out that automation is the entire point.
Secondly, yes, that is the expected behavior. MDT puts hooks in the registry to restart once the OS has rebooted, so in effect when you reboot you are telling it to "continue" from wherever you paused it. You could likely remove these entries, do your reboots, then put them back, but I'd go back to asking why it isn't being automated in the first place. If you are just testing to figure out how to automate your app install, you may want to figure those steps out outside the Capture Task Sequence, then build a script to accomplish it and automate the entire Capture as is best practice.
David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek
Thursday, January 10, 2013 11:09 AM
i don't think it is expected behavior at all when i suspend my task sequence i can restart all i want without problems with a suspended task sequence.
the only thing that could go wrong is if your boot order is wrong and it pxe boots to mdt again.
Thursday, January 10, 2013 8:56 PM
That is exactly my point, the condescending tone above didn't really help at all.
@DC The reason I haven't 'scripted' it as you put it, is because this particular application would be more effort to 'script' than the whole deployment has been so far. As this is just for a preliminary trial of Windows 8 to see if it is even worth going to, the effort at this stage is not warranted.
You might have nothing else to do all day, but at my work we are pressed for time as it is.
@Stefan Thanks for the response, from what I had read I should be able to restart as many times as I want until I run the script again. Seems really strange as I tested it with a fresh Windows 7 deployment to and it is still not behaving as I expected. Late yesterday I also created a fresh deployment share with Win 8 Pro and Win 7 Pro and I'm still getting that behaviour with both. One other thing is that apparently I'm supposed to see a pop-up to say that the task sequence has been suspended, but I'm not seeing that either.
At least I now know that isn't the way it's supposed to work I can look into it further.
Friday, January 11, 2013 8:27 AM
i think your task sequence isn't properly suspended then since you should get that pop up with that your task sequence is suspended.
i take it you have this in a run command line task?
cscript "%SCRIPTROOT%\LTISuspend.wsf"also advise to look in your log files if you can find out if something went wrong there.
Saturday, January 12, 2013 8:11 AM
I have 2 questions that may help.
1. Are you using MDT to create the image or MDT integrated into SCCM?
2. Where in the task sequence are you putting the command line to pause MDT?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
Sunday, January 13, 2013 8:46 PM
Yep, thats the command.
I actually just upgraded my own PC to Windows 8 and havent had a chance to reinstall the ADK so I'll be doing that today.
Sunday, January 13, 2013 8:48 PM
1. Just MDT, no SCCM currently.
The first time I tried it right at the end just before the last restart (before the capture tasks). When that didn't work I put it into the 'Custom Tasks' group but had the same result.
I've actually just formatted my workstation to put myself on Windows 8 so I don't have anything set up currently but I'll be getting that up today so I can do some more testing.
Thanks everyone for your time!
Wednesday, January 16, 2013 1:39 AM
After freshly rebuilding my workstation with Windows 8, ad starting from scratch with a new deployment share (with only Win7 Pro added) I haven't seen the problem recur. So unfortunately its fixed for me but with no solution.
I'll be adding Win8 again shortly so I guess I'll just report back if the problem happens again.
Thanks for everyone's time.