users H drive setting in AD...why two methods?

[kennysarmy]

I've just noticed that some of our student accounts have their H: drive set thus:

 

Local Path : \\servername\sharename$

 

and some are set:

 

Connect : H: To: \\servername\sharename$

 

What is the difference?

 

Regards.

[powdarrmonkey]

I've just noticed that some of our student accounts have their H: drive set thus:

 

Local Path : \\servername\sharename$

 

...is incorrect, and shouldn't work (but probably does, just in case it's been set like this...)

[kennysarmy]

...is incorrect, and shouldn't work (but probably does, just in case it's been set like this...)

 

incorrect why?

 

the pupils login script is:

 

net use h: /delete /yes

net use h: /home

 

 

everyone gets their H:\ drive...but I don't like things being inconsistent...

 

any comments anyone?

[powdarrmonkey]

incorrect why?

 

the pupils login script is:

 

net use h: /delete /yes

net use h: /home

 

 

everyone gets their H:\ drive...but I don't like things being inconsistent...

 

any comments anyone?

 

Because you can't control the letter that gets assigned to it, and it confuses the issue when troubleshooting.

[kennysarmy]

Because you can't control the letter that gets assigned to it, and it confuses the issue when troubleshooting.

 

so without the login script line:

net use h: /home

 

only those students who have the line in their profile that says

connect H:\ would get H: \ set as their home drive....

 

where would the system get the information to decide which letter to use for those students who have their profile just as :

Local Path : \\servername\sharename$

 

Regards.

[bio]

Personally i would not set these 2 items at all. just do this in your login script.

 

regards

bio..

[kennysarmy]

Personally i would not set these 2 items at all. just do this in your login script.

 

regards

bio..

 

interesting ...how would you do that though?

 

As I understand it the net use h: /home refers back to the information in active directory....

[powdarrmonkey]

interesting ...how would you do that though?

 

With:

 

net use h: \\someserver\%USERNAME%

 

or similar. I wouldn't do it though, I'd let AD do the work for me.

[tmcd35]

I always thought the first example, the 'Local Path', was for assigning the home folder on the local computers local hard drive, perhaps 'C:\home\'. And not for connecting the home drive to a network share.

 

Personally always used the second example - Connect: N: to \\server\$

[powdarrmonkey]

@tmcd35: correct.

[DMcCoy]

I always thought the first example, the 'Local Path', was for assigning the home folder on the local computers local hard drive, perhaps 'C:\home\'. And not for connecting the home drive to a network share.

 

Personally always used the second example - Connect: N: to \\server\$

 

Of even \\server\usershare\%username%

 

No need for individual user shares these days

 

Plus using this in AD means you can use if for the my docuements redirections etc. Why do it after in a script if it's actually a defined part of the logon process?

[powdarrmonkey]

No need for individual user shares these days

 

I keep telling my boss this... he disagrees

[DMcCoy]

I keep telling my boss this... he disagrees

 

I have several shares with different permissions depending on the depth, but since access based enumeration stopped the only "cosmetic" issue with seeing (but not having access) other users folders, I can't think of a single reason to use individual shares.

[sted]

i think the local path one is a legacy one from nt 4 (and possibly earlier) servers. SOme of our older setups are done this ways (or at least older users newer ones) use the connect u: \\server\users$\group\username

 

the other way woks fine in my experience but i do have the net use home line in my users logon scripts

[teejay]

Can anyone explain why you actually need a home drive any more? We just redirect My Documents to a network share and don't have a home drive.

[powdarrmonkey]

Can anyone explain why you actually need a home drive any more? We just redirect My Documents to a network share and don't have a home drive.

 

Because some badly written software insists on a network drive (I'm looking at you, Magix Studio).

[ascott2]

We had just found the same issue here a couple of days ago when we moved the home folders to a new server. The reason why it has worked for us up until now is that the net use /home command looks at the local path in NT User Account or AD and that is why still sets it.

 

It should be Connect To: or just redirected My Documents as mentioned previously.

[teejay]

@powdarrmonkey

 

Must have been really fortunate then, as I've not come across this problem so far. Been running without a home drive for 6 years now.

What we've done is write a specification of requirements for software, which we send to the software supplier and they have to agree to it before they supply us with the software. If the software has crappy things in it like needing a home drive mapped, or direct access to c:, or admin priveledges then the stuff goes back for a refund.

[plexer]

care to share that statement of requirements?

[kennysarmy]

This is all very interesting.

 

Thanks for all the comments.

 

Looks like the way to go is:

 

Edit all user accounts to use connect to method, then look at using the redirect for my docs. (We already use the redirect for the desktop and start menu...)

 

 

>>>Because some badly written software insists on a network drive

 

By this do you mean that the user actually has an H:\ drive mapping?

 

Regards.