Unable to set default printer

[joshuaparker]

Updated to 7202, removed all printers from the test machine. Fog added the printers but still does not set the default.

[joshuaparker]

0_1461016486872_fog_user.log

[Joe Schmitt]

I remoted into @joshuaparker 's system and found the issue. Its a bug with the v0.9.12’s ability to match network printers to WMI objects (basically, the client couldn’t link the printer name to the actual printer on the computer). The next version of the client will fix this.

[Joe Schmitt]

@joshuaparker v0.10 fixes this issue, when it is released can you confirm?

[Tom Elliott]

Bump? I think this is fixed as well, but a confirmation would be extremely useful please.

[joshuaparker]

Sorry for the delay, updated to 7462 today and when attempting to update client on test machine i get an unable to install CA certificate error.

[Joe Schmitt]

@joshuaparker If you update, v0.10.5 should fix this issue. Windows XP support was added to ensure maximum compatibility on all Windows installations.

[joshuaparker]

@Jbob Updated to v0.10.5, install worked fine. Client now sets default printer but it is not the correct printer.

[Joe Schmitt]

@joshuaparker Well that’s progress I suppose. Can you paste the content of C:\Program Files (x86)\FOG\settings.json here (feel free to strip our your server address if you feel the need to).

[joshuaparker]

@Jbob
{
“HTTPS”: “0”,
“Tray”: “1”,
“Server”: “10.12.47.50”,
“WebRoot”: “/fog”,
“Version”: “0.10.5”,
“Company”: “FOG”,
“RootLog”: “1”,
“server-version”: “7470”,
“alo-time”: “”\\wiwa207t\WI Accounts Payable"",
“gracePeriod”: “60”,
“Sleep”: “126”
}

[Joe Schmitt]

@joshuaparker Bug confirmed and patched. You’ll need to wait for the next client release to receive the fix.

[Tom Elliott]

@joshuaparker Why are the printer names stored in the form "\\blah\blah" (Not the slashes but the single/double quotes)?

You can just name them properly.

[joshuaparker]

@Tom-Elliott removed all printers and recreated 4 of them. Client continues to install original 6 printers and set incorrect default.

[Tom Elliott]

@joshuaparker join.me?

[Tom Elliott]

@Jbob I know you’re busy this week and @joshuaparker is aware too.

Here’s some of my findings:
Default Printer’s do not work right now. Neither (it appears) does removing printers.
Removing will, or so it seems, remove the icon, but the printer still exists under the HKEY_CURRENT_USER->Printers->Connections
(Maybe if you remove manually the definitions don’t go away until you log off/ log back on – didn’t get to test that aspect)
I can’t tell what printer it decides to initially set as default, and in some cases the default might accidentally be set correctly. I don’t know if this is specific to network printers, or all printers, either. I was only able to test with network printers.
Updating the default printer, though, doesn’t have any affect on the host. It will cycle the printers assigned and if they exist, will just say “already exists”, but it never shows anything about specifying if it should change/update/unset default printers (Or maybe that just isn’t logged?)

Of note, 7470 was the version in question, and he’s currently using the 0.10.6-RC file you provided earlier. These findings are with that Client and version of the OS.

[Tom Elliott]

Good news, I’m an idiot and didn’t remember default printers are a user based thing. Because of this, the foguserservice wasn’t running which is why the printer (on 0.10.6) was not set.

[Tom Elliott]

More good news, the printers currently are only removed from connection list (when using network printers) after the user logs off and back on.

[Tom Elliott]

@joshuaparker Can you confirm if printers are now working after the client is rebooted?

[Joe Schmitt]

0.10.6 released, it should fix this issue.

[Sebastian Roth]

@joshuaparker Did you get to test the new client version yet? I’d love to see this confirmed fixed!