How to migrate the Policy Manager Server to the new Windows Server?

How to migrate the Policy Manager Server to the new Windows Server? - F-Secure Community

Issue:

How to migrate the F-Secure Policy Manager Server to the new Windows Server?

Resolution:

How to migrate / move the F-Secure Policy Manager Server to a new host.

Backup the current Policy Manager database:
1. Policy Manager 15 and above
  1. Stop the F-Secure Policy Manager Server service (CMD: net stop fsms)
  2. Create a backup of the following directories:
    Mandatory:
    C:\Program Files (x86)\F-Secure\Management Server 5\data\events
    C:\Program Files (x86)\F-Secure\Management Server 5\data\h2db\
    C:\Program Files (x86)\F-Secure\Management Server 5\data\sdata
    
    Optional:
    C:\Program Files (x86)\F-Secure\Management Server 5\data\fspms.jks
    C:\Program Files (x86)\F-Secure\Management Server 5\data\fspms-ca.jks
    C:\Program Files (x86)\F-Secure\Management Server 5\data\fspms.db.config
    C:\Program Files (x86)\F-Secure\Management Server 5\data\fspms.proxy.config<F-Secure>\Management Server 5\data\h2db\
2. Policy Manager 14 and below
  1. Stop the F-Secure Policy Manager Server service (CMD: net stop fsms)
  2. Create a backup of the following directory:
    C:\Program Files (x86)\F-Secure\Management Server 5\data\h2db\
Start the F-Secure Policy Manager Server service (CMD: net start fsms)
Install the Policy Manager Server on to the new host
Apply the backed up Policy Manager database folder to the new Policy Manager:
1. Stop F-Secure Policy Manager Server service (CMD: net stop fsms)
2. Replace the directories with the backed up versions from step 1
3. Restart F-Secure Policy Manager Server service (CMD: net start fsms)
Configure both, new and old, Policy Manager Server address value in the policy to point to the new Policy Manager Server
1. For Policy Manager Version 14 and higher
  1. Open Policy Manager Console
  2. Go to Settings > Windows > Centralized management
  3. In the Policy Manager Server address text field, type in the new Policy Manager Server address and in the respective HTTP/HTTPS text fields the designated values for these ports
  4. Set the padlock icons tailing these text fields to the locked position, which will ensure to enforce the new value
  5. Distribute (Ctrl+D) the new policy
2. For Policy Manager Version 13
  1. Open Policy Manager Console
  2. Go to Settings > Centralized management
  3. In the Policy Manager Server address text field, type in the new Policy Manager Server address including the HTTP port (for example: http://myserver.local:80) and in the HTTPS text fields the designated values for these ports
  4. Set the padlock icons tailing these text fields to the locked position, which will ensure to enforce the new value
  5. Distribute (Ctrl+D) the new policy
Once the managed hosts have fetched the new communication settings from the old Policy Manager, they will start to communicate with the new Policy Manager Server.

Note #1: If the F-Secure clients continue communicating with the old Policy Manager Server, be sure to verify connectivity from the clients to the new Policy Manager Server's designated ports (HTTP/HTTPS).
Note #2: If the new host will preserve the DNS name of the old Policy Manager Server host and you are using that address the as main management server address, you can simply paste the H2-Database file from step 1 to the new Policy Server Manager host.

Article no: 000002290