Microsoft
Software
Hardware
Network
Question : Deploy Printer Drivers to WinXP Computers
Hi All,
I am needing to deploy a bunch of Printer Drivers to all workstations in a SBS 2003 environment so that when a User connects remotely to a workstation, they can use their Local Resource Printer via Remote Desktop Connection. Presently, if the workstation does not have the driver, a locally mapped printer object does not get created.
I can use
RUNDLL32 PRINTUI.DLL, PrintUIEntry /ia /f "\\SERVER\SHARE\PrinterDri
ver.inf" /m "Printer Model"
to install the driver, but ideally I would like to deploy this via a AD Security Group by adding a Computer to a Group. Thoughts to date are to either:
1
Create MSI and deploy MSI through Software Install of GPO
2
Add PRINTUI command to Logon Script, and let Logon Script parse group membership and apply accordingly.
3
Execute batch file for each printer (unmanaged)
Ideally I would like to store all Printer Drivers centrally on File Server and create security groups to manage deployment. When using the PRINTUI command, I noticed that even after using the /dd switch to remove driver the entry would still show in the list of Printers by Manufacturer and Model - strange ..... one would think that removing the driver would remove from the list of printers.
Ultimately I will have to be doing this for multiple printer models on multiple computers - having the control to target certain computers and not all is required.
Answer : Deploy Printer Drivers to WinXP Computers
The colour display schemes in XP are reached via the 'Personalization' and are now part of 'Themes'
Random Solutions
How do I add a domain address to my Exchange 2007 mail server?
Linq Tutorial
query to find days over 30 since event
SATA Drives within HP 6-Port SATA RAID Controller
Web site not working correctly with Mozilla, Safari...anything other than IE
strcpy : pointer targets in passing argument 1 of ‘strcpy’ differ in signedness
WIndows Server 2003
Using jquery to hide dynamically added divs
MS Exchange 2007 - Archiving Solutuions that do not use lots of overhead
Better way to print name tags from Access, anyone?