Topics created by ismith.hpu

@ismith-hpu Don’t feel like you have to but you are welcome to post here as well: https://forums.fogproject.org/topic/4382/organizations-using-fog Thanks for your post, appreciate that!

@Tom-Elliott said in Failure in Capturing an image: @ismith-hpu But the machine, indeed, does have an OS on the disk? I can only assume the -a0 is a part of the problem. I don’t know what the argument is doing for the 0.3.12 version of partclone. It’s to ensure compatibility with 0.2.89 images, allowing them to be deployed with 0.3.12. 0.2.89 had a broken checksum system, so we force it disabled on 0.3.12 in order to allow those images a normal deployment. It’s also faster and slightly smaller images, certainly not complaining about that part. It is curious that 0.3.12 doesn’t seem to work in this instance, though I wonder if a non-resizable (not raw) capture has been tried?

okay thanks for the reply

@Tom-Elliott This did resolve the issue.

Updated /var/www/html/fog/lib/fog/task.class.php getStorageGroup method to do: return new StorageGroup($this->get('storagenode')->get('storagegroupID')); This way it’s not relying on a potential return from the group that may not be assigned to the tasking. It relies on the storage node that was associated to the tasking. I will update the main codebase with this issue and fix. Thank you,

@ismith-hpu There are numerous posts on this topic in the forums! https://forums.fogproject.org/topic/12714/option-to-delete-files-when-deleting-multiple-images-snapins https://forums.fogproject.org/topic/13292/images-won-t-be-deleted-in-filesystem-when-using-the-webui-delete-option https://forums.fogproject.org/topic/13472/pb-free-space-fog-1-5-5 https://forums.fogproject.org/topic/13731/image-deletion-issue-if-mass-mode-used

@ismith-hpu To clarify, this will fix for any RAW imaging types.

@ismith-hpu said in Mac OSX renaming of Hostname & ComputerName post imaging: FOG Server CA NOT found in keystore You need to make sure you install and run the fog-client in the root context.

Solution was filename "undionly.kpxe"; next-server 10.33.97.251; VERSUS filename undionly.kpxe; next-server 10.33.97.251;