Subscribe to Windows IT Pro
May 27, 2008 12:00 AM

Set Up Printers Without GPOs

Help your users find the right printers no matter where they're logged on
Windows IT Pro
InstantDoc ID #98829
Rating: (6)
Executive Summary:

IT Departments have to meet the challenge of connecting users to the resources they need, such as printers, as well as maintaining appropriate security. Establishing appropriate naming conventions for printers should make it easier for users to use the Add Printer Wizard and other connection methods. Creating shortcuts to your printers on a public share might be the simplest way to help users make their printer connections.

What can you do to meet the challenge of connecting users to the resources they need, such as connecting to the right printer no matter what workstation the user is logged on to? With the advent of Active Directory (AD), making these connections certainly got easier. But some work environments aren’t amenable to implementing resource distribution with AD. For instance, you might work in a centrally managed AD environment, but your IT department is at the lower end of the AD food chain—meaning you aren’t allowed to implement Group Policy Objects (GPOs). Or your user needs could be so individualized that managing a GPO scheme would be next to impossible because everyone would need a different GPO. Or you could have to meet security regulations such as the Health Insurance Portability and Accountability Act (HIPAA) that require certain documents to be printed to a secured location, while other, nonconfidential documents can be printed on any printer.

In addition to the management problems, you might have users who are (how to say this and not be offensive . . .) lacking in most basic computer skills so that even getting them to use the Add Printer Wizard is difficult. If you find yourself in any of these situations and deployment with GPOs isn’t an option, you might consider making per-machine printer connections with the PMPMgr plug-in, which you can read about in the sidebar, “Recommended: PMPMgr for Printer Management.” Otherwise, you’ll need to find ways to help your users help themselves without putting excessive strain on your IT department. So let’s look at some ways you can help your users get connected without using GPOs.

Printer Connection Challenges
Although some printer information, such as drivers and ports, is stored machine-wide (i.e., it’s available to all users on the computer), information about the printers on the network that an individual user connects to isn’t. Users have to connect from each computer they use to each network printer they want to access. In some environments, this can be a challenge. For instance, a nurse might have the potential to log on to 50 different computers within a hospital on a particular day. Many businesses have shared workstations throughout their buildings that can be used by hundreds of users over the course of a week.

IT staff need to help users get to the printers appropriate for them, no matter where the users are logged on. To do so, an IT department needs to address

  • the per-profile settings (settings set for each user)
  • the company’s desire to decrease total cost of ownership (TCO), which means placing network printers only in key areas
  • the convenience to users of having a printer physically near them
  • helping users identify which printers they need
  • meeting regulatory compliance for security of sensitive print jobs

Sometimes the second and third items on the list will conflict, and it can be very trying when users complain that walking 20 feet down a hallway to reach the network printer is a hardship. It’s up to the IT department to consider every factor when placing printers.

Develop a Good Naming Scheme
Helping users identify which printers they need to use can be a daunting task. You can approach this in several ways. One way is to place a label on each printer stating its name—such as “HR Confidential Printer” or “Room 100 Printer”—following whatever naming scheme your company uses. It’s helpful if your naming scheme lets you be very descriptive about where the printer is and what special attributes it has, such as color printing or being located in a secured location. If you can’t work attributes into the naming scheme, you can use the Location and Comments field on the printer to give more information; users will need their Windows Explorer view set to Details to see this additional information. Users do have to put some effort into figuring out which printers they need. And, of course, every good IT department will tell its users to call the IT department or Help desk if they’re unsure or need assistance.

Some companies have complex naming conventions that might make sense to IT personnel but won’t make sense to regular users. I worked with a company that had a naming scheme of “company branchstate code-county code-department code,” which resulted in print servers that were named, for instance, CPH-12-056-343. Although IT staff knew all the codes, users didn’t. The company used this naming scheme to avoid using “Print Server” in the name, which was intended as a security measure against would-be hackers. But users could never remember the servers’ names, and Help desk calls increased as a result.

There’s always a balance between security and usability, which is something planners should consider with naming schemes. The name of a computer or other hardware device won’t stop a determined hacker. For that matter, anyone on your network can easily find every server name in one fell swoop. A good naming scheme might include the printer’s physical location, attributes, and department, yielding names such as Bldg50-Room100-Color, Bldg200-HR-Confidential, or Bldg300-CustomerService. Naturally, a company that has only one building wouldn’t include the building name in the printer name but instead use something such as Room100-Color, HR-Confidential, or CustomerService.

User education is something else you should consider: Let the users know the method behind the madness of your naming convention, and they should understand it better and use it more effectively. Remember, every company has its own business objectives; one company’s naming scheme might not work at all in the business located next door. So use common sense and figure out what works best for your situation. The best way to determine if your naming scheme works is to ask some of your users—both high-end and low-end. If they can’t figure it out, you probably need to tweak it some more.

Hocus Pocus: Using the Wizard
Now let’s look at some solutions for getting users connected to printers; your users should find at least one of these methods doable. I’m using Windows XP in this article; terminology and steps might vary if you’re using a different OS.

The most common method of connecting to a printer is by using the Add Printer Wizard. You access the wizard in the Control Panel Printers & Faxes applet. While using the wizard usually isn’t a challenge for IT staff, it can be daunting for users, especially if they have no idea what a Universal Naming Convention (UNC) is, what the print server’s name is, and so forth.

Related Content:

ARTICLE TOOLS

Comments
  • iuscrim
    4 years ago
    Jun 06, 2008

    OK, ok ... didn´t read the title :-O
    But you can start the mentioned scripts in different ways, for example also via a shortcut in a shared folder :-)

  • iuscrim
    4 years ago
    Jun 06, 2008

    Actually I´m wondering why nobody is using the easiest way to connect users with network printers: (login) scripts which starts "rundll32" for connecting to all the printers in the network ...
    I am using the following login script (via GP) to connect my users with the existing printers on my print server:
    rem this one makes the connection
    rundll32 printui.dll,PrintUIEntry /in /n"\\\\SERVERI\\black-white printer"
    rem ... and this one is for connecting ALL users
    Rundll32 printui.dll,PrintUIEntry /ga /n"\\\\SERVER\\black-white printer"

    That´s it. :-)

    Best regards from a german reader,
    Christian Greiner

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.