@pvwinters said in Ipxe boot to Uefi shell reboot afther +/- 5 min:

Question is there a way to hold the old ipxe server and remove the WDS and combine it with the new fog server?

I want to keep the IPXE Server as the default one and when my tech guys want to deploy or capture a image to can boot to the FOG server and do there thing.

Ok this changes the context a bit but its still possible. So let me tell you how FOG works then we can see what fits best for you. Personally I would remove the old pxe boot server and just use FOG for everything, but that is just my opinion not understanding your requirements.

So in a clean fog environment you have dhcp option 66 with the fog server IP address and dhcp option 67 to point to the ipxe boot loader you want to use (there are other options for this but lets not muddy the water right now). The client pxe boots and FOG’s ipxe boot loader is transferred to the client computer. That client computer then boots, requests dhcp address then starts running a script built into the ipxe boot loader where it uses dhcp option 66 to get the IP address of the FOG server and then chains to a file called default.ipxe. default.ipxe then again chains and loads boot.php which builds the FOG iPXE menu.

So with that said, from your current (legacy) ipxe boot server you can chain to tftp://<fogserverip>/default.ipxe to jump into FOG. As long as your legacy ipxe server is running a somewhat current version of iPXE that should work.

Now WDS has 2 ways you can configure it. One is using dhcp option 66 and 67, the other is with a ProxyDHCP service that will send out the pxe boot information that will override dhcp options 66 and 67. FWIW, you can chain from FOG into WDS if needed (I assume ipxe too) with the right chain command.

@otpyke If your web interface is not reachable make sure that apache server is running. It sounds like maybe no. The apache server should start independent of IP address used.

netstat -an | grep :80 should show you if your apache server is listening on the http port. The command ip a s should show you the ip address your fog server is at now.

@george1421 said in Ubunutu Server 21.10 Install Fail:

Now after you get FOG 1.5.9.110 or later installed, go into the FOG Web ui and download the latest FOS Linux kernel.

Just want to mention that FOG dev-branch will install the latest kernel directly. No need top manually do that.

@greg-plamondon What is your end goal for this fog server?

How many computers will have the fog client installed on them that will hit this FOG-Pi server?

@fogschut said in Image not resizing Windows partition:

I’m not going to try and debug a Ubuntu 12 to 14 update-on-update FOG-installation, so thanks for your help - the new FOG-version runs perfectly fine for our task

That’s the right way to go about this! Well done.

@greg-plamondon Yes, I never enable that nonsense 🙂

@novice83 The mentioned PDF export works just fine on my test setup (FOG 1.5.9). You might want to check apache and PHP-FPM logs to see if there is an error showing up. See my signature on where to find the logs.

@dashwell Just play with the settings to see what difference it makes. Can’t give you a clear advice on this as it behaves differently. This is not something FOG has a share in. It’s up to the vendors UEFI implementation.

@sebastian-roth The old memtest would loop forever. 9.4 “free” will stop automatically after 4 passes ( so you can’t leave it running overnight for a longer stress test ).

@WT_101 said:

I’m trying to change some wording such as “Host” to “Platform”

Not sure it’s wise to do as we don’t understand your working here in the forums. 😉

Take a look at what the installer does:

msgfmt -o ".../path/to/messages.mo" ".../path/to/messages.po"

How to use “web/management/language/en_US.UTF-8/LC_MESSAGES\message.po” and “packages\web\commons\text.php” ?

The later file was initally meant to be used for a general place to define variables for most used terms and phrases that could be used throughout the code. But I think it’s not being used in each and every stop in the code. Searching the code (or github) you can find many places where this variables are used: https://github.com/FOGProject/fogproject/search?q=foglang

@anwoke8204 Start by looking at the log file in C:\fog.log to see if the fog-client software is properly working.

@sebastian-roth
Thank you.

I saw that the printers in the list of a group are all printers not the assinged.
In the client there are the right ones.
thank you

@george1421 I must have missed the other persons post, this is my only post about it. Thanks for the info and I will check out that article

@george1421 OK I see, and thanks for that!

I went through the dirty bit and realised Sysprep was the issue in hand, as it was re-imaging over the same sysprepped image which seems to cause issues with cloning.

Removing the bit didn’t seem to work, so I then had to completely re-install a fresh Windows and start over again, and ran sysprep and fog cloned it successfully.

I see why using VM would be easier as you can sysprep as many as you need etc.

Thanks!

@wt_101 I do have a proof of concept for NFSv4 and I’m running it on one of my production FOG servers. https://forums.fogproject.org/topic/14791/feature-request-for-fog-1-6-x-configure-image-capture-to-use-nfsv4-instead-of-nfsv3/10

The tough spot is that you need different inits with NFSv4 enabled. The default inits that come with FOG have nfsv4 disabled. The other issue with nfsv4 is that the shares are changed a bit into a virtual share. My PoC thread also covers that. I really need to consolidate that into an easy to follow thread. I was going to save pushing for nfsv4 in FOG 1.6.x series but that series is getting pushed out because of the lack of dev time. Here are the inits from Jun 2021 with nfsv4 enabled: https://drive.google.com/file/d/1EHLhmM9-kXpFO7kfk3H1ydEZF3q8lID1/view?usp=sharing

I have found the correct file to change which is “pdodb.class.php”

Cert to add here
6fe5af73-ef3f-4cad-a605-3da5c1c0eca4-image.png

While the port can specify at $dsn
a83bd0c8-cc7c-4f80-bdd2-679fe4221514-image.png

@forcom5 Well we typically see this with older hardware. It looks like thise 280 G1 systems have a 4 gen processor in them, so that makes me think they are on the older side. BUT if you have a working solution, run with it.

@george1421 …having made my decision though, I have seen the REFIND option available in the Boot Exit Settings. I’ll drop back in if that fixes the universe in the more “legacy” approach to all this.

EDIT - it did not I got a snowstorm of odd characters marching across the screen. Quite pretty but not successful. All fine though, have my route to making this work now.

In the BIOS on the configuration tab, disable Intel VMD Controller and disable Secure Boot on the security tab. This is the only way i’ve gotten this to image.