Hello guys,

I do weekly updates to my FOG server, just to keep it running. I do the server updates, then a git pull each time.

For the database, do you think it would be possible to systematically display a page about the schema, update or not? I do get that sometimes the schema does not change, but each time I go through the fog install, I ask myself if everything is OK when no update page is displayed.

Thanks.

@george1421 I’d prefer to update the client of course. I’ll see what can be done about that.

The script looks interesting. I’ll keep that one in my back pocket.

However, for now, the plugin solution to update the clients is really interesting. I have not worked with them before. Are there any resources that could help me figure out how to use them?

@Tom-Elliott Well, considering I’m the IT guy, that should not be a problem.

Putting the new server on the old IP is one of the solutions I’m considering. The main problem I had with the new server since I migrated the configuration from the old server to it is that the old IP was still in some places. I’ll have to change all of these back again. I’ll try to find the page that helped me with that.

Thanks for the help. I’ll let you guys know how it goes.

@Tom-Elliott So, if I update the config.ini file with the new server’s IP, it will work, it just won’t update to the new client, right? I will still have to update it on all the machine at some point, right? The client should not have any trouble finding the new server, only the last octet of the IP address changes.

@george1421 Thanks a lot for the speedy response and help. Much appreciated

Server

• FOG Version: 1.3.0-RC-28
• OS: Ubuntu 16.04.1 LTS

Client

• Service Version: 0.1, from old server (See below)
• OS: WIndows 7

Description

After migration of old 1.2.0 server to trunk, had to do some modifications to get everything pointing to new IP (IP B), but it seems the client is still communicating with the old IP (IP A). The old machine is still there, since the new server is still in testing. I’m not opposed to keep the old server down for a while, though.

Here’s what happens:

• Boot machine
• Remove machine from domain
• Rename machine
• Reboot machine
• Log in. The machine reboots a few seconds later, gets renamed to old name.

Here’s what told me the old server was involved:

• Powered down old server.
• Boot machine
• Remove machine from domain
• Rename machine
• Reboot machine
• Log in. Machine does not react, aside from normal operations.
• Power up old server
• As soon as all services are up on old server, the machine reboots, gets renamed to old name.

Questions:

• I assume the Fog Tray application is not at the latest version. Does it matter for now if I leave those as is?
• Is there a way to change some configuration to get the Fog Tray to talk with the new server?