I am attempting to install the Exchange 2007 SP1 ManagementTools on a Windows Vista SP1 32-bit workstation. I am using the 32-bit version of Exchange 2007 SP1.I haveread and installed the prequisites including PowerShell, MMC 3.0 and .NET 2.0. This is the error that I am getting:"This computer is running Windows Vista and has not been assigned an IPv4 address. Check the network configuration. IPv6 is only supported in Exchange Server 2007 Service Pack 1 when it is installed on a computer running Windows Server 2008 that has both IPv4 and IPv6 enabled. See http://go.microsoft.com/fwlink/?LinkId=102391 for more details."This is a laptop and there are 2 physical adapters, one wired Gigabit and a wireless adapter. I also have a Cisco VPN Client adapter, a GSM, and 3G dial-up adapters. I was using a DHCP-assigned address for the wired connection and IPv6 was disabled, but I have tried all possible combinations of assigning static IPv4 addresses, and enabling or disabling IPv6 on the adapters. From a previous installation problem that I had, I also tried disabling IPv6, assigned static IPv4 addresses, and added entries for this address in the hosts file that pointed to the workstation's name.Any assistance would be appreciated.

Hi Jonathan,Well, two things I would say here...~ Uninstall Broadcom ASF Management software for Gigabit and try to install Management Tools, I saw somewhere that, this is the known issue.~ Disable IPv6 on your Windows Vista from registry too as per below article and try to install Management Tools...How to disable certain Internet Protocol version 6 (IPv6) components in Windows Vistahttp://support.microsoft.com/kb/929852Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Hi, We can try the steps below to troubleshoot the issue. 1. First please try to patch .net framework 2.0 sp1. 2. Please check and remove the trunking configuration on the Broadcom NIC and rebooting. 3. Please disable wireless adapters. 4. Please Started the remote registry service, uninstalled the Broadcom Advanced Application Suite, reregistered WMI using the following script:@echo offsc config winmgmt start= disablednet stop winmgmt /y%systemdrive%cd %windir%\system32\wbemif exist repository.old rmdir /s/q repository.old rename repository repository.old for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s wmiprvse /regserver winmgmt /regserver net start winmgmt 5. Please try to disjoin the computer and re-join it to the domain and then check the issue. Regards, Xiu Regards, Xiu

Thank you Amit and Xiu for your responses, but none of these suggestions have allowed the Management Tools to be installed. Xiu, the .NET link above is not for Vista, but I already have that SP. Here are the additional steps I have taken: I did see the same post about the Broadcom ASF Management software, but I did not have that installed, but removed the only Broadcom software that I did have. I disabled IPv6 using the registry key shown in KB929852. I removed the only other software that created logical network adapters, the Cisco VPN Client and the AT&T 3G/GSM software. I disabled my Bluetooth and Wifi adpaters in the BIOS. The only adapter shown in Network Connections is now the wired ethernet adapter. I used the script shown above to re-register WMI. I removed the computer from the domain, rebootedand re-joined it to the domain. The error message has not changed, and is frustratingly general about what the problem is. Any additional suggestions would be appreciated.

Hi, 1. Please try to manually assign IPV4 address for Windows Vista. 2. Please ensure that remote registry service and Windows Management Instrumentation services have been started. 3. Then please try to re-install Exchange Management Tools. (Note: How to Install Exchange 2007 SP1 Prerequisites on Windows Server 2008 or Windows Vista http://technet.microsoft.com/en-us/library/bb691354(EXCHG.80).aspx ) 4. If failed then please check logs in ExchangePreReqs folder and then post the error information here. 5. And then please run WMIDiag to check if you have WMI related error. Besides, have you tried to install Exchange Management shell on other Windows Vista based computer?Moreover,Id like to share document below with you: Domain Name System Client Behavior in Windows Vista http://technet.microsoft.com/en-us/library/bb727035.aspx Microsoft Windows Vista includes both Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) protocol stacks that are installed and enabled by default. Domain Name System (DNS) name queries and registrations can now involve both IPv4 address records (A records) and IPv6 address records (AAAA records). Regards, Xiu

Xiu,I have manually configured an IP Address for the only network adapter on this workstation. The Remote Registry Service was set to manual, but I have started the service manually. The WMI service is started. I ran setup again, with the same result. Here is the PreReqs text log: 08:21:23.156:StartingCollectingDataphase. 08:21:42.866:Error(Providerloadfailure)onWMIsearchSELECT__RELPATH,CaptionFROMWin32_NetworkAdapterWHEREAdapterTypeID='0'onscoperoot\cimv2onserver,skippingobject. 08:21:44.005:CompletedCollectingDataphase. 08:21:44.052:Error(Rulename'PreReq_szNodeName'referencedbyrule'PreReq_iPhysicalNodesInCluster'ininputfileisnotdefined)informatofrulesinconfigurationfile. 08:21:44.052:Error(Rulename'PreReq_szNodeMailboxInstallation'referencedbyrule'PreReq_iPhysicalNodesWithExchangeInCluster'ininputfileisnotdefined)informatofrulesinconfigurationfile. 08:21:44.114:StartingPostprocessingRulesphase. 08:21:44.145:CompletedPostprocessingRulesphase. The XML file is too big to paste in as code. I can find a way to host if it isneeded.Here is the WMIDiag Log: 5308410:28:34(0)**-----------------------------------------------------WMIREPORT:BEGIN---------------------------------------------------------- 5308510:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5308610:28:34(0)** 5308710:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5308810:28:34(0)**WindowsVista-Servicepack1-32-bit(6001)-User'DOMAIN\USERNAME'oncomputer'COMPUTERNAME'. 5308910:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5309010:28:34(0)**INFO:Environment:..................................................................................................1ITEM(S)! 5309110:28:34(0)**INFO:=>2incorrectshutdown(s)detectedon: 5309210:28:34(0)**-Shutdownon10February200916:04:30(GMT-0). 5309310:28:34(0)**-Shutdownon29January200917:33:03(GMT-0). 5309410:28:34(0)** 5309510:28:34(0)**Systemdrive:.......................................................................................................C:(Disk#0Partition#1). 5309610:28:34(0)**Drivetype:.........................................................................................................IDE(ST9120411ASGATADevice). 5309710:28:34(0)**TherearenomissingWMIsystemfiles:..............................................................................OK. 5309810:28:34(0)**TherearenomissingWMIrepositoryfiles:..........................................................................OK. 5309910:28:34(0)**WMIrepositorystate:...............................................................................................CONSISTENT. 5310010:28:34(0)**BEFORErunningWMIDiag: 5310110:28:34(0)**TheWMIrepositoryhasasizeof:...................................................................................41MB. 5310210:28:34(0)**-Diskfreespaceon'C:':..........................................................................................72247MB. 5310310:28:34(0)**-INDEX.BTR,8773632bytes,2/18/200910:09:10AM 5310410:28:34(0)**-MAPPING1.MAP,116912bytes,2/18/200910:09:10AM 5310510:28:34(0)**-MAPPING2.MAP,116912bytes,2/18/200910:08:40AM 5310610:28:34(0)**-OBJECTS.DATA,33800192bytes,2/18/200910:09:10AM 5310710:28:34(0)**AFTERrunningWMIDiag: 5310810:28:34(0)**TheWMIrepositoryhasasizeof:...................................................................................41MB. 5310910:28:34(0)**-Diskfreespaceon'C:':..........................................................................................72966MB. 5311010:28:34(0)**-INDEX.BTR,8773632bytes,2/18/200910:28:10AM 5311110:28:34(0)**-MAPPING1.MAP,116912bytes,2/18/200910:28:10AM 5311210:28:34(0)**-MAPPING2.MAP,116912bytes,2/18/200910:27:40AM 5311310:28:34(0)**-OBJECTS.DATA,33800192bytes,2/18/200910:28:10AM 5311410:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5311510:28:34(0)**INFO:WindowsFirewallstatus:......................................................................................ENABLED. 5311610:28:34(0)**WindowsFirewallProfile:...........................................................................................DOMAIN. 5311710:28:34(0)**InboundconnectionsthatdonotmatcharuleBLOCKED:...............................................................ENABLED. 5311810:28:34(0)**=>ThiswillpreventanyWMIremoteconnectivitytothiscomputerexcept 5311910:28:34(0)**ifthefollowingthreeinboundrulesareENABLEDandnon-BLOCKING: 5312010:28:34(0)**-'WindowsManagementInstrumentation(DCOM-In)' 5312110:28:34(0)**-'WindowsManagementInstrumentation(WMI-In)' 5312210:28:34(0)**-'WindowsManagementInstrumentation(ASync-In)' 5312310:28:34(0)**Verifythereportedstatusforeachofthesethreeinboundrulesbelow. 5312410:28:34(0)** 5312510:28:34(0)**WindowsFirewall'WindowsManagementInstrumentation(WMI)'GROUPrule:.............................................ENABLED. 5312610:28:34(0)**WindowsFirewall'WindowsManagementInstrumentation(DCOM-In)'rule:...............................................ENABLED. 5312710:28:34(0)**WindowsFirewall'WindowsManagementInstrumentation(WMI-In)'rule:................................................ENABLED. 5312810:28:34(0)**WindowsFirewall'WindowsManagementInstrumentation(WMI-Out)'rule:...............................................ENABLED. 5312910:28:34(0)**WindowsFirewall'WindowsManagementInstrumentation(ASync-In)'rule:..............................................ENABLED. 5313010:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5313110:28:34(0)**DCOMStatus:........................................................................................................OK. 5313210:28:34(0)**WMIregistrysetup:.................................................................................................OK. 5313310:28:34(0)**INFO:WMIservicehasdependents:...................................................................................3SERVICE(S)! 5313410:28:34(0)**-SecurityCenter(WSCSVC,StartMode='Automatic') 5313510:28:34(0)**-InternetConnectionSharing(ICS)(SHAREDACCESS,StartMode='Automatic') 5313610:28:34(0)**-SMSAgentHost(CCMEXEC,StartMode='Automatic') 5313710:28:34(0)**=>IftheWMIserviceisstopped,thelistedservice(s)willhavetobestoppedaswell. 5313810:28:34(0)**Note:Iftheserviceismarkedwith(*),itmeansthattheservice/applicationusesWMIbut 5313910:28:34(0)**thereisnoharddependencyonWMI.However,iftheWMIserviceisstopped, 5314010:28:34(0)**thiscanpreventtheservice/applicationtoworkasexpected. 5314110:28:34(0)** 5314210:28:34(0)**RPCSSservice:......................................................................................................OK(Alreadystarted). 5314310:28:34(0)**WINMGMTservice:....................................................................................................OK(Alreadystarted). 5314410:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5314510:28:34(0)**WMIserviceDCOMsetup:.............................................................................................OK. 5314610:28:34(0)**WMIcomponentsDCOMregistrations:..................................................................................OK. 5314710:28:34(0)**WMIProgIDregistrations:...........................................................................................OK. 5314810:28:34(0)**WMIproviderDCOMregistrations:....................................................................................OK. 5314910:28:34(0)**WMIproviderCIMregistrations:.....................................................................................OK. 5315010:28:34(0)**WMIproviderCLSIDs:................................................................................................OK. 5315110:28:34(0)**WMIprovidersEXE/DLLavailability:.................................................................................OK. 5315210:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5315310:28:34(0)**INFO:UserAccountControl(UAC):...................................................................................DISABLED. 5315410:28:34(0)**INFO:LocalAccountFiltering:......................................................................................ENABLED. 5315510:28:34(0)**=>WMItasksremotelyaccessingWMIinformationonthiscomputerandrequiringAdministrative 5315610:28:34(0)**privilegesMUSTuseaDOMAINaccountpartoftheLocalAdministratorsgroupofthiscomputer 5315710:28:34(0)**toensurethatadministrativeprivilegesaregranted.IfaLocalUseraccountisusedforremote 5315810:28:34(0)**accesses,itwillbereducedtoaplainuser(filteredtoken),evenifitispartoftheLocalAdministratorsgroup. 5315910:28:34(0)** 5316010:28:34(0)**OverallDCOMsecuritystatus:.......................................................................................OK. 5316110:28:34(0)**OverallWMIsecuritystatus:........................................................................................OK. 5316210:28:34(0)**-Startedat'Root'-------------------------------------------------------------------------------------------------------------- 5316310:28:34(0)**INFO:WMIpermanentSUBSCRIPTION(S):................................................................................6. 5316410:28:34(0)**-ROOT/SUBSCRIPTION,CommandLineEventConsumer.Name="BVTConsumer". 5316510:28:34(0)**'SELECT*FROM__InstanceModificationEventWITHIN60WHERETargetInstanceISA"Win32_Processor"ANDTargetInstance.LoadPercentage>99' 5316610:28:34(0)**-ROOT/SUBSCRIPTION,NTEventLogEventConsumer.Name="SCMEventLogConsumer". 5316710:28:34(0)**'select*fromMSFT_SCMEventLogEvent' 5316810:28:34(0)**-ROOT/CCM/POLICY,CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}". 5316910:28:34(0)**'SELECT*FROM__NamespaceCreationEvent' 5317010:28:34(0)**-ROOT/CCM/POLICY,CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}". 5317110:28:34(0)**'SELECT*FROM__ClassOperationEventWHERETargetClassISA"CCM_Policy_EmbeddedObject"' 5317210:28:34(0)**-ROOT/CCM/POLICY,CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}". 5317310:28:34(0)**'SELECT*FROM__ClassOperationEventWHERETargetClassISA"CCM_Policy_Config"' 5317410:28:34(0)**-ROOT/CCM/POLICY,CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}". 5317510:28:34(0)**'SELECT*FROM__ClassOperationEventWHERETargetClassISA"CCM_Policy"' 5317610:28:34(0)** 5317710:28:34(0)**WMITIMERinstruction(s):...........................................................................................NONE. 5317810:28:34(0)**INFO:WMInamespace(s)requiringPACKETPRIVACY:....................................................................5NAMESPACE(S)! 5317910:28:34(0)**-ROOT/CIMV2/SECURITY/MICROSOFTTPM. 5318010:28:34(0)**-ROOT/CIMV2/TERMINALSERVICES. 5318110:28:34(0)**-ROOT/MICROSOFTIISV2. 5318210:28:34(0)**-ROOT/WEBADMINISTRATION. 5318310:28:34(0)**-ROOT/SERVICEMODEL. 5318410:28:34(0)**=>Whenremotelyconnecting,thenamespace(s)listedrequire(s)theWMIclientto 5318510:28:34(0)**useanencryptedconnectionbyspecifyingthePACKETPRIVACYauthenticationlevel. 5318610:28:34(0)**(RPC_C_AUTHN_LEVEL_PKT_PRIVACYorPktPrivacyflags) 5318710:28:34(0)**i.e.'WMIC.EXE/NODE:"COMPUTERNAME"/AUTHLEVEL:Pktprivacy/NAMESPACE:\\ROOT\SERVICEMODELClass__SystemSecurity' 5318810:28:34(0)** 5318910:28:34(0)**WMIMONIKERCONNECTIONS:............................................................................................OK. 5319010:28:34(0)**WMICONNECTIONS:....................................................................................................OK. 5319110:28:34(1)!!ERROR:WMIGEToperationerrorsreported:...........................................................................2ERROR(S)! 5319210:28:34(0)**-Root/CIMV2,Win32_PerfFormattedData_TermService_TerminalServices,0x80041002-(WBEM_E_NOT_FOUND)Objectcannotbefound. 5319310:28:34(0)**MOFRegistration:'WMIinformationnotavailable(ThiscouldbethecaseforanexternalapplicationorathirdpartyWMIprovider)' 5319410:28:34(0)**-Root/CIMV2,Win32_PerfRawData_TermService_TerminalServices,0x80041002-(WBEM_E_NOT_FOUND)Objectcannotbefound. 5319510:28:34(0)**MOFRegistration:'WMIinformationnotavailable(ThiscouldbethecaseforanexternalapplicationorathirdpartyWMIprovider)' 5319610:28:34(0)**=>WhenaWMIperformanceclassismissing(i.e.'Win32_PerfRawData_TermService_TerminalServices'),itisgenerallydueto 5319710:28:34(0)**alackofbufferrefreshoftheWMIclassproviderexposingtheWMIperformancecounters. 5319810:28:34(0)**YoucanrefreshtheWMIclassproviderbufferwiththefollowingcommand: 5319910:28:34(0)** 5320010:28:34(0)**i.e.'WINMGMT.EXE/SYNCPERF' 5320110:28:34(0)** 5320210:28:34(0)**WMIMOFrepresentations:............................................................................................OK. 5320310:28:34(0)**WMIQUALIFIERaccessoperations:....................................................................................OK. 5320410:28:34(0)**WMIENUMERATIONoperations:.........................................................................................OK. 5320510:28:34(1)!!ERROR:WMIEXECQUERYoperationerrorsreported:.....................................................................1ERROR(S)! 5320610:28:34(0)**-Root/CIMV2,Select*FromWin32_NetworkAdapterWHEREAdapterTypeISNOTNULLANDAdapterType!="WideAreaNetwork(WAN)"ANDDescription!="PacketSchedulerMiniport",0x80041013-(WBEM_E_PROVIDER_LOAD_FAILURE)COMcannotlocateaproviderreferencedintheschema. 5320710:28:34(0)** 5320810:28:34(0)**WMIGETVALUEoperations:...........................................................................................OK. 5320910:28:34(0)**WMIWRITEoperations:...............................................................................................NOTTESTED. 5321010:28:34(0)**WMIPUToperations:.................................................................................................NOTTESTED. 5321110:28:34(0)**WMIDELETEoperations:..............................................................................................NOTTESTED. 5321210:28:34(0)**WMIstaticinstancesretrieved:.....................................................................................5363. 5321310:28:34(0)**WMIdynamicinstancesretrieved:....................................................................................0. 5321410:28:34(0)**WMIinstancerequestcancellations(tolimitperformanceimpact):...................................................3. 5321510:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5321610:28:34(0)**#ofEventLogeventsBEFOREWMIDiagexecutionsincethelast20day(s): 5321710:28:34(0)**DCOM:.............................................................................................................0. 5321810:28:34(0)**WINMGMT:..........................................................................................................0. 5321910:28:34(0)**WMIADAPTER:.......................................................................................................0. 5322010:28:34(0)** 5322110:28:34(0)**#ofadditionalEventLogeventsAFTERWMIDiagexecution: 5322210:28:34(0)**DCOM:.............................................................................................................0. 5322310:28:34(0)**WINMGMT:..........................................................................................................0. 5322410:28:34(0)**WMIADAPTER:.......................................................................................................0. 5322510:28:34(0)** 5322610:28:34(0)**2error(s)0x80041002-(WBEM_E_NOT_FOUND)Objectcannotbefound 5322710:28:34(0)**=>ThiserroristypicallyaWMIerror.ThisWMIerrorisdueto: 5322810:28:34(0)**-amissingWMIclassdefinitionorobject. 5322910:28:34(0)**(SeeanyGET,ENUMERATION,EXECQUERYandGETVALUEoperationfailures). 5323010:28:34(0)**Youcancorrectthemissingclassdefinitionsby: 5323110:28:34(0)**-ManuallyrecompilingtheMOFfile(s)withthe'MOFCOMP<FileName.MOF>'command. 5323210:28:34(0)**Note:YoucanbuildalistofclassesinrelationwiththeirWMIproviderandMOFfilewithWMIDiag. 5323310:28:34(0)**(ThislistcanbebuiltonasimilarandworkingWMIWindowsinstallation) 5323410:28:34(0)**Thefollowingcommandlinemustbeused: 5323510:28:34(0)**i.e.'WMIDiagCorrelateClassAndProvider' 5323610:28:34(0)**Note:WhenaWMIperformanceclassismissing,youcanmanuallyresynchronizeperformancecounters 5323710:28:34(0)**withWMIbystartingtheADAPprocess. 5323810:28:34(0)**-aWMIrepositorycorruption. 5323910:28:34(0)**Insuchacase,youmustrerunWMIDiagwith'WriteInRepository'parameter 5324010:28:34(0)**tovalidatetheWMIrepositoryoperations. 5324110:28:34(0)**Note:ENSUREyouareanadministratorwithFULLaccesstoWMIEVERYnamespacesofthecomputerbefore 5324210:28:34(0)**executingtheWriteInRepositorycommand.TowritetemporarydatafromtheRootnamespace,use: 5324310:28:34(0)**i.e.'WMIDiagWriteInRepository=Root' 5324410:28:34(0)**-IftheWriteInRepositorycommandfails,whilebeinganAdministratorwithALLaccessestoALLnamespaces 5324510:28:34(0)**theWMIrepositorymustbereconstructed. 5324610:28:34(0)**Note:TheWMIrepositoryreconstructionrequirestolocateallMOFfilesneededtorebuildtherepository, 5324710:28:34(0)**otherwisesomeapplicationsmayfailafterthereconstruction. 5324810:28:34(0)**Thiscanbeachievedwiththefollowingcommand: 5324910:28:34(0)**i.e.'WMIDiagShowMOFErrors' 5325010:28:34(0)**Note:TherepositoryreconstructionmustbeaLASTRESORTsolutionandONLYafterexecuting 5325110:28:34(0)**ALLfixespreviouslymentioned. 5325210:28:34(2)!!WARNING:StaticinformationstoredbyexternalapplicationsintherepositorywillbeLOST!(i.e.SMSInventory) 5325310:28:34(0)** 5325410:28:34(0)** 5325510:28:34(0)**1error(s)0x80041013-(WBEM_E_PROVIDER_LOAD_FAILURE)COMcannotlocateaproviderreferencedintheschema 5325610:28:34(0)**=>Thiserroristypicallyduetothefollowingmajorreasons: 5325710:28:34(0)**-TheapplicationqueriedbytheWMIproviderisnotinstalled,notavailableornotrunning 5325810:28:34(0)**atthetimeoftherequestwasmade.Thiserrorcanalsobegeneratedbecause 5325910:28:34(0)**theapplicationsupportingtheprovidershasbeenuninstalled. 5326010:28:34(0)**-SomeWMIproviders(i.e.RSOPPlanningMode,Exchange2003)areimplementedasaWMIservice. 5326110:28:34(0)**Makesuretherequiredservicesaresuccessfullystarted. 5326210:28:34(0)**-TheWMIproviderbinaryfilesarenotaccessible(i.e.accessdeniedACL). 5326310:28:34(0)**-AWMIproviderregistrationproblemattheCIMlevel(MOFCOMP.EXE)orattheCOMlevel(REGSVR32.EXE). 5326410:28:34(0)**Youmustre-registertheWMIproviderbyrecompilingitsassociatedMOFfilewithMOFCOMP.EXE 5326510:28:34(0)**Note:-IftheWMIproviderDLLCIMandCOMregistrationsarecorrect,thiserrorcan 5326610:28:34(0)**bereturnedbecausetheproviderhasadependencyonanotherDLLthatcannotbe 5326710:28:34(0)**loaded(missingorbadDLL) 5326810:28:34(0)**-DependenciescanbefoundwiththeDEPENDS.EXEtoolcomingwiththe 5326910:28:34(0)**WindowsXPandWindows2003SupportTools.Thecommandlineisasfollows: 5327010:28:34(0)**i.e.DEPENDS.EXE<PATH><Provider.DLL> 5327110:28:34(0)**=>WhenaWMIproviderfailstoload,itispossibletotracetheproviderloadprocessby 5327210:28:34(0)**submitting,viaWBEMTESTandasynchronously,thefollowingWMIeventquery: 5327310:28:34(0)**'Select*FromMSFT_WmiSelfEvent' 5327410:28:34(0)**ThenyoucantracethefollowingWMIevents: 5327510:28:34(0)**-Msft_WmiProvider_ComServerLoadOperationEvent 5327610:28:34(0)**-Msft_WmiProvider_InitializationOperationEvent 5327710:28:34(0)**-Msft_WmiProvider_LoadOperationEvent 5327810:28:34(0)**anddependingontheWMIoperationexecuted,youcantracethefollowingWMIevents: 5327910:28:34(0)**i.e.foranenumeration: 5328010:28:34(0)**-Msft_WmiProvider_CreateInstanceEnumAsyncEvent_PreandMsft_WmiProvider_CreateInstanceEnumAsyncEvent_Post 5328110:28:34(0)**i.e.foraputoperation: 5328210:28:34(0)**-Msft_WmiProvider_PutInstanceAsyncEvent_PreandMsft_WmiProvider_PutInstanceAsyncEvent_Post 5328310:28:34(0)** 5328410:28:34(0)**=>Ifthesoftwarehasbeende-installedintentionally,thenthisinformationmustbe 5328510:28:34(0)**removedfromtheWMIrepository.Youcanusethe'WMIC.EXE'commandtoremovetheprovider 5328610:28:34(0)**registrationdataanditssetofassociatedclasses. 5328710:28:34(0)**=>Tocorrectthissituation,youcan: 5328810:28:34(0)**-Installorstarttheapplicationsupportingtheseproviders. 5328910:28:34(0)**-RegistertheprovidersinCIM(MOFCOMP)orDCOM(REGSVR32). 5329010:28:34(0)**Note:Inthiscasetheprovidershouldalsobelistedinthe'missingWMI 5329110:28:34(0)**providerDCOMregistrations'orinthe'missingWMIproviderfiles'section. 5329210:28:34(2)!!WARNING:Re-registeringwithREGSVR32.EXEallDLLfrom'C:\WINDOWS\SYSTEM32\WBEM\' 5329310:28:34(0)**maynotsolvetheproblemastheDLLsupportingtheWMIclass(es) 5329410:28:34(0)**canbelocatedinadifferentfolder. 5329510:28:34(0)**YoumustrefertotheclassnametodeterminethesoftwaredeliveringtherelatedDLL. 5329610:28:34(0)** 5329710:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5329810:28:34(0)**WMIRegistrykeysetup:.............................................................................................OK. 5329910:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5330010:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5330110:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5330210:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5330310:28:34(0)** 5330410:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5330510:28:34(0)**------------------------------------------------------WMIREPORT:END----------------------------------------------------------- 5330610:28:34(0)**---------------------------------------------------------------------------------------------------------------------------------- 5330710:28:34(0)** 5330810:28:34(0)**ERROR:WMIDiagdetectedissuesthatcouldpreventWMItoworkproperly!.Check'C:\USERS\USERNAME\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0_VISTA.CLI.SP1.32_COMPUTERNAME_2009.02.18_10.09.30.LOG'fordetails. 5330910:28:34(0)** 5331010:28:34(0)**WMIDiagv2.0endedonWednesday,February18,2009at10:28(W:111E:9S:1).I have not tried installing on other Vista computers.

I have resolved this problem by continuing down the path that Xia started. A co-worker looked at the output from WMIDiag and suggested rebuilding the repository. I stopped WMI service, renamed the C:\Windows\System32\wbem\Repository folder and started the WMI service. Then ran "winmgmt /salvagerepository" from a command line. After these steps, setup was able to run properly. Thank youfor you assistance.

Hi, Glad to hear it works now. Besides, Id like to share with you some information about WMI Repository. We always say that the last thing during troubleshoot WMI related issue is to rebuild the entire Repository. Because there are some risks involved in wiping out and replacing the Repository. For example, the WMI Repository is primarily a storehouse for meta-information about WMI itself. However, some static class data can be (and often is) stored in the Repository as well. If you rebuild the Repository all that data will be lost. Admittedly, this will not cause problems for most people, but it is a possibility. So next time, if you encounter any other WMI related issue, I recommend you to read document below and try the steps in the document first and then to consider if you need to backup and then to rebuild WMI Repository. WMI Isn't Working! http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx Backup or restore the WMI repository http://technet.microsoft.com/en-us/library/cc780894.aspx Regards, Xiu