|
jhamel128 -> XPSP2 MDT2008 WDS LTI & Slipstreaming (4/16/2008 7:13:05 PM)
|
So there appears to be issues with XP SP2 being deployed via LTI w/MDT.
I started out quite ambitiously slipsteaming RyanVMs Updatepacks and Addons WMP11 and all current BTS Driverpacks method2, updated my source files via workbench, verified my unattend.txt info and booted via MDS PXE using the Lite Touch created wim. It seemed to be working flawlessly prompted for credentials asked the necessary questions for a LTI install then hangs with an error message that pops up behind the other current windows indicating that it couldn't find C:\MININT\unattend.txt. I Browsed the directory and verified that the file was absent. So I added a custom task (command line) to the task sequence: xcopy \\server\distribution$\control\buildname\etc\*.* C:\MININT\ . This caused the LTI script to bypass the login prompt and typical LTI questions and jumped right into installing XP SP2. After it completed it rebooted and started an unattended XP text mode install.
I terminated this and started over on my source files this time selecting BTS Driverpack method1 as I noticed that method2 runs a quasisetup to extract the drivers and add them to the registry I assumed the quasisetup was causing the issue. I reran setup using LTI failed no C:\MININT\unattend.txt readded the xcopy command line and this time it prompted me for credentials and asked me the LTI deployment questions. The source files took forever to copy so I checked file size and the driverpacks had ballooned the source files to over 1.5 gigs. I let this one run all the way through and it again rebooted and started an unattended text mode XP install. I allowed this one to run just to see what it produced, it ran setup, then reran setup, and finally bombed out I can't remember the error and don't care what it was.
I decided to go clean started with clean SP2 source no modifications, I did add the driverpacks files to the Out of Box drivers in workbench. Created New Client Task sequence disabled only the 3 unapplicable State Capture tasks and the State Restore sections. PXE to LTI asked all the right questions ran the unattened install rebooted and started an unattended text mode install.
I terminated this one and thought maybe it needs to reboot into PE to finnish out the LTI scrips so I added a apply WInPE task right after Install OS and Next Phase. This caused it to boot prompt for Windows Setup or Windows Setup with EMS support. I selected EMS and it booted to a PE environment and started running LTI scripts and said deployment was successful the computer is ready to use. I finnished out the wizard rebooted and it started running an unattended text mode install (which I allowed to finnish. This seems to have installed the OS using the unattened file I setup btw it did inject the drivers properly but this doesn't seem right.
If this is how the MDT deploys it's about the most unproductive productivity tool I've ever encountered.
I MUST be doing something wrong. Please enlighten me.
Thanks,
Ty
|
|
|
|
