map drives.

[ikendo]

Hi,

How do you creat a drives that automatically mapped when starting a windows clients?. I noticed by default I get F and Z drive automatically mapped when I login. How and what would I need to do to creat a \Home drive for a end user?. Its theres an login script somewhere on the SYS to config this??

thanks

 

[TheLad]

The login scripts are configured at the container level. You can amend these by using NetWare Administrator. The easiest thing to do is right-click on the container where you created the user and select Details. Use the Login Script tab. Format for mapping drives goes something like this:

MAP P:=SERVERNAME/VOL1:

When you create a user, you should have the option of selecting where to create the users home directory. If you want to create a drive mapping to the users home area, the script below is a suggestion (where P: is the drive mapped):

SET HOMEDIR="%HOME_DIRECTORY"
MAP ROOT P:=%HOME_DIRECTORY -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ikendo]

TheLad,

Thanks,I will give a try when I get home tonight. BTW, how come I see "F" and "Z" drive under My Computer(win2k base), yet I dont see any scripts written under the "users Profile". How does drive F and Z created anyway?

 

[TheLad]

They are automatic drive mappings that you get as standard. Even though they both appear to map to the same place, the Z: is actually a search drive to SYSUBLIC. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ikendo]

Hi,

So those F and Z drives is like default automaticaly eh? So if I want a user to map \Home folder, then I need to write a scripts on the Login Script tab? Ok let me try it.
I enter like this on the Profile?
SET HOMEDIR="%HOME_DIRECTORY"
MAP ROOT P:=%HOME_DIRECTORY

 

[TheLad]

Yes. There are other ways of getting a users home area mapped, I just find the above easier. Give it a whirl and let us know. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[FredNoB]

U can also include the script within a user account and then use it to create a template. U can then use that template for any other users u create automatically giving them the mapping

eg U want to map P to a users account Testuser. Create the account Testuser and set up a folder called testuser within a folder called Homedirs (or wherever). Click the tab Login script within Testuser account and add the line or similar:
map root p:= data:Homedirs\%login_name
Once you have amended this create a new template and select Testuser as the account to take the details from. From then on users created with this template will automatically map the home directories.

 

[ikendo]

Fred,

Thanks alot,I didnt know you can do scripting in soo many ways. Unlike ahem Windows, where you can use only one place. I give a try later one.

thanks guys.

 

[TheLad]

The only disadvantage of configuring login scripts under users is that if you have to make amendments you have to amend all users scripts. It is usually more practical to use the container scripts for anything generic (such as a home/application drive mapping) -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ITsmyfault]

FWIW
1- try not to write user login scripts.. try and write scripts by GROUP. Makes like much easier. Also, for stuff everyone gets, give the rights to PUBLIC or to the container (the OU)
2- the mappings (F & Z) you are seeing are the default login script which is there basically so you can install the OS.

Add the line NO_DEFAULT into your script somewhere so these don't get mapped. (I use the login script for the organization for this) No user should have a mapping (or rights!) to the root of SYS on any server, although they should have SYS/PUBLIC as a search drive
3- In the script(s) you can add options by group membership with IF/THEN clauses.. for ex:

IF MEMBER OF ".ADMINS.ACME_CO.AC" THEN
MAP ROOT M:=\\10.0.0.65\ADMIN"
ELSE
MAP (SOMETHING ELSE)
END

This way you can use one container login script and have it work for all kinds of users...

Remember you can use the MAP ROOT command to mount at a point anywhere in the filesystem and not show the lower levels (eg wherever you mount will look like /)

You can add your search drives as well (they start with Z and work backwards)

MAP ROOT INS S1:=MYSERVER\APPS
(etc)

4- Netware has much more useful (IMHO) filesystem rights, a lot like Unix. Read up on rights to determine what people need and give them only that. Users should have no NDS rights (save view) and limited filesystem rights. On top of that you get into individual file rights.. It can be really confusing as a Win admin to grok it at first, but once it gets clear it's very cool to have..

5 - you can have scripts at several levels (organization, OU and user) they run in this order and each over-writes the prior one (so anything in the user script is the final word..)

hth - Joe

 

[ikendo]

Woowee, that was some explaintion you got there. You guys done great, I really appreciated. Thank you very much.

 

[TheLad]

With Search drives, it can be better writing the login script like this to force a particular search drive to a particular drive letter:

MAP ROOT INS S1:=Z:=SYSUBLIC -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ikendo]

dang, why i see dupilcated drives?..LOL
Same Sys and Volumes.

 

[TheLad]

What do you mean? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ikendo]

TheLad,

I fixed. Now how do I assign each \Home dir to each indiviaul users?. I created a \home folder,but I can see other users files thats been saved. How can I make it so no other user can't see what i have in the \home dir??

 

[TheLad]

Users should have NO RIGHTS at all apart from to their own Home Directory. You may want to check out why users can see all home areas.

Have you created a seperate volume or are you storing the home areas on SYS? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ikendo]

Hi,

I have only one volume(1 drive) and yes i have it on \Home:SYS. So how do you go around it?
Can I creat something?