Greetings -
I've pushed out a zillion different printers using GPOs and Windows Server 2003 R2's pushprinterconnections.exe. The way I've traditionally done it is just list pushprinterconnections.exe as a script to run in the same GPO that the printer is configured in. (I hope that makes sense) That works great.
But from an optimization standpoint, that file gets run several times on some workstations. Putting multiple printers in one GPO really isn't feasible because of the complexities of coming up with every possible combination.
Curious as to how some of you are doing it. I thought about just calling it at the tail of the user login script, or just tossing it into a GPO by itself. But I'm open to other ideas.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
I've pushed out a zillion different printers using GPOs and Windows Server 2003 R2's pushprinterconnections.exe. The way I've traditionally done it is just list pushprinterconnections.exe as a script to run in the same GPO that the printer is configured in. (I hope that makes sense) That works great.
But from an optimization standpoint, that file gets run several times on some workstations. Putting multiple printers in one GPO really isn't feasible because of the complexities of coming up with every possible combination.
Curious as to how some of you are doing it. I thought about just calling it at the tail of the user login script, or just tossing it into a GPO by itself. But I'm open to other ideas.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -