General discussion

Locked

logon scripts

By agill ·
what does a correct logon script look like that provides the user with these resources:
Access to network drives
selected printers
and all network drives across servers
upon logon to the network.
please write a demo for illustration.
thanks

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

logon scripts

by ChannonP In reply to logon scripts

You need to use the NET USE command for network drives:

eg.

net use y: \\fileserver\public
net use x: \\fileserver\staff
net use v: \\fileserver\global

save this as logon.cmd or what ever and put it in your logon dir.
you'll need to change the user profile to use this logon script.

Printer wise for those that I can't put on the local machine I use kixstart, think this comes with the res kit. It's v.useful and you can do all sorts of stuff with it, worth reading documentation for.
Write a little kix file using the setdefualtprinter command.

then add this line to your logon script:

%0\..\kix32 printchg.kix

hope this is of some use

Collapse -

logon scripts

by agill In reply to logon scripts

Poster rated this answer

Collapse -

logon scripts

by dcassat In reply to logon scripts

The first answer is correct but here is a little additional info. I usually have a login script that removes the drives and printers about to be mapped first like:

net use x: /d (this line deletes the x drive)
net use lpt2: /d (this line deletes the printer)

Then I create the mappings like:

net use x: \\server\apps (apps is a shared directory on the server)

net use lpt2: \\server\laserptr (laserptr is a shared printer on the server)


From the above x: drive is now the same as the apps share on the server and lpt2: has been mapped to the laserptr printer. The printer mapping is only necessary when printing from the older DOS programs. You can also keep the lines from echoing on the screen by adding > null to the end of the line like:

net use x: /d > nul

You can name your batch file with a .bat or .cmd extension and put it in the winnt\system32\repl\import\scripts directory. Make sure that the script resides on every Domain Controller and Backup Domain controller or the scripts won't always run because they are being logged by a backup domain controller instead of the primary. Good Luck.


I hope this helps

Collapse -

logon scripts

by agill In reply to logon scripts

Poster rated this answer

Collapse -

logon scripts

by agill In reply to logon scripts

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums