sms: wbem_e_provider_load_failure causing odd sms client issues...

these are just as cryptic as it sounds since you don't really have any idea which provider is failing to load. the actual failure message looks like this: 0x80041013 - WBEM_E_PROVIDER_LOAD_FAILURE. your ccmexec.log may have exhibit strange errors like this:

Error loading service settings. Code 0x80041013 Phase 0 initialization failed (0x80041013) Service initialization failed (0x80041013)

if you're seeing these strange error messages, here's something you can try to fix it up:

1. switch over to %windir%\system32\wbem.
2. register all of the .dlls in this directory. here's a way that microsoft support stated:
   • for /f %s in ('dir /b *.dll') do regsvr32 /s %s
3. issue the following two commands:
   • wmiprvse /regserver
   • winmgmt /regserver

if this doesn't resolve it, try the steps again. this time, add in step 2b (below). i'm not sure under what condition this occurs, but we found that we had to register tscfgwmi.dll. you'd perform it doing this:

2b. regsvr32 %windir%\system32\tscfgwmi.dll

please let me know if this works for you. i'm curious how many others have experienced it.