Upgrade of Policy Manager

Existing setup
==============
Policy manager 12.31 installed on Windows 2008 server
Clients are mix Windows XP and Windows 7

 

Plan Setup
==========
Policy Manager 13.x latest on Windows 2016 server
Clients will be Windows 10 and Windows 7
Installation will be in parallel using new server and same license then move all PCs to new server one by one

 

Progress
========
- License was renewed recently and install the license in existing setup which is working fine as before
- Installed Windows 2016 with all windows updates, join the server to same windows domain
- Installed Policy Manager 13.x and try to configure it

 

- The server cannot search Active directory, every time it ask for authorization it shows failure to login while the user is part of "Domain Admins" in the domain stuck on the server


- For client windows 10 was installed and try to install through policy manager as manual but can not install
Extracted an MSI file from Policy manager and tried to install it but it shows blue screen.

 

We need to upgrade our environment ASAP but we cannot proceed without Anti-Virus installed

 

Please explain how to upgrade or direct me to upgrade path

Best Answer

  • BenBen Posts: 2,640 F-Secure Product Expert
    Accepted Answer

    Hi, 

     

    For Policy Manager migration I would advised to follow the instruction from Siltanen  in this thread.

     

    Regarding the AD problem this thread might help shed some light. 

     

    Finally BSOD after installation are usually compatibility issue (with other antivirus typically). 

Comments

  • PM and AD are within same domin and still i have a problem gettin AD to connect, old server still ON and working fine without any additional setting.

     

    Please give direct instruction or direct me to the right document

  • Note that I got prompt at first time when opening the console and pressed Continue

     

    Console Prompt.png

  • MJ-perCompMJ-perComp Posts: 1,098 Superuser

    sure, it is a self signed certificate. Accept (continue) or replace it  by a different certificate.

  • I already continue and didn't get the prompt again, i assume this will make it as trusted with CA.


    PM and AD are within same domin and still i have a problem gettin AD to connect, old server still ON and working fine without any additional setting. What I am missing???

     

    Please give direct instruction or direct me to the right document

     

This discussion has been closed.