SOLVED Procedure for Migration from 1.2.0 to 1.3.0 RC

  • Server
    • FOG Version: 1.3.0 RC19
    • OS: Centos 7
    • Service Version:
    • OS:

    I have an in-place solution using undesirable hardware of FOG 1.2.0 on ubuntu following the directions on the wiki. I now have a 1.3.0 RC19 on better hardware. I am not certain what the process to migrate my host systems to the new FOG server. The images on the current server do not need to be saved. I have the reference systems available. I would like to save my host directory and groups, to avoid the labor of registration.

    I am aware that the server and the client have a trust relationship, I am not sure how to set that up, or even how it works really. I am not sure if the PXE boot has some sort of trust relationship.

    My poor understanding aside, does the community have any recommendations?

  • Successfully migrated! Mark as solved please

  • I can not attempt this as of yet, as I have now run into a database issue. The forum post can be found here

  • If you’re coming from 1.2.0, you would have been using the legacy client. There’s no trust relationship for the legacy client - which is one of the many reasons why the legacy client isn’t secure. So no worries there.

    I think 1.2.0 had a host export feature? I don’t remember exactly. But, on the old server look at Host Management and look for an export link on the left menu.

    If there’s not one there, you could just export the whole DB and import it into the new server. If the new server has a different IP than what the old one used, you’ll need to adjust certain fields via the web interface post-import so those IP addresses get fixed. Steps on that here: Remember you’d just be changing the web gui stuff, nothing in the backend would need changed.

    And lastly, if your new server has a new IP, you’ll need to update your DHCP server’s option 066.

    And, if the new server has a new IP, and you installed the legacy clients using an IP, well then don’t worry about them anymore. You can use Group Policy startup scripts to uninstall the old client via msiexec /x {product code here} /qn and then install the new client and give the proper arguments to point it at the correct server and use the options you want it to use. Steps on that are here: I recommend the MSI installer if you’re going to deploy out the new client with policy.

    Another option, if you don’t rely on the fog client, is to just not worry about the exiting clients or deploying. Your systems will get the new client the next time you image them.