Posts made by astrugatch

@Tom-Elliott

Thanks. I’ll give it a shot.

I’ve searched but haven’t found a solution. I’m migrating machines from one Fog Server to another and want to uninstall the client that currently points to the old server so that I can re-install and point to the new server.

Does anyone have a script to remove the fog client? I already have a working installer script.

@anwoke8204

I think you’re misunderstanding what those fields are asking for. Those fields are asking which OU in which fog should look for the groups and users. Then you specify the groups with access in the admin group field.

From your screenshot you have some configuration errors.

Both Search Base DN and Group Base DN should be OU’s not CN’s.
Also you should likely have Search Scope set to Subtree and Below

If you want to use LDAPS you will need to have a publicly trusted Cert on your domain controller OR you will need to add the root cert to the cert store on your fog server.

@eazis

Did you make the changes for your admin group setting to be a group rather than an OU as you have it?

Can you go to Fog Configuration then to Fog Settings then Plugin: LDAP and screenshot what is there for LDAP ports and User Filter?

Also For “Admin Group”, that shouldn’t be the name of an OU but rather the name of a security group that your users are a member. That group should be located somewhere within the parameters set by the Group Search DN.

Nevermind. For whatever reason my host module settings were all deselected. No idea why. I am using persistent groups and these are set in that group.

Running 1.5.9 163 on Ubuntu 18.04.x
Imaging a Dell 5530 with windows 10 LTSC

Imaged a system with an existing image that has the client pre-installed. Host is registered, and has active directory settings set. System is never rebooting and not binding / renaming. I’ve reimaged it a couple times, and reset encryption. I’ve also disabled and re-enabled active directory settings for the host.

Fog log on the system shows.
Middleware: Response Module is disabled on host.

@jveronese

This is the expected behavior. What you want is persistent groups.

https://forums.fogproject.org/topic/8836/basic-persistent-groups-and-1-3-0rc16

Can you take a screenshot of your ldap configuration pane?

@jack_chapman

As a personal rule (not from the FOG team). I would recommend sticking with LTS OSes when setting up servers unless you want to regularly be upgrading or migrating. Ubuntu Interim standard support from Canonical is SHORT (9 months).

See 21.10 vs 18.04:
https://ubuntu.com/about/release-cycle

@wayne-workman said in Fedora 35 & FOG:

Knowing our limited developer resources, and to keep cost low, I suggest we cease testing Fedora as well as cease supporting Fedora - in the sense of fixing installation code to make new versions work.

Considering fedora is generally the bleeding edge version or REHL I would classify it under NOT LTS and pull it from the supported OS list.

@wayne-workman

That number makes sense given the number of commits since the GA release and how many are bug fixes.

One option for limiting support to reduce workload would be to limit to LTS branches only. So only 18.04 and 20.04 for Ubuntu and skipping the intermediary releases and dropping those that go out of support by their vendor (eg ubuntu 14.04, 16.04).

Finally got a chance to run the upgrade again and figured out my issue.

For some reason safari wasn’t happy with the upgrade. I can open fog fine from a private window or if I cleared history. It doesn’t open in Chrome, which was my other test because chrome doesn’t trust the ssl cert and no longer gives an option to bypass by default.

When I run :

SELECT * FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%';
SELECT * FROM hosts WHERE hostID IN (SELECT hmHostID FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%');

I get output pertaining to the host that I had deleted via the GUI. Is there a way to delete those records from the DB using the MAC?

I have a couple hosts that I deleted via the fog GUI (1.5.9.98) and when I go to reenroll them they are complaining that the MAC is already in use. Any way to completely purge these?

@sebastian-roth

Going from 1.5.9.98 to 1.5.9.111.

The fog server gets weekly updates via Landscape so unless entirely new packages get installed somewhere between those two version I doubt that is it. I’m going to snapshot, pull the config from .98 and run the upgrade and compare the two configs to see if anything stands out

I also upgraded rather recently from 1.5.8 to 1.5.9.98 without issue.

@george1421

But if I roll back to the snapshot I take before the update it responds to the dns name. nslookup resolves fog.domain.org to 10.10.70.4 as it should. The record is a static A record in our local DNS server (active directory domain).

I am running the latest dev version on Ubuntu 18.04 and it is no longer responding to the alias in the apache config. I can access the page via the IP address, but we have the hostname entered into all of our clients so this is pretty key to keeping things communicating with the server.