@george1421
Hi George!
I wanted to circle back and let you know that all is working now thanks to your help.

I have some other questions but I will open new tickets for those.
This crisis is complete and working now. I was able to boot one of the tablets
and gather an image off of it.

Thank you soooo much for the help.

Chris

@sebastian-roth

Once I setup a bridged virtual network adapter for the vm within the
KVM Virtual Machine Details, I was able to make everything communicate.

Issue Resolved.

@sebastian-roth said in Fog for Dev - Save each capture in its own folder automatically.:

No, this is not something FOG does out of the box. While I can see the use case for this it’s kind of rare as most users would not have enough space for a history of the image.
I am not saying it’s impossible to add this feature to FOG but it’s not on our list (which is long and the dev team quite small). So if you are really keen you can dive into this topic and work on it.

Totally get it. Limited Dev team here as well but we are all over the place.
How do I launch rsync myself with the parameters after FOG captures the device image?

Capture done, rsync Tuesdays capture to Tuesdays folder that lives… here.

Only thing I can see being an issue is making sure you have the DriverStore for the larger laptop
saved off of it before you put the tiny image on it. Device manager will go nuts when it can’t find the updated drivers for the larger laptop. Do not blow them away before you image or you will have to waste time download them again.

Windows activation after resolving all the driver issues will be the next.
Make sure you expand the Large laptop hard drive to its max size.

Once you have a good working Large, capture it as you Large master image.

@george1421

This feature can be added to FOG, but it will not be used internally for anything. Do you have something external that can consume these md5sum files that are generated during imaging? I’m just questioning the value of adding this feature.

I am sharing captured images from clone zilla to off site dev teams all over the globe
where their internet is questionable at times. The MD5sums make sure they have a good
file. Moving away from CZ to fog.

Ok… so If not md5, I want to replicate my image repository at a remote site(s),
how do I have FOG push the images from default to remote site repository/file share?

Right now there is too many manual steps for all the image handling going on.
Wanting to use FOG to automate all this for me.

I have FOG running in a Development environment.
Running scheduled jobs is working. But…

Is there a way I can schedule a capture job for the same device and have each
capture of that device go in their own unique sub-directory automatically so that I have an audit trail for that device? I don’t want the capture to overwrite the previous build.

If Thursdays dev build of the device is garbage, I can image with Tuesdays build that was automatically captured the same week. Snapshots in a way but full drive captures.

Chris

@sebastian-roth

Once I setup a bridged virtual network adapter for the vm within the
KVM Virtual Machine Details, I was able to make everything communicate.

Issue Resolved.

@george1421 I’m using:

Your version of FOG is up to date.
You’re running the latest stable version: 1.5.9

What was the final solution for this?

Thanks

Chris

and if I wanted the FOG client to kick off a .BAT file before it reboots and captures the image, where do I configure that?

CZ/Partclone combo will allow an MD5 file to be created after image capture. Expert Mode.

Can I automatically generate an MD5 file and place it in the captured directory when capturing an image with FOG?

Thanks

The setup and proof of concept is working great in Virtual Box at my desk.
Its not a speed daemon, but works for testing. Time to step it up for larger scale use.

I converted the Fog Virtual Box VMDK file I created over to a QCOW2 file
for use in KVM. Loaded the vm into KVM and the VM is running BUT…

KVM wants to open and run the Fog VM in the 192. scope instead of bridged and run in
10. IP addressing scope.

How do I configure KVM to stop running the Fog VM in the 192. scope and grab or manually assign an IP in the 10. scope?

Chris

@george1421
I am already having to do a bunch of manual tasks with the CZ solution and image files.
Unleash the automated robots! That’s what computers are for! lol

Can I use any of this still to add CZ to the Pxe Menu or is there a new set of docs someplace for this?
https://forums.fogproject.org/topic/9606/trying-to-add-clonezilla-to-pxe-menu

Thanks

Chris