My customer is running FNMS 2022 R1 on Windows Server 2012 R2 and SQL Server 2012 SP4. Due to EOL it is required to upgrade those to newer versions.
There are more than 10 Beacons and 2 SQL Servers so an in-place upgrade is being considered as the action plan. What is the supported process to bring the servers to newer versions, both Windows and SQL? Regards.
IN place upgrade will not help in flexera Db & beacon. It will break your configuration. So best advice to create a new VM of server & restore DB from latest backup. Beacon can fresh install as it will not take much time.
Been through this a couple of times and it is easier to just stand up a new SQL environment. Then you can either backup the databases and restore them to the new SQL server, or use MS Data Migration Assistant to migrate all the SQL databases and logins etc. You could run compatibility assessments from this MS tool as well if you wanted to.
Then just reinstall the FNMS server roles on your new servers and point them at the databases hosted on your new SQL environment.
IN place upgrade will not help in flexera Db & beacon. It will break your configuration. So best advice to create a new VM of server & restore DB from latest backup. Beacon can fresh install as it will not take much time.
In my experience, doing an in-place upgrade of Windows is a fragile process and likely to lead to a range of difficult-to-resolve problems. So I would recommend doing a clean OS install and then installing FlexNet Manager Suite on that.
I don't think an in-place upgrade of SQL Server would likely be as difficult though, so that's probably OK to do.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
Thank you all for your suggestions and I completely agree with them.
Yet what is the supported way? Because I was not able to find any doc with a statement and need to provide a documented and supported process to customer.
Been through this a couple of times and it is easier to just stand up a new SQL environment. Then you can either backup the databases and restore them to the new SQL server, or use MS Data Migration Assistant to migrate all the SQL databases and logins etc. You could run compatibility assessments from this MS tool as well if you wanted to.
Then just reinstall the FNMS server roles on your new servers and point them at the databases hosted on your new SQL environment.
