Imaging X201 with MDT 2010

I'm wondering if anyone else has seen this issue with the new X201 hardware - I have a captured WIM image of Windows XP SP3 that I am deploying out of MDT 2010. The image is deployed to the machine without any issues, but once it reboots and tries to begin the mini-setup, the machine hangs at a black screen.
I know that the proper storage drivers are installed, since the boot process does make a little progress - when I try to enter safe mode, the machine stops after (or maybe during) loading AGPCPQ.DLL, which appears to be some kind of video driver. These X201s have an Intel HD Graphics adapter. Has anyone else seen this issue? I'm on the most recent BIOS version, and the last thing I know to try would be including the X201 video driver in my reference image, which is something I'd rather not do. Has this issue bitten anyone else?
Thanks,
Andrew

With Lenovo's System Drivers for the Intel Chipset, extract them to a temp directory and import into Out of Box Drivers. Use Inject Driver step in task sequence and ensure Selection Profile includes MDT folder holding the files.

Similar Messages

WAIK 8.1 with MDT 2010.1

I worked on an SCCM contract about a year ago and ran SCCM 2012 SP1 with MDT 2010.1 integrated. Now the client has screwed around as they do and decided to upgrade SCCM to R2 to see if they could fix failing Task sequences. I've been asked to look into it
- I had a brief remote look and saw that the MDT database could not be accessed message was about the WAIK. Now I know you have to uninstall ADK 8.0 and install ADK 8.1 for SCCM 2012r2 upgrade which I think they did. I suspect therefore there's a
mismatch in the MDT version and newer
My question is can you upgrade i.e. install MDT 2013 on the server without affecting the setting in the existing MDT database which I set up previously?
Ian Burnell, London (UK)

Bump - anybody ?
Issue is I need to upgrade from MDT 2010 to MDT 2013. Because the client has installed ADK 8.1 in order to install SCCM 2012 R2 will I even be able to access MDT if I install MDT 2012.1 in order to upgrade the database which I don't want to loose. Perhaps
I might need to temporarily uninstall ADK 8.1 ??
Ian Burnell, London (UK)

Need to clone an Image created with MDT

Hi All,
I have a custom image which I created in VMWare with MTD 2013. The MDT server is local, I am the only one using it and it is not on the network or available in other sites. I was asked to provide an Acronis or Northon Ghost cloned image so that other admins
can image workstations/laptops without having to ship the device to me, to deploy with MDT. I thought about imaging a workstation and cloning the drive before sysprep starts, but the problem is that I run a task sequence at the end
Final Configuration for MDT 2013 LT created by Jonan, to delete any leftover by MDT (C:\MININT, C:\_SMSTaskSequence) and auto login the first time. I might be wrong, but I believe that the workstation needs to be connected to the MDT server for all task
sequence to complete.
What is the best way to clone this image?

Hi,
The simplest option IMHO would be to completely deploy a simalar machine using MDT and then, after deployment completes, run sysprep manually. Used with the option "shut down", your machine sould be off and in a syprepped state. Than manually create
the Acronis/Ghost image and distribut that.
Even better howerver would be to provide MDT deployment in your other sites. You can utilize DFS Replication to maintain a single point of administration, while still proving a coherent deployment method throughout your network.
Hope this helps,
Regards,
Martin
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.

Image creation with MDT task sequence- "Windows has recovered from an unexpected shutdown"

I'm using MDT 2012 U1 to build and capture a Windows 7 x86 image for deployment with ConfigMgr 2012 SP1. I'm using the standard client task sequence in MDT.
The MDT task sequence consistently fails after the reboot in the "Postinstall" group. The install OS, Copy Scripts, Configure, Inject Drivers, Next Phase, and Restart Computer tasks all execute successfully, then the MDT-initiated reboot
completes successfully. There is nothing else helpful in the SMSTS.LOG, these are the last entries in the log:
Successfully complete the action (Restart Computer) with the exit win32 code 0
Sending status message
Executing in non SMS standalone mode. Ignoring send a task execution status message request
Set a global environment variable _SMSTSLastActionRetCode=0
Set a global environment variable _SMSTSLastActionSucceeded=true
Expand a string %_SMSTSMDataPath%\Logs
Deleting file without retrying
The error message on the reference computer says, "Windows has recovered from an unexpected shutdown" along with "An existing in-progress deployment was found but is not in an expected state. Would you like to ignore this in-progress
deployment and start a new one?"
I have found one post that suggested modifying customsettings.ini with HideShell=Yes, which I tried. It didn't help.
I am not sure why MDT thinks the reboot was unexpected? Has anybody run into this? What steps can I take to narrow down the problem?
Any help/suggestions are appreciated.
Thanks,
FP

Thanks for your reply Phil.
Setuperr.log is empty, zero bytes. Setupact.log looks good to me, it has these entries at the end:
OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [Image_State_Complete]
OOBELdr.exe exiting with code [0x0]...
Process exited with exit code [0x0]
c:\windows\panther\SetupInfo succeeded.
c:\windows\panther\setupinfo.
Windeploy.exe exiting with code [0x0]
SetupSQM Started
Panther path is C:\windows\Panther
SQM not opted in
SetupSQM is finished
Our image environment was created during an MCS Engagement, so we have the solution pack and there are many variables in customsettings.ini. I will need to find out how to narrow this down but I'm not finding a log file that tells me where it's choking...
Any suggestions are appreciated.
Thanks,
FP

Windows 7 Embedded & MDT 2010 Update 1

Hi,
Is it possible to deploy Win 7 Embedded with MDT 2010 U1 ? Is it supported by MS ?
Thanks,
Regards.

Hi,
Yes you can. Please see this video
Deploying Windows Embedded Standard 7 with Style
regards,
Blog Microsoft |
Déployer Windows 7 |
Améliorer les performances de Windows 7

The Computer Restarted Unexpectedly 'loop' MDT 2010

I'm lost here, someone please save me! I have a WDS server with MDT 2010 and have been deploying successfully for months. All of a sudden we went to deploy a machine and the deployment stalls on step 52 of the task sequence. This is the first reboot of the
deployment where it is installing devices. It gets to 30% and just reboots. When it comes back it comes to the recovery page asking if you want to boot into safe mode or start Windows normally. I've been working on this all evening and am spent. It's the end
of my shift and I'm heading home but look to dig in first thing tomorrow. Please let me know what would help. All the logs look normal but I will be more than glad to provide anything that may help in someone getting me out of this mess.
Regards,
Joseph N. Sunderman | IT Professional

This will give an overview of MDT troubleshooting :
http://blogs.technet.com/b/askcore/archive/2012/05/08/mdt-2010-amp-2012-my-deployment-failed-what-and-where-are-logs-i-should-review.aspx
you can post your issues in MDT forums, in case you find something :
http://social.technet.microsoft.com/Forums/windows/en-US/home?forum=mdt
Arnav Sharma | http://arnavsharma.net/ 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.

How can i using MDT 2010 to deploy multiple partitions Windows 7 image?

Hello,
I am planning using MDT as a deploy windows 7 solutions. My Windows 7 is setup on parition 1 "C:" and users profile on parition 2 "D". I am already capture WIM for each paritions. How can i using MDT 2010 to deploy multiple partitions for Windows 7
image? together
Thanks

Having the users folder on a separate partitions is a bad idea because the Windows Setup was not really designed for it, it's more of a afterfix. In addition to that the deployment solutions in general have problem dealing with multiple partions.
Put it this way - The big warning text in the WAIK documentation about redirecting the users folder to another drive is there for a reason. It will break future offline servicing.
It doesn't mean it can't be done, it just means it will take you three times (at least) longer to setup/troubleshoot your deployment solution, and you will be in a world of pain the next time you want to re-image the machine.
This quote from a good friend of mine (Andreas Hammarskjold) describes it very well:
Generally I would always recommend to only have ONE partition these days. Going down the route of making multiple partitions is like having multiple wives/girlfriends/lovers… it’s all fun and games for a while but ends with disaster
- Andreas H.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Deploy win7 and linux image with MDT

We have been using mdt 2010 for our deployment in the last few months. It works perfectly. Now i am facing a bit problem, our organization decide to include a linux image into the standard one. Is there anyway we can deploy this linux image in mdt?

Sure you can, but it's not supported (at all) by Microsoft... :)
It's been a while, but I have tested two ways of doing this
1. Have a custom task sequence create a 50 MB fat partition, make it bootable using syslinux, copy the linux boot image to c:\, copy the kickstart script, create the syslinux.cfg, reboot, allow the kickstart setup to do the rest...
2. Have a custom task sequence use a disk image utility like dd for windows to just dump a cloned image...
I like option 1 the most...
Please don't consider dualbooting, its a beating, it just adds additional complexity... If they really need Linux and Windows on the same box, run Linux in a VM (or the other way around).
/ Johan

Office 2010 post SP2 updates deploy with MDT

So I'm looking forward to deploy my office 2010 pro plus (VLK media, activating via KMS host) with MDT, and I have some configs setup using Office Customization Tool to install it. I have the SP2 installer that installs after Office 2010 is installed.
Everything works well, however until i realize that are still a few hundred MB's of update (security patches etc) after the SP2 install. So allowing MDT to install the update on run time is not ideal ( consumes more time and bandwidth) so my question is where
can I get all the post SP2 updates for office pro 2010? (I'm assuming they're all .msp files where i can dump it all into the update folder in office).
Thank you for your feedback!

Hi Jack,
Microsoft Office sustained Engineering team publish news about security updates, public updates, service packs for Office in this site:
http://blogs.technet.com/b/office_sustained_engineering/archive/tags/office+2010/default.aspx
You can find all the Office updates that released each month in this site. However, the updates that applicable to your computer are really depend on your setup environment, not all that released are applicable.
I would suggest you to go to Windows Update, and Check for updates. Windows Update will automatically search updates that are applicable to your computer. You can choose to download the updates manually and save it
to your computer.
Thanks,
Ethan Hua CHN
TechNet Community Support

Install Font in Windows 7 with MDT

I need to install company fonts in windows 7. I use MDT 2010 to install OS and my applications, this works great, but when I try to install fonts (the way I use to do for XP,...objFontsFolder.CopyHere FontName...) it just does not work. The fonts are not installed.
How can I install a font using MDT in Windows 7
Thanks
Daryl

yes create a windows and fonts folder
yes I have done it under post install
It better to store reg file in the deploymentshare because during installation it is not easy to run or access a reg file from a network share.
Chris
I made folder as suggested and copied fonts that I wanted to use with new win7 image but after I re-imaged one of out laptops I cant see that those fonts are actually copied/installed.
Let me explain in steps what I did to avoid any confusion:
1. made folder under deployment share D:\DeploymentShare\$OEM$\$1\Windows\Fonts and added 10 diff fonts
2. added new tasksequence under post install (run command line) and added line regedit /s %SCRIPTROOT%\fonts.reg
3. made fonts.reg and added it to D:\DeploymentShare\Scripts
This is how fonts.reg looks like:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"somefont1 (TrueType)"="somefont1.TTF"
"somefont2 (TrueType)"="somefont2.TTF"
and so on to nr 10...
What am I doing wrong ?

MDT and Macs running Bootcamp – worked in MDT 2010, now does not in MDT 2012

I haven’t been able to find much info on this so I thought I would try here and see if anyone can help.
We’ve been using MDT 2010 for the last couple of years to install Windows 7 on Macintosh’s running Bootcamp and it’s been working fine.
We recently upgraded to MDT 2012 and the same process we used to use for this does not work anymore and I would like to find out how to make it work on 2012.
Here’s how the process works:
First, setup Bootcamp on the Mac. This creates another partition on the Mac for the Windows OS (partition 3 for MAC OS 10.6 and lower, partition 4 for OS 10.7 Lion because of the recovery partition).
Unfortunately Bootcamp cannot create NTFS partitions so it formats it as FAT32.
We then create a standard client task sequence using MDT and the Windows 7 source files (not a custom image) and give it a name to make it obvious it’s for Mac’s – “Windows 7 for Macintosh running Bootcamp”.
We edit that task sequence and disable the built in “Format and Partition Disk” step since we don’t need to create the partition, only format it as NTFS.
We then create a custom diskpart.txt file called BootCamp_Lion.txt with the following contents:
SELECT DISK 0
SELECT PARTITION 4
FORMAT FS=NTFS QUICK OVERRIDE
We place this file in the “Extra directory to add” location we’ve specified in the Win PE Customization section so it is located on the root of X:\ when it boots into Win PE.
We then add a command line to the task sequence: diskpart.exe /s x:\BootCamp_Lion.txt
to format the existing bootcamp partition as NTFS. Then in the “Install Operating System” step we set it to apply to a specific disk and partition – Disk 0, Partition 4.
This installs Windows 7 on the Bootcamp partition and leaves the Mac OS intact and has been working fine in MDT 2010.
Now with MDT 2012, the task sequence starts fine, formats the partition, installs Win 7, but when it comes up in the full OS for the first time I get the error “Unable to find the SMS Task Sequencer.
The deployment will not proceed.” And the task sequence stops.
I know the partitioning part has changed in 2012 and have read that you can get this error if you deploy to something other than disk 0, partition 1 but I’m wondering if I can accomplish the same thing that I used to have working in 2012.
Is there a different way I can do this? Any help would be appreciated.
Thanks,
Robb

Hi Guys
I have been having the same problem.
What I have done to get around it is
add a custom command as we all did in MDT 2010 to format partition 3 or 4 depending on the version of OSX
don’t disable the Format and Partition Disk task but tick in create active partition then remove the partition properties and then click on options and check
continue on error
then under install operating system change the partition that you want to have windows installed on
Once the deployment has completed you will receive the message that deployment has completed but with one error
Hope this helps
Regards
Matthew

MDT 2010 - USB 3.0 issue after OS Install and Inject Drivers steps

Hello,
I'm using MDT 2010 and I'm booting and image PCs from a USB drive. On some newer systems (eg: Latitude El530) I have issues when I use the USB 3 ports (if media is connected to USB 2 port, everuthing is fine). The systes recognizes the USB stick and I can
start the Task Sequence just fine. I pass the Install OS step and Inject Drivers step, but after the first reboot, I get the prompt to insert the media to continue the deployment. This happens only if the stick is connected to the USB 3.0 ports. If I
check Device Manager, I see the USB device withouth driver. The drivers are already on the USB stick...I puled them from FileRepository from an updated system with all the drivers. Is anyone else having similar issues? I see other people have USB 3 issues,
but mostlly to start the deployment from it, or at partitioning...I don't have that issue. My issue starts after the OS is installed.
Any sugestion is appreciated...Thank you...
aburica

You should be able to do this. nVidia Optimus video drivers have the same issue. How we solved this
We create selection profiles for each make and model
We inject every single driver in profile for each make and model
The Optimus driver then gets installed because it is local to the machine already.
Why it didn't work before is the child device never gets detected during the PNP enum that happens when you have 'Install only matching drivers from the selection profile' so never ends up in the local driver store.
P.S. We ONLY have the drivers that install imported into each make model folder.
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. ”
How to ask a question that is fixable.

WDS Multicasting MDT 2010 created SOE

I'm just wondering if the following scenario is possible with the setup we currently have. The architecture we've implemented is:
MDT 2010 on Win2008 R2. No clients build from this server.
Windows 2008 R2 servers with the WDS Transport Server role only. We have no AD in the environment, so this is what I'm limited to. Clients connect via PXE to these servers to image, using a WinPE LTI.
Multicast has been setup and configured, and it working successfully for the base OS .wim file only. Once the client moves further into the task sequence and begins installing additional applications, their traffic falls back to Unicast.
Is it possible to maintain multicast throughout the entire imaging process given this environment and its limitations?

Interesting setup. I think the answer is no. My thought process is:
- Boot LiteTouch wim via PXE - unicast for multiple machines
- multiple machines establish a session from which the deployment server starts sending out the blocks for the install.wim via multicast to clients at the same time.
- task sequence starts up at different times for the clients for first boot\OOBE and complete final tasks via unicast.
Once the install.wim is deployed, that piece is complete from multicast perspective. This would happen if you had a domain, so I don't think you environment piece is a factor. By the way, you may want to evaluate Windows Server 2012 as it supports
WDS with non domain joined configuration called "stand alone".
Configure Windows Deployment Services (WDS) In Standalone Mode in Windows Server 2012
http://technet.microsoft.com/en-us/video/configure-windows-deployment-services-wds-in-standalone-mode-in-windows-server-2012.aspx
If I recall multicast is actually slower than unicast unless the number of deployments you have going concurrently are quite high. This is the best link that I know of that shows the speeds based on deployment type:
Optimizing Performance and Scalability
http://technet.microsoft.com/en-us/library/cc732088(v=WS.10).aspx
Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
I concur with Dave's post.
It's not a limitation of your environment, however multicast is only supported for data images. Once the OS is actually deployed, and the task sequence continues within Windows, all network traffic will be unicast as it will only access the deployment share
through smb.
The 'general' cutoff as to where multicast will become more effective vs unicast in terms of computers starts at about 50, more then 50 unicast connections at the same time will generally cause the wds server not being able to keep up to serve the data.
This still depends on the server's hardware, unless it's a really high end machine with fast storage you might be able to serve more then 50 unicast at a reasonable speed.
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter:
@Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT
How to configure Windows RE/OEM Recovery Partition with MDT 2012 Update 1

MDT 2010 hangs on uefi equipped machines

Hi all,
I'm new to MDT (Started playing with the betas earlier this year), but I've been using WDS for nearly a year or so. I have an MDT 2010 server running on a Windows 2003 box with all of the latest service packs, fix packs, etc. The MDT server has been configured to deploy our install images to our test lab (We run everything from 2003 R2 up to 2008 R2). So far the MDT server (I upgraded the betas to the RTM code) has been running great on almost all of our machines, with the exception of our uEFI based machines.
We are primarily an IBM lab (We have a smattering of Dell and HP boxes, but none yet that have a uEFI Bios). We have mostly xSeries and BladeCenter products.
Our scenario:
We're running MDT 2010 in an LTI setup. No database, we just want the end user to be able to PXE boot the box, boot the Lite Touch 32 or 64 bit wim and then get the MDT screen that allows them to pick what operating system they want installed. Let the install start in the WinPE mode and then the WinPE mode reboots and continues on its installation path (DOS boot mode for the 2003 R2 installs , 2008 GUI setup, etc)
That part works fine for all of our regular xSeries (ie non uEFI) blades and servers. The user picks their OS, the preinstall phase starts, finishes and reboots out of the WinPE shell and then continues on with its next phase of the install.
Our uEFI enabled boxes (Mostly IBM HS22, x3200 M3, x3250 M3) boot into the MDT selection screen just fine. We can choose our os and the install starts in the PE phase (Sorry if I'm messing up the phase names still learning MDT as I go). Once the WinPE phase finshes, instead of rebooting (like the non uEFI boxes do) these boxes automatically open a Command Prompt window and then sit there until you close the window or type exit. I have not opened the command prompt (I know you can hit F8, but this is being done by MDT on its own). Once you manually close this window, the install continues just like it should.
I've updated alll firmware levels on these boxes to see if it might be something going on there, but no luck. MDT 2010 continues to hang (opens the command prompt) after completing the WinPE portion of the installation.
Has anybody else out there seen this behaviour? Anyone have any ideas how to correct it?
Thanks,
Jim Kosek

Hi there,
This is the original poster.
I had meant to list out our steps to correct this issue earlier this week, but this is the first chance I got to update this. Hate being the only one in on a holiday week :(
Like Keith stated above this is caused by the NETIMM.INF driver. Thanks to Keith's guidance in parsing through the log files (Especially since I had no idea where most of them were hiding) we were able to see that the NETIMM.INF driver would try and load during the Windows PE Setup phase. This driver does not appear to load correctly in Windows PE (I've been trying to get it to load into a different PE image for the better part of a year for other reasons). When this driver gets loaded during the PE phase, the installer would see that the driver did not load correctly. The installer would pop open a command prompt window to allow you to debug what went wrong. Since this driver isn't really needed for the installation, you could exit the command prompt window and your install would continue along just like it should.
If you look at your wpeinint.log file you should see something like this:
Info      Installing device usb\vid_04b3&pid_4010 X:\WINDOWS\INF\netimm.inf failed with status 0xe0000219
Info      Spent 19095ms installing network drivers
Info      STATUS: FAILURE (0xe0000219)
Warning   Applying WinPE unattend settings failed with status 0xe0000219; ignoring shutdown settings
This is what hangs the box.
When Keith first pointed me to the driver being the problem, I just removed the driver from my Out-Of-Box-Drivers and still had the issue. The NETIMM.INF file is part of the base install media so it shows up anyway. I then did just what you did by disabling the Commands on the USB Interface. This basically stops that device from being available during the install, so no device, no driver and MDT is happy and reboots like it should.
The problem I have with that solution is that all of the OS Firmware update disks from IBM want to try and communicate through that USB device when you go to update anything on that machine (uEFI code, Diagnostics, ASU, etc). So if that device is not there, then you cannot use any of the on-line flash utilities to update your machine. Not sure how many machines you have (or how often you upgrade the Firmware on them), but that might come back to bite you later. Plus you also have to remember to disable that on all of your IMM equipped machines BIOS's. And then when a user resets the Bios back to defaults that USB device gets turned back on again and you start getting calls that the deployments are hanging. I'm in a test lab and we get new machines brought to us all of the time. I may not be the one to set it up and then I have to rely on somebody remembering to change a setting in Bios. I'd rather just change it globally from my end and then I know its fixed. But to each their own.
I did like Keith suggested and edited the WIM files. I simply renamed the NETIMM.INF to NETIMM.OLD and closed the WIMs back up. I too was worried about having to change the WIM files repeatedly. I'm the one that built out our MDT server. My co-workers know enough to rebuild the deployment share if need be, but they don't use MDT enough to know about mounting WIMs and changing files and such. What I did was I changed these on our base install media. In my case, MDT picked Windows 7 to build out the 32 Bit LiteTouch.wim and 2008R2 for the 64 bit LiteTouch.wim file. Once I changed these on the original disks, all of my LiteTouch rebuilds have kept this change intact. Now if I ever change these original disks and have to completely rebuild the WIM files, I'm sure I'll forget to make that change. However I'd rather deal with that then (My end users will let me know if the installs start hanging again) instead of having to remember to change each machine's bios settings.
Now since the NETIMM.INF driver is no longer on the install media, I need some way to add that driver during the installation and not during the PE phase. What I did was to add the NETIMM.INF file into my Out-of-Box Drivers section. I then created a new selection profile called LiteTouch. I added all of my necessary drivers, with the exception of the NETIMM.INF driver, into that new LiteTouch selection group and I changed my LiteTouch Components to only load from the LiteTouch Selection group during the PE phase. I then call my All Drivers group during the installation of the Operating Systems. That way I do not get the driver during PE, but I get the driver installed during setup and I can then talk to the IMM for updates and such.
My way might not be the best way for everyone else, but it does what I need it to do.
I would like to take a minute though and thank Keith again for all of his help in troubleshooting this problem. We have a lot of remote users and this was causing them some grief because they would start a deployment and expect it to be done when they came back later. On the IMM equipped machines, they would be staring at a command prompt screen and have no idea what went wrong. I would then get calls stating that the install failed. Without Keith's help I'd still be getting those calls from our users.
Jim Kosek

MDT 2010 Vista cannot finish after joining domain

Hi,
I have a problem with deployment process after joining domain. I am deploying Vista using MDT 2010 with LiteTouch. Everything works fine. However, deployment process stops after joining domain. I suppose that autologon is disabled/don't work after joining domain and all following steps can't be started.
What is wrong with my configuration or Task Sequence?
Thanks in advance, Jan.

Hi Jan,
Thank you for your post.
As you said that the deployment process stopped after joining domain, may I know if there is any error received? If so, please let me know the details.
Meanwhile, I would like to share the following with you:
Avoiding Legan Notice that breaks MDT autologon
http://blogs.msdn.com/alex_semi/archive/2009/08/28/avoiding-legan-notice-that-breaks-mdt-autologon.aspx
Thanks.
Nicholas Li
TechNet Subscriber Support in forum
Nicholas Li - MSFT

Imaging X201 with MDT 2010

Similar Messages

Maybe you are looking for