Sysprepping a customized image on a VM

[Hellbovine]

I think we should be careful not to derail anymore, this is why I tried to keep it simple, because 99.99% of all computer users just don't need to know or worry about stuff like this. Not trying to argue, rather steer us back on course to be productive. This thread is already all over the place enough as is.

 

[Kasual]

Read yourself:

I think we should be careful not to derail anymore, this is why I tried to keep it simple, because 99.99% of all computer users just don't need to know or worry about stuff like this. Not trying to argue, rather steer us back on course to be productive. This thread is already all over the place enough as is.

Seems like you like to "derail" threads:

Fair enough, I was going to mention the defaultuser0 thing, but thought it best not to complicate things though

 

[Hellbovine]

I actually immediately deleted that post. I asked Garlin to restore it, because he replied faster than I could delete it, and for posterity it needed to be there since he quoted me.

 

[Kasual]

Back on thread.

Understood thank you, but what about the 'Who's going to be using this device: user or organization?'? What triggers that? I only see that in the VM, not on a physical machine

You have the answer

Okay this is crazy but I am posting this comment to give an update:

1 problem that I remain to have is: I set both the 'HideLocalAccountScreen' and the 'HideOnlineAccountScreen' settings to 'false', as well as the 'SkipMachineOOBE' and 'SkipUserOOBE' settings. So all these 4 were set to 'False. However, I am only prompted to create a local account, not an online account. Even tho I set them 'both' to false. Why is this?

Change those settings to false, is the same as leave it by default.

Start with a clean and updated source, use an autounattended.xml containing entries to Audit or none at all as the image is going to be captured, you will save a lot of time, moreover if you pay carefully attention to replies and proceed as guide is shared by someone trying to help.

 

[SM03]

Here:

And here:

And here too:


Also, you can do a search for defaultuser0 here in the forums.
Doing some google search, Windows 11 have this "bug".

Just FYI
I don't see that anymore in W11, left W10 on Nov 21 so can't say anything about that
Not that I really care or check that much, just checked now after you mentioned (quoted) my old comment (from 2020) here once again
& here's the screenshot from one of my system(s) running on the latest 22622.590 W11 Pro, no defaultuser0 folder here

 

[garlin]

There was a known bug with leftover defaultuser0 in early W10 builds (pre-19H?), which was fixed in later releases. While it's useful to note, most users don't see the original problem today.

 

[bseklecki_ge]

There was a known bug with leftover defaultuser0 in early W10 builds (pre-19H?), which was fixed in later releases. While it's useful to note, most users don't see the original problem today.

Sorry to pick up on an old thread:

Is it possible the if the last command run in [sources\$OEM$\$$\Setup\Scripts ] SetupComplete.cmd doesn't return errorlevel/RC=0 that defaultuser0 will remain?

The NTLite default seems to include a cleanup call to rd.exe, but possibly some background install jobs are still running and that rd.exe returns non-zero?

 

[garlin]

No, it's unrelated. The defaultuser0 problem was already reported in sysprep failures (you can search answers.microsoft.com for examples).

defaultuser0 is a temp account created to allow OOBE to run, and it's to be removed on exit. By the time SetupComplete is executed, there shouldn't any defaultuser0 on the system.

 

[bseklecki_ge]

defaultuser0 is a temp account created to allow OOBE to run, and it's to be removed on exit. By the time SetupComplete is executed, there shouldn't any defaultuser0 on the system.

Thanks; so if DefaultUser0 is chronically remaining, where to look for clues? Panther logs in %systemdir%\Panther\ ?

My current working theory is that one of the 200 changes I'm making in my SetupComplete script (which calls a PowerShell script) is breaking something.

As far as actual troubleshooting, "ComputerName: failed to get the current computername" is the only error I'm seeing in PANTHER.

 

[garlin]

I dunno. Because the problem's very inconsistent, I don't think there's a clear way to troubleshoot the root cause.

Here's one thread:
https://www.reddit.com/r/SCCM/comments/sjton0/windows_11_osd_defaultuser0_persisting_postsysprep/

 

[Kasual]

Thanks; so if DefaultUser0 is chronically remaining, where to look for clues? Panther logs in %systemdir%\Panther\ ?

DefaultUser0 is created due to a bug
By design, the accounts that runs are SYSTEM at an early stage and Administrator at the last stage, once the setup ends, the Administrator account is disabled and the .\User\Administrator is removed (the Administrator folder exist, if you explore the mounted image, you will see it)

 

[bseklecki_ge]

My DefaultUser0 bug is fixed; it was one of the (200) steps I was doing in my SetupComplete.cmd (which is calling PowerShell to make 200 changes) (Not sure which yet, but probably UAC ( since D**K UAC ETERNALLY) >:} )

1) Adjusting the UAC Levels
2) Joining a workgroup (add-computer)
3) Setting the passwordDoesntExpire flag (set-localuser) on the OOBE admin created users (which I also now know is proably invalid to do in SetupComplete.cmd, because those users aren't created until after SetupComplete.cmd finishes when most of OOBE funcion runs)

 

[Kasual]

My DefaultUser0 bug is fixed; it was one of the (200) steps I was doing in my SetupComplete.cmd (which is calling PowerShell to make 200 changes) (Not sure which yet, but probably UAC ( since D**K UAC ETERNALLY) >:} )

1) Adjusting the UAC Levels
2) Setting the passwordDoesntExpire flag on the OOBE admin created users (which I also now know is proably invalid to do in SetupComplete.cmd, because those users aren't created until after SetupComplete.cmd finishes when most of OOBE funcion runs)

For the 1, you can use power run
For the 2 you can create a user in the specialize stage but it's not going to be in any group, you have to add it to a group in setup complete, when you create an user once Windows loaded the desktop, it is created as a standard user (in the Users group).
If you are installing Windows in a branded computer, oobe is skipped and setupcomplete would run at a different stage.