Re: Profile Created on TS- not wanted
Nothing, this is by design.
When you log on to any Windows OS, you need a profile. If you don't
have one, it will be created for you. By default, the profile is
created in C:\Documents and Settings\%username%.
The only supported way to change this location (but not to avoid
the creation of the profile altogether) is during an unattended
setup of the OS, as documented here:
236621 - Cannot Move or Rename the Documents and Settings Folder
http://support.microsoft.com/?kbid=236621
You can (and should) define a TS specific profile for the users,
which you can locate on a shared network drive on a file server.
But even if you do that, a local copy of the user's profile will
still be created in C:\Documents and Settings as soon as the user
logs in to the TS. However, you can configure the server to delete
these local copies again when users log off. Configured like this,
your TS will never contain more profiles than you have concurrent
users on the system.
The above is easiest configured through a Group Policy. Here are
the settings:
Computer Configuration - Administrative templates - Windows
Components - Terminal Services
"Set path for TS roaming profiles"
Computer Configuration - Administrative Templates - System - User
profiles
"Delete cached copies of roaming profiles"
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
compsosinc@gmail.com wrote on 01 nov 2007 in
microsoft.public.windows.terminal_services:
> We just setup a Terminal Server, added TS Device CALs, etc. We
> have not setup any GP on the DC yet but intend to.
>
> We setup a user & computer account on the DC for one of the TS
> Clients. We setup a Remote Desktop Connection on the client and
> successfully connected to the TS. On the TS, we now have a
> folder for the user under the Documents & Settings directory. We
> have 9 other users that wil connect to the TS and do not want a
> folder created for each one.
>
> What can we do to avoid this?
>
> Thanks!