Win7 Unattend.xml Not Being Applied

[sukh]

Hi

 

Can you post the WDS Client unattend.xml?

 

Regards

Sukh

[djameson]

WDSUnattend.xml

 

OnError

1

Primary

true

true

NTFS

WinXP

C

1

1

0

true

acsd4.local

wds

###

OnError

Image Name as displayed in WDS

Image Group

WIM Image Filename

0

1

 

Thanks.

[sukh]

Hi

 

Can you let me know how the results of the $OEM$ test ?

 

If this failed, can you also do the following.

 

1. From WSIM save the answer file as Autounattend.xml

 

2. Copy the Autounattend.xml file to a USB flash drive, then try to install Windows 7 from DVD on an reference computer. Or copy the Autounattend.xml to the root od the DVD which has the Windows 7 source files.

 

 

 

Note: Windows 7 Setup (Setup.exe) will begin automatically. By default, Windows Setup will search the root directory of all removable media for an answer file called Autounattend.xml.

 

Regards

Sukh

[tarquel]

just to add another option to point 2, with a particularly nippy USB pen, put the install on the pen, along with the answer file, and boot and install it from that

 

To do that easily, use this: Microsoft Store: Windows 7 USB/DVD Download Tool Help

 

Direct link to the download: http://images2.store.microsoft.com/prod/clustera/framework/w7udt/1.0/en-us/Windows7-USB-DVD-tool.exe

 

Instruction on how to do it (tho its very very simplez) are on the page of the first link

 

Cheers

[djameson]

I continue to appreciate all the help and suggestions but I am not trying to "install" Win7....I am working with a reference image.

 

I began with saving the unattend file with the name "Autounattend.xml". The name appeared to make no difference as some resources referred to it as the autounattend, others as imageunattend, and still others as just unattend. Regardless of the name I use, WDS moves the unattend file to a location of it's choosing and renames it when it is assigned to the image through the image properties.

 

I will give the older WinXP $OEM$ format a go and see what that does.

 

So far my testing shows parts of both unattends are being applied while parts of both are not. The WDSunattend is naming the drive but not adding the computer to the domain or prompting for our naming convention for the computer name. The imageunattend is handling the EULA correctly and the time zone correctly, but not the Network type (Home, Work), not adding the CD Key, or the administrator password. If I remove the imageunattend, the WDSunattend works as expected....and the computer reboots with all prompts (time, EULA, etc.)

 

I feel as though there is some WDS setting or setting on the reference computer itself that is set up incorrectly or not at all. Since the unattend is being copied from the WDS server to the computer during imaging, I feel something is failing to "tell" the imaging process to apply the unattend file completely.......or there is confusion between the two unattends.

 

Again, thanks for all the time, help, and suggestions. It is GREATLY appreciated.

[sukh]

Hi

 

The suggestion to use the Autounattend.xml was to validate your answer file.

 

If we can get the computer joined to the domain then I guess we can elminate Network Type as Work as all computers joined to the domain will show as Domain.

[sukh]

Hi

 

Under the Windows PE Phase there are 2 keys.

 

1. Microsoft-Windows-Setup\UserData\ProductKey\Key

Specifies the Windows image to install during Windows Setup. If this setting is used by itself, Windows Welcome will prompt for a product key.

 

2. Microsoft-Windows-Shell-Setup\ProductKey

Specifies a Product Key to activate Windows. If this setting is used, Windows Welcome will not prompt for a product key. This setting can be used with Microsoft-Windows-Setup\UserData\ProductKey\Key, and the two product keys can be different.

 

If you are using a Volume License Multiple Activation Key (MAK), it must be specified using this setting.

 

Can you try this?

 

Regards

Sukh

[djameson]

Sukh...I appreciate all the help but I am going to have to move to another project for a few days and come back to this a little later.

 

Again, I appreciate all your time. I'll post back if I get it working or when I get to come back to this.

 

Thanks again.

[sukh]

Hi

 

Please do, this one has been a pain and would like to know.

 

Dont give up on this one :-)

 

Regards

Sukh

[djameson]

Sukh...

 

Had a little time yesterday to play around again. I talked with a neighboring tech guy and he gave me one of his imageunattend.xml that he uses. I compared and the only difference I saw was the location of the components. The components were the same but most of mine were in WindowsPE and OOBE....most of his were in Specialize and OOBE. I edited his xml and low and behold....it ran fine. The only thing that did not work was the prompt on network location. All others populated fine.

 

So....I guess the location of components is important!!

 

Again, thanks for all your help.

[sukh]

Hi

 

Thanks for the reply. I didn't have a chance to look into it more but I the passes are important. Specialise will come after PE. I will have a look at the unattend.xml so I can put my mind at rest.

 

The oobeSystem pass is the only section where the NetworkLocation will be applied. If your PC is joining the domain then this will be "Domain" anyway. Alternatively, you can set a GPO for this.

 

Let me know if this is an issue andif you want to continue troubleshooting this particular pass.

 

Thanks

Sukh

[tarquel]

The only thing that did not work was the prompt on network location. All others populated fine.

 

You might find its because of this:

 

A "Set Network Location" dialog box appears when you first log on to a domain-joined Windows 7-based client computer

 

so you'll need to slipstream this into the WIM of wni7

 

Note that in Win7 SP1, it is already included

 

Cheers

Nath