I posted my problem in another thread and was asked to post in a specific thread, so here it is.
After the help of the forum and lots of tests at end i’ve been able to deploy printers through FOG.
In the documentation you should really mention the program PrinterManagerHelper.exe that can be very useful to sort problems. This program can also add a new printer the same way that the client, so it’s much faster to check if your parameters work.
One mistake in my setup was a wrong name in the UNC path to the inf file. It helped to check with
psexec -s -i cmd.exe if the path was accessible.
Some doubts/problems I still have after double checking everything.
If the drivers of the printer are not installed in the host, the installation fails even if the right driver was in the specified path.
After that the client thinks that the printer is already configured.
It’s not clear what the name of the printer has to be. In the docs states that should be contained in the .inf file, but the name that is shown in PrinterManagerHelper is not there, so the best option is use this program to check the name of the printer after installing it manually.
If there’s some mistake in the name of the printer or the driver, the IP port is created, and there’s no error in the client log, but the printer does not appear. Don’t know if an error message could be added.
When you add or remove a printer in the Web UI you have to go to the host list and select the host to see the changes reflected.
When the printers are removed, it only removes the spool queues. But the first printer added still remains. That’s nothing really important and perhaps is just an issue of the HP universal PCL driver.
Thanks for your support!!