Topics created by imagingmaster21

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

@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.

@wayne-workman Running that command fixed the issue.

@imagingmaster21 Then follow George’s guide.

@imagingmaster21 said in Renaming Images:

Also any best practices with this?

Best practices is to name it right the first time 😉
You can change the name in the GUI no problem, but don’t mess with the path unless you actually change the path on the disk too.

@quazz
Thanks that fixed the issue!

@sebastian-roth we had an extensive IM chat session. The OP found where the issue was and identified the need for snponly.efi for a specific hardware configuration. I had him start with the examples from the fog wiki and work from there. Where we left it was he was going to see if he could collect the system uuid to see if we could write a better dhcp filter to only send i386-efi/snponly.efi for that specific model and send ipxe.efi for the remainder of the arch 0007 hardware types.

@imagingmaster21 I need model numbers.

@george1421

yes!

Well I can see from the message, you are trying to boot a uefi system. What exactly do you have configured for dhcp option 67? If its undionly.kpxe then that is your issue. You need to send a uefi boot loader like ipxe.efi.

@sebastian-roth
Thanks that worked for it!

@tom-elliott said in Joining to Domain:

First, disconnect the domain.
Second, install FOG Client.
Third, configure the host/s with the AD Joining Information in the GUI.

Only needed if sysprepping.

Fourth, disable the auto startup of the client.
Fifth, sysprep the machine with shutdown

Done sysprep.

Sixth, create capture task.
Seventh, restart/power on machine.

If doing SysPrep, don’t forget to add something to your SetupComplete.cmd to turn the FOG client back on!

@imagingmaster21 That is probably a bit overkill for the FOG server. But as they say more is always better.

Just make sure you order it with an array controller that is compatible with linux. The cheap windows only raid controllers (SXXX series adapters) won’t work with linux, so don’t even try if you are installing linux on bare metal.

@george1421
I got it fixed, seems to be working.

@quazz
No I did not, I just thought of that yesterday and was able to get it working fine now. I just now have to try out making the image with removing Edge and the Windows 10 Apps with PS Scripts.