DL Appliance tab error "No instances of 'CIM_ComputerSystem' have been found" (4040716)

After running RUU 3.0.587 or newer, you receive am error when opening or using functions on the Appliance tab:

"No instances of 'CIM_ComputerSystem' have been found."

Stack Trace:

This has been identified as a defect, RR-101752 - DLXX00 - Sporadic Error "No instances of 'CIM_ComputerSystem' have been found" when opening Appliance Tab. Issue is due to LSI WMI object corruption. Issue is still being investigated by development.

This issue is resolved starting with Rapid Recovery 6.1.2. Please upgrade to the latest version of Rapid Recovery.

Pre 6.1.2 Solution:

Note:
* This solution requires a patch for RR-101752. Before applying the solution, please contact support for your build specific patch.
* If possible please upgrade to 6.1.1.137.
* This solution requires a reboot of the appliance.

1. Stop the Rapid Recovery Core Service.
2. Stop the DL Appliance SRM Web Service.
3. Install the patch:
   1. Open an elevated Powershell (or CMD).
   2. Change directory to the location of the patch msi and run the msi file.
   3. Be sure to uncheck Start service after installation?, we do not want to start the Core Service at this time.
4. Repair LSI WMI objects:
   1. Open an elevated Powershell (or CMD).
   2. Change directory to C:\LSI
   3. Run unregister.bat. This command removes the LSI WMI objects.
   4. Run compile_mofs_wmi.bat. This command adds back the LSI WMI objects.
5. Verify the repair is successful by running the attached script, DLApplianceLSIWMICheck in an elevated PowerShell window: 
   1. The script checks the basic functionality of the LSI namespace and logs the results in a log located in the user's Downloads folder. The log bears the name of the appliance on which the script runs and adds the result of each new run.
   2. Compare results to the attached result file example, KINGCOBRA01.good.txt. Check for any erros in results. Usually you will see them in the Class 'cim_computersystem' Specific Info section.
   3. If you do encounter errors, repeat step 4 until clear.
6. Extend memory quotas for WMI processes:
   1. Download the attached script, WMIQuotaChanges.ps1, open an elevated PowerShell, change directory to ps1 location, and run it.
   2. You will be prompted to back up the WMI repository, click Yes. Name and save file any where you like.
   3. Type 2, press Enter, type 2GB, and press Enter.
   4. Type 3, press Enter, type 1GB, and press Enter.
      
   5. Type q, press Enter, and click Yes to restart WMI services.
   6. Close PowerShell.
7. Reboot the appliance. After reboot open the Core Console, go the Appliance tab and verify it functions with out error.

Attached

• DLApplianceLSIWMICheck.ps1 (the script to check the health of the WMI Objects)
• KINGCOBRA01.bad.txt (log example with an error solved by the method above)
• KINGCOBRA01.good.txt (log example with no errors)
• WMIQuotaChanges.ps1 ( script to increase memory quotas for WMI)