• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 231
  • Last Modified:


After sysprep, on a Windows 7 64bit system, the administrator folder is sometimes created in the users folder as follows: c:\users\administrator.system10384 (system1 being the computer name given before sysprep).

The users folder would have both the administrator folder and the new administrator folder.  Previous answers to this state that this happens when the computer has been logged onto a domain.

1. How would I verify if this computer has been logged onto a domain?
2. Why is this happening?
3. How can I prevent it from happening?
4. If I can't prevent it from happening, how can I clean up the administrator profile?

Recreating the image is not an option at this time.  Thank you.
  • 2
1 Solution
Lionel MMSmall Business IT ConsultantCommented:
How many times have you run sysprep on this image?
1. You can look in the event logs and/or you can look at the C:\Users and see if there are any users named UserName.DomainName
2. Are you using an answer file for sysprep or are you manually entering the required info, like username, pc-name, admin password, ID codes
3. Depends on your answers to the other questions--but yes
4. Make a copy of C:\user\Administrator; then delete the folders in the original and see if it affects anything. If it were me I would create another Admin user--reboot-logon as that other Admin user; delete the C:\user\Administrator folder--reboot and logon as Administrator again and create a new profile.
atomconAuthor Commented:
I would not be able to log into the Administrator profile, because the profile data would be missing if I delete the contents in c:\users\Administrator.  It would log me into a temporary profile, but this is defeating the purpose.

If anyone else has this issue in the future, I would suggest the following:

cmd prompt
cd to c:\program files (x86)\Symantec\Symantec Endpoint Protection\
smc -stop

then sysprep

Symantec could be locking the directory during sysprep and Windows tries to recreate it.  SMC -stop would stop the SEP services, and disables it.  It will reenable by itself.

This is my theory only, but worth a try.
atomconAuthor Commented:
This is a good theory as to why the issue is happening.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now