Printer Manager doesn't work

[Matthieu Jacquart]

Yes, I could try

Before fog I used to install printers on each computers, now i find printer manager very useful !

I now what to do on moday

[Joe Schmitt]

I believe I have patched the issue. When you are available for teamviewer, PM me and I’ll test it.

[Tom Elliott]

This should work for the legacy client. The new client is, well, new and not all the kinks have been worked out. Hopefully @Jbob has fixed this and we can release a new client relatively soon.

[Wayne Workman]

In addition - I’ve had problems with deploying a non-shared printer via the new client. I need a good example or three on how to do that.

[Wayne Workman]

@Jbob mentioned something about creating a helper application that will simply provide you with the information needed to deploy any printer that is currently installed on the system it is ran on.

Keep in mind that this application is not made YET, but, the way he explained it to me, it works like this:

• Install an IP printer, Shared network printer, or local printer on a machine - test to confirm it works.

• Run the helper application on that machine - this application will then report all the settings you need to enter to deploy the printer via the new FOG Client.

personally, I’m looking forward to the helper application - I’m sure that others are too.

[Matthieu Jacquart]

@Jbob Your patch works perfectly !
I replace my file in fog client installation path with yours, add a shared printer to my computer, and 1 minute after it was map

There is the log for printer manager

------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 07/09/2015 16:25 Client-Info Version: 0.9.4
 07/09/2015 16:25 PrinterManager Running...
 07/09/2015 16:25 Middleware::Communication URL: http://192.168.10.60/fog/service/servicemodule-active.php?moduleid=printermanager&mac=74:27:EA:6C:AA:0D|02:50:F2:00:00:01||00:00:00:00:00:00:00:E0&newService=1
 07/09/2015 16:25 Middleware::Communication Response: Success
 07/09/2015 16:25 Middleware::Communication URL: http://192.168.10.60/fog/service/Printers.php?mac=74:27:EA:6C:AA:0D|02:50:F2:00:00:01||00:00:00:00:00:00:00:E0&newService=1
 07/09/2015 16:25 Middleware::Communication Response: Success
 07/09/2015 16:25 PrinterManager Creating list of printers
 07/09/2015 16:25 Middleware::Response DEBUG: Parsing List...
 07/09/2015 16:25 Middleware::Response DEBUG: --> 9
 07/09/2015 16:25 PrinterManager Creating printer objects
 07/09/2015 16:25 Middleware::Communication URL: http://192.168.10.60/fog/service/Printers.php?id=9&mac=74:27:EA:6C:AA:0D|02:50:F2:00:00:01||00:00:00:00:00:00:00:E0&newService=1
 07/09/2015 16:25 Middleware::Communication Response: Success
 07/09/2015 16:25 PrinterManager DEBUG: Removing extra printers...
 07/09/2015 16:25 PrinterManager DEBUG: Stripping printer data
 07/09/2015 16:25 PrinterManager DEBUG: Stripping \\impression\s151laser1
 07/09/2015 16:25 Middleware::Communication URL: http://192.168.10.60/fog/service/printerlisting.php?newService=1
 07/09/2015 16:25 Middleware::Communication Response: Success
 07/09/2015 16:25 Middleware::Response DEBUG: Parsing List...
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s054laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s056laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s072laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s081laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s101laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s104laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s107laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s108laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s109laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s135laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s140laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s142laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s151laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s155laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s156laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s157laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s158laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s160laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s161laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s163laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s164laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s165laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s174laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s254laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s258laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s259laser1
 07/09/2015 16:25 Middleware::Response DEBUG: --> \\impression\s260laser1
 07/09/2015 16:25 PrinterManager Adding printers
 07/09/2015 16:25 NetworkPrinter Attempting to add printer:
 07/09/2015 16:25 NetworkPrinter --> Name = \\impression\s151laser1
 07/09/2015 16:25 NetworkPrinter Return code 0
 07/09/2015 16:25 NetworkPrinter Return code 0```

[Joe Schmitt]

Awesome! You’ll notice that your logs will be filled with “DEBUG” messages, this is because I gave you a debug build. These builds are incapable of being imaged without throwing constant errors (inorder to prevent debug builds from being used in production). So be sure not to use that in your images.

I’ll release v0.9.5 as soon as possible for you though.

[Matthieu Jacquart]

No problem for debug version it’s just on my pc.
Thanks a lot for your help, glad that forum is back

[midas1989]

I can 8 connect a printer under Windows .
In Windows 7, it works

fog.log

I hope you can help me

Best regards

Midas Wollinger

[Joe Schmitt]

@midas1989 Your logs indicate this is for the legacy client. Mind posting this in a new thread?