Yes, sure. I have to set up a machine for another one of our labs. I am going to do a capture with the “shutdown” option on, and one without it. Let’s see what happens.

Also, I am going to gather data during deployment. I have 2 more labs to deploy next week. Will post here as soon as I have it.

It turns out this is working fine - we just didn’t have the correct folder on our FOG server for the model of laptop (which the script relies on). We’ve made some adjustments to the script and can confirm this now works.
Thanks very much for the help!

@george1421

Everything is working.
Thank you very much.
How to mark that the subject is solved ?

@CRASHABBOTT I guess you went to use fog_vm_0.27 as this is the “latest” pre-build VM we have for download on sourceforge. Don’t use that. It’s from 2009 and there have been countless major changes within FOG. We don’t support those old versions anymore. As George suggested start over with a clean install of your favorite Linux system (FOG supports centos/redhat/fedora, debian/ubuntu, arch) and take it from there. Current stable FOG version is 1.4.4.

About your network. Make sure you set things up properly in bridged mode. There is no way you can make FOG work properly in NAT mode. Though it can reach out to the internet your other systems are not able to connect to your FOG server for imaging (this is kind of a security feature build into NAT!).

I updated to RC 10 and it fixed the issue.

What I said was “It is like…” it seemed “like” it couldnt tell between the different mac addresses.

@george1421

That is exactly the case. I need to further investigate.

@jdd49 The image seems to have worked now after rebooting the Hypervisor this morning, though I’m now getting the following error message when trying to boot the VM:

0_1511280177376_1.PNG

I’ve recreated the VHD on a different Hypervisor and still run into the same issue. Annoyingly (but also thankfully), the actual physical machine I’m trying to virtaulise runs perfectly fine and doesn’t have this issue.

@stepkinetic You are welcome! Marking this solved…

i try a virtual machine …

Bild Text

Please see:
https://forums.fogproject.org/topic/10768/can-t-add-location-under-location-managment/2

@sebastian-roth: yes, we have a web automation tool that deploys the images nightly.

As for contributing, I am not sure the depth of my knowledge of the project is enough to contribute as of yet. Thanks, I will contribute what I feel I can. You guys are doing great work.

@Brian-David alright, thanks for testing. This will require a bit more work than I was hoping for it seems.

@fallingwax FWIW, I just checked at the H330 is $155 more than the S130. For a moment I thought they removed everything but the S130, but you need to select the hot plug drive trays before the H330 is an option. I know it was there because I purchased a R330 in July and linux is installed on that box right now, so know I didn’t pick a S130. But anyway, I hope you are able to turn on that option in the firmware. It looks like the S130 is using the intel software raid controllers, so you may have some luck with madm.

@tom-elliott This is the part I didn’t know when I restarted. Im back on 1.5 and good now.

@slimzy said in ipxe with sanboot:

is there a way to bind a root-path per item in the menu or we can’t?

I’m not sure I understand this ^^

But, I think I have an understanding of what is going on. I can see at the end of the kernel init it attempts to contact the local cdrom. If it doesn’t find it the kernel then starts the network install bits. When you pxe boot I can get the kali linux loader to work (without the dvd iso image). It loads and the reaches out to the internet to download what it needs and completes the installation. I suspect that when you boot off the cdrom that it loads the files directly from the dvd and does not reach out to the internet.

After checking the log I saw that it was still looking at eno1. I found where I missed changing the interface under the default storage node under Storage Management. After changing the Interface setting from eno1 to enp7s0f0 all is good. Hopefully someone else will find this useful.

@sebastian-roth don’t worry, it’s an exception. I’m managing many fog servers and it’s great (and still my first choice).

@imagingmaster21 security chip disabled, usb nic allowed in host config, it’s atom: I don’t think it has virtualization support.

Unfortunately, I don’t have any device available to make further tests.

@bmorine said in DeepFreeze Snapin:

ERROR: Object reference not set to an instance of an object.

Host settings -> reset encryption data should solve this.

@sebastian-roth

Not to ignore you, but when I came in this morning, me and my boss had a conversation. He was messing around with another VM that was also having speed issues. He turned off VMQ under the Hardware Acceleration for the VM’s NIC on Hyper-V. His file transfer speed issue immediately went away. Naturally, I tried this for the FOG VM. When I booted up a machine, PXE boot ran as expected. I never saw the TFTP spinning, and both bzimage and init loaded instantly. However, I turned VMQ back on and tried again and the speed issue was still gone, so I don’t know if this was a problematic setting or not.

If the speed issue comes back, I will go ahead and do the tcpdump, unless you’d like me to do it now anyways just for sake of gaining info. FOG is running on the latest Ubuntu Server OS.