Changing Print Server - GPP to deploy printers - Replace option not working?

[Koldov]

Due to recent 'Print Nightmare' issue I am trying to move my Print Server onto a VM.

 

I have spun up the VM and got the role installed, I've got all the printers on there ready to go.

 

Now I have got the task of finding all the GPPs with printers deployed to all the users and point them to the new server.

 

The printers are deployed by GPP (just basic shared 'name' printers) and reading up on CRUD I presumed I should use 'Replace'.

 

But, I'm not quite sure how this should work...

 

In the GPO do I open the properties of the original GPP, change it to replace and type in the new path - because I've tried this and it just creates a new printer (and it makes a lot of sense because it doesn't have the info anymore of what the old path for the object was).

 

The original GPP was CREATE:

 

\\SERVER1\PRINTER

 

So, when I change it to REPLACE:

 

\\SERVER2\PRINTER

 

It just creates \\SERVER2\PRINTER, but I still also have \\SERVER1\PRINTER

 

Because from reading this (although it doesn't explicitly state how to do it), changing it to replace should work... It seems like there should be another line that says what the original was and then what you want to replace it with!

 

https://www.itpromentor.com/gp-crud/

 

EDIT: UPDATE also just creates a new printer...

Edited July 13, 2021 by Koldov

[Cache]

Yeah, what you need to do is either have a Delete all or a delete for each of your printers that were on Server1 and an update or create for your printers on Server2.

 

The Replace command remaps the printer, so say you wanted to reapply the print defaults (handy for those who change things from black and white to colour in the print control panel) it works well, but it can't replace the server1 printer with server2 as it doesn't really know what it's replacing.

[Koldov]

Yeah, that's what I figured. Strange... from reading up on it I thought those sort of configuration changes were done by 'UPDATE' and replace was... replace...

 

One day I will read up on something and try it and it will actually be just how they've written it and it will work perfectly... one day.

 

Actually, I know it might be extra work but...

 

...to be on the safe side, is there any problem with me deploying the printers from the new server 'side by side' for a while?

 

If I just ask everyone to print from the SERVER2\PRINTER and see how that goes.

 

Then if they have any issues they can still print from SERVER1\PRINTER and just let me know...

 

By the end of next week, anyone who prints a lot will have shouted and then if no problems I can just change all the SERVER1\PRINTER GPPs to delete.

[Cache]

Are all the printer share names the same? I'm guessing so - if there server isn't doing anything else and there's no issues with mapping the printer, you could just set SERVER1 as a DNS alias of SERVER2.

 

In regards to any issues having them deployed side by side, not that I'm aware of - I've had printers deployed from multiple servers before, it's no different from having both mapped manually.