Server migration - Name changing issues



  • 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?

  • Moderator

    A year ago maybe I tried using a snapin to remove the old client and install the new one. I didn’t have any luck, I ended up using the hammer for it (group policy computer based startup script).



  • @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?


  • Moderator


  • Moderator

    @Tom-Elliott said in Server migration - Name changing issues:

    Or, and maybe just cause I like the new stuff better, pushing out a GPO remove the old client, and install the new (one time only of course – per machine).

    As long as we are just throwing stuff out, this could also be done (for free) with PDQ Deploy. That is what we use for package deployment instead of snapins.


  • Moderator

    @Yanis-Sauve said in Server migration - Name changing issues:

    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.

    Wayne created a script to fix up the FOG install if the IP address has been changed for FOG 1.3.0. Let me see if I can find the link.


  • Senior Developer

    Or, and maybe just cause I like the new stuff better, pushing out a GPO remove the old client, and install the new (one time only of course – per machine).


  • Moderator

    @Yanis-Sauve If you were handy with scripting you could just push out a new ini to each workstation to update the ini or create a snapin on 1.2.0 server to update the ini to the new server. There is a bunch of ways to update that ini file.



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


  • Senior Developer

    @Yanis-Sauve I can’t say it “will” or “won’t” work.

    If you still have the old server, you would need IT to have the new IP address setting. Even with that, you still have to reboot the machines for the new changes to take effect.

    It may just make more sense, if your last octet is the only thing changed, to change the new server to the original IP address.



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


  • Senior Developer

    @george1421 Correct. Or you can use “client updater” to update the config.ini, but it won’t do any good if the clients can’t find the new server to begin with.


  • Moderator

    @Tom-Elliott So in this case its best to just remove the old fog client and then push down install a new one with the proper MSI flags to point to the new 1.3.0 fog server (??)


  • Senior Developer

    @george1421 I have to add a caveat.

    The Legacy client will not auto update to the new fog client. So if you’re running FOG version 1.2.0 with the FOG client, just updating to the RC’s will not push the New Fog client down onto the host.


  • Moderator

    @Yanis-Sauve for the older clients you should be able to update the configuration ini to point to the new fog server. Just be aware that when the new fog client is installed it will be tattooed with the certificate of the 1.3.0 FOG server so you can’t hop fog servers like you could with the older FOG client. When the old fog client checks in to the new FOG server the fog client should update itself, at that point it will retain the tattoo of the new fog server.

    You might want to consider updating your fog install too since the latest rc release is 36


Log in to reply
 

358
Online

38989
Users

10713
Topics

101692
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.