Skip to main content
lokean13
New Member
August 22, 2016
Question

Forticlient EMS Integrated Deployment

  • August 22, 2016
  • 1 reply
  • 14185 views

Hello, I'm working on deploying EMS into an existing Forticlient environment.  First, I have a question on deployment.  With my current Forticlient deployment, I have several profiles that are assigned depending on AD group, but when I import these profiles into EMS, it wants to assign them using OU.  What's the best practice on this?  Do I need to create OUs for the different profiles?  

Second, I did create one test OU and put my machine in there that already had Forticlient 5.4.1 installed on it, and I followed the cookbook on how to push out an uninstall and install.  I noticed the Windows notification saying I had no AV turned on but then never saw the system reboot to complete the uninstall or reinstall and Forticlient just stayed like it was with EMS stuck on saying it was installing.  I manually uninstalled Forticlient then did the remote install again, and even though it did install on the machine, and register it to the Fortigate, on EMS, it still says not installed on one column and still says installing on another.  Has anyone come across this?  

    1 reply

    SteveG
    New Member
    August 23, 2016

    I see the same stuff with PC's being listed as unregistered or not installed when EMS has pushed the install. EMS has lots of potential but it's real buggy at the moment. Usually after 24 hours and a reboot of EMS and the client PC the client status is listed correctly.

    lokean13
    lokean13Author
    New Member
    August 23, 2016

    OK, It's been since Friday and I've rebooted both.  I may try uninstalling and pushing the install again.  

     

    Any idea about the imported profiles? 

    SteveG
    New Member
    August 23, 2016

    We've performed a clean install so haven't migrated anything, in the process of moving from Sophos to Forticlient.