Re: problem mapping NT 4.0 client home folders

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Todd J Heron (todd_heron_no_spam_at_hotmail.com)
Date: 09/17/04 

Date: Fri, 17 Sep 2004 17:49:51 -0400

If a user is mapping to a share rather than to the home directory specified
in Active Directory, use subst in a domain login script, which will allow
mapping to folders below the root Share to a drive letter. "Net Use" (in
Windows 95/98/Me/NT) can only connect the root of the drive to the sharename
and not any subsequent subdirectory (unless mapping to a Novell share, which
is a special case). As a workaround, for Windows NT/XP, use the "Subst"
command instead of "Net Use" in the login script, as follows:

subst H: \\Server\Share\%username%

In this example the root of H: will be mapped to the directory corresponding
to the user name, under the share called "Share" on server "Server".

For single home directory creation:
1. Create a new user
2. Create a user share on a File Server (or the PDC if none other is
available)
3. In User Manager for Domains, click on the Profile button
4. Select a drive letter that will be to connect to the share, then type the
path to the share: \\servername\sharename\%username%

For mulitple home directory creations:
1. Create the users shares on a File Server (or the PDC if none other is
available)
2. In User Manager for Domains, select all user accounts and then select
properties in the menu
3. Click on the Profile button.
4. Select a drive letter that will be to connect to the share, then type the
path to the share like this: \\servername\sharename\%username%

This will create a home directory for each user in the Share specified. The
%username% is a variable that will be replaced by the username. 

-- 
Todd J Heron, MCSE
Windows 2003/2000/NT
"Joe" <anonymous@discussions.microsoft.com> wrote in message
news:0e3101c49cf3$f8992ab0$a501280a@phx.gbl...
> This is probably a very simple thing I'm missing but here
> goes -
>
> Setup a homefolders share on serverA granting everyone
> access to the shared folder. Then from AD, I set up home
> folder mapping to Z drive using \\serverA\homefolders\%
> usernae%. Everything works fine for Windows 2000 and XP
> clients. But with NT 4.0 client it appears to map to the
> homefolders directory instead of the homefolders\%
> username% directory. And becuase of this users get an
> access denied message when they try to access the Z drive.
> However when I goto a command promt, the defualt directory
> is z:\%username% and the user can write and read to it no
> problem. This doesn't work well though because when I user
> goes to save something from a windows app only the Z:
> drive is listed and access is denied. It appears the
> probelm is in the inital mapping. Why does NT 4.0 map
> differently then W2k?
>
> Thanks,
> Joe

Relevant Pages