Deployment Solution

 View Only
  • 1.  unattend.xml for custom-named administrator account

    Posted Dec 11, 2014 11:00 AM

    I'm trying to make a Windows 7 image with DS 7.5 where, upon bootup, the local administrator account is *not* disabled.

    One catch: for reasons of simplicity and speeding up support, I have a GPO that renames the local administrator account to "ali". After capturing an image, then deploying the image to a PC, I try logging with ali and the password, and I get incorrect login or password. I try logging in with "administrator" and the password, and I'm told the account is disabled--sysprep obviously renamed the account back to "administrator".

    The article found at http://www.symantec.com/business/support/index?page=content&id=TECH185748&actp=search&viewlocale=en_US&searchid=1418313251565 lists, as a solution, to use their supplied unattend.xml, which has the following code. This didn't work; should I change "administrator" to "ali" here?

    <component name="Microsoft-Windows-Deployment" processorArchitecture="@ProcessArchitecture" 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>cmd /c net user administrator /active:yes</Path>
                        <Description>Enable Admin</Description>
                    </RunSynchronousCommand>
                </RunSynchronous>
            </component>

    Thanks!



  • 2.  RE: unattend.xml for custom-named administrator account

    Posted Dec 11, 2014 11:54 AM
    I've found it easiest to just create another local account and make it admin in the unattend.xml


  • 3.  RE: unattend.xml for custom-named administrator account
    Best Answer

    Trusted Advisor
    Posted Jan 28, 2015 04:54 AM

     

    To clarifywhat Andy has said here, typically this is done directly in the XML using Microsoft elements. 

    We do this in the oobesystem pass, using the UserAccounts element as follows,

       <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" 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">
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            
                            <Name>myLocalAdmin</Name>
                            <Password>
                                <Value>mypassword</Value>
                                <PlainText>true</PlainText>
                            </Password>
                            <Group>Administrators</Group>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
            </component>
        </settings>