I have noticed something that might not be expected.
In environments where DSHeuristics is set, the "//XML/HealthcheckData" directly contains the DSHeuristics
This is the only value I have seen that is stored this way.
This behavior seems to have been around for at least 1 year.
I guess it should have been stored that way:
<?xml version="1.0" encoding="utf-8"?><HealthcheckData xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><EngineVersion>3.1.0.0</EngineVersion><GenerationDate>2023-13-09T09:09:09.0000009+09:00</GenerationDate><Level>Full</Level><MaturityLevel>1</MaturityLevel><DomainFQDN>customer.dom</DomainFQDN><NetBIOSName>customer</NetBIOSName><ForestFQDN>customer.dom</ForestFQDN>[...]<DSHeuristics>0000002001001</DSHeuristics>[...]
I have noticed something that might not be expected. In environments where DSHeuristics is set, the "//XML/HealthcheckData" directly contains the DSHeuristics
Here is an example:
<?xml version="1.0" encoding="utf-8"?><HealthcheckData xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" DSHeuristics="0000002001001">[...]
This is the only value I have seen that is stored this way. This behavior seems to have been around for at least 1 year.
I guess it should have been stored that way:
<?xml version="1.0" encoding="utf-8"?><HealthcheckData xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><EngineVersion>3.1.0.0</EngineVersion><GenerationDate>2023-13-09T09:09:09.0000009+09:00</GenerationDate><Level>Full</Level><MaturityLevel>1</MaturityLevel><DomainFQDN>customer.dom</DomainFQDN><NetBIOSName>customer</NetBIOSName><ForestFQDN>customer.dom</ForestFQDN>[...]<DSHeuristics>0000002001001</DSHeuristics>[...]