Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 13 replies
  • Answers 2 answers
  • Subscribers 7 subscribers
  • Views 30645 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Guest VM Agent Installation Failure

PMIAdmin

The Guest VM Agent installation fails with the error "sophos gvm management service failed to start".  It looks like the account the installer creates does not have sufficient rights to start the service.  This is a new Windows Server 2016 VM.  Has anyone experienced this issue?



This thread was automatically locked due to age.
  • 0

    I don't know if this will help others since I'm using Windows 7, and it seems like most others are using Windows Server.  But I found that if I go in and do a full uninstall of MVC++ 2015, and then restart, I can then successfully install the VM agent with no issues.  I don't know why this has anything to do with services not able to start due to permissions issues, but it has worked for me on 3 straight machines that had the issue.

  • 0

    As others have stated, the server installation failure is happening on domain controllers.  Member servers have "NT SERVICE\ALL SERVICES" added to "Log on as a service" allowing the Sophos accounts to run the services.  Domain controllers, using the default domain controller group policy, do not.  You can add "NT SERVICE\ALL SERVICES" to your domain controller group policy, refresh the policy on your domain controllers and perform the Sophos Guest Agent install.  After the installation, you can remove "NT SERVICE\ALL SERVICES" from your domain controller group policy and add "NT Service\SGVMManagementService", "NT AUTHORITY\SYSTEM" and "NT Service\SGVMScanningService".

  • 0 in reply to DavidRabenberg

    I found that if I go in and do a full uninstall of MVC++ 2015, and then restart, I can then successfully install the VM agent with no issues.

    I suspect that they've pinned it to a very specific build version of these libraries as I'm seeing the same problem on systems with the 2015 package already installed. Unfortunately, they're on systems that can't be rebooted very often so it's a bit of a hassle & definitely eliminates the option for automating my installs. But this is basically a 1.0 public release so there are bound to be some undiscovered glitches now that it's in the wild.

Unfiltered HTML