GPP Shared Printer Conundrum

[ITchick]

Hello! We are starting to deploy printers via GPP using the Shared Printers option. This option is uber easy but we are facing an issue with default printers. Here's the scenario:
We have setup all the printers using the 'replace' option and using the OU for targeting. We used replace so that we could take advantage of 'remove after no longer applied' this gives us a clean printer environment and we like that. However, now that we have it setup we have stumbled upon an issue with default printers. When the user chooses a default printer and reboots the default printer reverts back to the first printer applied (according to order of GPP). I realize this can be corrected by using the 'update' option but then we lose the tidiness of 'remove after no longer applied' . If we try to use the built in default printer option we then run into an issue that printer A & B are installed in two areas(two OU's), but one area wants printer A to be default and area 2 wants printer B to be default. The other thought is multiple printer objects, but then we have to track which area(OU) wants which printer to be default and maintain this somehow, not to mention more GPPs to process. The other option is to find a way to do the cleanup that the 'replace' option gives us that would be managed. For instance, if a PC is moved from one OU to another we would want the previously connected shared printers to be deleted and only the new ones applied.
Any thoughts on this? I cannot find a way to turn off the automatic default printer being set by the order of GPP when using replace. And I am not coming up with another managed solution for this issue.
Thanks in advance.

[kshields]

Hi. What did you end up doing to resolve this?

[rutger]

Hi,

We have same issue. If I only use option 'replace', the printers are deleted and recreated, and the standard printer stays the same, it is untouched. If I use the option 'remove if no longer applied', the printers are deleted, recreated and unconvinently the standard printer-hat goes to the printer that's first created bij the group policy preference.

Hopefully someone knows why there is this difference between plain 'replace' and the 'special' replace (in case you use 'remove if no longer applied').

[ramclain]

This is a problem here as well. I also preferred the 'remove if no longer applied' option as computers move around frequently. However, I push many printers for an OU, but individual users choose their own default. Using this method wipes their default, even if I don't specify one. I have resorted to the upgrade method. This way, the users keep their default, but I loose printer clean-up when a pc moves.