ERROR:
Cannot connect to WMI provider. You do not have permission or the server is unreachable.
Note that you can only manage SQL Server 2005 and later servers with SQL Server Config-
-uration Manager. Invalid namespace 0x8004100e

OCCURANCE:
This error occurs when you click on Configuration Manager after installation of virtualized package.

FIX

CREATE PACKAGE:

1. On clean machine, install ThinApp.
2. Run Prescan.
3. Install .Net Framework 2.0.
4. Install MS SQL Server 2005 Express.
5. On Registration screen, uncheck "Hide Advanced Configuration Options."
6. On feature Selection screen, select the features you wish to install.
7. On Authentication screen, select Windows Authentication Mode.
8. Complete installation.
9. Stop SQLSERVER services (go to start->Run->type Services.msc in run window, Select MySql from listed services and stop it)
10. Run Postscan.
11. Save the project
12. To enable cmd.exe, in package.ini, put a semicolon in front of Disabl1=1 under - cmd.exe
13. Build the project with msi.

COPY PACKAGE:

1. Copy the package to the C:\ drive on a clean machine.
2. Install using msi.

TEST PACKAGE:

1. Launch virtualized Cmd from the Bin folder.
2. To get rid of the error of “WMI provider”, run the following command in the virtualized command prompt:

mofcomp " C:\Microsoft .NET Framework 2.0\%ProgramFilesDir%\Microsoft SQL Server\90\Shared\ sqlmgmproviderxpsp2up.mof"

3. You will receive confirmation that the .MOF file has been successfully parsed.
4. In Virtualized CMD, Run command “Services.msc”.
5. A virtualized copy of Servcies.msc will open and you will be able to see the SQLSERVER Service running.

NOTE: The virtualized MYSQL service will only be visible in the virtualized Servcies.msc. If you goto the native
Servcies.msc, you will not see this service there.

6. Goto Service “SQL Server VSS writer”. Right click and start this service.
7. Scroll down the services list and find the service ” Windows Management Instrumentation”.
8. This service will be already started. Right click and Restart this service.
9. Now, close Virtual CMD and open MS SQL Server Configuration Manager.
10. It runs fine without any errors.

Cheers!!

Maddy
(Request: Please award points if helpful/answered and mark answered for others to refer.)

Read more at: http://communities.vmware.com/message/1525322