The Case of the Disappearing Task Sequences November 13, 2009
Posted by tmintner in MDT 2010, VBscript.Tags: DeployRoot, Empty, MDT, Task Sequences
trackback
We’ve gotten quite a few emails on this so I figured it was time to put this on the blog. 
The problem that most people run into is that sometimes when they go through the Lite Touch Client Deployment Wizard, the task sequence list is empty. So what causes the task sequence list to be empty? The simple answer is if the DeployRoot cannot be found or is incorrect. The DeployRoot is the location of the DeploymentShare or content of the MDT Media Point.
Here is the basic process that should help troubleshoot the problem:
· Windows PE boots up and runs litetouch.wsf
· Litetouch.wsf calls ztigather /inifile:bootstrap.ini and the DeployRoot value is read from the bootstrap.ini
· Litetouch.wsf then makes a call to connect to the DeployRoot using the wizard credentials or the credentials in the bootrap.ini
· Litetouch.wsf then calls ztigather and reads the values from the customsettings.ini (note if a full Media Deployment is inserted in the DVD or USB drive the customsettings.ini will be read from that location instead of the DeployRoot)
· If the DeployRoot value has changed In the customsettings.ini, the value is updated and Litetouch.wsf tries to connect to the DeployRoot
· The wizard is started and the tasksequences.xml file is read from the DeployRoot
· If the DeployRoot does not contain a valid tasksequences.xml then a blank Task Sequence wizard is displayed
Steps to troubleshoot:
· Open BDD.Log
· Search for the value DeployRoot and do a Find Next to make sure that all values in the log file for DeployRoot are the same. If they are not then there is some setting either in CustomSettings.ini, the database, or on local media that is changing the value
I also had this issue when booting litetouch X86 and looking for x64 task sequence. They are hidden
That is a great point! That would be another scenario where the task sequences would not be displayed
[...] Often the issue involves the DeployRoot value isn’t quite correct. Tim Minter does an excellent job discussing this on his blog: http://deployment.xtremeconsulting.com/2009/11/13/the-case-of-the-disappearing-task-sequences/ [...]
I’d hoped this blog thread would help solve a problem that showed up with our upgrade from MDT 2008 to 2010, but our problem is slightly different than that described above.
After booting to PXE from the client PC via WDS, WinPE challenges for credentials as normal but it now takes about 10 minutes for the Task Sequence menu to display! Once it does, everything works as expected but I’m totally stuck trying to figure out why there’s now this long delay.
I’m fairly new to the MDT world and so am not completely versed in the idiosyncrasies and what all of the multiple scripts do. I did use one of your articles to get the hardware model device driver database working (thanks!), but this one totally has me stumped.
Hi Warren
Did you ever manage to resolve this issue ? We just upgraded WDT from 2008 to 2010 and have the same issue. infact for us it take more thn 20 minutes for the TS menu to show up. If you manged to get this resolved , can you please let me know how it was done? Thanks in advance.
Geez! I thought I’d posted our solution. My apologies.
We discovered that each section of the CustomSettings.ini file had a reference to the SQLShare on the MDT server. We commented all of those out based on info gathered from other sources. The connection speed reverted to normal.
Hope that helps!
Another possible issue is NTFS permissions inside deploy share.
Deploy share was restored from archive.
I had the empty list.
NTFS permisson’s replace is fixed the issue.
FYI.
I noticed that this is also happening for me too. I’m trying to deploy Win 7 x64. Created the Lite Touch boot image and placed in WDS. Booted up with the Lite Touch x64 boot image and when it was time to display the list of available task sequence it was empty. So I cancelled that window and in the command prompt I ran cscript //nologo litetouch.wsf /debug:true from x:\deploy\scripts and this time the available task sequence is now populated.
Has anyone else seen this? If so can you help in resolving this issue?
Hi Tim,
Can you post the question and the bdd.log file to the MDT technet forums or just post your bdd.log in the comments.
Thanks