Since I recently posted pretty much everything that needed to be done to get this working properly on TechNet forums, I figured I might as well write a proper guide for it now.
I can imagine that some are like “why would you even want to?” well, it’s rather simple… there are still end-users who use this OS. And some of them can’t install Windows themselves, so they bring their pc to a local pc store, or any other pc system builder (with the exception of the “A”-brand OEM’s). Depending on the size of these companies, some might actually still do everything manually when it comes to installing Windows. Some might still keep a Win2003 server with RIS around for Windows XP installs. When I was setting up our deployment server, we already had a running deployment solution with RIS/WDS running on a server 2003 in hybrid mode. Windows Vista and Windows 7 installs were very slow due to the slower network stack and larger file sizes of the images to deploy. At first I created a new server to install just the Vista/Win7 with WDS, and soon thereafter using MDT as well (MDT had some limitations for me at that time which I first needed to work around creating scripts). But I was still stuck with an old RIS server for Windows XP installs, and really wanted to stop using 2 virtual servers for the deployments so it’s less management. Windows XP Professional was all very easy to do on MDT, however Windows XP Home Edition causes me a few errors down the road. I’ll describe the error’s you’ll run into when trying to deploy windows XP Home Edition with MDT 2010 and how to fix them.
First off, when you try to Import a new OS from source files and select a Windows XP Home disk, you will get an error saying:

Import Error

To fix this error, you will need to fool MDT thinking that the OS you’re trying to import is Windows XP Professional. To do this, you will need to rename a file in the root directory of the XP Home source files. One of the files below will suffice, however you can change them all if you want, the “highest” SP level that is changed from IC to IP will be the one that MDT will detect as an XP Professional source file directory.
• Win51IC > Win51IP (changing only this file, will make MDT recognize the imported OS as Windows XP Professional)
• Win51IC.SP2 > Win51IP.SP2 (changing only this file, will make MDT recognize the imported OS as Windows XP Professional SP2)
• Win51IC.SP3 > Win51IP.SP3 (changing only this file, will make MDT recognize the imported OS as Windows XP Professional SP3)

XP Home detected as Professional SKU

Above is an example where I only changed Win51IC.SP3 to Win51IP.SP3, notice how the default name MDT suggests is Windows XP Professional SP3?
Now you can continue to import the OS into the workbench.
The next error that you will run into is that MDT will try to auto-logon as the built-in Administrator account, named “Administrator”. While this account is actually marked as active, it’s not possible to log into this account unless booting from safe mode. Sometimes you might not actually see there is an error happening at this point and you will simply see this screen:

Windows XP Home logon screen

However, if you look closer and ALT-Tab you’ll see the following error:

Windows XP Home logon error

To resolve this, you will need to change the auto-logon settings.

Update: 04/11/2012;

To simplify the auto-logon fix discard my previously written explanation as the following method is far easier. You need to edit the Unattend.txt file of existing task sequences and change the following value as displayed below. Alternatively you can enter the same value (Computer’s Owner) during the creation of a task sequence in the screen that asks for Owner (this is the field you need to fill in with this value), Company name and website.
Note: Despite this value is written in English, it will translate correctly to all other languages of Windows XP Home you will install. I have verified this with multiple different language editions of XP Home, and the Autologon works correctly.

[UserData]
FullName=”Computer’s Owner”

 

We will need to edit the file “unattend.txt”, you can easily edit this file if you open the properties of the Windows XP Home task sequence (I presume you already created one after importing the OS, if you didn’t yet you will need to create one first) and go to the OS Info tab. From there click Edit Unattend.txt
The part we’re looking for is this;

[GuiRunOnce]
“cscript.exe C:\MININT\Scripts\LiteTouch.wsf /start”
“cscript.exe D:\MININT\Scripts\LiteTouch.wsf /start”
“cscript.exe E:\MININT\Scripts\LiteTouch.wsf /start”
“cscript.exe F:\MININT\Scripts\LiteTouch.wsf /start”

We’ll add a command in here that will change the Auto-logon value to the correct username. For the English version of Windows XP Home, it will be “Owner”, you will have to find the correct username if you use a different language. This is the default account created by the setup.

[GuiRunOnce]
“regedit /s C:\MININT\Autologon.reg”
“cscript.exe C:\MININT\Scripts\LiteTouch.wsf /start”
“cscript.exe D:\MININT\Scripts\LiteTouch.wsf /start”
“cscript.exe E:\MININT\Scripts\LiteTouch.wsf /start”
“cscript.exe F:\MININT\Scripts\LiteTouch.wsf /start”

Now, create a new text file, and make sure to include the following text. Then save it as Autologon.reg (or name it differently if you want, but then adjust the filename again in the GuiRunOnce section of the Unattend.txt

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
“DefaultUserName”=”Owner”
“AutoAdminLogon”=”1”
“AutoLogonCount”=”999”
“DefaultPassword”=””

At last you need to ensure that this file will be present on every single Windows XP Home installation. There are several ways you can achieve this, for example creating a new task in one of the early TS stages. The method I used, was making use of the $OEM$ folder within DeploymentShare\Operating Systems\{OS Name}. An example of this is shown in the picture below.

Windows XP Home $OEM$ folders

Now that the autologon will work again, the task sequencer can continue just like a normal Windows XP Professional installation. I hope this information was helpful to those few people who might actually need to deploy Windows XP Home edition for whatever reason, and couldn’t get it to work with MDT and for that reason were still stuck with RIS. If you happen to run into an issue, feel free to leave a message or contact me.

Stephan-

Be the first to comment
Share this by email. Share on Facebook! Tweet this! RSS 2.0 TOP

[Edit 03/11/2011] Hotfix KB981542 fixed this problem. Service Pack 1 for Windows 7 also resolves the problem.

I’ve tried to assist someone on the TechNet forums who was getting an error once he had created his reference image to his wishes and
ran sysprep to use it for further deployments and then try to boot into it. Here’s the link to the topic on TechNet;

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/88fd6905-0454-4db0-ab5f-3718b640fbb5

The error looks like this (if you let it reboot, it will just come up again, over and over):

Windows could not finish configuring the system. To attempt to resume configuration, restart the computer.

We both realized quite soon that it had something to do with Live Essentials 2011, so I went to test a lot…

I think I’ve done about 5 installs of windows, clean installs, one of my old images that I have at my
test deployment environment at home and images that we ship out to ourcustomers,
I loaded all of these in VM’s and ran sysprep around 30 times, it starts to get old.. fast

At first I could not trigger the issue at my work pc’s, and the reason for that is because I don’t need to generalize the pc’s there (unless we
have a large order for a company). As soon as I manually ran sysprep with the generalize option, I was getting exactly the same error.
This was an image that I built in early July right after the Office 2010 OPK was released. It contained most updates up to this date Live Essentials 2010 and Office 2010 Starter.
If I ran sysprep /generalize right after the deployment of this image, without letting it self update and install WLE2011 there was no error.
I then ran WLE2011 to update the 2010 programs, and tried again and the image was still ok.
However, after applying the more recent updates after WLE2011 was installed on the machine, and I’d try to sysprep /generalize the error would be there!

It’s really simple to recreate this error, pick any flavor of Windows 7, x86 or x64, Starter all the way through Ultimate/Enterprise, they will all do the trick.
Do a clean rtm install, install WLE2011, either through WU (this will download the executable of 160mb containing the everything),
or download the web-dl installer from the WLE site, or install it through the OPK and then lastly run all the windows updates.
Once that is all done, sysprep your pc with the generalize option, and the error will be there.

Next I’ll list all the various combinations that will trigger this error, and what does not. And at the end of all this, I’ll provide you with a solution.
The error can appear if you fulfill any of these requirements.

Applies to any version of Windows 7 (I did not test this on Vista)

  • It will not  matter which WLE2011 installer you use; whether it’s the OPK, wlsetup-all.exe or wlsetup-web.exe results are the same.
  • The error applies to any particular part of WLE2011, it’s not just one component as soon as any component has been installed, or all you become eligible for this problem.
  • If you have this problem, and have already installed WLE2011 prior to running Windows Update, it will not solve the problem by simply uninstalling WLE2011.
    As soon as it has been installed, and still have updates to install, then
    you’re out of luck.
  • Only updates that require you to reboot your pc, will cause the error.

The error will not show up if you do not generalize your
image.

At least there is a solution, [cut] apply the appropiate hotfix or sp1.

 

Be the first to comment
Share this by email. Share on Facebook! Tweet this! RSS 2.0 TOP

What makes it worth writing about this? Well the thing is, with this new reference driver nVidia has changed the installer, it’s no longer
using their old Installshield setup meaning the current command line switches will not work anymore.

What I’m not too fond of is that both nVidia and Ati (now AMD) provide no real explanation for proper command line switches to deploy these drivers.
My friend at nVidia sent me the internal document containing the entire command line switches and some other stuff.

Here are some of the general parameters for installing these drivers;

“[installerpath]\setup.exe /n /s /i /k /passive /noeula /nofinish”

Note: The above command will not work, it’s just a list of some of the available commands.

A short explanation of the parameters:

  • /n – This is the ignore reboot switch (will not reboot your pc after the driver has been installed).
  • /k – This is the force reboot switch (whether a reboot is required or not, your pc will be rebooted).
  • /i – Do not show welcome/reboot, but show package selection UI if needed and progress.
  • /s – Silent install, will not show any UI.
  • /passive – Passive install, this will not ask for any user input, but will show you a progress window.
  • /noeula – Allows you to skip the accept/decline EULA page.
  • /nofinish – Skip the summary page.

Well that’s it for now, I figured this was a nice post to start with, if you find this information useful feel free to check out my blog once in a while.

Kind regards,

Stephan-

Be the first to comment
Share this by email. Share on Facebook! Tweet this! RSS 2.0 TOP