Categories

• Announcements

  Get the latest news on what's happening.
  176
  Topics
  735
  Posts

  O

  @UWPVIOLATOR

  Yes here -> https://github.com/FOGProject/fogproject/compare/1.5.8...1.5.9

• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  2112
  Topics
  16924
  Posts

  B

  @sebastian-roth @JJ-Fullmer Thanks for your help, for unknonwn reason the file was deleted well i put it a third time and its work perfectly, i capture a 500Gb HDD disk and deploy in 120Gb SSD.

  d1.partitions

  fog@fog:/images/Salle-Technologie$ cat d1.partitions label: gpt label-id: 79FE4766-EDD2-4DD0-826C-6DD816A2E7C6 device: /dev/sda unit: sectors first-lba: 34 last-lba: 976773134 sector-size: 512 /dev/sda1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=5217DE87-4A45-4AC4-A4DD-0C8EB1C5CF5B, name="EFI system partition", attrs="GUID:63" /dev/sda2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=15C5E73F-7855-4DA4-A464-4694B0E56628, name="Microsoft reserved partition", attrs="GUID:63" /dev/sda3 : start= 239616, size= 975486976, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=E130C384-3F46-4D8F-AD25-B85FDB0127CD, name="Basic data partition" /dev/sda4 : start= 975726592, size= 1046528, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=D3FA37D6-10A7-4303-976C-6D8F23C4258F, name="attrs=\x22RequiredPartition GUID:63", attrs="RequiredPartition GUID:63"

  d1.minimum.partitions

  fog@fog:/images/Salle-Technologie$ cat d1.minimum.partitions label: gpt label-id: 79FE4766-EDD2-4DD0-826C-6DD816A2E7C6 device: /dev/sda unit: sectors first-lba: 34 last-lba: 976773134 sector-size: 512 /dev/sda1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=5217DE87-4A45-4AC4-A4DD-0C8EB1C5CF5B, name="EFI system partition", attrs="GUID:63" /dev/sda2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=15C5E73F-7855-4DA4-A464-4694B0E56628, name="Microsoft reserved partition", attrs="GUID:63" /dev/sda3 : start= 239616, size= 72336566, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=E130C384-3F46-4D8F-AD25-B85FDB0127CD, name="Basic data partition" /dev/sda4 : start= 72577024, size= 1046528, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=D3FA37D6-10A7-4303-976C-6D8F23C4258F, name="attrs=\x22RequiredPartition GUID:63", attrs="RequiredPartition GUID:63"```
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  10250
  Topics
  100927
  Posts

  

  @joyboy11111 Since you are using Centos 6, that is Sys-V compliant OS so that would be service dhcpd restart or service dhcp restart. Or just reboot your server.

  Almost all modern Linux OS use systemd commands, which is what I gave you previously.

• Developers

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

  General

  Feature Request

  Bug Reports
  2154
  Topics
  20090
  Posts

  G

  Re: Associate all new hosts with Snapin

  I read through the linked thread above, and it seems there may be a known issue with settings applied to a host via the use of the persistent group plugin are not actually deployed when imaging.

  I’ve set up the plugin and my templates. Assigned a snap in and image - When registering a host it picks up the correct image and deploys, Snapins however are not. I cannot see any events under snapin history for the new host either

  Is this something unavoidable? I can manually task snapins to be deployed via the group after imaging, but ideally snapins would be deployed as part of the imaging process