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

AD Sync Automatic Deployment Retry

platham

Hello, we are looking to migrate from McAfee VSE 8.7/EPO 4.5 to Sophos ES&DP 9.5/EC 4.5. At the moment I have our EPO server set to synchronise with AD at 1AM, run a query to see what systems are discovered are unmanaged by the server, then every two ours it tries to push out the McAfee agent to any unmanaged systems in the database. This works great, even catches the people with laptops who rarely plug them in to the network for more than a few hours a month. I've set up a 30 day trial Sophos server and can't seem to replicate this functionality. I set up a Container, set it to Synchronise with an OU in AD, Automatically protect clients etc, Synchronise every 60 mins (also set it to 5 for testing). If the PC is turned off or not on the network when EC first discovers it via AD sync it then logs an error 0000002e but then that's it, it never tries again - is this correct? Is there no way to get the EC to re-try the push either next synchronisation or every two hours or something? If not then it will require us to manually contact the user, get them to plug it in, then Right click > Protect computers (or delete all the errored devices several times a day) - this is obviously no good. Another option of course is AD logon scripts or deploy with Zenworks or SMS but that's just rubbish compared to the EPO set up, I want as much automation as possible with little administrator interaction.

Anyone any ideas?

Thanks,

Paul

:3728


This thread was automatically locked due to age.
Parents
  • 0

    I find it bizarre this feature request isn't gettting more attention, it is the biggest flaw in an otherwise great product. It's a big enough flaw to make a lot of potential customers using AD sync bail out at eval stage. I purchased the product after a very rushed evaluation, and frankly couldn't believe it when I discovered SEC couldn't handle what appears to be such a simple function post purchase.

    What's the use in great endpoint protection if you cannot be confident it is actually getting deployed to the endpoint? The amount of time I have to waste chasing rebuilt, newly added or mobile endpoints around in the console is ridiculous. Deployment via GPO/MSI would be a far better solution, but there appears no support for this.

    :5617
Reply
  • 0

    I find it bizarre this feature request isn't gettting more attention, it is the biggest flaw in an otherwise great product. It's a big enough flaw to make a lot of potential customers using AD sync bail out at eval stage. I purchased the product after a very rushed evaluation, and frankly couldn't believe it when I discovered SEC couldn't handle what appears to be such a simple function post purchase.

    What's the use in great endpoint protection if you cannot be confident it is actually getting deployed to the endpoint? The amount of time I have to waste chasing rebuilt, newly added or mobile endpoints around in the console is ridiculous. Deployment via GPO/MSI would be a far better solution, but there appears no support for this.

    :5617
Children
No Data
Unfiltered HTML