Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 9342 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

Deploying Sophos to Windows 8 and Server 2012 not working from SEC 5.2.1

asester

Hey all,

I know that support for deploying to 8.1 and Server 2012R2 from SEC is coming soon...but I'm currently experiencing issues trying to deploy to Windows 8 and Server 2012 original releases.  I am running SEC 5.2.1 with the Recommended AV package (10.3.1), and every time I try to deploy I get the following error:

The installation could not be started: The parameter is incorrect. The computer may need additional configuration before installation.  See knowledgebase article 29287.

I have visited the article, of course, and followed all instructions listed.  I have made sure remote registry, task scheduler, and windows installer are all running.  It's not a DNS issue.  The share is shared properly and I can access it from each of the servers/PC's that I'm attempting to deploy to.  Any help would be appreciated!

Thanks,

Adam.

:44845


This thread was automatically locked due to age.
  • 0

    So you see the error for both Windows 8 and 2012?  Does 2012 have the GUI installed?

    I'd suggest UAC is the most likely cause.  After turning that off you have to reboot.  If you have turned it off via a GPO make sure it's taken affect on the computer you're deploying to and that that computer has been rebooted afterwards.

    :45055
  • 0

    According to http://www.sophos.com/en-us/support/knowledgebase/29287.aspx UAC being enabled shouldn't effect anying past SEC 5.1. Is this not correct?

    :45669
  • 0

    True.  As detailed in the deployment guide: www.sophos.com/deployment

    And we how have a video (see below) showing SEC 5.2.1 R2 being installed on Server 2012 R2 (with a functional level of 2012 - don't forget to factor that in).  Then a GPO created for two services and four firewall rules.  Protecting a Windows 8.1 client then works successfully.

    I suggested UAC in my reply above as, thought we have gone through as many scenarios as possible in testing, if there is a problem we have to start ruling things out.

    Common reasons for deployment to fail are: required services not started, the Windows client firewall blocking the creation of a scheduled task, the account not having full permission to run the task/access the share, the share is not accessible, DNS problems.

    :45671