Problems Mapping Home Drives 1

[furtech]

Hello,

I seem to have an issue mapping home drives for some users...

I’m trying to map users home drives by going to \\<server>\homes\%username% and then in the login script I have “net use q: /HOME”

For some users when they login, Q: drive is showing \\<server>\homes\ and listing all user home drives

I’m trying to avoid mapping \\<server>\<username> as i dont want several hundred shares running off the one server.

It's a Windows 2003 server and Windows XP workstation.

Thanks,


---------------------------------------
Matthew Collins

http://www.furtech.net

---------------------------------------

 

[porkchopexpress]

If you're using 2003 and XP then i would take a look at this FAQ on logon scripts, you can do so much more with VB and Mark has given examples of how to perform most common tasks so it's just a matter of copy and past really. faq329-5798

 

[r8j8t]

Besides VB scripts you can also implement DFS.
users will not be aware of which physical server their home folder maps to. You can distribute your users to differnet servers with the same drive letter for their home folder.
Then use a small logon script and apply it to the GPO. Users will be mapped to the home folder drive specified by the logon script and they do not have to know the //server/sharename.

 

[Titleist]

furtech,

Try using "net use Q: \\<server>\homes\%username%" in the login script...

John

 

[dvannoy]

I had the same issue you do. I switched everything to vbScript with GPO and issue gone..

 

[WhoKilledKenny]

If you don't go the VB route...
Also add 'Net use q: /delete' before the Net use command to map. This will insure older mappings are removed as well as mappings the user may have done manually. Then when your script maps Q: it will not be shown as in use.

 

[w33mhz]

I have a question why are you doing that through a logon script? Why not set it up in AD. That is a scriptable setting you can script so that you don't have to go into each account in AD and set the home drive by hand. Just to make note of this, the more logon scripts or more that you have in a logon script does cause a delay in logon. Doing it the way I stated is done at a different phase of the logon process and is a little faster.

 

[furtech]

w33mhz,

Do you know of any KB articles you could direct me to?

Thanks,

---------------------------------------
Matthew Collins

http://www.furtech.net

---------------------------------------

 

[porkchopexpress]

Did you look at the FAQ i posted furtech? It should tell you most of what you need to know.

faq329-5798

 

[w33mhz]

This tell you how to setup in AD:

http://support.microsoft.com/kb/320043/en-us

This gives a general discription of what to put in your script to add the property to your accounts in AD.

http://support.microsoft.com/kb/271657/en-us