Server 2k3 profile question

[Revolucion]

Every time a user logs into our terminal server, it creates a new profile: first.last.domain.001 but it keeps going and i have a couple useres where that number reaches up to 306. we do have a roaming profile that is on a completely different server. It is controlled through GPO. My question is if we use GPO enforced roaming profiles, why does it create a local one on the terminal server. network specs: Terminal Server- Server 2003 x64 all SP installed, Workstations-all XP Pro, Profile Server is Server2003 x64 all SP installed. If any more info is needed, let me know i will be happy to provide.

 

[davethegrey]

Hi There,

I assume you use a terminal service profile setting in a GPO, meaning :

use a Group Policy, linked to the OU which contains the Terminal Server machine account, and configure the setting

Computer Configuration - Administrative templates - Windows components - Terminal Services
"Set path for TS roaming profiles"

Note that you should not add %username% here, just something like \\server\TSprofiles.

To avoid filling up your system disk on the TS, combine both options above with the following setting


If you enable Group Policy, any local copy of a user's roaming profile is deleted when the user logs off. However, the roaming profile still remains on the network server that stores it.

You can configure a Group Policy Object (GPO) to perform the preceding behavior by performing the following steps:

1. Edit the GPO that you want to modify.
2. Locate the following section: Computer Configuration \ Administrative Templates \ System \ User Profiles.
3. Double-click Delete cached copies of roaming profiles (the Group Policy setting).
4. Click Enabled.

 

[Revolucion]

Thank you very much, that seems to be what i need to do, i will test this out today and post results hope this helps other people as well.

 

[Revolucion]

Thank you very much for the advice worked great. Login speed increased. Job well done sir.