Useful Logon Script Commands

active-directorylogon-scripts

Please post useful commands that you use in your logon script.

Here are some that I use:

map a network drive:
net use v: \fileserver\apps
map a network printer:
RunDll32.EXE printui.dll,PrintUIEntry /in /n
"\\printserver\Xerox DC1100 PCL"
delete a network printer:

RunDll32.EXE printui.dll,PrintUIEntry /dn /q /n
"\\printserver\HP LaserJet 2300"
disable windows firewall:
netsh firewall set opmode disable
install a new program:
if not exist "C:\Program Files\Antivirus\"
"V:\Antivirus\install.msi"

create a shortcut on users Desktop:
copy "V:\shortcuts\dictionary.lnk" "%USERPROFILE%\Desktop"

Best Answer

I might get down voted for this, but so be it. I've always considered logon scripts to be kind of hack'ish and try to only use them as a last resort. There are so many ways to manage systems and users these days with things like Group Policy, Group Policy Preferences, and SCCM/SMS. I mean, there's always going to be cases where there just isn't a better way to do things. But many of the examples provided so far can easily be done without a login script like installing software and mapping network drives.

Related Solutions

Active Directory logon script not updating

It sounds like you don't know if the users are executing the new version of the script or the old version. (I'm guessing that you have a single domain controller and that this isn't a file replication issue between the DCs. Theoretically, it could be, but we'll go there only if you indicate that you're seeing replication problems with the NETLOGON share between your DCs.)

My gut says that you're doing something like a "NET USE ..." and the users have persistent "drive mappings" enabled. As such, when the "NET USE ..." attempts to "map" the "drive" letter the command is failing because the "drive" is already "mapped".

I'd add a "NET USE x: /D" on the line before the drive letter in question, like:

@echo off
NET USE Q: /D
NET USE Q: \\server\sharename

This deletes the existing "mapping" for "drive" Q: before creating one.

By default, these "legacy logon scripts" run visible during logon. As such, you can add debugging line "echo on" and/or a "pause" at the end of the script, then logon as a user and see what's actually executing. This is your best bet if you can't get it to work-- see what's actually executing and debug it.

Logon Script, detect network status

Why do this with batch file gyrations when you can just link GPOs to site objects? The "bonus" being that if you add addt'l subnets or move subnets around you'll never have to edit your script.

If you're looking at this being a user logon script that you want to apply only when users logon to specific computers then you'll need to look at using loopback group policy processing as well.

Best Answer

Related Solutions

Active Directory logon script not updating

Logon Script, detect network status

Related Topic