how can I enable & set the admin account as default without settin

[avi952]

^

title

thanks for anyone who'll help

[MrJinje]

Run this from your unattend.xml specialize pass.

        <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">
                    <Description>Enable Admin Account</Description>
                    <Order>1</Order>
                    <Path>net user administrator /active:yes</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>

Run this from your oobesystem pass

            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                    <Password>
                        <Value>EDIT</Value>
                        <PlainText>true</PlainText>
                    </Password>
                        <Description>Default Administrator Account</Description>
                        <DisplayName>Administrator</DisplayName>
                        <Group>Administrators</Group>
                        <Name>Administrator</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>

If you need more details, check out the "Ask your seven XML here" sticky in the Windows 7 unattended forum

Edited September 16, 2012 by MrJinje

[avi952]

^

will this skip the OOBE as well? if not, how can i? I mean I don't plan on setting any users but the admin (I'm aware of its restrictions, such as no apps etc.)

[MrJinje]

^

will this skip the OOBE as well? if not, how can i? I mean I don't plan on setting any users but the admin (I'm aware of its restrictions, such as no apps etc.)

Just get the sample xml in post #432. That is what I am using, it has both x86 and x64 blank unattended.xml files that automate everything except for choosing your partition and OS version.

[Octopuss]

That command in specialize pass is not needed at all.

[avi952]

Run this from your unattend.xml specialize pass.

        <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">
                    <Description>Enable Admin Account</Description>
                    <Order>1</Order>
                    <Path>net user administrator /active:yes</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>

Run this from your oobesystem pass

            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                    <Password>
                        <Value>EDIT</Value>
                        <PlainText>true</PlainText>
                    </Password>
                        <Description>Default Administrator Account</Description>
                        <DisplayName>Administrator</DisplayName>
                        <Group>Administrators</Group>
                        <Name>Administrator</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>

If you need more details, check out the "Ask your seven XML here" sticky in the Windows 7 unattended forum

Thanks, I tried it as autounattend.xml and it worked perfectly , now help with one more thing, not related to the title but to the forum - how can i deploy/slipstream a reg file?

[MrJinje]

Use setupcomplete.cmd and put the reg file in the same folder. It runs under local system privilege right before the first logon occurs, so changes you make using regedit will apply before a user profile is created.

regedit /s %~dp0Set-ExecutionPolicy.reg

Also there is a setting to disable first logon animation, gets you to the desktop a minute faster.

    <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">
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v EnableFirstLogonAnimation /d 0 /t REG_DWORD /f</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">
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v EnableFirstLogonAnimation /d 0 /t REG_DWORD /f</Path>
                </RunSynchronousCommand>                                 
            </RunSynchronous>
        </component>
    </settings>

[avi952]

^

could you please give some more info about setupcomplete.cmd and where does it appear? (sorry about my ignorance until now i relied too much on unattended programs)

[MrJinje]

Not a problem.

Goes in your $OEM$ folder on your DVD or USB.

Sources\$OEM$\$$\Setup\Scripts\setupcomplete.cmd

Edited September 18, 2012 by MrJinje

[avi952]

i know but the problem is that i don't have a $OEM$ folder at all, how do i create it? regularily or by windows setup like in XP?

[myselfidem]

Create yourself manually inside your distribution folder | inside: .\sources

.\sources\$OEM$\$$\Setup\scripts\SetupComplete.cmd

You must create all these files yourself:

$OEM$

$$

Setup

scripts

SetupComplete.cmd

Edited September 18, 2012 by myselfidem