asked on

domain user folder naming

When a domain user logs on to the network on a client PC, Windows creates a profile for the domain user on the local system. IN my limited experience the name of the folder structure that is created is normally Documents and Settings\username.domainname.

I was doing some testing on one of my desktop systems to find the most effective way to copy local user profiles to domain user profiles and in the process copied a local profile to username.domainname - like Smith.Mydomain. When the user Smith logged in on the PC (for the first time) that already had a Documents and Settings\Smith.Mydomain, Windows created a Documents and Settings\Smith.Mydomain.000 I figured this was OK - BUT, every subsequent domain user that logs onto this PC gets a profile created with the folder name = Documents and Settings\username - Windows is leaving off the domainname suffix !

Now I like being able to look in Documents and Settings to see who the local and the domain users are. How do I fix this so that Windows starts adding the .domainname suffix again?

ASKER CERTIFIED SOLUTION

oBdA

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Fatal_Exception

And just to followup on oBdA's comment, here is the proper way to copy a profile:

http://www.petri.co.il/copy_user_profiles_in_windows_xp.htm

This may help also:

How to Create and Copy Roaming User Profiles in Windows

http://support.microsoft.com/default.aspx?scid=kb;EN-US;142682

Be aware that you must be logged in as the administrator, and not the user you wish to copy the profile from for this to work....

FE

oBdA

Stupid me, forgot the "copy" part while explaining the user profile naming; Fatal_Exception is of course right when it comes to the actual copying.
For a mass profile change, you might want to have a look at moveuser.exe from the Resource Kit Tools:
Windows Server 2003 Resource Kit Tools
http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en

Fatal_Exception

*grin* But it was such a nice explanation of how these profiles are named.. well done..!!

oBdA

Actually, I just thought of a rather easy solution to find out which profile belongs to which user (assuming you're using standard NTFS permissions).
Open the security settings of the profile folder, and check who (apart from Administrators and System) has Full Control over the folder; there should only be one account.