@Wayne-Workman I apologize I meant to say storage group, I figure ‘“default” storage group’ leaves enough context clues for the reader to infer that a “storage account” is a storage group.

@Sebastian-Roth thank you for the speedy response as well!

The solution to the issue was that I had to create a separate storage node to correlate to the storage group being created, and then setting the storage node to the corresponding storage group. The purpose for this was to better organize snap-ins to certain “task groups” like what is present in Norton Ghost, I hope that this helps.

@george1421

I got it working, I had to change the permissions slightly differently.

Cross linking with https://forums.fogproject.org/topic/11573/increased-network-traffic-since-1-5-0-upgrade-snapins , as a replication bug could cause the web GUI slow down.

Can you explain a bit more about how/why you are using grub?

I don’t have my flash drive with me but if I remember correctly you can chainload from grub to tftp://<fog_server_ip>/ipxe.efi to chain from grub into FOS’s iPXE menu.

This has been resolved. I updated to FreePBX 14 (CentOS 7) on the golden image and it correctly sets up the NIC’s on the imaged machines. Thanks for the help

For future readers, this article outlines how to migrate a fog server: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

Yeah I’m really surprised time has anything to do with it?? @Tom-Elliott is time involved anywhere? I know that checksums are not affected by access/modification times at all.

@imagingmaster21 said in Image Not Capturing:

The blue part clone does show up on the client and does act like it went through on the client …

What do you mean by “does act like”. Does it actually read data from the drive. I mean do you see the byte count go up at reasonable speed or does that jump as well? Sorry if this sounds stupid but I just haven’t got an idea yet. Maybe you can take a video of the client screen while this is going on. Possibly there is something that jumps at us.

@tesparza said in Snapin arguments? For EXEs:

Kurzweil 3000 v15

http://support.cambiumtech.com/index.php?pg=kb.page&id=1827#link5

I would think that’s up to the software drivers themselves. Simply doing “IP Printer” would not be sufficient. For this I’d recommend installing the printer fully (via IP_port as possible) and seeing that the driver is likely not pre-installed on all the machines, I’m not sure that you’ll be able to regain the functionality (Maybe if you inject the driver before imaging?). Once you’ve installed the printer and can validate it has printing and scanning capabilities download the PrinterManagerHelper.exe

This should give the exact config you would use for configuring your printer in fog.

@tom-elliott It does, this was incredibly helpful thank you.

@salted_cashews said in Is a direct upgrade possible in this scenario while retaining all previous configurations and images?:

To be honest, I’m not 100% sure how our guy knew that was causing a problem.

People with even some Linux experience normally check free space as a first-step in troubleshooting. Glad you got it figured out.

@adrien17 I sent you a chat message earlier with some further debugging information. You should be able to see it in the little chat button next to your profile picture on the top navbar.

@sebastian-roth
The dhcp-10-8-34-106 is what Debian auto set as my host name when it auto-configured on my Internets dhcp when i installed Debian.

As for the stated fix below i got to the "Configuring dhcp… " in the last step of fog install and then it says Failed! and sends me back to the command line.

I am going to attempt a fresh install and see if it does it still… It no longer gives me a No address or No DNS it just gets past that step then says failed when configuring the dhcp.

I had a similar issue, but (dumb) lucked into a solution.

Dell Optiplex 3040, BIOS set for UEFI: Onboard NIC (IPv4) first, Windows Boot Manager second.

Installed Win10 Enterprise from USB. After the install and first time on the desktop, before installing anything else, a reboot would come out of the UEFI network boot with Preparing for Automatic Repair. (I gave it plenty of time — about 14 hours! — never got past that screen.) I installed again and got the same results.

I made one change in the BIOS: added a check to ‘Enable Attempt Legacy Boot’ and then installed again. This time, at the first reboot, the screen went dark and … nothing. Manually powered off and back on and was able to log into Windows. But the next reboot, again the screen went dark and stayed that way. So I removed the check from ‘Enable Attempt Legacy Boot’ and now Win10 is working fine, normal reboots, exiting from the UEFI network boot into Windows.

Hope that might be helpful to someone.

@sebastian-roth I forgot to mention, since I only saw it once, but on one of the startups with REFIND_EFI selected and before changing “scan_delay” to 0 the computer attempted to boot into “automatic repair” mode but froze on the screen. After rebooting the PC I wasn’t able to reproduce that.

@Tom-Elliott, I imagine the situation is “you’re damned if you do and damned if you don’t”. It will fix some and break others. However, having the option in the GUI would be useful.

We figured out the problem and got it running properly now thanks though.

@tom-elliott Hi Tom, sorry for the late answer, yes that sql statement solved my issue. Solved!

UPDATE globalSettings
SET settingCategory=‘FOG Boot Settings’
WHERE settingKey
IN (‘FOG_ADVANCED_MENU_LOGIN’,‘FOG_EFI_BOOT_EXIT_TYPE’,‘FOG_PXE_MENU_TIMEOUT’,‘FOG_PXE_MENU_HIDDEN’,‘FOG_PXE_ADVANCED’,‘FOG_KEY_SEQUENCE’,‘FOG_NO_MENU’,‘FOG_BOOT_EXIT_TYPE’,‘FOG_PXE_HIDDENMENU_TIMEOUT’,‘FOG_IPXE_MAIN_COLOURS’,‘FOG_IPXE_MAIN_CPAIRS’,‘FOG_IPXE_MAIN_FALLBACK_CPAIRS’,‘FOG_IPXE_VALID_HOST_COLOURS’,‘FOG_IPXE_INVALID_HOST_COLOURS’,‘FOG_IPXE_HOST_CPAIRS’,‘FOG_IPXE_BG_FILE’);

@george1421 helped out with sorting the command 😉

@culture20 FWIW, The developers put this document together a while ago. https://forums.fogproject.org/topic/6162/firewall-configuration

There is also guidance on selinux: https://forums.fogproject.org/topic/6154/selinux-policy

I have not heard of any issues having ipv6 enabled with FOG.

@brendojohnso The message is clear, the file system is not safe to mount. Look over this article and you should be able to fix it: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit