Microsoft Deployment Toolkit 2012 (MDT) and WDS - Task Sequence not showing on WinPE
-
Friday, February 08, 2013 3:01 PMFor some odd reason, the Task Sequence list doesn't show when booting of PXE with WinPE.
Environment:
- Windows Server 2008 R2 Enterprise
- WDS Installed
- MDT 2012 Update 1 installed
- ADK installed (tried prior with AIK)
- System fully patched.
I created the DeploymentShare on MDT and configured only a basic Win 7 x64 OS deployment. Nothing else at this point. Added Boot Image on WDS (x64) and successfully booted through the network. When WinPE initiates, the Task Sequence shows blank.
Now, if I cancel the Task Sequence selection window and I type "cscript //nologo litetouch.wsf /debug:true" the Task Sequence window then shows successfully the task sequence I created.
I added credentials on the bootstrap.ini and CustomSettings.ini files and they clearly seem to be working as when run manually it all seems to work.
I have tested with both AIK - plus supplement - and now with ADK - achieving same results.
Any ideas? I spent way too many hours trying to get this to work. Is this a bug on Microsoft's part? HELP!
Thanks in advance!
All Replies
-
Friday, February 08, 2013 7:48 PMPlease post your customsettings.ini
-
Friday, February 08, 2013 8:34 PM
Here it is:
CustomSettings.ini
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
UserID=username
UserDomain=domain
UserPassword=password
DeployRoot=\\DIRECTOR\DeploymentShare$
SkipBDDWelcome=YES
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipDeploymentType=NO
SkipComputerBackup=NO
SkipBitLocker=YES
EventService=http://director:9800 -
Saturday, February 09, 2013 6:35 AMNote that UserID, UserDomain, UserPassword, and DeployRoot belong in your bootstrap.ini, not in your CustomSettings.ini. SkipBDDWelcome should be present in both CustomSettings.ini and bootstrap.ini if you are setting it.
David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek
-
Sunday, February 10, 2013 4:59 AM
I corrected this on CustomSeetings and still not working. What I don't understand is why it doesn't work on the first place, but if I run "cscript //nologo litetouch.wsf /debug:true" it then works fine.
Other thoughts? Thanks.
-
Sunday, February 10, 2013 6:54 AMAfter updating the bootstrap and CustomSettings, did you regenerate the Boot Disks and put the updated boot disk on WDS?
David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek
-
Sunday, February 10, 2013 1:58 PM
Yes, I even deleted them first to make sure they get recreated fully. I also added both x86 and x64 and tested both.
Is there a way to review the logs to find out what's going wrong? I reviewed the logs on the X drive after canceling the blank Task Sequence window, but couldn't find anything failing.

