Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows 2000 / Terminal Services / July 2003

Tip: Looking for answers? Try searching our database.

Home Directory prevention

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
AL - 31 Jul 2003 10:58 GMT
We have an NT domain with a few 2K servers running
terminal services.  How do I prevent users Home directorys
from connecting when they log onto the terminal server?  I
know in user manager for domains you can set the users
terminal server home directory but I havn't set this and
it seems to use the normal Home directory setting.  I hope
this makes sense.
Vera Noest [MVP] - 31 Jul 2003 12:38 GMT
Since you haven't set a TS-specific home directory, the general one is
used. Define a local home directory for the users instead (note that this
is fine as long as you have only one TS, but will become a problem when you
build a farm with more than one TS).
Why do you want to do this? Users tend to get confused when they have more
than one home directory, and the documents they need are always in the
"wrong" home directory.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

> We have an NT domain with a few 2K servers running
> terminal services.  How do I prevent users Home directorys
[quoted text clipped - 3 lines]
> it seems to use the normal Home directory setting.  I hope
> this makes sense.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.