Jaan Posted September 30, 2021 Posted September 30, 2021 Hi all...... I've been here before but can't remember what i did to fix it..... Short story is i've had to rebuild the Fog server today. Fog installed everything fine, Set a image definition in fog, fired up my Windows 10 VM (Image client). in hope to upload it to fog.... and it just hangs @ initialising device. Now i have been here before, but i can't find anything on here on my historical posts or via Google...... I'm sure it's something really really simple. Anybody kick me in the right direction? Legacy nic, non uefi. all the clients on site can boot to pxe fine, and upload a image. Just not my Hyper-v VM. I'm sure it's something to do with hyper-v Win10 1809 ltsc Server 2019 Help me edugeeks
Jaan Posted October 4, 2021 Author Posted October 4, 2021 I've tried various Kernals, gen1, legacy NIC. I'm stumped. No idea why it wont boot....... ALso tried a "ISO boot pxe" with the same result.
Oaktech Posted October 4, 2021 Posted October 4, 2021 Humour me and restart the TFTP service on the fog server...
Michael Posted October 4, 2021 Posted October 4, 2021 If you boot from an LTSC disc, can you see the relevant partitions?
Jaan Posted October 4, 2021 Author Posted October 4, 2021 Humour me and restart the TFTP service on the fog server... iI got excited for a moment then...... But no go - - - Updated - - - If you boot from an LTSC disc, can you see the relevant partitions? Sorry i don't follow?
skyline_17 Posted October 5, 2021 Posted October 5, 2021 Does the new server have the same ip address as the old one? What do you use for dhcp
Jaan Posted October 5, 2021 Author Posted October 5, 2021 Does the new server have the same ip address as the old one? What do you use for dhcp Yes it does as well as the same name and MAC address. We are using Windows for DHCP. It getting an IP address All our physical machines can boot to the FOG screen fine. cheers
skyline_17 Posted October 5, 2021 Posted October 5, 2021 Are all your other clients legacy? As I know for our new laptops I have to change the dhcp setting 67 from undionly.kpxe to ipxe.efi to allow them to boot into fog As our desktops are legacy booting
Jaan Posted October 5, 2021 Author Posted October 5, 2021 Clients aren't uefi. we have fog setup like this..... it was fine until i borked the ubuntu install and had to rebuild it (oh the irony)
Jaan Posted October 11, 2021 Author Posted October 11, 2021 I'm not getting anywhere with this..... Do you think the best bet is to put WDs and MDT on a single HYper-v VM and go from there? Get rid of Ubuntu/FOG I already have a "Golden Image" VM on hyper-v that is already syspreped. I assume i can just capture and deploy that then do the magic finetuning stuffs later on? I'm really Green to WDS/MDT anybody know if a decent guide that i could follow? Thanks in advance.
skyline_17 Posted October 11, 2021 Posted October 11, 2021 Hi you could maybe try the suggestions here, as it sounds like the same problem https://forums.fogproject.org/topic/14871/server-2019/5 alternatively you could clone the drive in vm to a real hard drive then put in a working computer and clone it Just depends on how desperate you are to get the image
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now