Automating the Dial-up Logon Process by Using Switch.inf Scripts

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Automating the dial-up logon process by using Switch.inf scripts

To automate the logon process, you can use the Switch.inf file (or Pad.inf on X.25 networks) instead of the manual Terminal window described in Using the Terminal feature for the remote logon process.

Automated scripts are especially useful when a constant connection to a remote computer is needed. If your network connection is configured to use a script, and a remote connection fails, your connection automatically redials the number and reestablishes the connection. Scripts also save time if you frequently log on to a remote system and do not want to manually log on each time.

The Switch.inf file provides a generic script that you can use with little or no modification. You can try Switch.inf without modification and if it does not work, then copy and modify the generic script to match the logon sequence of the remote computer to which you want to connect.

The script language is also designed to communicate with other devices, including modems. If you are unfamiliar with modem scripts, scripting can be difficult to understand. You may find it easier to copy, then modify, one of the generic sample scripts.

This section covers:

• Using device command (.inf) files

• Creating Switch.inf Scripts for Network and Dial-up Connections

• Stepping through an example Switch.inf script

• Getting through two-second gaps and large blocks of text in Switch.inf

• Using commands and carriage returns in Switch.inf

• Troubleshooting logon scripts