Home Drive mapping to \\server\share\folder maps to \\server\share

Guys

Can someone help me here, how Home drive is set in active directory to
map to:

Connect H to \\srvfile1\users\%username%

This works say 95% of the time, but sometime the drive is mapped as
\\svrfile1\users, which causes a few issues with applications that are
looking for H: rather than the UNC path.

Our Active Directory is Windows 2003, the file server is Windows 2003,
and the clients are a mix of Windows 2000 and Windows XP.

Any ideas on this would be great!?

Also, randomly users appear to loose a mapped drive. All our mapped
drives point to the same server:

OK H: \\svrfile1\users\roger rabbit
OK I: \\svrfile1\group
OK O: \\svrfile1\common
OK S: \\svrfile1\controlrm

Now say in a few hours I could open windows explorer and find that o:
is missing, however all the other drives are still there...

Again, any ideas on what could cause this?

Thanks

David

Hello,
(E-Mail Removed) wrote:
> Can someone help me here, how Home drive is set in active directory to
> map to:
> Connect H to \\srvfile1\users\%username%
> This works say 95% of the time, but sometime the drive is mapped as
> \\svrfile1\users, which causes a few issues with applications that are
> looking for H: rather than the UNC path.

sounds strange.

> Our Active Directory is Windows 2003, the file server is Windows 2003,
> and the clients are a mix of Windows 2000 and Windows XP.
> Any ideas on this would be great!?

Did this happen exlusively to one of the mentioned client classes?
Do you have enabled the Always wait for network policy?
Any issues reported in the event log?

> Also, randomly users appear to loose a mapped drive. All our mapped
> drives point to the same server:
>
> OK H: \\svrfile1\users\roger rabbit
> OK I: \\svrfile1\group
> OK O: \\svrfile1\common
> OK S: \\svrfile1\controlrm

Well, this I have seen also recently.
And if I opened a cmd prompt and checked there, the drive was there. Only
the Windows Explorer lost it from its access.
net use O: /delete
and
net use O: \\server\share
was the quick workaround.

On server side you can also try
net config server /autodisconnect:-1
if the issue is caused by the server.
Best greetings from Germany
Olaf

Hi

Well since your losing map drivers on your clint stations, you shoud create
a script which will map the drivers for you everytime a user logs on, like a
simple batch file:

Try this:

Echo off
net use /delete * /y (optional if you whold like to delete all maped
drivers)
net use I: \\svrfile1\group
net use O: \\svrfile1\common
net use S: \\svrfile1\controlrm
exit

Once you have the batch file you can aply the batch file under you group
policy settings under (user configuration)

For your user profile you should ensure that all user have the write UNC
path under they account properties. Since the net use command whon't create
the user folder under you share.


"(E-Mail Removed)" wrote:

> Guys
>
> Can someone help me here, how Home drive is set in active directory to
> map to:
>
> Connect H to \\srvfile1\users\%username%
>
> This works say 95% of the time, but sometime the drive is mapped as
> \\svrfile1\users, which causes a few issues with applications that are
> looking for H: rather than the UNC path.
>
> Our Active Directory is Windows 2003, the file server is Windows 2003,
> and the clients are a mix of Windows 2000 and Windows XP.
>
> Any ideas on this would be great!?
>
> Also, randomly users appear to loose a mapped drive. All our mapped
> drives point to the same server:
>
> OK H: \\svrfile1\users\roger rabbit
> OK I: \\svrfile1\group
> OK O: \\svrfile1\common
> OK S: \\svrfile1\controlrm
>
> Now say in a few hours I could open windows explorer and find that o:
> is missing, however all the other drives are still there...
>
> Again, any ideas on what could cause this?
>
> Thanks
>
> David
>
>