disable local user after OSD

Question

Hi experts,

We are using a OSD task sequence to image our Windows 10 devices. It works well, but after OS completion, users are prompted to create a local user and can't skip this step. But due to our company policy, we have to delete the local user account after creating, it's boring. Is there any way to get past this step?

Answer 1

Method 1: Modify the unattend.xml file

1. Locate the unattend.xml file used in your OSD task sequence. This file is typically stored within the Operating System deployment files or on the MDT server.
2. Open the unattend.xml file using Windows System Image Manager (SIM) or a text editor.
3. In the unattend.xml file, add the following settings in the appropriate configuration pass (usually the oobeSystem pass):

<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">
    <OOBE>
      <HideLocalAccountScreen>true</HideLocalAccountScreen>
      <ProtectYourPC>3</ProtectYourPC>
      <SkipUserOOBE>true</SkipUserOOBE>
      <SkipMachineOOBE>true</SkipMachineOOBE>
    </OOBE>
  </component>
</settings>

1. Save the modified unattend.xml file.
2. Update the deployment share or distribution points to include the updated unattend.xml file.

Method 2: Use a provisioning package

1. Install the Windows Configuration Designer from the Microsoft Store if you haven't already.
2. Open the Windows Configuration Designer and create a new provisioning package.
3. In the package settings, navigate to Runtime settings > OOBE.
4. Set the following options:
   • HideLocalAccountScreen: Set to True.
   • ProtectYourPC: Set to 3 (Do not show Express Settings and prevent the collection of usage data).
5. Save the provisioning package and include it in your OSD task sequence.