Posts made by ty900000

@george1421 Version 1.5.0 RC-12

@EAHarvey I went to my profile settings and changed the skin back to Default or No Skin and everything seemed to revert back to its correct size. Selecting a skin seems to mess things up.

Hello all! I remember a few FOG releases back we could create a user whose only role was to image computers, but it could not log into the webpage. With all the updates, that functionality (at least, in its original location) has disappeared. Does anyone have any ideas about this or was it something that was removed due to lack of use? Thanks!

I just wanted to post to close this out.

I got a test environment working with better switches and FOG was able to pass 64-bit UEFI traffic correctly the first time, every time. Thanks all for the big help! I really appreciate it!

@Psycholiquid

That’s cool; I understand.

@Psycholiquid

Did you happen to have any luck with Hyper-V 2016 this weekend? I’m in the process of setting up a testing environment at my company, but wanted to see if you had any luck. Thanks!

@sudburr

Nice… At this point, it really doesn’t surprise me that it seems to work for everyone else since our network infrastructure is so old and unmanageable.

@george1421

No, I haven’t made any changes to force 32 bit anything to anything else. Where would I look to double check?

@george1421

I tested the UEFI boot with a physical laptop, a brand new Dell Latitude E5570 and I got this iPXE error.

I took a video of it as it was PXE booting and did confirm it picked up the ipxe.efi configuration file from DHCP.

I went to that website and it just says try the latest version of iPXE. Is this just an iPXE error and not a FOG error?

It does copy an image down just fine when I boot from legacy NIC.

I’m sorry for being such a hassle with all this!

@george1421

Okay, yeah. I just did a quick Google and Hyper-V can make templates akin to VMWare’s operation. (I’m new to Hyper-V, myself) That may be our best option going forward. Thanks for the tip.

And, it is possible our network is wonky. I’m the same guy from the Multicast being really slow issue: https://forums.fogproject.org/topic/10017/fog-server-cpu-requirements. So, it wouldn’t surprise me if 99% of the world had this working and my company is part of the 1% with a bad network setup.

But, yeah. If this is a more common issue than just me, I’m more than willing to help in any way I can with it.

@george1421

Ha! Yeah, I had to fight to use Hyper-V in the first place…

I work for a federal government contracting company and we have orders to harden our systems, network, infrastructure, etc by the end of the year. One of our guys already created an image of a 2016 server with a hardened baseline. I was hoping I could just blow that image to a VM, rather than use the generic ISO and rebuild all the security hardening from scratch every time we need to set up a server.

@Psycholiquid @george1421

Thank you both for the help! Let me know if there is anything else you need from me for debugging/verification.

@x23piracy

No, neither of those posts is mine. For the Spiceworks post, I am getting a DHCP address pulled in. And for the Fog Forum post, I am using a Gen 2 machine, not a Gen 1. I can boot a Gen 1 machine via PXE, but would like to make a Gen 2 machine.

@george1421

Cool. Thank you. I appreciate it a lot.

@x23piracy

Before I even boot a server, I change a bunch of settings: add more processors, change checkpoint type, disable secure boot, etc. before I click Start… in Hyper-V.

@george1421

Thanks for looking at it. Yeah, I disabled Secure Boot before I even booted the server the first time.

@george1421

0_1493998262034_output.pcap

Is this okay?

@george1421

Yeah, I got some time. Thanks!!

I tried 00002, 00006, 00008, 00007, 00009 and made the appropriate .efi file change in DHCP. The only one that picked up the proper .efi file was the 00007. If that makes sense.

@george1421

@Psycholiquid

I changed it to ipxe7156.efi and DHCP pointed to the right file. But, it timed out again. Same error as above.

Hello all!

FOG Server version: 1.4.0-RC-9.3
Linux version: CentOS 7

I am attempting to image a Generation 2 Hyper-V VM with FOG over UEFI boot. I know Generation 1 with legacy boot works , but I really want to get migrate everything to Generation 2. I have followed the guide on: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence and the PXE boot is now picking up the ipxe.efi file as the correct configuration file. However, it still throws an error and claims there was a “server timeout.” Has anyone had any luck with this? Or does anyone have any ideas about what I can try next?

Thanks all!!!

0_1493997397380_FOG PXE.PNG

@george1421

I added a Cisco switch in the mix, but I couldn’t get it to pass any traffic, even from the switch itself. I don’t know if adding a layer 3 switch into the mix confused everything?

Anyway, I’ll wait until we get new equipment and then debug it from there, like you suggested. We’re going to be reimaging multiple machines at a time before we get new network equipment anyway, so I most likely need to get a RAID 10 set up.

Once we get new equipment in, I’ll give the Multicast a shot and then reply back to this thread. But, that’s way in the future. Probably several months or more.

I appreciate all the help you guys have put in to this! Thanks a bunch!