I am 99% sure this is normal behavior if you are creating the profile with a policy. If it is created in the users AD account profile then it doesn't happen. Now with that being said I know you can stop this from happening with Home directories if you create the director first and give the user full control to the directory. If the user does not have full control then it will create a new directory with the domain name on the end. I am not sure if it would work with the profile but you can give it a shot. Chris ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Stratton, Doug ISMC:EX Sent: February 2, 2009 6:58 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Roaming profile with Domain extension For some reason we are getting the following problem with our new servers. W2k3 XA 4.5 We have Roaming profiles setup We are in a domain. But profiles are not loading. What I found out so far is that it is looking here for the roaming profile \\servername\sharename\username.domain<file://\\servername\sharename\username.domain> USERENV(1294.12b0) 15:01:43:704 LoadUserProfile: lpProfileInfo->lpUserName = <dougtes_s> USERENV(1294.12b0) 15:01:43:704 LoadUserProfile: lpProfileInfo->lpProfilePath = <\\feat\s002\basic\dougtes_s.OurDomain<file://\\feat\s002\basic\dougtes_s.OurDomain>> Up until now we have never had to have a folder with the domain name on it. Once in a while we had domain names added as extension but that was when profiles were stuck in memory and the person was logging on a second time. That is not the case this time. Right out of the gate it is appending the domain name to the end. So my question is what can I do to prevent it from using domain extension? I am not sure if it is related but profiles are not unloading either (no errors that I could find in the event log) Regards, Doug Stratton, Shared Service BC Service Desk Email: 77000@xxxxxxxxx Service Desk Tel: (250)387-7000 ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________