Printer link to LinkPrintserver

[cotec]

Hi,

i tried to link a client to print-server with FOG-Client.
Installed a Windows Server 2012R2 with Printermanagement, setup a simple Printer (shared -> \server\printer1)

In FOG-GUI -> Printer Managment -> Create new Printer -> Network-Printer -> inserted Path to Printer “\server\printer1”
Added Printer to Host, and Host-LOG means:

FOG::PrinterManager Failed: it looks like the local printer is missing.

Fog-Client should create this printer so why the printer missing, so this error is not very helpful… or iam wrong? ó.Ò
Have searched in wiki (https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Group_Printers), but the videotutorial is down or wrong linked… =/

Regards,
confused cotec

[george1421]

While I haven’t deployed printers using FOG. I did notice that your UNC path is not correct. This may be just a type-o but it appears twice in your post (“\server\printer1”). A correct unc path should start with a double backslash so the target system knows its not local

i.e.

\\server\printer1

[Tom Elliott]

I think the forums are escaping the first \ in the case double slashes.

Your approach to display:

\\server\printer1

is correct.

THis is how it shows with double slashes but not in code statement:

\server\printer1

Another way to display it within the text without code would be to escape both slashes with a slash essentially making it as:

\\server\printer1

and in code statement it’s read as:

\\\\server\printer1

[george1421]

@Tom-Elliott One might think if you had to escape the first double slash you would have to do it for all like such:

\\\\server\\printer1

Sometimes you see things like this escaped in the registry but its not very common now on the windows side.

[cotec]

any suggestions to my problem?
yes i have postet with double backslashes

[Sebastian Roth]

@cotec @Tom-Elliott Any solution to this?

[Sebastian Roth]

@cotec I am pretty sure this issue was solved: https://forums.fogproject.org/topic/5990/printer-issues-continue

Please make sure you update to the latest version (FOG and FOG client) and try again.