Categories

• Announcements

  Get the latest news on what's happening.
  166
  Topics
  688
  Posts

  

  @jburleson Yes both firefox and chrome uses the windows cert store as Tom posted. I know because we had to do this with our vCenter servers. You need to take the public root certificate of the self signed certificate and import it into the machine’s trusted root certificate store. Once you do that then there is no warnings in any of the three browsers. While these instructions are specific to vCenter the process would be the same for any self signed root certificate. https://tinkertry.com/how-to-get-rid-of-vsphere-browser-certificate-warnings-in-windows
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  1883
  Topics
  15247
  Posts

  P

  I didn’t update kernel. it still working for me. Thanks,
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  8899
  Topics
  87436
  Posts

  L

  Hello! I just updated my version of FOG from 1.5 to 1.5.6. My previously working AD Join no longer works. In an attempt to fix it, I went in and re-set my password in the Active Directory Defaults area. (My password has not changed recently, but I thought maybe something went wrong during the upgrade and it needed to be re-entered.) Prior to this, any time I changed my password here, it would auto-encrypt the password I put in, so that if you clicked the view button, my password was not view-able but now, it just leaves my password as password. I checked the log on the client machine and the hostname changer has “Unknown return code 1909” in it. I then tried upgrading to 1.5.6.2, but that didn’t fix my issue. I’ve also noticed that all of my images now belong to fogproject instead of fog on the server. Is this normal? Anyone have any thoughts?
• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  1999
  Topics
  19013
  Posts

  

  @Sebastian-Roth said in Failed to Set Disk GUID (sgdisk -U) (restoreUUIDinformation): I just booted a client into FOS and see that we still have 4.7 MB of free space Didn’t we update this initfs to 256MB with this change to the build root config file? If I remember correctly the fog default was 100MB. BR2_TARGET_ROOTFS_EXT2_SIZE="256M" I’ll have to boot my last initrd file to see the free space, but 4MB sounds small. I might understand if its tempfs that is out of space. I think I remember that defaults to 4MB. That might be the space we are having issues with.