Topics created by Omar.rodriguez

That solved it @Tom-Elliott thank you very much. Life saver!

@Joe-Schmitt said in Fog client not renaming computers:

OG Client

Hey Joe just want to give a huge thank you for helping me out. This solved the issue!

For future reference if anyone has the same issue. This is what we were doing on our end. We are running Ubuntu 16.04 server with KVM. We have multiple virtual network devices which created multiple mac addresses. In return trying to deploy the same image from one machine to others caused a conflict with FOG which made the client not work on the machines. Following what Joe quoted tom on fixed our issue. In my instance using the first 3 hex pairs in FOG_QUICKREG_PENDING_MAC_FILTER solved the issue and the client is working as it was intended to 🙂

In plainer terms, you can update Ubuntu from an older version to a newer one - sure. But if it fails or leaves fog crippled, we don’t just “know” what went wrong. We don’t know how the old OS was setup, what was installed, how it was configured, and so on. It can be troubleshooted but how long that will take or if it’s successful or not, I can’t tell you. The Developers and Moderators and other community members are normally willing to help people - but your pace is limited to their free time.

So… Last night I wrote an article about migrating fog. For this - we know all the steps, and it’s less risky - and you can follow along with it and work at your own pace instead of relying on us.

If you’re strong with Linux and you’re Google-Foo is up to snuff, sure upgrade your OS. If you’re a newbie in a crunch don’t want risks, migrate.

@Wayne-Workman I didn’t get a chance to test this snapin as I needed to have it done the following Monday. What I ended up doing was installing office 2013 and just not open it at all as the timer for office will not start until you open any of the applications.

@Wayne-Workman Just want to update you that for some reason I kept running into the issue, instead I made MySQL services be the first services to boot and I have not ran into the issue since. (just another work around)