@lawrence1997 On this model, have you run through the FOG compatibility tests from the iPXE menu?

@digi One last comment is if you can find the newsid utility on the internet. Then just deploy that with a FOG snapin. That will change the workstations SSID still.

I just checked my current copy of Ghost and that software no longer contains the sid update utility either.

@Tom-Elliott Another example:

You have a lab of 30 computers. 8 of them are Dell, 22 are Lenovo. You have an image that works on the dells, and an image that works on the Lenovos, but not an image for both yet.

You’d make three groups. ONe for the dells, one for the lenovos, and one for all 30 of them.

Use the dell group to apply the Dell image to all the dells. Use the Lenovo group to apply the Lenovo image to all the Lenovos. Use the bigger classroom group to apply Active Directory settings, Snapin Settings, Printer Settings, and whatever else.

Another example:
You have a building with 500 computers. 250 of them are Dell Optiplex 7010 models. The rest are other models. For this, you could have two or more groups. One group for all Optiplex 7010 models, and one group called “Blah-blah-Building” for every computer in the building. You’d use the building group to deploy updates for things like Chrome, and you’d use the model-specific group to do mass re-imaging when that time comes.

@jjacobs Thanks for the help!!!

This morning, I checked a new time, reboot the machine, and I got the same error in the log.

Remark, when I change the status of the “Reboot host on hostname changes and AD changes even if users are logged in?” check box, the Host Product Key is blanked.

@Quazz said in GIT Update not working?:

@Joe-Schmitt It was in permissive for OP and did not work, though 😕

If it was really in permissive mode and still not working, then it’s not an issue with SELinux. That older article on CentOS 7 is incorrect.

@george1421 I just changed search scope to subtree and below and magically I was able to login with domain user ID (no domain name is needed). I can’t thank you enough for your support. Thank you!!!

@Wayne-Workman if there’s enough demand for such a snapin I can make it (It just requires some know-how concerning the design of the legacy and new client).

Maybe somebody out there can make the suggestions?

I’m going to try detecting smaller size and automatically applying it as a “fixed” partition, but I really need others to help determine if this is the best/safest route?

I removed the required first partition fixed size due to some potential hdd layouts.

I have now solved the issue.

It was on multiple vlans which was confusing it, i needed to set it to the single vlan member.

Thank you very much Tom.

Hi there,

thank you for the answers, this will work! automated versioning would be nice, be requires a lot of setting up and storage.

Nevermind, I figured it out myself haha.

This has now been solved.

I forgot to add /24 to the end of the IP in the nmtui configuration.

@george1421 Bookmarked!

@Tom-Elliott I was in the good folder, but the trunk install didn’t work. I havn’t the screenshot anymore but the installation was stuck at “install and update package… Failed”. Like i said, i tried to install/update fog in many ways. I still don’t know why it didn’t want to install (when in was at /root/fogproject/bin) but this is not really important. V1.3.4 is running great, i’ve no issue since yesterday.

@george1421 Thank you for your help.
Since we have only few other computer models and static dhcp entries for all computers that might be used with fog, knowing that “testing” the different PXE-Loaders (if the ipxe.kpxe doesn’t work) helps a lot.

I hope I gain enough experience, that I can give this great community a bit back some times.

@Tom-Elliott I believe everything else is working fine for now.

@kibade cool beans.

The troubleshooting articles most times will lead you to the problem if nothing else. Glad to see they are still helping folks.

@Wayne-Workman I’ve already cleaned it up.

Sorry other pull in changed version accidentally.

If you pull it should be corrected for now.