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

Reinstall Sophos after failed installation automaticaly

4ndr3

Hello

I want to ask, if someone knows if it is possible to configure SEC, that it trys to install the endpoint security again and again(for example every 30 minutes), if the first automatic installation failed until Sophos is installed on the PC

Problem is, we install our PCs with SCCM and after the Installation finisched and the PC is added to our AD, there is many other Software, that will be installed by SCCM. Sophos syncs every 60 minutes with the AD and trys to install Endpoint Security on new PCs. In this time mostly other Software installations are in progress and the Sophos installation failes.

I know, that it is possible to install the Sophos Client via SCCM, but we want to outsource our SCCM Server and after that, the SCCM Server wouldn't have access to the Sophos Server.

:35843


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

    We are having the same issue.

    Our understanding for the sync feature would be to allow us to ensure that if a computer exists in AD, it would automatically be protected via this feature.

    Our situation (that commonly happens), is that the computer is off for a period of time, and that is why the install attempt failed.  Once the computer comes back online, we want to ensure protection is added.   This quit after 1 attempt is no way for your protection to stay compliant within the enterprise.

    I understand not re-trying every machine in the domain every 5 minutes, but a retry interval should be implemented, perhaps adding a front end check that retries if it failed due to unable to connect, or checks for a connection before retrying, or something similar.   Failing to protect a computer just because it was off at the first try is no way to operate a "Security" product.

    :36661
Reply
  • 0

    We are having the same issue.

    Our understanding for the sync feature would be to allow us to ensure that if a computer exists in AD, it would automatically be protected via this feature.

    Our situation (that commonly happens), is that the computer is off for a period of time, and that is why the install attempt failed.  Once the computer comes back online, we want to ensure protection is added.   This quit after 1 attempt is no way for your protection to stay compliant within the enterprise.

    I understand not re-trying every machine in the domain every 5 minutes, but a retry interval should be implemented, perhaps adding a front end check that retries if it failed due to unable to connect, or checks for a connection before retrying, or something similar.   Failing to protect a computer just because it was off at the first try is no way to operate a "Security" product.

    :36661
Children
No Data