Subcategories

• General

  General Developer questions relating to FOG.
  350
  Topics
  5124
  Posts

  

  @quazz I already got it working on the working-1.6 repository. I started working to limit the amount of error messages too, though that’s going to be a project in and of itself.

  For dev-branch:

  https://github.com/FOGProject/fogproject/blob/dev-branch/packages/web/lib/db/databasemanager.class.php#L47

  Change the implode($noDBpattern, "|") to implode("|", $noDBpattern)

  That should fix the issue as it seems PHP 8 standardized their usage of implode/explode for ease.

• Feature Request

  Request a new feature to be implemented.
  603
  Topics
  3941
  Posts

  

  @jj-fullmer I haven’t done a full thorough fog windows 11 test. But it seems that some of the cpu and bios security “requirements” aren’t hard requirements. As long as your cpu supports TPM 1.2 you can do a clean install of windows 11, you just can’t in place upgrade (without a registry change).

  I am also posting this on a computer with windows 11 on it, with an i7-6700. I didn’t use fog, and secure boot got enabled by the windows 11 installer (it might have already been enabled, I didn’t double check sadly). However I just disabled secure boot and could still boot.

  So the concerns about a secure boot requirement may be unfounded. This is my home computer and I don’t have a fog server at home, but I’ll come back here once I get a chance to test creating and deploying a windows 11 image to see if there are any issues with secure boot. If anyone wants to test this out @testers before I get some time, you can download a windows 11 iso here https://www.microsoft.com/en-us/software-download/windows11?ranMID=24542&ranEAID=0JlRymcP1YU&ranSiteID=0JlRymcP1YU-aILwA1rXpThxrraz01AUgg&epi=0JlRymcP1YU-aILwA1rXpThxrraz01AUgg&irgwc=1&irclickid=_2cqgd3xf9kkf6xflm1yfj9km9e2xoz2ov3bwz2yp00

• Bug Reports

  Report a bug with FOG.
  1243
  Topics
  11395
  Posts

  T

  Finally I found where the problem came from !

  We are using a NAS Synology to share the printers drivers. It’s a share accessible without password (guest account enable on the NAS). We’ve got no access problem to this share at anytime.
  This NAS is joined to the domain… And here is the problem !

  As soos as we unjoined the NAS from the domain, FOG printers are pushed without problem.

  I don’t know why but if you execute printui command as local system account when the drivers files are shared on a NAS member of a domain, there is an access error. If you try the same command as local Administrator, it works…

  So unjoining the NAS from the domain was the solution.