Differences in deploying XP via MDT 2012 vs deploying Windows 7?
-
Tuesday, September 11, 2012 6:53 PM
I set up an XP deployment in Windows XP and the same task sequences that worked fine with Windows 7 deployments seem to be ignored on XP.
The OS installs, the computer is joined to the domain and it stops at a login prompt. We have to log in to install applications and install Windows Updates manually when they ran automatically as task sequences when added to Windows 7.
We also don't get a notification screen at the end to let you know the deployment either succeeded or failed.
Is this normal or do we need extra steps in the task sequences for XP?
All Replies
-
Tuesday, September 11, 2012 7:27 PMThere shouldn't be a difference, MDT scripts take care of the different deployment techniques between OSes, for example, sysprep.inf or unattend.txt are used with XP, unattend.xml is used with Vista and above
David Sebban | Nelite North America | My Blog | Follow me on twitter : @davidsebban
-
Tuesday, September 11, 2012 8:02 PM
We are using a custom XP image that is already sysprepped and joins the domain as part of the sysprep process.
When we run deploy the image using a standard task sequence, the first part works. The drives are formatted and partitioned, the files are copied from the network, the computer reboots and joins the domain and then it just stops at a login prompt. It does not do automatic log on to run additional task sequences for installing applications or anything else and it does not show any failure messages.
-
Wednesday, September 12, 2012 1:50 PMYou should try to capture the reference WIM image using MDT too, there might be a conflict between your custom sysprep.inf file and the one used by MDT
David Sebban | Nelite North America | My Blog | Follow me on twitter : @davidsebban
-
Friday, November 09, 2012 4:59 AM
You should try to capture the reference WIM image using MDT too, there might be a conflict between your custom sysprep.inf file and the one used by MDT
David Sebban | Nelite North America | My Blog | Follow me on twitter : @davidsebban
I have just built a model PC with the basic apps that all users use and I would like to have it sysprep, and configure all the prompts that would otherwise pop up regarding language region, time zone and XP product key, join the domain and the have it install additional updated applications and install Windows Updates.
Our customsettings.ini is geared to Windows 7 which doesn't need a product key since we use KMS, so this seems like a conflict if we try to also deploy XP which requires us to enter the volume license key.
The way we have done it in the past is sysprep the computer manually, then import the pre-sysprepped WIM file into the deployment share.
What is the better way to do this? I have had problems attempting to sysprep and capture from MDT, so have been doing the sysprep in advance, but when we sysprepped in advance, task sequences past joining the domain do not run.
- Edited by MyGposts Friday, November 09, 2012 5:03 AM
-
Thursday, November 15, 2012 4:20 PM
there are several tasks to do when manually syspreping a machine and capturing it to make it useable with MDT. If you capture with MDT, then the build and capture task sequence should take care of them.
If you still want to do it manually, make sure you follow all the steps here http://technet.microsoft.com/en-us/library/dd349348(v=ws.10).aspx
David Sebban | Nelite North America | My Blog | Follow me on twitter : @davidsebban
-
Thursday, December 06, 2012 5:54 PM
Hello,
Try net use from client to map your mdt deployment share first.
I have a problem before when deploy win xp sp3, OS just go fine but no apps installed (access denied)
The problem was the mdt deployment share (Before i have this (MDT PROD XP)change to this no spacing MDT-XP and Everything work so good.
After that apps install, if you use spacing in share for win 7 deployment share its work.
.png)
