Forum Discussion
ATA Client on a Server 2019 Domain Controller
MicrosoftPlease open a support case , and mentioned to the assigned engineer to add me to the thread as well.
We have some progress with the initial case, I want to make sure you are failing on the same thing.
Question: Do you have Windows hello for business installed there?
We have Windows Hello for Business deployed on our domain. The upgrade to 2019 broke that as well: WhfB works when off the network but not at the sites that have the upgraded DCs. Is that related somehow? We have an incident opened with MS support on this but have not got anywhere with it yet.
Doug,
Windows Hello and ATA are both broken on 2019 DC's. I have gotten word that a fix is coming in Feb and I was able to open a premier ticket and get a private hotfix to hold us over until the public fix comes out.
- EliOfek
Just to be clear, in this case lsass is borken, The Sensor just acts as a fast trigger for it. in theory it can happen even if the sensor is not installed. This is why we have to wait for the windows fix cycle.
Thanks Eli, have opened a support case via the Azure portal [seems to be some issue on the AATA portal with opening a case]
Forum has limitations on PM, so putting details directly here:
GMT +1 for me [Malta, EU]
Details of case from Azure Support Portal:
Case Name: 2019 DC's reboot after Sensor causes lsass.exe crash
Case ID: 118112725001888
Created: Tue, 27 Nov 2018 13:13:53- EliOfek
If you can share the case # in a private message, I will do my best to get this case prioritized.
What timezone are you located in?
No, do not have Windows Hello for Business configured yet.
- EliOfek
We need a support case with this one to have a secured workspace where we can exchange instructions and dump files to check exactly what happened.
