Have a working answer file in which at the stage OOBESystem
creates a user with the specified name. This user belongs to two groups: Administrators
. Next, using a synchronous command the user will be excluded from the group of Users
, remaining only in the group Administrators
. In addition, the system already has a built-in account Administrator
, which is disabled. I thought, "why create another account with administrator rights, if you can use existing?".
Task: using the answer file AutoUnnatend.xml
enable integrated account of Administrator
and thus skip creating a new user.
I made changes to the stage OOBESystem configuration pass
of your answer file. Now it looks like this (excerpt):
<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">
At the end of installation appear window enter your user name and password. Upon completion of the system loaded into the built-in account <i>Administrator</i>, but the system is also present created in the last step account.<br>
How to make a sub account was not created, if possible?<br><br>
PS. A possible solution to the problem - immediately after the first login the Administrator with the command <b>net user</b> to remove just created a sub account. Not yet tested, but the solution is not "elegant".</plaintext></password></autologon></component></settings>