During general troubleshooting or SCCM(System Center Configuration Manager) troubleshooting at client side, we may need to intentionally corrupt or malfunction WMI(Windows Management Instrumentation). However its not recommended to modify/malfunction WMI.
As we know that WMI is heart of OS(Operating System) as well as of SCCM. If it gets corrupted, we need to fix it in order to run OS and depended application smoothly. WMI uses the Common Information Model (CIM) industry standard to represent systems, applications, networks, devices, and other managed components. CIM is developed and maintained by the Distributed Management Task Force(DMTF).
We can corrupt WMI by removing a namespace. CIMv2 is not of the critical namespace of WMI. So, it can delete it, we will get success to corrupt WMI. We can use below Powershell command to delete CIMv2 in order to corrupt WMI.
Get-WmiObject -computername localhost -query "Select * From __Namespace Where Name='CIMV2'" -Namespace "root" | Remove-WmiObject
Hope, this helps those who are looking for intentional corruption of WMI.
As we know that WMI is heart of OS(Operating System) as well as of SCCM. If it gets corrupted, we need to fix it in order to run OS and depended application smoothly. WMI uses the Common Information Model (CIM) industry standard to represent systems, applications, networks, devices, and other managed components. CIM is developed and maintained by the Distributed Management Task Force(DMTF).
We can corrupt WMI by removing a namespace. CIMv2 is not of the critical namespace of WMI. So, it can delete it, we will get success to corrupt WMI. We can use below Powershell command to delete CIMv2 in order to corrupt WMI.
Get-WmiObject -computername localhost -query "Select * From __Namespace Where Name='CIMV2'" -Namespace "root" | Remove-WmiObject
Hope, this helps those who are looking for intentional corruption of WMI.
