Table of Contents
Advertisement
Troubleshooting Login Scripts
4
Although login scripts are useful in setting up drive mappings, search mappings, the user's printing
environment, and displaying important messages and other commands, they can sometimes be a
source of frustration when they don't work as expected.
A majority of the problems that occur with login scripts are associated with mapping drives and
capturing printers. Usually, these problems can be attributed to syntax and spelling errors.
Correcting spelling errors and using variables in the right way resolve many problems. For example,
you must put quotes around a login name in an IF..THEN statement.
Section 4.1, "Locating the Problem Statement in the Windows Login Script," on page 59
Section 4.2, "Turning Off the MAPROOT Function in Windows 2000/XP," on page 60
Section 4.3, "Limitations of Tree Command in Login Scripts," on page 60
Section 4.4, "Lowercase Passwords Not Supported When Using the Tree Command in Login
Scripts," on page 60
Section 4.5, "Other Common Login Script Problems," on page 60
4.1 Locating the Problem Statement in the
Windows Login Script
Try the following to locate the problem statement in the login script:
Set MAP DISPLAY and MAP ERRORS to ON in the login script.
By setting MAP DISPLAY and MAP ERRORS to ON, the errors display, often providing clues
as to why a certain command did not execute as expected. After seeing that the login script
performs all map commands without error, the MAP DISPLAY and MAP ERRORS parameters
can be turned OFF.
Use the WRITE or MAP commands together with the PAUSE command prior to the script
command which doesn't work as expected.
By adding the PAUSE command after the WRITE or MAP command, you have an opportunity
to see what is happening when the script is executed.
For example, if the login script didn't seem to be completing an IF..THEN statement, put both
a WRITE and a PAUSE statement immediately before the IF..THEN statements to verify that
the script executed to that point. Then, place a WRITE and PAUSE inside the IF..THEN to see
if it gets past the IF correctly. It would also be helpful to have the WRITE statement give the
value of the variables being tested to make sure that the variables are correct going into the
script. For example, WRITE "This is the login name: %LOGIN_NAME".
You can also use the PAUSE command with the MAP command to determine when and where a
certain mapping was created in a login script.
Make a test login script file either on the local drive or a network drive using any DOS text
editor.
Test this script file by using the /S parameter at the DOS prompt:
LOGIN /S drive:\filename servername/username
Troubleshooting Login Scripts
4
59
Advertisement
Table of Contents
