1.3.0-RC-8 Issues I have found...
-
Server
- Version: 1.3.0-RC-8 SVN Revision: 5948
- OS: Centos 7
Client
- Version: 0.11.5
- OS: Windows 10 64x
Description
On the SmartInstaller install Address is spelled wrong: Server Adress:
Also the Printer Config file does not import. I can do it manually via RUNDLL32 even with a unc path, but it doesn’t restore the settings via fogservice, no errors in the logfile. Just returns 0, Might be because the the spooler is restarted too late / too soon?!
-
Actually, What I thought was fog was this: https://social.technet.microsoft.com/Forums/en-US/030ee94a-047d-460a-bc39-52351a199364/kb3163912-breaks-point-and-print-restrictions-gpo-settings?forum=winserverGP
This “Package Aware” drivers problem was causing my headaches.
-
Pinging @Joe-Schmitt. He’ll be able to fix the typo in a jiffy, but can you elaborate further on the printer config issue?
-
Just a guess, but I think he’s referring to the printer config text field in the printer setup.
BTW, this field is not an import field. While it does seem it should do such a thing, the idea of that is just to tell the client what file to look at for configuration settings that’s within the Client’s space. So the text field is simply a place holder telling the client where to look at for the file (and what file to look at), it does not upload the file and send it with the printer passing.
-
I guess that might be a future enhancement. Printer Config File Field.
I was looking in the 11.5 client source code and seen the function calling rundll32 printui so I assumed it did copy the file down.
Ok, I also noticed that when you have group policy printers being pushed and fog managed printers selected for the host, group policy printers do not get pushed unless I add a printer in fog. It can be a dummy printer pointing to nothing in fog.
-
@PatrickG said in 1.3.0-RC-8 Issues I have found...:
Ok, I also noticed that when you have group policy printers being pushed and fog managed printers selected for the host, group policy printers do not get pushed unless I add a printer in fog. It can be a dummy printer pointing to nothing in fog.
That’s by design. FOG Managed Printers - means - Printers defined in FOG are managed by fog. And if said printer is not assigned to said computer, the client enforces this - and removes that printer from that computer if it’s present. Same thing the other way, if a printer defined in fog is assigned to said computer in fog and FOG Managed Printers is turned on for that host, the client will enforce it’s installation - doesn’t matter how many times someone deletes it, it just comes back. Same with default printers - this is enforced when FOG Managed Printers is on for said host.
-
Thanks for clearing that up.
-
@PatrickG the spelling mistake will be fixed in v0.11.6, thanks for reporting.
As for the printer config file, you say you used a network share? Make sure that share has anonymous read access.
-
I have found that for Windows Server 2012 R1 and R2, to make a share readable by the FOG Client, you need read permissions for 2 users.
ANONYMOUS_LOGONandguestin BOTH the sharing permissions and the security permissions (aka CIFS/SMB permissions and NTFS permissions). -
Actually, What I thought was fog was this: https://social.technet.microsoft.com/Forums/en-US/030ee94a-047d-460a-bc39-52351a199364/kb3163912-breaks-point-and-print-restrictions-gpo-settings?forum=winserverGP
This “Package Aware” drivers problem was causing my headaches.
