Re: Windows Terminal Services and SAN
That's what roaming profiles are for: the users use the same
profile, irrspective of on which TS they are working.
You can define a TS roaming profile path in a GPO which is applied
to the OU which contain all Terminal Server computer accounts:
Computer Configuration - Administrative templates - Windows
Components - Terminal Services
"Set path for TS roaming profiles"
To avoid filling up your system disk on the TS, combine the option
above with the following setting (see KB 274152):
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 ___
=?Utf-8?B?YTQwNjIyMjQ=?= <a4062224@discussions.microsoft.com>
wrote on 03 maj 2008 in
microsoft.public.windows.terminal_services:
> Yes, but to the users, they will only see 1 TS so the servers in
> the farm are acting as one server. If I have a iscsi SAN on the
> network and the TS servers are connected to the SAN over the
> iscsi network. How would the users profile work when the
> profile is on the SAN and ts client does not login into one
> particular Terminal Server. I want to have the users profiles,
> my documents stored on one central location.
> o