Can you figure this out? (Other user)

Don't enable SkipMachineOOBE & SkipUserOOBE.

There are no user accounts created (or having the Administrator enabled) by the Unattended file, so you can't skip OOBE. Both settings are deprecated, and shouldn't be used for W10/11 installs.
 
garlin said:
Don't enable SkipMachineOOBE & SkipUserOOBE.

There are no user accounts created (or having the Administrator enabled) by the Unattended file, so you can't skip OOBE. Both settings are deprecated, and shouldn't be used for W10/11 installs.
Click to expand...
maybe these options should then be removed (or atleast prompt the user a warning when he modifies a win10/11 .iso) this had me in confusion also quite alot of time ngl.
 
No problem with SkipMachineOOBE
Unattended creates the specified user correctly

I have no "requests" whatsoever during the installation
 
CodeBro, tistou77

Sorry to dug this Thread out but i recently stumbled upon a "mysterious" Phenomenon. I am constantly improving my Image with NTLite and also automize my Installation Process via Unattended.


"SkipMachineOOBE" causes , with no specified Local User Account in Unattended, to install Windows properly but you will be greeted with the Sign-In Screen and NO Local User Account to actual login to.

I can't remember if i set this Option to be active during many Trials but was confused why the Setup Process didn't asked for any Input to create a Local Account. Loaded my NTLite .xml Config File 5 Minutes ago and wondered why this would happen, till i realised that right above the Switch for "SkipMachineOOBE", when activated, some Settings were greyed out that are coherent to automize Things like Skip EULA, Setup a Microsoft Online Account etc. Switched "SkipMachineOOBE" to off/Standard and i was able to regain "Control" of said Options. Want to let you know just in Case someone has the same Problem.
 
Last edited:
I specify the local account, etc., in the unattended, so there are no issues with that option.
But thanks for the heads-up regarding the others.
 
Thanks for the reply.

It isn't an issue per se, but if someone want to create an Image with the Ability to choose the Name of the Local Account during the Installation Process and didn't take Notice of this subtle "Change" then it would be a little bit confusing.

Right now i am testing with only SkipUserOOBE set and see how the Setup Process behaves.
Edit: Changed nothing really.

Would you mind sharing your Local Account Setup in the Uanttended File? Like, do you define an "Admin" Account and a Standard User Account or do you only specify a Local Account with Adminstrator Priviliges? I must admit it is very nice, with set SkipMachineOOBE, SkipUserOOBE and defined Local Account, to not really have to interact with the Setup Process other than choosing the Partition Layout maybe.
 
Last edited:
In the .xml file
Code: 
<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">
        <OOBE>
            <HideEULAPage>true</HideEULAPage>
            <HideLocalAccountScreen>true</HideLocalAccountScreen>
            <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
            <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            <NetworkLocation>Home</NetworkLocation>
            <ProtectYourPC>3</ProtectYourPC>
            <SkipMachineOOBE>true</SkipMachineOOBE>
        </OOBE>
        <UserAccounts>
            <LocalAccounts>
                <LocalAccount wcm:action="add">
                    <Group>Administrators</Group>
                    <Name>tistou</Name>
                    <Password>
                        <PlainText>true</PlainText>
                        <Value></Value>
                        </Password>
                </LocalAccount>
            </LocalAccounts>
        </UserAccounts>
    </component>
</settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Security-SPP-UX" 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">
            <SkipAutoActivation>true</SkipAutoActivation>
        </component>
        <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">
            <ComputerName>tistou-PC</ComputerName>
        </component>
    </settings>
 
You must log in or register to reply here.
Back
Top