Home > Uncategorized > Use the MOFCOMP Utility to fix MED-V Error 7006

Use the MOFCOMP Utility to fix MED-V Error 7006


A WMI feature of MED-V v2 lets you configure your environment to detect certain network changes that might occur after MED-V workspaces are deployed and that can affect MED-V. The feature includes a component running in the guest operating system that is notified of network configuration changes on the host computer. It allows a non-Microsoft ESD or other application that is running in the guest to resolve to the same network endpoints that the host ESD or application resolves to.

This feature is only available if the virtual machine is configured for network address translation (NAT) mode. If the virtual machine is configured for BRIDGED mode, no change indications are generated.

If you are finding this feature is not functioning properly, please look for the following in the MED-V Guest event log:

Event Type:         Information

Event Source:     MEDV

Event Category:                Network Settings

Event ID:              7006

Detail: The rootccmNetworkConfig WMI namespace does not exist. Network configuration change events will not be processed.

You will get this error without the SCCM NAT patch for MED-V installed. More information can be found here: http://support.microsoft.com/kb/2278056

If you are not using SCCM or if you are using SCCM, have installed the SCCM NAT patch and are still getting this error, you will need to open up the workspace to a command prompt or Notepad or a Text Editor using administrative rights. Using Notepad or another text editor, create a Managed Object Format (MOF) file that will look for the network configuration changes that you want to monitor. Use the following code snippet:

 

#pragma namespace (“\\.\root\ccm\NetworkConfig”)

 class CCM_IPConfig

{

    [NotNull: ToInstance ToSubClass] uint32 AddressFamily; // AF_INET, AF_INET6

    [Key, NotNull: ToInstance ToSubClass] string IPAddress; // IPv4 or IPv6 address

    [NotNull: ToInstance ToSubClass] string SubnetMask; // IPv4 subnet mask

};

 

class CCM_NetworkAdapter

{

    [Key, NotNull: ToInstance ToSubClass] string Name;

    [NotNull: ToInstance ToSubClass] uint32 DHCPEnabled = 0;

    [NotNull: ToInstance ToSubClass] uint32 Quarantined = 0; // To check if it is quarantined.

    CCM_IPConfig IPConfigInfo[];

};

 class CCM_NetworkAdapters

{

    [NotNull: ToInstance ToSubClass] String ProviderName; // MED-V or other provider

    CCM_NetworkAdapter AdaptersInfo[];

};

 

Save the file in the %SYSTEMROOT%System32wbemmof directory of the guest OS as medvnet.mof.

Compile the MOF file using MOFCOMP.EXE in the guest.

Restart the Guest OS.

You can then use the WMIC command to verify the namespace:

Categories: Uncategorized Tags: , , ,
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: