Automating Network Printer Setup

Unattended Setup is not designed to install printers. However with little effort, you can configure your environment to install a network printer when a user logs on to a computer running Windows NT or Windows 2000 for the first time.

Use the following steps to configure your environment to install a network printer when a user logs on to a computer running Windows NT or Windows 2000 for the first time:

1. Install and share the desired printer on the Windows NT or Windows 2000 server.
2. To start System Policy Editor to create a profile, execute poledit from a Run dialog box:
   1. From the File menu, click New Policy.
   2. Double-click Default Computer.
   3. Open System\Run.
   4. Put a check mark in the box next to the Run option.
   5. Click the Show button.
   6. Click the Add button.
   7. Type a descriptive name for the item.
   8. Add the UNC path pointing to the Windows NT 4.0 or Windows 2000 printer share.
   9. Click OK 3 times.
   10. From the File menu, click Save and save the file to Ntconfig.pol located in the folder used for the Netlogon share. For example:
       
       \\<Servername>\Netlogon\Ntconfig.pol
       
       NOTE: Ntconfig.pol must exist in the Netlogon share of all domain controllers. This may require manually copying the file to the correct location or setting up replication.
       
       For additional information on configuring Windows NT for directory replication, please see the following article in the Microsoft Knowledge Base:
       101602  (http://support.microsoft.com/kb/101602/EN-US/ ) Configuring Windows NT for Replication

When a user first logs on, he or she will need to access the printer from the Run dialog box by entering the printer's share name. Clicking the Yes button will set up the printer. Each subsequent time the user logs on, a properties window for the printer will open. Although this window does not present any problems, it can be eliminated by removing the item from the Run option in the Ntconfig.pol file.

The above procedures can be modified to work in environments that are not organized by a domain. This modification would require enabling manual profiles. Refer to System Policy Editor Help for more information on Manual Updates.