Printer issues continue

[johnomaz]

Here is a video of what I’m seeing:
https://youtu.be/I8iyfXtuFPI

When you do a search for a printer, it will show as \\\\server\\share\\file.inf but if you go to any printer details or list all printers and then sort from the list, it shows as \\server\share\file.inf. I am no longer able to deploy printers on any computer I’ve tried running Windows 7 64bit or Windows 10 64bit. I was running a build about a month old two days ago and it worked fine, but after updating to 5020, then to 5030 and now on 5044, I cannot deploy printers. I’m on Fedora 22 and SVN 5044

With the legacy client, I get this:

 10/22/2015 12:45 PM FOG::PrinterManager Printer update was request from fog tray...
 10/22/2015 12:45 PM FOG::PrinterManager Management level = 1
 10/22/2015 12:45 PM FOG::PrinterManager Adding new printers to host...
 10/22/2015 12:45 PM FOG::PrinterManager 4 found on server side.
 10/22/2015 12:45 PM FOG::PrinterManager Installation requested for E125 DesignJet 510 Win7
 10/22/2015 12:45 PM FOG::PrinterManager Printer Installed: E125 DesignJet 510 Win7
 10/22/2015 12:45 PM FOG::PrinterManager Installation requested for E125 HP OfficeJet 7100
 10/22/2015 12:45 PM FOG::PrinterManager Printer Installed: E125 HP OfficeJet 7100
 10/22/2015 12:45 PM FOG::PrinterManager Installation requested for E125 HP401n
 10/22/2015 12:45 PM FOG::PrinterManager Printer Installed: E125 HP401n
 10/22/2015 12:45 PM FOG::PrinterManager Installation requested for HP m601n - Student Printer 1
 10/22/2015 12:45 PM FOG::PrinterManager Printer Installed: HP m601n - Student Printer 1
 10/22/2015 12:45 PM FOG::PrinterManager Setting Default Printer...
 10/22/2015 12:45 PM FOG::PrinterManager Failed: it looks like the local printer is missing.

It scrolls through the printers immediately without installing them.

On client 0.9.5, I get this:

------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 10/22/2015 12:32 PM Client-Info Version: 0.9.5
 10/22/2015 12:32 PM PrinterManager Running...
 10/22/2015 12:32 PM Middleware::Communication URL: http://10.60.219.99/fog/service/servicemodule-active.php?moduleid=printermanager&mac=90:B1:1C:6A:C3:0D|&newService=1
 10/22/2015 12:32 PM Middleware::Communication Response: Success
 10/22/2015 12:32 PM Middleware::Communication URL: http://10.60.219.99/fog/service/Printers.php?mac=90:B1:1C:6A:C3:0D|&newService=1
 10/22/2015 12:32 PM Middleware::Communication Response: Success
 10/22/2015 12:32 PM PrinterManager Creating list of printers
 10/22/2015 12:32 PM PrinterManager Creating printer objects
 10/22/2015 12:32 PM Middleware::Communication URL: http://10.60.219.99/fog/service/Printers.php?id=9&mac=90:B1:1C:6A:C3:0D|&newService=1
 10/22/2015 12:32 PM Middleware::Communication Response: Success
 10/22/2015 12:32 PM PrinterManager ERROR: Object reference not set to an instance of an object.
 10/22/2015 12:32 PM Middleware::Communication URL: http://10.60.219.99/fog/service/printerlisting.php?newService=1
 10/22/2015 12:32 PM Middleware::Communication Response: Success
 10/22/2015 12:32 PM PrinterManager Adding printers
------------------------------------------------------------------------------

I have no programming experience, but it feels like its pulling the UNC path of \\\\server\\share\\file.inf when trying to load the driver, which to windows doesn’t mean anything. I understand from a recent post and your explanation that java has a difficult time reading and displaying a backslash the way its used for the UNC path, but since these printers were deploying in an older build (around 4650 or so) and not deploying on an unchanged workstation with the current that has had no issue installing the printer before, I feel something has changed with FOG for it to stop.

Crap, sorry, thought I put this in the Bug Report forum

Another user having issue here https://forums.fogproject.org/topic/5989/printer-installs-fail

Mod edited to use code boxes.

[Wayne Workman]

Moved to bug reports.

You could use a Script via snapins or a script via Group Policy to push the drivers to the computers, and then use a local path instead of using UNC paths… That would be a work around. I think the UNC Path issue needs addressed though. @Jbob ideas?

[johnomaz]

@wayne-workman I’d prefer to use the UNC path instead of a local path. I used to use a local path but kept running into issues, usually small but annoying. Plus, using the UNC path, I can manage the drivers with ease.

[Scott B]

@johnomaz said:

@wayne-workman I’d prefer to use the UNC path instead of a local path. I used to use a local path but kept running into issues, usually small but annoying. Plus, using the UNC path, I can manage the drivers with ease.

I have to 2nd using UNC if at all possible, so much nicer to manage.

On another note, I made a test printer pointing to a local path and FOG filled in the path with “\” where just “” is needed. Same thing we see on our UNC printers.

[Scott B]

@johnomaz said:

@wayne-workman I’d prefer to use the UNC path instead of a local path. I used to use a local path but kept running into issues, usually small but annoying. Plus, using the UNC path, I can manage the drivers with ease.

@Wayne-Workman said:

Moved to bug reports.

You could use a Script via snapins or a script via Group Policy to push the drivers to the computers, and then use a local path instead of using UNC paths… That would be a work around. I think the UNC Path issue needs addressed though. @Jbob ideas?

I did try pushing out a printer via FOG using a path to local driver files and I ended up with the same result as if the drivers were accessed via UNC.

[Wayne Workman]

@Scott-B said:

You could use a Script via snapins or a script via Group Policy to push the drivers to the computers, and then use a local path instead of using UNC paths… That would be a work around. I think the UNC Path issue needs addressed though. @Jbob ideas?

I did try pushing out a printer via FOG using a path to local driver files and I ended up with the same result as if the drivers were accessed via UNC.

Very strange. Are you using the new client or legacy?

[Scott B]

@Wayne-Workman said:

@Scott-B said:

You could use a Script via snapins or a script via Group Policy to push the drivers to the computers, and then use a local path instead of using UNC paths… That would be a work around. I think the UNC Path issue needs addressed though. @Jbob ideas?

I did try pushing out a printer via FOG using a path to local driver files and I ended up with the same result as if the drivers were accessed via UNC.

Very strange. Are you using the new client or legacy?

Currently legacy across the district.

[Joe Schmitt]

I believe @Tom-Elliott did some modifications to how slashes were handled recently.

[johnomaz]

I just installed the latest copy…like just this minute. I’ll be testing it on my workstation momentarily.

–

@Jbob @Tom-Elliott Just updated FOG and printers are still not deploying. The UNC path still recognizes as \\\\server\\path\\file.inf

https://dl.dropboxusercontent.com/u/114466/2.PNG

 10/26/2015 8:54 AM LocalPrinter Attempting to add printer:
 10/26/2015 8:54 AM LocalPrinter --> Name = HP m601n - Student Printer 1
 10/26/2015 8:54 AM LocalPrinter --> IP = 10.60.219.21
 10/26/2015 8:54 AM LocalPrinter --> Port = IP_10.60.219.21
 10/26/2015 8:54 AM LocalPrinter --> File = \\\\phs-campus\\Distribution\\ljm601n\\hpcm600u.inf
 10/26/2015 8:54 AM LocalPrinter --> Model = HP LaserJet 600 M601 M602 M603 PCL6
 10/26/2015 8:54 AM LocalPrinter Return code 0

Above is just one of the printer lines in fog.log to show the UNC path.

[Tom Elliott]

I’m solving this thread for now. I would love to ensure there isn’t a problem with just the legacy client so if we can get more details I can probably squish this real quick.

I’m solving this as I have remoted in with @johnomaz and we verified things were finally working as expected. There was some issues but it was purely a configuration thing, not a fog bug issue. And I will state it’s a rarity that it isn’t something I caused.

At any rate I just hope it’s working properly for everybody now.