Have a Windows 2003 Terminal Server setup, that is also doing domain logins (Active Directory) for a local network. I want users both logged onto the terminal server, and roaming profiles on Windows XP clients to have the same profile, and for their home directory to always be mapped to H: What I currently have configured: In the properties of each profile, under the 'profile' tab, Profile path: \\SERVER\Profiles\MattW Logon script: \\SERVER\netlogon\logon.bat HOME FOLDER CONNECT: H: to \\SERVER\Profiles\MattW "Profiles" is a share of "C:\Documents and Settings\" on the Windows 2003 server. Everything works fine - only problem is every user has two profile directories, for example: C:\Documents and Settings\MattW C:\Documents and Settings\MattW.WINDOMAIN Where WINDOMAIN is the domain of the server. It appears the server is being slowed down heavily because they seem to be a copy of each other, that's happening every time the user logs in. It's also using up unnessecary disk space. This is happening for every terminal server user - including those that don't use XP clients. I'm doing something wrong - what is it, and how do I fix it? Thanks

Your profiles path can be \\SERVER\profiles\%username% but the share "profiles" must be something else than "Documents and settings". You can create and share a folder "profiles" in c:\.

why is that? i wish to use the same profiles for roaming profiles.

You asked how to configure roaming profiles and I gave you the answer. What you did is not the good config of roaming profiles. To use roaming profiles you must share your profiles (\\SERVER\profiles) and your computers will download them to "C:\doc n settings\" when the user will log on. With what you did your TSE will find the profile in "C:\doc n settings" and download it to... "c:\doc n settings". But there already is a folder named "Mat" there so you computer will create a new folder named "Mat.DOMAIN".