Deploying printers in SBS 2003 was pretty sweet: Add the printer in the SBS Console, and the SBS setup script would take care of installing it on the client when the user logged in.
SBS 2008 does not use this feature anymore.
With SBS 2008, we need to deploy the printers via Group Policy. But, not too worry, it is actually not that painful at all with the new Windows Server 2008 print management capabilities.
Essentially, you setup your printer on SBS, then use the Print Management Console to deploy the printer via GP.
We create a Default Printer Deployment Policy object at the Computers OU level so that both workstations and servers would inherit the printer deployment. We deploy per-computer unless there is a need to deploy per-user.
For Windows Vista, the GP deployed printer shows up and is available as soon as the Vista workstation refreshes its Group Policy settings, or via a GPUpdate /force command in the Run box or Search box.
For Windows XP Professional, you will need to tweak that GPO:
* Client computers running Windows 2000, Windows XP, or Windows Server 2003 must use the PushPrinterConnections.exe
The above is from the SBS 2008 Help file.
A sample finished GPO:
Main Topics
Browse All Topics





by: d0n7_5h007Posted on 2009-08-21 at 05:08:34ID: 25150916
I've used login scripts with KIXtart to map printers depending on the security group. You can assign a log on script in GPO also. Is that not an option for you?