@sebastian-roth
You’re probably right in terms of the value for $129, considering what Casper Secure Drive offers is so unique. BTW, you’re right that the files are accessible in a Bitlocker drive, but when I open Bitlocker management in Windows, there’s an option for Bitlocker to be in a locked (active bitlocker) or unlocked (bitlocker turned off, but the disc is not decrypted). I.e., I’ve got a Bitlocker drive that’s encrypted, but when in Windows I have the option for Bitlocker management to have Bitlocker turned on or off (locked vs unlocked), even though the drive itself remains encrypted. Bottom line, no other software will do a proper clone of an encrypted drive when the Bitlocker management has it in a locked, active state, thereby producing a cloned and encrypted drive. Again, though, I couldn’t test its resizing function because it’s only the trial version. I also didn’t test that it works with PGP encryption (Opal 2.0), although it’s supposed to. I have communicated with the developers, and they are very prompt to respond, so my guess is that any problems will be addressed pretty quickly with this software. Any idea how something this unique is so “under the radar”? I never see it mentioned in reviews.

@BiologyBen Ok, I’ll mark this solved then. Please open a fresh post for when you tackle the update and run into an issue.

@natefog There was a recent thread on that topic… Read through this thread: https://forums.fogproject.org/topic/10712/upgrade-to-debian-9

@tonytonyistony Any news on this one?

@george1421 After a lengthy IM session we discovered that their dhcp server wasn’t sending out the boot-file and next-server values properly in the ethernet header. There were dhcp options 66 and 67 being set. This particular pxe booting client was only looking at the etherent header for the boot server info. Once the OP updated his dhcp server the target computer booted correctly into the FOG iPXE menu.

@plegrand Thanks for reporting back on this. Marked as solved.

[Moderators note] Duplicate post to here: https://forums.fogproject.org/topic/10700/issues-after-kernel-update

The problem is your Windows DHCP server is already handing out Boot info.

Your client sees this info and tries to boot from it immediatly.

ProxyDHCP can only step in and help out if the Network boot info isn’t passed on yet.

For ubuntu/kubuntu by @kmstory https://forums.fogproject.org/topic/10403/boot-iso-from-ipxe-menu/5 Note that you will need to place the ubuntu extracted images in /images/ubuntu on the fog server to access them via nfs. If you are using fog 1.3.0+ you can use the built in functions to build the ipxe boot menu.

kernel nfs://${next-server}/images/xubuntu/casper/vmlinuz.efi initrd nfs://${next-server}/images/xubuntu/casper/initrd.lz imgargs vmlinuz.efi acpi=off root=/dev/nfs boot=casper netboot=nfs nfsroot=${next-server}:/images/xubuntu locale=en_US.UTF-8 keyboard-configuration/layoutcode=us mirror/country=US boot

@EAHarvey Shall we mark this solved or are you still looking into getting FOG setup within Drobo?

@Benjamin_D Is this solved?

its okay thanks for your help

0_1500471038531_091f047d-6905-4f8b-81ae-16f6e29ee5ec-image.png

Thank you.

@ewilk2600 You have to do it from terminal on the Ubuntu Server.

Your database will update to the newer format automatically (you just have to navigate to the FOG management URL when it asks you to and click upgrade), but it will make a backup first, just in case.

@sudburr I’m not sure what is going on or what you’re trying to do - but virt-manager typically only connects to hosting systems via SSH, not the guests. Virt-Manager provides direct console access to guests, but SSH to the guest is not involved in this, it’s via ssh to the host.

@sudburr The reboot isn’t necessary, but otherwise great job on the post below - it’ll help many folks in the future.

I’m using mostly ubuntu and all my images are set to “single disk, resizable” .

the order you should go in short:

on the desktop pc:
setup the desktop you want to clone
enable pxe boot in the bios of your desktop pc

on the fog server (gui):
create new image (single disk, resizable) (image management)
register host pc with the server(there are multiple ways to to that, check the wiki 🙂 )
assign your created image with the entry of the desktop pc (select host image in host management)
click on capture image at the entry of your desktop pc
if you don’t run the fog client on the desktop pc, you should reboot your pc so it does the magic 🙂

deploy a image:
is mostly the same as above: create new host, assign image, click on deploy.

you should also look for the “fog client” - running it on the desktop pc is very usefull! 🙂

I hope I did not forget anything. 😉

Thank you for the response.

I ended up going back and comparing the file to another one I downloaded on another computer, and they were different sizes. Moved the new one in and it was able to mount fine.

@notaspy If you force this system to fail, then boot the fog server up.

Run the following commands.

ps aux | grep dhcp this should show you if the dhcp server is running in memory. netstat -an| grep 67 this should show you that the dhcp server is listening on its data port. You should see something like this udp 0 0 0.0.0.0:67 0.0.0.0:*

Lets start with those. That will give us an idea if the dhcp-server is running and / or listening.

Edit: It looks like ubuntu 16.04+ is based on systemd so these commands will be useful. Don’t use them until we can understand what’s going on here.

sudo systemctl restart isc-dhcp-server sudo systemctl status isc-dhcp-server sudo systemctl enable isc-dhcp-server

@VijayBomble This thread is extremely old and I have no idea what your particular problem is. based on the message of “on this switch it works, but that one it doesn’t” leads me to think a configuration issue on the switch that’s not working. There’s not anything that I can do to figure out what the problem is.