Re: Drive mapping error



In news:56CD3F9D-D879-4E89-AC50-6258525AEBFE@xxxxxxxxxxxxx,
D Clark <DClark@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Sorry, my wording was probably not very clear. When I said random
about when and who it happens to, I should have said it was a
intermitent problem. The problems happens to myself, it will work
fine one time, then next time i log in it will map to parent folder.
Then will be fine again next time.

OK - take a look at the event logs on the client when this happens....

"Lanwench [MVP - Exchange]" wrote:



In news:E23AA6DD-8915-47FF-B0D4-871AEE4BC3A1@xxxxxxxxxxxxx,
D Clark <DClark@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Thanks for the reply.

It is a batch file we run. We have the persistent:no line in the
script at the start and we map the H drive using Net Use H: /home.

Meaning,

net use h: /home /persistent:no
?

The H drive in then specified in ADUC as
\\server\department\%username%



Hope this helps.

I've seen this happen when NTFS permissions on the user's folder
weren't set up properly - I like Administrators & System = full
control, user = modify, for each of the folders - double check, and
push the settings down through all child folders.

"Lanwench [MVP - Exchange]" wrote:



In news:B33FBE98-F023-472E-B7A1-E31D1BEC48A5@xxxxxxxxxxxxx,
D Clark <D Clark@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hi all.

I work for a NHS Trust and we run Windows Server 2003 with AD.
When users log on they execute a log in script that is defined in
their profile. The user has a H drive which maps to their home
directory specified in their profile. The H drives map to
\\Server\Department\Username.

Maybe OT, but how are you specifying this in the script - is it a
batch file, and is it

net use h: \\server\department%username%
or even
net use h: /home
(presuming that the users' home directory paths are specified
in their ADUC properties) ?

I suggest adding
/persistent:no
to the end of the net use line, too. But that's probably not
relevant - it just helps keep things tidy.


When users are logging in, sometimes their H drive maps correctly,
or it maps to the parent folder (Department) instead. Its
completely random who it happens to and when it happens.

I was wondering if anyone has come accross this before or knows
why it his happening. If anyone needs more info, please let me
know. All help and advice greatfully received.

Double check the permissions that each user has to their subfolder
under the Department share.....should be either Modify or Full
Control (and subfolders under the username folder should inherit
the settings therein).

Also, helps if you mention your client OS version and SP
level.....and if you have any event log errors on the client.


.

Relevant Pages

  • Re: Drive mapping error
    ... script at the start and we map the H drive using Net Use H: ... I've seen this happen when NTFS permissions on the user's folder weren't set ... The H drives map to ... but how are you specifying this in the script - is it a ...
    (microsoft.public.windows.server.networking)
  • RE: NT4 client access to W2K Member server in NT4 Domain
    ... Actually, in the pre-Windows 2000 systems, we cannot map to the down-level ... subfolders in a certain shared folder. ... In other words, on Windows NT ... |>issues accessing the W2K3 member server in the NT4 ...
    (microsoft.public.windows.server.migration)
  • Re: Standardize drive assignments
    ... > part of more than one group...he mapped those map drives but ...not all ... a new folder, share it out, and map it to drive G: ... If you can make this change it will simplify the logon script, ... >>> I think this nesting group is called LOOPG function inside. ...
    (microsoft.public.windows.server.scripting)
  • Re: Schema Map need to be in the same folder?
    ... did you create the map in the project root and then ... Have you tried right-clicking the /map folder ... Mike Vallier ... Microsoft BizTalk Support Professional ...
    (microsoft.public.biztalk.general)
  • RE: NT4 client access to W2K Member server in NT4 Domain
    ... |Actually, in the pre-Windows 2000 systems, we cannot map to the down-level ... |subfolders in a certain shared folder. ... In other words, on Windows NT ... ||>issues accessing the W2K3 member server in the NT4 ...
    (microsoft.public.windows.server.migration)