Is WMI reached EOL for Windows 10 21H2 version of IoT Enterprise LTSC ?
Heard that, the Windows Management Instrumentation Command-line (WMIC) reached End of Life (EOL). I mainly wanted to know and get key information on these queries - We are using Windows 10 OS 21H2 IoT Enterprise LTSC version (build 19044) on on of our product and building application on top of that Windows 10 OS 21H2 uses WMI component. So, is EOL WMI affect this Windows 10 21H2 LTSC Enterprise as well ? - If so, is there any official information available WMIC reached EOL for "Windows 10 - 21H2 IoT Enterprise LTSC" as well and should be replaced with powershell. Because "Windows 10 - 21H2 IoT Enterprise LTSC" has end of support / service till Jan 13th 2032. So, does WMI EOL really imacts this version of Windwso 10 - 21H2 IoT Enterprise LTSC ? nikita Windows10LTSCWindows 11 assigned access - setting kiosk mode over powershell and WMI
Hey guys, so currently as this article states, kiosk multi app mode in Intune for windows 11 is on the roadmap, but there is no ETA, when it comes live. https://techcommunity.microsoft.com/t5/windows-it-pro-blog/multi-app-kiosk-mode-now-available-in-windows-11/ba-p/3845558 I then tried as this article shows (https://learn.microsoft.com/en-us/windows/configuration/lock-down-windows-11-to-specific-apps to run the stated powershell script with my own configured XML file, as you can see here: $nameSpaceName="root\cimv2\mdm\dmmap" $className="MDM_AssignedAccess" $obj = Get-CimInstance -Namespace $namespaceName -ClassName $className Add-Type -AssemblyName System.Web $obj.Configuration = [System.Web.HttpUtility]::HtmlEncode (@" <?xml version="1.0" encoding="utf-8" ?> <AssignedAccessConfiguration xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config" xmlns:win11="http://schemas.microsoft.com/AssignedAccess/2022/config"> <Profiles> <Profile Id="dca70007-6874-49b3-930f-26ead1d85918"> <AllAppsList> <AllowedApps> <App AppUserModelId="Citrix.Workspace" rs5:AutoLaunch="true"> <App AppUserModelId="MSEdge" /> <App AppUserModelId="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App" /> <App AppUserModelId="Microsoft.Windows.Explorer" /> </AllowedApps> </AllAppsList> <win11:StartPins> <![CDATA[ {"pinnedList": [ {"desktopAppLink":"%ALLUSERSPROFILE%\\Microsoft\\Windows\\Start Menu\\Programs\\Citrix Workspace.lnk"}, {"desktopAppLink":"%ALLUSERSPROFILE%\\Microsoft\\Windows\\Start Menu\\Programs\\Microsoft Edge.lnk"}, {"packagedAppId":"windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel"}, {"desktopAppLink":"%APPDATA%\\Microsoft\\Windows\\Start Menu\\Programs\\File Explorer.lnk"}, {"packagedAppId":"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App"} ]} ]]> <win11:StartPins/> <Taskbar ShowTaskbar="true"/><Taskbar/> </Profile> </Profiles> <Configs> <Config> <AutoLogonAccount/> <DefaultProfile Id="{c374b80f-6aea-4c02-b1db-7bb1dfc4fe84}"/> </Config> </Configs> </AssignedAccessConfiguration> "@) Set-CimInstance -CimInstance $obj but im getting following errors: Get-CimInstance: C:\Users\michael.woerner\GitHub-Repo\Github_Work\Intune\Scripts\Kiosk-XML-WMI.ps1:3:8 Line | 3 | $obj = Get-CimInstance -Namespace $namespaceName -ClassName $classNam … | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Zugriff verweigert. InvalidOperation: C:\Users\michael.woerner\GitHub-Repo\Github_Work\Intune\Scripts\Kiosk-XML-WMI.ps1:5:1 Line | 5 | $obj.Configuration = [System.Web.HttpUtility]::HtmlEncode | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | The property 'Configuration' cannot be found on this object. Verify that the property exists and can be set. Set-CimInstance: C:\Users\michael.woerner\GitHub-Repo\Github_Work\Intune\Scripts\Kiosk-XML-WMI.ps1:44:30 Line | 44 | Set-CimInstance -CimInstance $obj | ~~~~ | Cannot bind argument to parameter 'InputObject' because it is null. Can you guys help me with that?WMI unknown account in security permissions
Hi everyone, We are using WMI on Azure AD computers to give our NAC system (PortNox) access to read a certain process in the client. We have an issue where for some reason the account was mistakenly deleted and in this case when opening the WMI CIMV2 namespace security we see that an unknown account remained in the security permissions. When I try to use PowerShell to remove the unknown account I get unknown error. Anyone has any idea what I can do to get out of this mess? Thanks in advance, Rahamim.
Retrieving node information in WMI causes memory leaks
Hi, Inquiry Summary Retrieving node information in WMI causes memory leaks [Environment] Execution Environment Microsoft Windows Server 2016 Datacenter 10.0.14393 N/A build 14393 Multiprocessor Free Application Build Environment Microsoft Windows Server 2012 R2 Standard Microsoft Visual Studio Professional 2015 Version 14.0.25420.01 Update 3 Visual C++ 2015 00322-50052-73614-AA667 Inquiries. A module created in VC++ has a daemon that gets the node information in WMI. This module is experiencing a memory leak. I created a test program to get the values of VirtualSize and WorkingSetSize repeatedly with reference to the following site The test program also showed a memory leak when I created https://docs.microsoft.com/en-us/windows/win32/wmisdk/example-creating-a-wmi-application Below are the results of 20,000 attempts. VirtualSize is 7340032 bytes, 702,728,736 bytes increase. ----- ... 0 wmitest.exe VirtualSize:57511936 WorkingSetSize:6836224 1 wmitest.exe VirtualSize:57511936 WorkingSetSize:7028736 2 wmitest.exe VirtualSize:57511936 WorkingSetSize:7036928 3 wmitest.exe VirtualSize:57511936 WorkingSetSize:7041024 4 wmitest.exe VirtualSize:57511936 WorkingSetSize:7041024 5 wmitest.exe VirtualSize:57511936 WorkingSetSize:7041024 6 wmitest.exe VirtualSize:57511936 WorkingSetSize:7045120 7 wmitest.exe VirtualSize:57511936 WorkingSetSize:7045120 8 wmitest.exe VirtualSize:57511936 WorkingSetSize:7045120 9 wmitest.exe VirtualSize:57511936 WorkingSetSize:7045120 1022 wmitest.exe VirtualSize:57511936 WorkingSetSize:7770112 1023 wmitest.exe VirtualSize:57511936 WorkingSetSize:7770112 1024 wmitest.exe VirtualSize:58560512 WorkingSetSize:7831552 1025 wmitest.exe VirtualSize:58560512 WorkingSetSize:7847936 : : 2798 wmitest.exe VirtualSize:58560512 WorkingSetSize:8470528 2799 wmitest.exe VirtualSize:58560512 WorkingSetSize:8536064 2800 wmitest.exe VirtualSize:60657664 WorkingSetSize:8650752 2801 wmitest.exe VirtualSize:60657664 WorkingSetSize:8654848 : : 9242 wmitest.exe VirtualSize:60657664 WorkingSetSize:10366976 9243 wmitest.exe VirtualSize:60657664 WorkingSetSize:10375168 9244 wmitest.exe VirtualSize:64851968 WorkingSetSize:10653696 9245 wmitest.exe VirtualSize:64851968 WorkingSetSize:10665984 : : 19997 wmitest.exe VirtualSize:64851968 WorkingSetSize:13864960 19998 wmitest.exe VirtualSize:64851968 WorkingSetSize:13864960 19999 wmitest.exe VirtualSize:64851968 WorkingSetSize:13864960 ----- [Questions] (1) Are there workarounds, bug information, HotFix, etc. for the above? (2) Is there anything I can do to help determine the cause of the problem?
