Good morning everyone! I appoligise for not replying any sooner. I did some testing and this i was able to solve my problem. I realized that i was able to PXE boot from a physical machine. Just not with a virtual machine with Windows 7 X64 in Hyper-V. I found a post that explain to use a legacy network card. I did the change and i was able to register my VM in FOG. Thank you all for your help. Incase, here is the link i found…
https://www.petri.com/boot-hyper-v-virtual-machine-using-pxe

Good day Yall! 🙂

@Quazz ah, yes you are right. I didn’t think about that, enterprise only. And not installed by default. But the FTP test should work from Windows. I would try connecting to the FTP share from the CentOS that should give you an indication as to if the server with NFS is accessible.

@Wayne-Workman AHA! Thank you!

George is right.

Also - if this DHCP service isn’t run by your company - you can block it totally at the router level and just run your own as well. That’s another option.

@Tom-Elliott Mine is imaging! Thanks!

@Wayne-Workman said:

@Sebastian-Roth Have you had any time to mess with this?

Have been on a short holiday far away from net and power… but working on it right now. 😉

@Sebastian-Roth the package ist called

php7.0-mcrypt

but the problem still exists after installing.

I’m working on a fresh install in parallel, so I think I won’t touch this one anymore. Thanks so far!

Just going to guess that the other two threads I responded two dealing with different, but VERY similar issues, this is likely fixed now. Of course a test and report will still be very useful.

https://forums.fogproject.org/topic/7148/attempting-to-expand-fill-partitions-failed
https://forums.fogproject.org/topic/7103/fog-after-update-could-not-recreate-main-partition

Sorry for so many relies, seems to be an issue with mysql, after a restart of the service I’m able to log into the web UI.

@popoyo Making backups is always a good idea. Do a configuration save, and a hosts export too.

@herrpommesfrite Please tell us what happened, and what you did to resolve the issue so that future readers can be helped by this thread.

@RLane Yes that is how it works.

I did create a hack to make a pseudo persistent groups if you want to give it a try. Understand this is unsupported by the FOG Project. So use it at your own risk.

https://forums.fogproject.org/topic/6902/fog-1-3-persistent-groups/12

But what happens here is that the sql script creates a trigger when a device is connected to a group. That trigger will look in the list of hosts for a host name that is the same as the group name. If it finds a host with the same name as the group name, it copies the fields for that host into the host that was just inserted into the group. It sounds complicated but its not. Just install the trigger and then create a group and host name that matches exactly. Then just add the computers to the group and the group setting should be persistent.

@ITSolutions said in Adding larger partition:

Edit: Sorry but I am not a linux “expert” and not great with fedora in general, usually on debian/ubuntu distros. But I think I see what the issues seem to be.

So I am assuming you have /run/media/root/fedora-expanded/images and /run/media/root/fedora-expanded/images/dev?

Have you tried this article https://wiki.fogproject.org/wiki/index.php?title=Adding_Storage_to_a_FOG_Server?

If you want all of your images moved to this new spot and not have the original location it maybe best to set it up like this and make sure the mount points are /images and /images/dev otherwise you need to make many more changes to make everything work. It sounds like just changing your mount point would be easiest and best now that everything is moved to your new drive.

That did the trick.

Thanks.

@lebrun78 No clue. But glad it works.

The master that the nodes were looking at needed the bind-address setting to be commented.

Once commented, restarted mysql and all was well.

Not quite an uninstall but it did the trick for what I wanted.

mysql -u root -p DROP DATABASE fog; mv /opt/fog /opt/fog.old

just stumbled across this thread, felt i should mention that the latest FOG trunk is still working on Ubuntu 12.04 LTS

@ITSolutions That was it; I’m normally better at catching that, or leaving it set to AHCI (which most of our computers come in as) but it just never crossed my mind.

@Arrowhead-IT

I do not sysprep. (yet - I want to try it out) I have. Did not check that as @ITSolutions idea fixed it when I tried it.

ok it work now the timezone in the fog settings wasn’t good
thanks a lot for your help guys 🙂