@mystic said in Replication already running loop.:

Does this message ever go away or does it continuously replicate?

The message goes away when the image files are properly replicated. Depending on the link speed this can take a fair amount of time.

@argylega said in Name Change & Domain Join Not Working:

The request was aborted: Could not create SSL/TLS secure channel.

This points to an issue we had up until the 0.12.0 client. Should be fixed in 0.12.1 (will be part of the next FOG release).

@george1421 Thank you, That worked.

@alexamore90 Sorry I don’t use that application. If you are more comfortable to post in your native language you may do that. We try to keep the posts in english, but find sometimes we get better detail when the poster uses their native language and we translate. I will only post in english through.

If you have a basic drawing of your setup that might help too, Remember we have to imagine your configuration based on the words you use.

One additional question I should have asked, is your current configuration for a home lab or a business?

@mystic I ended up changing the sql password on the fog server and rerunning the installer. Thanks @Sebastian-Roth for your help!

@technolust It looks like your Storage node is pointing to /fogserver/images. Verify if it exists otherwise change your image path and FTP path to /images

@editor FWIW If you are having issues with dnsmasq not doing what you want you can review this post: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

The reason why I mentioned it is because a 3 second count down is not part of the standard dnsmasq settings. If you are missing those you might be missing others listed in the above post.

If your dnsmasq configuration is working perfectly there is no need to review the post.

@alexamore90 Douple posting in different languages is not going to help. Please stick to one topic: https://forums.fogproject.org/topic/16140/slow-server-fog

@ggiesen Similar post: https://forums.fogproject.org/topic/16130/activate-fog-plugins

I guess it’s possible via SQL update commands send via shell scripting or something like that. Give it a try and let us know here.

@bylkem You can run whatever you want via snapin BUT it needs to run unattended (no user interaction) without GUI and access rights as SYSTEM user.

So for MSI/EXE installer you will need to find out if it can be run in so called silent installer mode. Ever program is different and ther is no general information we can provide about this.

This all is beyond what we as the FOG team can do for you.

Douple post on github and the forums. Will discuss this on github.

@matthewmandegar said in Host is NOT registered!:

we have to use USB-C>RJ45. when I PXE boot iPXE see the SYSTEMS MAC but once connected to FOG and I register it see the DONGLES MAC.

Have you looked into the UEFI/BIOS settings yet? Played with the MAC passthrough setting?

also here are the errors that I see when registering.

Don’t worry about this as long as it’s proceeding after that. ACPI errors don’t mean too much.

ok i find TASKING ADV SHUTDOWN ENABLED i will try

thanks !!!

if you can help me with plan B it will be great !

Thanks a lot !!

@mikmatcr Try placing a dumb/unmanaged/cheapie switch between the pxe booting computer and building switch. See if that gets you past the no configuration methods succeeded.

@robertkwild I can’t say about v11. I use 10.7 at the moment and install from DVD (kind of). It does prompt you to sync with an internet repository but will just use the DVD if you say no to the internet. Understand that your install will be out of date on patches but Debian will run just fine.

@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.