• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

NT home directories/drive mapping

V

VoterX

Junior Member
This question is somewhat of an administrative boggle in NT server 4.0, service pack 6. At the moment I'm configuring a second server for the small (read: "owner and 4 employees") company I work for. I want to set up home directories for users I create, but he method I found in a book published by microsoft didn't work to my satisfaction.

The method recommended (for use with NTFS) was to create a general users directory (named "users") which is shared so that all users have full control access to it. Each user then has a subdirectory controlled with NTFS permissions. Then the home directory for each user would be [ driveletter ]:\users\%username%. The problem I'm having is that when I set a user's home directory to the path given above in user manager for domains, The user gets a drive mapped to the "users" directory, not directly to that user's subdirectory. Here's an example:

The user is bob.
Bob's home directory would be: D:\users\bob
In user manager for domains, I set Z: to map to D:\users\bob
bob logs in and sees Z: as mapped to D:\users

Is this normal operation?
I had seperate problems with lonon scripts that I won't detail here, but I was just wondering if there was a solution short of either sharing the user's home directory explicitly, or mapping the drive from the client computer.

Thanks.
 
Yeah I got the same, there was a way to set it, but I dont remember, i know in w2k it fixes the problem where your Z will be his users\bob, someone here should know, i'll try to dig up my old notes.
 
NT4 doesn't know how to map a drive to a folder within a share. You will need to use the subst command to get around it. Look in NT's help on how to use it.
 
Thanks Bignick, it looks like that command will do what I want it to. It looks like I'll have to run it on the client machine, though. Any reason why it wouldn't work as part of a logon script? (My instinct is no)

This may also explain the system error 67 network name could not be found I was getting with the "net use" command in the logon scripts trying to call out a subdirectory of a shared folder.

Edited to avoid confusion
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top