win 2000 server does not map home drives to 98 clients 1

[kennyheatrick]

does anyone know why it might be, that after entering in each users properties under the profile tab a users home drive mapping the user still has to map their home drive manually.

as i understand, an entry in this field should automatically map the home drive and also this should be the default directory at the dos prompt. the clients are all win 98, does this have something to do with the problem??

thanks in advance

kenny

 

[peterve]

I'm having the same problem...
I've set the home folder mapping in the login script and thus solved the symptom (but not the problem itself...)

Peter Van Eeckhoutte
peter.ve@pandora.be

 

[Zelandakh]

Easy one Kenny.

The home directory will automatically map for NT clients, but for 9x clients you need to also select the logon script and run it. I use home.bat which has a single entry in it:

net use k: /home

which will map the k drive to their home directory as specified by User Manager.

Drop this home.bat into the netlogon share of your DCs and ensure that the logon script is specified and everything works fine...

Damn I'm good.

 

[peterve]

That was what I said... Peter Van Eeckhoutte
peter.ve@pandora.be

 

[Zelandakh]

It was designed this way as yet another excuse to force you to go the NT route.

9x was supposed to be the home user route.

 

[peterve]

... hmmm I thought Win9x was the route to hell....

;-) Peter Van Eeckhoutte
peter.ve@pandora.be

 

[Zelandakh]

If you've ever supported home users, you will know it is hell!

 

[peterve]

I did... I had more than 500 home users a few years ago...
Win9x = poison : it kills you !!

Anyway, the only good solution to solve this problem is
- installing NT/Win2K based solution
or
- map everything manually from a login script !

Peter Van Eeckhoutte
peter.ve@pandora.be

 

[kennyheatrick]

thanks guys for your responses.....they were both helpful and amusing

 

[RobLM]

I am using Win2000 Advanced Server. On my Win98 clients I try the direct map in the logon script. My logon script has a "net time /set /yes" command first. That works fine. But when it gets to the "net use h: /home" command it says that the user is not logged on. After the script finishes, I explore to the NETLOGON share and double click the script and it works fine. How do I fix this?

 

[duggin]

"net use h: /home" is fine for a shared folder called "home". But what if you want to open the user's home folder directly based on their username?

Would "net use h: /home/%username%" open the user's specific folder?

 

[peterve]

I would create a share for every user,
(not subdirectories under a share called home, because otherwise you would have to put NTFS restrictions on each subdirectory, which increases the maintenance & TCO

Also, if you try to use the 'home' variable, it will not work with Win9x clients

net use h: \\server\%username% in the logon script
---------------------------------------------------------------------
I have not failed, I've just found 10,000 ways that don't work
---------------------------------------------------------------------
Peter Van Eeckhoutte
peter.ve@pandora.be
*:->* Did this post help? Click below to let me know !

 

[duggin]

Ah ... many thanks. Can this folder be created automatically (if it doesn't exist)when a new user logs on?

Is this done through the "Policy" tab in the user's PROPERTY options?

 

[peterve]

it's not automatically created, but
- you can write a dos batch file to create a user, create a directory, and share the directory (all in one...) using some nice NT Resource Kit tools ---------------------------------------------------------------------
I have not failed, I've just found 10,000 ways that don't work
---------------------------------------------------------------------
Peter Van Eeckhoutte
peter.ve@pandora.be
*:->* Did this post help? Click below to let me know !