FOG Client 0.11.1 - Printer Manager error
-
@Raymond-Bell Is this good or bad?
-
@Tom-Elliott VERY BAD!!!
Dont need all printers in the whole district on every computer in the district
It added them to the Host Printer Configuration
-
@Raymond-Bell what version are you running?
-
@Tom-Elliott FYI i just went back to SVN Revision: 5742 and now change
-
@Raymond-Bell that’s because all prints got associated accidental from a separate revision.
-
@Tom-Elliott said in FOG Client 0.11.1 - Printer Manager error:
@Raymond-Bell that’s because all prints got associated accidental from a separate revision.
So i going to have to go back and redo all printer associations ???For all 800 host
-
@Raymond-Bell Yes, but not totally.
Update your server again please.
Then hit me on chat, and i can try helping remotely please.
-
@Tom-Elliott said in FOG Client 0.11.1 - Printer Manager error:
@Raymond-Bell Yes, but not totally.
Update your server again please.
Then hit me on chat, and i can try helping remotely please.
OK will do
-
@Tom-Elliott Join.me sent
-
For others that may have this issue restore DB from back before today and update trunk…
@Tom-Elliott Remoted in and restored database from earlier revision… To fix the adding all printers issue. -
It was an unfortunately thing that caused the “massive” printer issue.
@Wayne-Workman When you can, please check your layout too. Make sure you update again and let us know please.
Your issue is likely totally separate, and may require using the debugger.
-
I don’t have any printers deployed through fog yet.
-
Doesn’t matter. I need to see what’s happening (and why). Even if you don’t have any printers.
-
Ok. I’ll update tomorrow.
-
Last night Joe and I found a potential issue with the client in regards to the fog client having “bad” data and we patched it. With any luck, bad cycle data should no longer happen and this should be automatically fixed if it was a problem due to the bad cycle data.