2.236 - sensor fails to start

[robmacf9108931]

Is anyone else seeing the Azure ATP Sensor service fail to start on 2.236? I have delayed update on half of our sensors; all those running 2.235 are OK.

Machines running 2.236 are not OK ("Failed to communicate with configured domain controllers" in Microsoft.Tri.Sensor-Errors.log)

Also interested on how I can block auto-update on the machines still running 2.235 while I open a support ticket.

[#2]

I am not aware of any changes in 2.236 that can cause this.
There is no option for you to delay the updates beyond 72 hours.
You mentioned that 2.235 sensors are still running correctly, can you restart some of them without upgrading to check if they are still able to start in 2.235 ?
It's possible that the issue is with starting after something environmental changed, and the upgrade to 2.236 just forced a restart.
If 2.235 will be able to restart without issues, that will give us a clue that maybe it is something related to 2.236.

[#3]

I now have some sensors starting on 2.236. It could be an environment issue as you suspect. I'll work on the servers experiencing the failure with support.