Hi Tom,
For users to get to the home share, whey will need permissions on the folder
and share permissions on the share under which the mapping will occur. If
you let AD create the folder itself, you'll find that it assigns the user as
the owner of the folder and the permissions are done as the owner.
To actually map the drive you have two options. If you wanted the X: drive
to be the home folder, you could:
Specify home drive and the folder path in Active Directory Users and
Computers. With Server 2K3, you can do this to multiple user accounts at
once with a path like \\<serverName>\<ShareName>\%username%
- or --
You can do this in the logon script as:
net map x: \\<serverName>\<ShareName>\%username% /home
It should also be noted that many people are abandoning the concept of home
folders for folder redirection using the My Documents folder as the network
synchronized space. This lets users work off line if they have to (roaming
laptops) and captures more than just a home directory would. The trade off
is if you have a long history of a home folder ingrained in your users or if
you are training NetWare users to work in the windows world.
Let us know if you have any problems.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
http://www.techsterity.com
Chicago, IL
Remember: Marking helpful answers helps everyone find the info they need
quickly.
"Tom" wrote:
> Hello,
> We are running Windows 2003 Server. We have about 20 Vista Business pc's
> that work great on the network but for one problem. When the staff log-in,
> their home directory that is listed in Active Directory won't map
> automatically. Is it necessary to share their specific folder on the server
> so that it can map to it? I had this same problem with pre2000\xp machines.
> The root directory of the staff folders is shared on the network, but not the
> individual staff folders. Any help would be greatly appreciated.
> Thanks,
> Tom