@loosus456 If you have not resolved this, then make sure your network team has set the building switch to use one of the fast spanning tree procools like (FastSTP, RSTP, or what ever your switch mfg calls it). This will allow the port to start forwarding data then detect if there is a loop back second. (pessimistic vs optimistic forwarding)

Does your company have direct internet access or do you use a proxy server. The error is not really an error it’s just that the fog server can’t reach the internet.

@Tom-Elliott

Yes, thank you.

@lmioperations said in Fogupdater.sh "Attempting Download Failed" for all mirrors:

I was nervous about the install (based on the horror stories I was seeing in various communities online

Well that concerns me a bit there are negative posts out there. Yes there can be problems (especially when the linux distro changes stuff without notice), but that is why we are here in the fog project to help IT admins deploy FOG and help identify issues when they come up. FOG IS insanely complex using multiple other open source technologies. Its a delicate dance to keep everything in step.

Glad you have it going

Works fine thank you for your help!

@george1421 I actually ended up testing on the last batch of HP Streams! (28 to be exact!) Everything went very smooth! Thanks for your help George!

@Tom-Elliott I reran the installer script a second time on the nodes and that seemed to fix my problems! I want to thank everyone for your support and ideas! Much Appreciated!

@george1421 You are an absolute legend George. It works now and I was able to PXE boot from my client PC and upload it to the Hosts screen. I can view it on the network and everything is working correctly.

Thank you so much!

@Tom-Elliott Thank you for the workaround. It works now, so that will give me the time to look into network issue. Thanks again, you always come through.

@CamGreezy If the subnet is at the same site then as long as routing is working then you can image. It uses the same tools. There is an issue with WOL (wake on lan) if you have different subnets you need to allow directed broadcasts on your network. But from an imaging stanpoint as long if the fog server can reach it, it should work.

Now if your remote site is connected over a low speed link (like mpls) then you might want to think about installing a fog storage node at the remote location to help with the imaging process.

@nitelife There is still something going on here that is not clear. Are these 10 systems of the same manufacturer and model?

If you change the target computer’s bios to not pxe boot but to boot from the local hard drive do they get an IP address?

If the fog server and one of these 10 pxe booting clients are on the same subnet then I think we need to see a pcap of what the hey is going on with the dhcp process.

This tutorial will walk you through setting up the fog server to capture the dhcp process. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Hi Tom

Apologies for the first post. I meant to edit the post and add more info in and got caught up researching what happened. I found the answer below and wanted to post it here for future reference or anyone else that might run into this issue.

I’m on FOG 1.4.4 and Ubuntu 16.04 LTS w/ latest updates.

On Chrome the Hosts tab would just provide and error that it could not load.

I found in the Apache logs at /var/log/apache2/error.log that php was using too much memory since I have so many hosts.

I then went to /etc/php/7.1/apache2/php.ini and edited the Resources to increase Memory Limit to 512M.

After increasing the memory limit I was able to load the hosts page fine.

@Tom-Elliott @george1421 Moving those folders and running the installer again has resolved the issues. Thank you again!

@george1421 It is a physical machine with 1 onboard NIC and (now) one TP-Link networkcard.
Works fine now.

Thanx for the help!

@Dark000 1.4.4 includes the aforementioned fixes already.

Please create a new thread detailing this problem.

@UCJared Excellent, I’m glad you have it worked out. ipxe.kpxe “should” work for all hardware nics, you may run into an odd-ball one where undionly.kpxe works better. The advantage of undionly.kpxe is that is smaller and quicker to load and usually a better chance of compatibility (except for those darn realtek chips).

I’m confused. FOG wouldn’t capture an inconsistent system in the first place. So how is this error appearing at deployment rather than capture?

Typically when you see “Object reference not set to an instance of an object” errors from the fog client, this most typically means tge encryption needs reset for that host.

the reset can be done from the web gui, on the host’s general page. It’s a big button towards the top.

If this fails to fix the issue, try reinstalling the client on that box. Make sure there are reboots between Uninstall and reinstall.

If several hosts have the issue, this points to an image problem - perhaps reboots were not done (two at least) prior to capture after all software has been installed.

@Tom-Elliott said in Windows 7 Activation issues:

So MAK has a limit, typically, of 25 or 50 keys to the server it’s activating against. Is the activation limit possibly met?

Depends on the site. My last job asked Microsoft to raise our limit from 10,000 to 20,000 activations. They gave it to us, no questions asked.

Nothing else seemed to work so redid the system and now it works