midiboy

Windows 7 Beta1 Unattended

3 posts in this topic

Hi guys,

I have not found any threads on Windows7 unattended problems so I am starting one myself. I have just tried to create an unattended Windows 7 beta1 installation DVD by copying the autounattend.xml over from my Vista installation dvd and it ran quite well.

The only thing I had to remove was the <ProductKey> value.

However, there is a problem with the Administrator user. In my autounattend.xml I have the following code:

<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">
<AutoLogon>
<Enabled>true</Enabled>
<LogonCount>4</LogonCount>
<Username>Administrator</Username>
<Password>
<Value>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</Value>
<PlainText>false</PlainText>
</Password>
</AutoLogon>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</Value>
<PlainText>false</PlainText>
</Password>
<Description>Administrator</Description>
<DisplayName>Administrator</DisplayName>
<Group>Administrators</Group>
<Name>Administrator</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
</component>

This works fine in Windows Vista. In Windows 7 however, the unattended setup will stop with a wrong user/password message. Thats because Windows 7 created an Administrator_ploc (strange name, hah ?) user instead of just activating the Administrator user and setting the proper password to that user.

Anyone else has this ? Happens all the time, even with plain passwords.

All the other stuff like setupcomplete.cmd, WPI etc. seem to work fine. (limited testing so far).

Have a happy new Year !

Alex

0

Share this post


Link to post
Share on other sites

Hi again,

just found out that it works fine if the Administrator created during setup is named Administrator2 instead of Administrator. Installation is still running but it seems to work fine now.

Any idea why this is happening ? bug or feature ? :whistle:

Bye,

Alex

0

Share this post


Link to post
Share on other sites

win7 have new system to unattained u could use dism.exe and set it as possible

[vlite already had problem setting it]

or wait for the newer waik for it

Edited by aviv00
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.