Announcement: New Knowledge Base

4 June 2020: We are pleased to announce the launch of a new Knowledge Base, Changelogs for Business Security Products, where you can find more details, such as bugfixes or new features, about the most recent releases of our business-related products.

Moving workstations from one policy manager to another

Situation is that all our workstations (about 900) will be moved to another domain in the near future and under the new Policy Manager. The new Policy Manager has a different key set than old. What is the best course of action to do this. Old Policy Manager version is 10.??. New one is 11.10. I am posting this from home so I don’t remember exactly  the version of the Policy Manager.

Best Answer

  • PeterPeter Posts: 186
    Accepted Answer

     

    Hi Ile,

     

    There is a tool available which can address this use case without requiring to reinstall the clients. Please contact support and ask for a Admin -Key-Replacer.jar package. Please attach the following information with your support request:

     

    1. fully qualified domain name or the IP address of the new Policy Manager Server
    2. TCP port used for host communication on the new Policy Manager Server (default is 80)
    3. admin.pub file exported using Policy Manager Console connected to the new Policy Manager Server

     

     

     

Comments

  • etomcatetomcat Posts: 1,312

    Hello Peter,

     

    I don't think I understand this one? Why should they need a special tool to replace the key on 900 workstations, when it is trivially easy to export, transfer and import the already established key-pair (and the DB contents) to the new PM?

     

    Best Regards: Tamas Feher, Hungary.

  • I think the newly installed PMS probably already is having quite some hosts managed.

     

    So a 'mergin' is inevitable. I know it's not the best option, but I also had such situation with a customer once.

    It may happen...

     

    BR

    Costas

     

This discussion has been closed.