Printer deployment windows 2008 r2

Let me know what error says. One thing that constantly goofs me up is the Print Processor. Yes - be very careful with it and test first. It can be useful to clean things up before installing but be aware that you could leave users with no printers if it runs in the wrong order. It happened to me due to no time given to test first, not a major problem but should be avoided. My main point of using this feature is that we have Terminal Server with 2 accounting softwares, with which work almost users.

When every users connects via RDP, it redirects all printers from host. That;s why I thought of creating gpp for terminal server so all "secondary" vere deleted and main printers are left. There are several ways to do this, just be sure to use Item Level Targeting correctly so you don't remove everyone's printers by accident.

Maybe do a few at a time. To continue this discussion, please ask a new question. Spiceworks Help Desk.

Of course, this means that this setting also requires the Windows XP and Windows Vista systems to wait for the network to start before running this policy because the printer is deployed using Group Policy settings as well as a startup or logon script. Also it must be noted that simply removing the policy does not remove the printer.

Deploying printers with group policies can also be performed using the Print Management console, which is one of the Print Services Tools, and using this tool actually provides more functionality during printer deployment.

Because of the added functionality, the recommended deployment method for Group Policy deployed printers is to use the Print Management console. To deploy a printer to a computer using Group Policy, perform the following steps:. To support deployed printer domain policies for systems other than Windows Vista, Windows 7, Windows Server , and Windows Server R2, perform these additional steps:.

Deploying printers using GPOs to users follows mostly the same process; except when deploying the printer, the check box to deploy in the user section should be checked and instead of a computer startup script a user logon script should be defined. Deploying printers using GPOs for computers or users simplifies the installation and removal of printers but does not set the default printer if multiple printers are installed on the computer or in the user profile.

Setting the default printer should be performed by the end user, or the new Printer settings available in the User Configuration Preferences node can be used to install and set the default printer. To deploy a printer to a computer using Group Policy, perform the following steps: Log on to a designated Windows Server R2 administrative server.

In the tree pane, expand the Print Servers node to reveal domain print servers. Browse to find a print server or type the server name, click Add to List, and then click OK to return to the Print Management console. TL;DR If you get the error 0xbcb when deploying your printers follow the instructions below. The security prompts I configured as follow: When installing drivers for a new connection: Do not show warning or elevation prompt When updating drivers for an existing connection: Show warning only This week we migrated an old print server from Windows Server R2 to Windows Server Essential tools for engineers September Tags gpo , gpp , printer , system administration , system engineering , windows r2 , windows server June Printer deployment with Group Policy Preferences and error 0xbcb Tags credentials , engineering , exchange , exchange , hybrid , it , office , password , system engineering , teamscandurra , Technology , username , windows r2 , windows Follow Following.

Sign me up. Already have a WordPress. Log in now.