Further testing with firmware version 18.104 to me suggests it does rectify the DCOM aspect of this, but the WMI query that the server passes can easily break and then break the entire AD integration facility. The below i believe is the reason for it. they are using the IWbemServices::ExecQuery method In their code which if the data set is too large or the DC doesn't provide the information in a specific time means it just breaks the whole query. They need to be using the IEnumWbemClassObject::Next method. The below is an example of an error i've seen that shows the memory max being hit, i also receive others but they relate to errorcode 0x80041032, which then when looking at the article further below from microsoft explains the potential error and how to fix it. Which would require the Meraki coders to amend their code to use the "Next method". Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = ; User = nnn\Ouradmin; ClientProcessId = 2836; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\cimv2 : SELECT EventCode,InsertionStrings,RecordNumber FROM Win32_NTLogEvent WHERE Logfile = 'Security' AND EventType=4 AND (EventCode=540 OR EventCode=672 OR EventCode=4624 OR EventCode=4768) AND RecordNumber > 4100256909; ResultCode = 0x80041032; PossibleCause = Throttling Idle/stack Tasks in hitting Max Memory quota https://learn.microsoft.com/en-us/troubleshoot/windows-client/system-management-components/wmi-activity-event-5858-logged-with-resultcode-0x80041032 I think there are other issues as well as the above, as i cant get any Domain Controllers on server 2022 to pull user information at all despite them showing green on firmware 18.104. This could also be the above issue but im unable to tell for sure there isnt another issue influencing it.
... View more
