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
  15248
  Posts

  

  GParted 0.33.0 x86 First we’ll create the required directories: mkdir -p /tftpboot/gparted mkdir -p /tmp/gparted Download the gparted zip file from sourceforge site and save it to the /tmp/gparted directory Change to the /tmp/gparted directory and expand the zip file. Then change into the live directory and finally copy the required files to the tftpboot/gparted directory cd /tmp/gparted unzip gparted-live-0.33.0-2-i686.zip cd live cp {vmlinuz,initrd.img,filesystem.squashfs} /tftpboot/gparted In the fog WebGUI go to FOG Configuration->iPXE New Menu Entry Set the following fields Menu Item: os.GParted Description: GParted 0.33.0 Parameters: kernel tftp://${fog-ip}/gparted/vmlinuz initrd tftp://${fog-ip}/gparted/initrd.img imgargs vmlinuz initrd=initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=tftp://${fog-ip}/gparted/filesystem.squashfs boot || goto MENU Menu Show with: All Hosts 5. That’s it, just pxe boot your target system and pick GParted 0.33.0 from the FOG iPXE boot menu. References: https://gparted.org/livepxe.php
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  8904
  Topics
  87523
  Posts

  J

  @Wayne-Workman said in Error after sysprep and capture (FOG related): @jemerson93 Read the sysprep section here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep Hi Wayne, I have FOG Service disabled in the golden image and all of the individual images afterwards. I have the service set to start on first login on a custom script we have run to do various tasks (delete sysprep folder, change power settings, start fog, etc) The issue is that my unattend script and capture works fine on Windows 10 1809. It’s specifically 1903 that is causing this issue and I can’t seem to pinpoint why. It has something to do with FOG capturing the image (as I mentioned if I sysprep and then boot, it’s fine) It isn’t the service starting to early though. Any other ideas?
• Developers

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

  General

  Feature Request

  Bug Reports
  2001
  Topics
  19022
  Posts

  S

  @EduardoTSeoane Good point. We’ll look into this.