Admin profile name after sysprep

[Avaryan]

Server

• FOG Version: SVN Revision: 5837 (Yes, we need to update)
• OS: Ubuntu

Client

• Service Version: 0.11.2
• OS: Windows 7 & Windows 10

Description

This isn’t really a FOG issue, as I’ve seen it before with Ghost. Figured someone here would likely know the answer.

Sometimes, not always, after a PC is finished with sysprep I’ll check in the Users directory and the local Administrator profile will be Administrator.<Computer Name> or Administrator.<Computer Name before FOG renamed it>.

Observed happening on Windows 7 and Windows 10.

I’m thinking it has something to do with the Admin profile being logged in automatically while the FOG client is renaming the machine.

[Tom Elliott]

This is not because of FOG Client at all.

This is normally because the Administrator account used to “Sysprep” the system is no longer valid, but because the Administrator folder exists, the way to ensure the “now new” system is distinct, it appends the computername to the local accounts, and often will do similar methods for different domains if using an AD account to sign in.

[Avaryan]

Did not mean to insinuate that it was the fault of the FOG client, as I’ve seen it before even when not using FOG.

Do you know of a way to have it use the original Administrator user folder and not create a new one?

For reference:
When creating the image I’m hitting Ctrl + Shift + F3 to boot to Audit mode during the Windows install.

During the Specialize phase of sysprep with the Microsoft Windows Deployment component I’m creating a synchronous command to activate the admin account.
net user administrator /active:yes

During the OOBE phase I set the password as well as auto logon details.

This is really a minor issue, but there have been times where it would have been helpful to be able to deploy files straight to the admin desktop; which would be difficult if the directory name isn’t always the same.