Hi all ...
My company is planning an upgrade of FNMS from 2019R1 to 2022R1.
The plan is to spin up all new servers for FNMS 2022 (application server, database server, beacons) to get onto a more recent version of Windows Server and to also get faster hardware.
Since mistakes "on paper" are cheap, we’d like to get the upgrade plan as accurate as possible “on paper” before we begin the process.
The high level plan goes something like this:
I've read the Upgrade On Prem guide from cover to cover. I still have questions regarding the deployment of the new beacon servers and the transfer of inventory data from existing agents to the new beacon servers.
For my questions, let's assume my FNMS infrastructure is a single application server W, a database server X, and 2 inventory beacons Y and Z.
Let's further assume that my new FNMS infrastructure will be also be a single application server A, a database server B and 2 inventory beacons C & D.
Q1: After I copy and migrate the databases onto new server B, what part of the upgrade process changes the migrated data to point to the new infrastructure? Is it the running of .\Config.ps1 "Config\FNMS Windows Authentication Config.xml" forceUpdateConfig?
Q2: When the new infrastructure is up, the old beacon servers Y and Z will still have the subnets assigned to them, but beacons Y and Z are not going to report into the new application server A. To reassign the subnets to the new beacons C & D, is it “simply” a matter of going to an old beacon in the list, removing all the subnets on the old beacon (making them unassigned), then assigning these unassigned subnets to the new beacon? Then we would delete the old beacon from the list?
Q3: We also have FNMS agents already deployed using "third party inventory". Up until this migration, they would have received updated policy from inventory beacons Y and Z. How are these agents told that they are to report into one of the new beacons C & D; that is, how do they get a new policy with the new beacon details? Would I have to push a new agent to these servers with a new initialization file? (I'd eventually be pushing a new agent to these servers anyway as a later step in the upgrade, but I presume there's a way for the existing agent to be told to report to the new beacon servers without having to update the agent.) Also, does the agent installer support an upgrade in place or do I have to delete the old agent first and then install the new one?
I'm fairly new at this so I hope my questions are clear.
Appreciate any and all advice you can provide. Thank you!
Apr 12, 2022 11:34 AM
Apr 12, 2022 12:02 PM
Your reply got me thinking - maybe I should better leverage what I already have.
Using my example scenario above, what if I temporarily kept my existing beacons while I spun up new ones. The flow would be like this after the new FNMS server was stood up:
What are your thoughts about this approach? I think it avoids the need to alter SSL certificates to include the DNS alias, right?
Apr 13, 2022 08:31 AM
A1: Yes, you'll need to run the config (forceUpdateConfig) and enter all the new variables in the process. Be aware that Compliance Connection details are not automatically updated, you'll have to do this for the FNMPDataWarehouse & FlexNet Manager Suite connections.
A2: I guess you could try that. Maybe you can just delete the old Beacons and assign the subnets to the new ones? Not sure if the WebUI will let you do that.
A3: Migrating agents to a new environment, I believe, has repeatedly been discussed in the forum. Typical approaches are:
Apr 28, 2022 08:47 AM