C
chemken
Guest
Dear Community,
i am currently working on always on vpn and we noticed some weird behavior on some of our machines.
With the Cmdlet
Get-WMIObject -Namespace root\cimv2\mdm\dmmap -Class MDM_VPNv2_01
or alternatively
Get-CimInstance -Namespace root\cimv2\mdm\dmmap -Class MDM_VPNv2_01
the querry takes around 3 minutes. These machines also show a not functional always on behavior. (The vpn itself works.)
However, if i querry something else like:
Get-WmiObject -Class Win32_ComputerSystem -Namespace root\cimv2
the result shows up immediately.
I already used ProcMon to see if something suspicious is happening, but I cannot notice. Only a few threads start and stop. No loops or anything else.
The problem occurs on several different devices as well as OS build versions of Windows 10.
Does anyone noticed already some kind of similar behavior? I am happy for every kind of idea
Greetings,
Christian
More...
i am currently working on always on vpn and we noticed some weird behavior on some of our machines.
With the Cmdlet
Get-WMIObject -Namespace root\cimv2\mdm\dmmap -Class MDM_VPNv2_01
or alternatively
Get-CimInstance -Namespace root\cimv2\mdm\dmmap -Class MDM_VPNv2_01
the querry takes around 3 minutes. These machines also show a not functional always on behavior. (The vpn itself works.)
However, if i querry something else like:
Get-WmiObject -Class Win32_ComputerSystem -Namespace root\cimv2
the result shows up immediately.
I already used ProcMon to see if something suspicious is happening, but I cannot notice. Only a few threads start and stop. No loops or anything else.
The problem occurs on several different devices as well as OS build versions of Windows 10.
Does anyone noticed already some kind of similar behavior? I am happy for every kind of idea
Greetings,
Christian
More...
