Jump to content
myselfidem

Create your own Autounattend.xml All-In-One (x86/amd64)

Recommended Posts

About User accounts:

Group

Group

specifies the name of an existing local security group to which a new LocalAccount will be added during installation. You can add a user to multiple groups by entering multiple group names separated by semicolons.

The Microsoft-Windows-Shell-Setup component recognizes the following English group names and sets the appropriate localized group name, regardless of the default language of the Windows® image:

  • AccountOperators
  • Administrators
  • BackupOperators
  • CryptoOperators
  • DCOMUsers
  • Guests
  • IUsers
  • NetworkConfigurationOperators
  • PerfLoggingUsers
  • PerfMonitoringUsers
  • PowerUsers
  • PrintOperators
  • RemoteDesktopUsers
  • Replicator
  • SystemOperators
  • Users

Specify the account names and group names by using language-neutral names. The language-neutral account and group names are specified in English—for example:

Administrators, Power Users, and Guest.

This is required because the shell account settings are processed before a default user interface (UI) language is applied to the computer.

Enable and Disable the Built-in Administrator Account:

http://technet.microsoft.com/en-us/library/dd744293(WS.10).aspx

Using the net user command

You can run this command after configuring the computer.

Use the account names in the local version (example):

Start | Run write: cmd and use:

net user Administrateur /active:yes (French)

You will see the Administrator account inside Control Panel | User accounts

http://support.microsoft.com/kb/251394/en-us

post-23163-0-70773700-1322152500_thumb.g

post-23163-0-78491000-1322152509_thumb.g

Edited by myselfidem

Share this post


Link to post
Share on other sites

myselfidem, I think ur autounattend.xml will not work if we add some extra command in setting specialize also OOBE, an example I make 2 firstlogon command (one for x86, 2nd for x64), becuz since x64 have x86 feature too in the image, it will check x86 setting too even we choose x64 image, that will mess up installation command if we make that separately depend on the system architecture itself (mostly worse in specialize setting, if we choose x86 as first, it will use x86 n ignore x64), all u need to change is move amd64 first as first setting than x86 as 2nd setting in autounattend.xml.

u could test that by urself, thx!

note: I think for windows pe setting, u dont need to make double, just use x86 since it based on ur boot.wim, right? (Please correct me if I'm wrong)

Edited by ar_seven_am

Share this post


Link to post
Share on other sites

it's not bout the firstlogon command, it's about numeration, an example if I use this :


<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\Daemon\SPTDinst-x64.exe add /q</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\Daemon\SPTDinst-x86.exe add /q</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>

will work to install sptd drivers for x64 in x64 OS, but if I use this :


<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\Daemon\SPTDinst-x86.exe add /q</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\Daemon\SPTDinst-x64.exe add /q</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>

it will choose x86 setting even what we choose to install is x64 in the first of windows 7 installation (only in windows 7, in windows vista doesn't have effect, it will work).

notice the different mate? only change amd64 first, n the 2nd is x86 setting.

Share this post


Link to post
Share on other sites

The valid pass for SynchronousCommand is:<settings pass="oobeSystem">

Example:

<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>c:\synccommands\command1.exe</CommandLine>
<Description>Description_of_command1</Description>
<Order>1</Order>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>c:\synccommands\command2.exe</CommandLine>
<Description>Description_of_command2</Description>
<Order>2</Order>
</SynchronousCommand>
</FirstLogonCommands>

SynchronousCommand specifies a single command to run the first time a user logs on to the computer.

FirstLogonCommands are run after logon but before the user sees the desktop.

If you create a user account that does not include administrative privileges, the following commands may not be executed:

  • If User Account Control is enabled, then when that user logs in for the first time, a dialog box appears, prompting the user with an option to allow an administrator to apply the commands. If the user selects Cancel, these commands are not executed.

  • If User Account Control is disabled, these commands are not executed.

RunSynchronousCommand specifies a single command to run during the windowsPE Configuration Pass.

To start a command that needs to finish before other commands can start, use synchronous commands. To run services or commands that can start at the same time, use RunAsynchronousCommand instead.

All RunSynchronous commands run in the system context.

Edited by myselfidem

Share this post


Link to post
Share on other sites

have u check in WSIM? how can that feature enable if we cant use the advantage? u can use that in audit, specialize also OOBE, it doesn't related to be more specific as long u put in correct place.

just try to add RunSynchronousCommand in ur multi autounattend, u'll find that case.

Share this post


Link to post
Share on other sites

First, we must keep in mind that Autounattend.xml AIO isn't documented by Microsoft!

Twice, we can try to found a workaround about some trouble, like RunSynchronusCommand and FirstLogonCommand!

A workaround to install SPTDinst-v179-x86.exe or SPTDinst-v179-x64.exe is to create separate folders, like this (example):

Programs are located inside the distribution folder:

DVD\sources\$OEM$\$1\Install\Apps\86\SPTDinst-v179-x86.exe

and

DVD\sources\$OEM$\$1\Install\Apps\64\SPTDinst-v179-x64.exe

There is two options for RunSynchronus inside Autounattend.xml file!


<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\86\SPTDinst-v179-x86.exe add /q</Path>
<Description>SPTDinst 32-bit</Description>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\64\SPTDinst-v179-x64.exe add /q</Path>
<Description>SPTDinst 64-bit</Description>
</RunSynchronousCommand>
</RunSynchronous>
</component>

If needed, we can use ONLY ONE PASSS for x86 or amd64 for FirstLogonCommand or RunSynchronusCommand!

We must adapt the Autounattend.xml AIO file to suit our needs!

*Edit: Please try to write good english, because english it's not my mother tongue. Thanks

Edited by myselfidem

Share this post


Link to post
Share on other sites

why it need to be complicated? why not just move x64 unattend setting as first n x86 as the 2nd, do u get what I mean? also sptdinstal is only virtual driver for daemon, I only made that as example :D, no need to be serious.

The main reason I put that in specialize setting so in OOBE setting, in firstlogon.cmd u can run daemon installer silently n the virtual driver already there (not needed actually if u use audit setting in autounattend).

I dont trust the documentary 100%, almost all of my problem solved in forum.

for virtual machine, I use vmware, but if u want to run x64 aplication, ur processor must have x64 criteria otherwise u cant run that.

note: I use translator too, so I'm sorry if u dont understand, I try my best to explain.

Share this post


Link to post
Share on other sites

why it need to be complicated? why not just move x64 unattend setting as first n x86 as the 2nd, do u get what I mean? also sptdinstal is only virtual driver for daemon, I only made that as example :D, no need to be serious.

It's not complicated, just answered your question and try to find a workaround!

The main reason I put that in specialize setting so in OOBE setting, in firstlogon.cmd u can run daemon installer silently n the virtual driver already there (not needed actually if u use audit setting in autounattend).

I dont trust the documentary 100%, almost all of my problem solved in forum.

If it's solved for you. Nice!

for virtual machine, I use vmware, but if u want to run x64 aplication, ur processor must have x64 criteria otherwise u cant run that.

Of course, I know that also!

Image OS 64-bit:

https://skydrive.live.com/?cid=d178ea021b182b88&sc=documents&lc=1036&id=D178EA021B182B88%21114#!/?cid=d178ea021b182b88&sc=documents&uc=1&id=D178EA021B182B88%211345!cid=D178EA021B182B88&id=D178EA021B182B88%211394&sc=documents

note: I use translator too, so I'm sorry if u dont understand, I try my best to explain.

u=you It's too difficult to write = you??

ur=your it's too difficult to write correctly?

n=and ?

Stop it, please!

Edited by myselfidem

Share this post


Link to post
Share on other sites

I'm not having problem, I'm just give you suggestion, is it clear to YOU?

instead DISCUSSION or TEST of this multi autounattend setting, YOU complaining for my language?

oh well nevermind.

Edited by ar_seven_am

Share this post


Link to post
Share on other sites

I think your question is solved now!

You have updated your post after my answer!

Yes I'm complain about your writing message! And I found a workaround about your question!

And I've made many TESTS!

What do you want exactly?

Edited by myselfidem

Share this post


Link to post
Share on other sites

@myselfidem,

I believe the general question remains: Is it better or more reliable to order the x64 sub-section before the x86 sub-section in any area of the Autounattend.xml? If it solves a problem for anyone, and does not cause a problem for anyone else, wouldn't it be better to do it that way?

Cheers and Regards my friend

Edited by bphlpt

Share this post


Link to post
Share on other sites

@myselfidem,

I believe the general question remains: Is it better or more reliable to order the x64 sub-section before the x86 sub-section in any area of the Autounattend.xml? If it solves a problem for anyone, and does not cause a problem for anyone else, wouldn't it be better to do it that way?

Cheers and Regards my friend

this is what I'm tryin' to suggest bphlpt, thx for posting that.

Share this post


Link to post
Share on other sites

The best method about Autounattend.xml AIO (x86/amd64) , using options with "RunSynchronousCommand" and/or "FirstLogonCommand" is to use separate batch files!

*Edit: post updated

Edited by myselfidem

Share this post


Link to post
Share on other sites

Thanks hornet512 :rolleyes:

I've updated the batch file. Let me know if it's OK for you. Made many tests and all works fine for me.

Now, no errors will be made with Automatic method to insert keys!

And I will update the SetProductKey.rar folder!

*Edit:post updated

Edited by myselfidem

Share this post


Link to post
Share on other sites

Thank you Myselfidem

Your updated batch file is OK for me. There aren't any errors.

If I were you, I would cut one of the confirmation questions. But that is unessential.

Tha batch file works fine and the dos screens are well designed :prop:

Please let us know, when you update the setProductKey.rar folder.

Regards.

Share this post


Link to post
Share on other sites

myselfidem, thank you very much for the help in this thread. I've managed to make a complete unnatended setup for windows 7 by changing one of your .xml examples in this thread, that was perfect for my needs. I attached it.

However, I have some trouble. If I install from a dvd - everything is ok. If I install from an USB, the unnatended doesn't work. And it's not the software that helps make the usb bootable, I tried several with the same unwanted result.

So, please check in WAIK if there is an option for unattended that needs to be checked if the origin of the installation process is an USB stick. Thanks. :)

Edited by RicaNeaga

Share this post


Link to post
Share on other sites
Please let us know, when you update the setProductKey.rar folder.

And perhaps leave the link to the folder at the beginning of the first post in this thread for easy access?

Cheers and Regards

Share this post


Link to post
Share on other sites

:)

@hornet512

SetProductKey.rar updated (and I removed one confirmation question!).

@bphlpt

It's already done since the first post I've made!

You can downlaod SetProductKey.rar at first post in this thread.

Thanks to let me know if there is errors.

@RicaNeaga

Nice and thanks!

Edited by myselfidem

Share this post


Link to post
Share on other sites

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.


×
×
  • Create New...