Jump to content

Autounattend.xml not working - where is my fault ?


caphp
 Share

Recommended Posts

I just start testing the "Unattended Creator" in the W7Toolkit and add the following little things...

Accept EULA

Computer Name: Intel

Full Name: Intel

Serial

I saved the file to the folder, where I extracted the W7 iso and used the "ISO Maker" to generate a new iso.

Then I create a new vm using the iso, but after installing W7, the computername was not "Intel".

Then I used the "WIM Manager", select the operating system and "Apply unattended", choosing the "Full" method - building another iso.

But after creating another W7, the computername was not "Intel".

So...where is my fault ? Can someone help my ?

P.S.: the ProductKey is replaced by XXXXX-XXXXX-XXXXX-XXXXX-XXXXX ;)

post-26823-0-05835900-1327770009_thumb.j

Autounattend.xml

post-26823-0-90743100-1327770407_thumb.j

Link to comment
Share on other sites

Try to use another "computer name" and "full name", because Intel is a trademark and maybe it's the reason:

http://www.intel.com...egal/third2.htm

Thanks to let us know the result after these changes.

However we can see the Computer Name used with Autounattend.xml file inside:

C:\Windows\Panther\UnattendGC\setupact.log

Example mine (read the first lines): ComputerName set to Se7en


[windeploy.exe] ------------------------------------------------
[windeploy.exe] WinDeploy.exe launched with command-line []...
[windeploy.exe] Setup has not completed, adding pending reboot.
[windeploy.exe] Found generalization state [0x4], setup.exe completion flag [False] --> launching setup.exe.
[windeploy.exe] Launching [C:\Windows\system32\oobe\setup.exe]...
[Shell Unattend] Running 'specialize' pass
[Shell Unattend] ComputerName set to Se7en
2012-01-04 19:59:38, Info ...

Cheers

Edited by myselfidem
Link to comment
Share on other sites

Strange... here are a few lines from the C:\Windows\Panther\setupact.log


2012-01-28 22:20:11, Info IBS ==== Computername wird initialisiert ====
2012-01-28 22:20:11, Info IBS Generating a random computer name
2012-01-28 22:20:11, Info IBS No computer name specified, generating a random name.
2012-01-28 22:20:11, Info IBS Renaming computer to MININT-PJP2K0M.
2012-01-28 22:20:11, Info IBS Acquired profiling mutex
2012-01-28 22:20:11, Info IBS Service winmgmt disable: 0x00000000
2012-01-28 22:20:11, Info IBS Service winmgmt stop: 0x00000000
2012-01-28 22:20:11, Info IBS Service winmgmt enable: 0x00000000
2012-01-28 22:20:11, Info IBS Released profiling mutex
2012-01-28 22:20:11, Info IBS STATUS: SUCCESS (0x00000000)

and


2012-01-28 22:20:17, Info [0x064047] IBSLIB MarkUnattendSettingAsProcessed: Marking unattend setting [ProductKey\ProductKey] as processed.
2012-01-28 22:20:17, Info [0x060114] IBS Callback_Productkey_Validate_Unattend:User specified an unattend xml file.
2012-01-28 22:20:17, Info [0x060115] IBS Callback_Productkey_Validate_Unattend:Using ProductKey WillShowUI value of [OnError]. Setting will not be used as product key UI page can no longer be displayed. Retrieving key from unattend file...
2012-01-28 22:20:17, Info IBS Callback_Productkey_Validate_Unattend:No product key found, continuing validation and image selection in keyless setup mode.
2012-01-28 22:20:17, Info [0x060122] IBS Callback_Productkey_Validate: Entry
2012-01-28 22:20:17, Info [0x06012c] IBS Callback_Productkey_Validate: No product key provided on the blackboard. Running keyless setup.
2012-01-28 22:20:17, Info IBS Callback_Productkey_Validate: Using EulaType (a.k.a. ChannelType) for keyless setup. Eula type is [NoKeyChannel].

The file C:\Windows\Panther\UnattendGC\setupact.log say's


2012-01-28 22:26:37, Info [msoobe.exe] Successfully installed product key

...but there is no computername as I specified and my produktkey is not inserted

:g:

Edited by caphp
Link to comment
Share on other sites

Strange... here are a few lines from the C:\Windows\Panther\setupact.log


2012-01-28 22:20:11, Info IBS ==== Computername wird initialisiert ====
2012-01-28 22:20:11, Info IBS Generating a random computer name
2012-01-28 22:20:11, Info IBS No computer name specified, generating a random name.
2012-01-28 22:20:11, Info IBS Renaming computer to MININT-PJP2K0M.
2012-01-28 22:20:11, Info IBS Acquired profiling mutex
2012-01-28 22:20:11, Info IBS Service winmgmt disable: 0x00000000
2012-01-28 22:20:11, Info IBS Service winmgmt stop: 0x00000000
2012-01-28 22:20:11, Info IBS Service winmgmt enable: 0x00000000
2012-01-28 22:20:11, Info IBS Released profiling mutex
2012-01-28 22:20:11, Info IBS STATUS: SUCCESS (0x00000000)

Yes I have also the same result but with another random name. It's not an error!

It seems that the key isn't accepted and Windows use the default key to finish the silent installation.

Or there is a problem with "Apply Unattended" process!

Edited by myselfidem
Link to comment
Share on other sites

@caphp

I made a complete test successfully using your settings for Autounattend.xml but using this one at the root of the distribution folder.

Computer Name Intel and productkey installed with succes!

You can see the images here: (Intel TEST and Intel TEST-2)

https://skydrive.live.com/?cid=D178EA021B182B88&id=D178EA021B182B88%211408&sc=documents#cid=D178EA021B182B88&id=D178EA021B182B88%211442&sc=documents

Link to comment
Share on other sites

My main harddrive is a ssd and I made the vm installation on it.

The iso is placed on a normal sata hdd, but ...

I tried on a normal Dell Vostro under VM with no SSD, only normal HDD, but the result is still the same.

No productkey inserted and a random computername.

Edited by caphp
Link to comment
Share on other sites

@caphp

I made a complete test successfully using your settings for Autounattend.xml but using this one at the root of the distribution folder.

Computer Name Intel and productkey installed with succes!

So Legolash2o and myselfidem, does this imply there is a bug that the Autounattend.xml is not being placed in the correct place, or was it user error and how can it be prevented?

Cheers and Regards

Link to comment
Share on other sites

I found the following solution ( do not use the "Easy Install" from VMware Player ):

- "Create a New Virtual Machine"

- do NOT use "Installer disc image file (iso):"

- instead use "I will install the operating system later"

- choose the Windows Version

- choose a name for the vm ... and so on

- after creating choose "Edit virtual machine settings", click CD/DVD and choose "Use ISO image file:"

With this procedure the VMware Player will use the Autounattend.xml file.

CU

Edited by caphp
Link to comment
Share on other sites

  • 8 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...