WMI: Win32_Account class

Hello!
One of our vbs scripts monitors any changes in Win32_Account class:
strComputer = "."
Set objWMIService = GetObject("winmgmts:{(Security)}\\" & strComputer & "\root\cimv2")
Set objEventSource = objWMIService.ExecNotificationQuery ("Select * From __InstanceOperationEvent WITHIN 10 Where TargetInstance isa 'Win32_Account' and
TargetInstance.LocalAccount=TRUE")
The problem is that in spite of adding TargetInstance.LocalAccount=TRUE
this code still captures Win32_Account class's changes in ANY domain of our enterprise domain tree, even when connected to
"." (locally).
This page https://msdn.microsoft.com/ru-ru/library/windows/desktop/aa394061%28v=vs.85%29.aspx says:
"The Win32_Account abstract WMI class contains information about
user accounts and group accounts known to the computer system running Windows.
User or group names recognized by a Windows domain are descendants (or members) of this class."
Q1: Does this definition mean that connection to the LOCAL Win32_Account class (".") will capture not only local but domain account modifications (if a computer is a member of a domain) as well, because
User or group names recognized by a Windows domain are descendants (or members) of this class?  -
that's what I see in my network.
Q2: What should I do to narrow down the scope of the command to the single domain - city2.enterprise.local?
Thank you in advance,
Michael

Hi Michael,
To solve the issue related to VBScript, I recommend you can post in The Official Scripting Guys Forum for more efficient support:
https://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?forum=ITCG
Since Windows Powershell can also be used to query WMI class, and I tested the script with "localaccount" as below, which can filter the local user account:
Get-WmiObject -Class WIN32_account -Filter "LocalAccount = TRUE"
we can also specify the remote computername in the -computername parameter.
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

  • WMI __SystemSecurity class GetSecurityDescriptor method reports error 0x8004101d Unexpected error on Windows 2008 R2 for WMI namespace "\root\cimv2"

    WMI __SystemSecurity class GetSecurityDescriptor method reports error 0x8004101d Unexpected error on Windows
    2008 R2 for WMI namespace "\root\cimv2"
    On Windows 2008 and Windows 2012 R2 GetSecurityDescriptor works fine.
    Thanks,
    Sandygg
    Dev

    Hi Anna,
    No event getting generated under Application / Security, but following event was reported under Microsoft-Windows-WMI-Activity/Operational
    log.
    Id = {01EAEC48-F800-0001-5A81-6ADB7E6CD001}; ClientMachine =
    sever2008r2; User
    = sever2008r2\user;
    ClientProcessId = 12580; Component = Unknown; Operation = Start IWbemServices::ExecMethod - root\cimv2 : __SystemSecurity::GetSecurityDescriptor; ResultCode = 0x8004101d; PossibleCause = Unknown
    Will let you about WMI Diagnosis tool result.
    Thanks,
    Sandy
    Dev

  • Could not create WMI locator class (80040154) - Win7 x64 OSD

    Hello All,
    I'm attempting to deploy a Win7 x64 OS to a Dell Optiplex 3010 through SCCM 2012 via PXE, a process I've done many times in the last few months. All of a sudden, on this one machine, I can't get it to work.
    The first strange thing that happened is, after the initial check for a PXE server I am told to "Press F12 for network service boot". I've never seen that before on any other system. Secondly, after supplying the password to begin the OSD process
    I'm met with error message 80040154. An excerpt from my log file is below:
    spLocator.createInstance( ((bUseAdminLocator == true) ? CLSID_WbemAdministrativeLocator : CLSID_WbemLocator ) ), HRESULT=80040154 (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,264)    TSPxe    1/8/2015 10:00:45
    AM    268 (0x010C)
    Could not create WMI locator class (80040154)    TSPxe    1/8/2015 10:00:45 AM    268 (0x010C)
    spNamespace.Open(c_szCIMv2Namespace), HRESULT=80040154 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,604)    TSPxe    1/8/2015 10:00:45 AM    268 (0x010C)
    Failed to connect to WMI namespace \\.\ROOT\CIMV2 (Code 0x80040154)    TSPxe    1/8/2015 10:00:45 AM    268 (0x010C)
    TS::Policy::GetClientIdentity (&m_oHttpTransport, m_sSiteCode, sMediaGuid.c_str(), m_sClientGUID, m_sNetbiosName, bUnknown, sServerNames, sImportedClientIdentity), HRESULT=80040154 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,867)    TSPxe  
     1/8/2015 10:00:45 AM    268 (0x010C)
    I see this error happening for people attempting a Win 8.1 OSD without the proper WMI file. But that's not what I'm trying to do. This exact process has worked on many other Optiplex 3010's and 3020's since May when I started using it. Any suggestions?

    Ok, here's what was happening. Boy do I feel stupid.
    When I went to enter this latest batch of computers into SCCM, I went into the BIOS, copied the MAC, and used it as I should to import the system into SCCM. I assigned it to my OSD collection, then deployed my OSD TS to that collection. This is when I started
    having major issues. Reason being: I transposed two of the digits in the MAC I entered. As a result, the computer booted as part of the “Unknown Systems” collection and was assigned a generic OSD TS that didn’t contain the necessary drivers to complete. I
    never assigned a TS to that collection, and I'm the only one that's been using SCCM for OSD. I can only assume someone else was playing around with it trying to learn and did this themselves.
    When I removed the outdated boot image the Unknown Computers TS was supposed to use, I began being unable to even PXE boot (of course). After trying many and varied solutions (including double-checking the MAC I had written down
    incorrectly), thinking it was a PXE or boot image issue I began looking at the PXE boot logs on my DP. I noticed it kept saying that there were no advertisements to this system, which made no sense. I had deployed an OSD TS to it 5 minutes ago! I finally
    noticed the MAC address was incorrect and fixed it. Guess what? It’s imaging as I type.
    Thanks for all the help guys - lesson learned.

  • Referencing WMI Manageable class from another WMI Class

    Hi,
    I am trying to have WMI manageable class referring to another WMI manageable class
    Something like
    [ManagementEntity]
    Class A
    [ManagementEntity]
    Class B
            [ManagementReference(Type = "A")]
            [ManagementProbe]
            public A AClass;
    When trying to install the class, I am getting “Type unsupported”
    I tried the Microsoft
    ManagementReference sample,
    http://msdn.microsoft.com/en-us/library/system.management.instrumentation.managementreferenceattribute.aspx
    (working fine but the LetterPhonetic class won’t show on the WMI Object Browser)
    Ideas will be highly appreciated
    My Sample code
    using System;
    using System.Management.Instrumentation;
    using System.Collections.Concurrent;
    using System.Collections;
    [assembly: WmiConfiguration("root\\ConsoleC", HostingModel = ManagementHostingModel.Decoupled)]
    namespace ConsoleDecoupled
        [System.ComponentModel.RunInstaller(true)]
        public class TheInstaller : DefaultManagementInstaller
        public class Program
            public static void Main(string[] args)
                for (int i = 0; i < 10; ++i)
                    TestEnumWmi ms = TestEnumWmi.CreateTestEnumWmi();
                    ms.teststring = i.ToString();
                InstrumentationManager.RegisterType(typeof(TestEnumWmi));
                InstrumentationManager.RegisterType(typeof(RuntimeConfigSettings));
                Console.WriteLine("Press enter to exit");
                Console.ReadLine();
                InstrumentationManager.UnregisterType(typeof(TestEnumWmi));
                InstrumentationManager.UnregisterType(typeof(RuntimeConfigSettings));
        [ManagementEntity(Singleton = true, Name = "ConfigurationSample")]
        [ManagementQualifier("Description", Value = "Configuration Sample Application")]
        public class RuntimeConfigSettings
            [ManagementProbe]
            public string[] ReadMe;
            private int myVar;
            [ManagementConfiguration]
            public int MyProperty
                get { return myVar; }
                set { myVar = value; Console.WriteLine(value); }
            [ManagementReference(Type = "TestEnumWmi")]
            [ManagementProbe]
            public TestEnumWmi MSS;
            [ManagementBind]
            public RuntimeConfigSettings()
                ReadMe = new string[10];
                for (int i = 0; i < 10; ++i)
                    ReadMe[i] = "blah " + i;
        [ManagementEntity(Name = "TestEnumWmi")]
        public class TestEnumWmi
            private TestEnumWmi()
            static internal TestEnumWmi CreateTestEnumWmi()
                TestEnumWmi ms = new TestEnumWmi();
                ms._id = Guid.NewGuid().ToString();
                ms.teststring = "blah";
                ms.TestInt = new Random().NextDouble();
                instantlist.TryAdd(ms._id, ms);
                return ms;
            [ManagementConfiguration()]
            public double TestInt { get; set; }
            [ManagementConfiguration()]
            public string teststring { get; set; }
            [ManagementKey(Name = "ID")]
            public string _id;
            [ManagementBind]
            static public TestEnumWmi GetInstant([ManagementName("ID")] string ID)
                TestEnumWmi ms = null;
                if (instantlist.TryGetValue(ID, out ms))
                    return ms;
                else
                    throw new InstanceNotFoundException();
            [ManagementEnumerator]
            static public IEnumerable EnumerateTestEnumWmis()
                foreach (var i in instantlist)
                    yield return i.Value;
            static internal ConcurrentDictionary<string, TestEnumWmi> instantlist = new ConcurrentDictionary<string, TestEnumWmi>();

    Hi,
    The Microsoft ManagementReference sample you mentioned contains a bug:
    Instead of:
    inst.LetterNumber = "Letter = " + i;
    inst.PhoneticNumber = "Phonetic = " + i;
    The exact text (where spaces in the string are important and must be removed) should be:
    inst.LetterNumber = "NumberLetter.Number=" + i;
    inst.PhoneticNumber = "NumberPhonetic.Number=" + i;
    With this fix, the hierarchy can now be navigated properly.
    c.f. my response to the following blog post:
    http://juggledthoughts.blogspot.co.uk/2008/06/wmi-association-classes.html
    I have also
    logged a bug on MSDN Feedback so please vote on this if you'd like them to fix the sample.

  • Meaning and default value of WMI MSCluster_Resource class property ResourceClass

    Somehow cannot get clear with MSCluster WMI class MSCluster_Resource property named ResourceClass. Does anybody know the meaning and the value by default?
    Guntars Svilpe

    Hi,
    I found the following third party article about use the “MSCluster_Resource class” may can give you some tips:
    Cluster resource monitor
    http://community.whatsupgold.com/library/activemonitors/cluster_resources_monitor
    the Cluster Owning node name using powershell
    http://serverfault.com/questions/445015/get-the-cluster-owning-node-name-using-powershell
    #PSTip Monitoring Cluster Shared Volume (CSV) availability
    http://www.powershellmagazine.com/2014/02/26/pstip-monitoring-cluster-shared-volume-csv-availability/
    More information:
    Playing around with the Root\MSCluster WMI Namespace and WMI Notifications
    http://blogs.technet.com/b/rspitz/archive/2011/05/11/playing-around-with-the-root-mscluster-wmi-namespace-and-wmi-notifications.aspx
    However this form is not for the develop issue discuss, about the develop question please post to the MSDN forum.
    MSDN forum Developer Network
    http://social.msdn.microsoft.com/Forums/en-US/home?forum=WAVirtualMachinesVirtualNetwork&filter=alltypes&sort=lastpostdesc
    Thanks for your understanding and support.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • WMI V2 equivalent of WMI V1 for Classes, Method or attribute

    Hi Guys,
    Since in Hyper V 2012 R2 the support for WMI 1 is removed, Hence we are migrating our applications from WMI V1 to WMI V2, Is there is any table or something which can give me WMI V2 (Classes, Method and attrib) equivalent of WMI V1 (Classes, Method and attrib).
    Thanks

    For most of them you simply add the v2 to the namespace, that is it.
    There is MSDN documentation: 
    http://msdn.microsoft.com/en-us/library/hh850319(v=vs.85).aspx
    and a series of blog posts by Taylor Brown as well: 
    http://blogs.msdn.com/b/taylorb/
    (unfortunately, he didn't tag them as v2 examples so you have to dig through the list)
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • DFS replication stopped working and cannot be debugged because WMI repository cannot be accessed

    Hello,
    two days ago our DFS replication suddendly stopped working sometime around midnight local time. At least this is what our second domain controller is reporting. Event log is flooded with event id 5002 from DFSR. It is unclear what caused this sudden problem
    and even worse, how to solve it. First thing I tried was to perform propagation tests. According to propagation report none of them was successful. Creating an integrity report brought me to another problem: It fails with two errors. First it is unable to
    connect to the other DC. Second it is unable to access local WMI repository. This is true for both machines.
    First I tried to find information on possible problems with WMI. WMIdiag provided a lot of information. However, opinions I found on the net largely disagree whether output from WMIdiag is useful or not. Yet I tried to re-compile .mof files and rebuild the
    repository. So far, nothing changed. This is my output from WMIdiag:
    34309 13:02:46 (0) ** WMIDiag v2.1 started on Donnerstag, 22. Mai 2014 at 12:49.
    34310 13:02:46 (0) **
    34311 13:02:46 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    34312 13:02:46 (0) **
    34313 13:02:46 (0) ** This script is not supported under any Microsoft standard support program or service.
    34314 13:02:46 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    34315 13:02:46 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    34316 13:02:46 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    34317 13:02:46 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    34318 13:02:46 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    34319 13:02:46 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    34320 13:02:46 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    34321 13:02:46 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    34322 13:02:46 (0) ** of the possibility of such damages.
    34323 13:02:46 (0) **
    34324 13:02:46 (0) **
    34325 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34326 13:02:46 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    34327 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34328 13:02:46 (0) **
    34329 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34330 13:02:46 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'COM\ABCDEF' on computer 'DC2'.
    34331 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34332 13:02:46 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
    34333 13:02:46 (0) ** INFO: => 1 possible incorrect shutdown(s) detected on:
    34334 13:02:46 (0) ** - Shutdown on 01 April 2014 10:20:54 (GMT-0).
    34335 13:02:46 (0) **
    34336 13:02:46 (0) ** System drive: ....................................................................................................... C: (Datenträgernr. 0 Partitionsnr. 1).
    34337 13:02:46 (0) ** Drive type: ......................................................................................................... SCSI (Adaptec Array SCSI Disk Device).
    34338 13:02:46 (0) ** There are no missing WMI system files: .............................................................................. OK.
    34339 13:02:46 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    34340 13:02:46 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
    34341 13:02:46 (0) ** AFTER running WMIDiag:
    34342 13:02:46 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
    34343 13:02:46 (0) ** - Disk free space on 'C:': .......................................................................................... 10665 MB.
    34344 13:02:46 (0) ** - INDEX.BTR, 4276224 bytes, 22.05.2014 12:52:30
    34345 13:02:46 (0) ** - MAPPING1.MAP, 67248 bytes, 22.05.2014 12:52:30
    34346 13:02:46 (0) ** - MAPPING2.MAP, 67168 bytes, 22.05.2014 12:48:33
    34347 13:02:46 (0) ** - OBJECTS.DATA, 23126016 bytes, 22.05.2014 12:52:30
    34348 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34349 13:02:46 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
    34350 13:02:46 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
    34351 13:02:46 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
    34352 13:02:46 (0) ** => This will prevent any WMI remote connectivity to this computer except
    34353 13:02:46 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
    34354 13:02:46 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
    34355 13:02:46 (0) ** - 'Windows Management Instrumentation (WMI-In)'
    34356 13:02:46 (0) ** - 'Windows Management Instrumentation (ASync-In)'
    34357 13:02:46 (0) ** Verify the reported status for each of these three inbound rules below.
    34358 13:02:46 (0) **
    34359 13:02:46 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
    34360 13:02:46 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
    34361 13:02:46 (0) ** - You can adjust the configuration by executing the following command:
    34362 13:02:46 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
    34363 13:02:46 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
    34364 13:02:46 (0) ** You can also enable each individual rule instead of activating the group rule.
    34365 13:02:46 (0) **
    34366 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34367 13:02:46 (0) ** DCOM Status: ........................................................................................................ OK.
    34368 13:02:46 (0) ** WMI registry setup: ................................................................................................. OK.
    34369 13:02:46 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
    34370 13:02:46 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    34371 13:02:46 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    34372 13:02:46 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
    34373 13:02:46 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
    34374 13:02:46 (0) ** this can prevent the service/application to work as expected.
    34375 13:02:46 (0) **
    34376 13:02:46 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    34377 13:02:46 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    34378 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34379 13:02:46 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    34380 13:02:46 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    34381 13:02:46 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    34382 13:02:46 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    34383 13:02:46 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    34384 13:02:46 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    34385 13:02:46 (2) !! WARNING: Some WMI providers EXE/DLL file(s) are missing: ............................................................ 1 WARNING(S)!
    34386 13:02:46 (0) ** - ROOT/MICROSOFTACTIVEDIRECTORY, ReplProv1, replprov.dll
    34387 13:02:46 (0) ** => This will make any operations related to the WMI class supported by the provider(s) to fail.
    34388 13:02:46 (0) ** This can be due to:
    34389 13:02:46 (0) ** - the de-installation of the software.
    34390 13:02:46 (0) ** - the deletion of some files.
    34391 13:02:46 (0) ** => If the software has been de-installed intentionally, then this information must be
    34392 13:02:46 (0) ** removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
    34393 13:02:46 (0) ** the provider registration data.
    34394 13:02:46 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\MICROSOFTACTIVEDIRECTORY path __Win32Provider Where Name='ReplProv1' DELETE'
    34395 13:02:46 (0) ** => If not, you must restore a copy of the missing provider EXE/DLL file(s) as indicated by the path.
    34396 13:02:46 (0) ** You can retrieve the missing file from:
    34397 13:02:46 (0) ** - A backup.
    34398 13:02:46 (0) ** - The Windows CD.
    34399 13:02:46 (0) ** - Another Windows installation using the same version and service pack level of the examined system.
    34400 13:02:46 (0) ** - The original CD or software package installing this WMI provider.
    34401 13:02:46 (0) **
    34402 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34403 13:02:46 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
    34404 13:02:46 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    34405 13:02:46 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    34406 13:02:46 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    34407 13:02:46 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
    34408 13:02:46 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    34409 13:02:46 (0) **
    34410 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
    34411 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
    34412 13:02:46 (0) ** - REMOVED ACE:
    34413 13:02:46 (0) ** ACEType: &h0
    34414 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34415 13:02:46 (0) ** ACEFlags: &h0
    34416 13:02:46 (0) ** ACEMask: &h7
    34417 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34418 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
    34419 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
    34420 13:02:46 (0) **
    34421 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34422 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34423 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34424 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34425 13:02:46 (0) **
    34426 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
    34427 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
    34428 13:02:46 (0) ** - REMOVED ACE:
    34429 13:02:46 (0) ** ACEType: &h0
    34430 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34431 13:02:46 (0) ** ACEFlags: &h0
    34432 13:02:46 (0) ** ACEMask: &h7
    34433 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34434 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
    34435 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
    34436 13:02:46 (0) **
    34437 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34438 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34439 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34440 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34441 13:02:46 (0) **
    34442 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
    34443 13:02:46 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
    34444 13:02:46 (0) ** - REMOVED ACE:
    34445 13:02:46 (0) ** ACEType: &h0
    34446 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34447 13:02:46 (0) ** ACEFlags: &h0
    34448 13:02:46 (0) ** ACEMask: &h7
    34449 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34450 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
    34451 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
    34452 13:02:46 (0) **
    34453 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34454 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34455 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34456 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34457 13:02:46 (0) **
    34458 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    34459 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
    34460 13:02:46 (0) ** - REMOVED ACE:
    34461 13:02:46 (0) ** ACEType: &h0
    34462 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34463 13:02:46 (0) ** ACEFlags: &h0
    34464 13:02:46 (0) ** ACEMask: &h1F
    34465 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34466 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34467 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34468 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34469 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34470 13:02:46 (0) **
    34471 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34472 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34473 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34474 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34475 13:02:46 (0) **
    34476 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    34477 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
    34478 13:02:46 (0) ** - REMOVED ACE:
    34479 13:02:46 (0) ** ACEType: &h0
    34480 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34481 13:02:46 (0) ** ACEFlags: &h0
    34482 13:02:46 (0) ** ACEMask: &h1F
    34483 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34484 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34485 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34486 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34487 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34488 13:02:46 (0) **
    34489 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34490 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34491 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34492 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34493 13:02:46 (0) **
    34494 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
    34495 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
    34496 13:02:46 (0) ** - REMOVED ACE:
    34497 13:02:46 (0) ** ACEType: &h0
    34498 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34499 13:02:46 (0) ** ACEFlags: &h0
    34500 13:02:46 (0) ** ACEMask: &h1F
    34501 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34502 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34503 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34504 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34505 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34506 13:02:46 (0) **
    34507 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34508 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34509 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34510 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34511 13:02:46 (0) **
    34512 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
    34513 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
    34514 13:02:46 (0) ** - REMOVED ACE:
    34515 13:02:46 (0) ** ACEType: &h0
    34516 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34517 13:02:46 (0) ** ACEFlags: &h0
    34518 13:02:46 (0) ** ACEMask: &h1F
    34519 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34520 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34521 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34522 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34523 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34524 13:02:46 (0) **
    34525 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34526 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34527 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34528 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34529 13:02:46 (0) **
    34530 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
    34531 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
    34532 13:02:46 (0) ** - REMOVED ACE:
    34533 13:02:46 (0) ** ACEType: &h0
    34534 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34535 13:02:46 (0) ** ACEFlags: &h0
    34536 13:02:46 (0) ** ACEMask: &h1F
    34537 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34538 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34539 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34540 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34541 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34542 13:02:46 (0) **
    34543 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34544 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34545 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34546 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34547 13:02:46 (0) **
    34548 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
    34549 13:02:46 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
    34550 13:02:46 (0) ** - REMOVED ACE:
    34551 13:02:46 (0) ** ACEType: &h0
    34552 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34553 13:02:46 (0) ** ACEFlags: &h0
    34554 13:02:46 (0) ** ACEMask: &hB
    34555 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34556 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34557 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34558 13:02:46 (0) **
    34559 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34560 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34561 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34562 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34563 13:02:46 (0) **
    34564 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34565 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
    34566 13:02:46 (0) ** - REMOVED ACE:
    34567 13:02:46 (0) ** ACEType: &h0
    34568 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34569 13:02:46 (0) ** ACEFlags: &h0
    34570 13:02:46 (0) ** ACEMask: &h1F
    34571 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34572 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34573 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34574 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34575 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34576 13:02:46 (0) **
    34577 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34578 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34579 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34580 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34581 13:02:46 (0) **
    34582 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34583 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
    34584 13:02:46 (0) ** - REMOVED ACE:
    34585 13:02:46 (0) ** ACEType: &h0
    34586 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34587 13:02:46 (0) ** ACEFlags: &h0
    34588 13:02:46 (0) ** ACEMask: &h1F
    34589 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34590 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34591 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34592 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34593 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34594 13:02:46 (0) **
    34595 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34596 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34597 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34598 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34599 13:02:46 (0) **
    34600 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34601 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
    34602 13:02:46 (0) ** - REMOVED ACE:
    34603 13:02:46 (0) ** ACEType: &h0
    34604 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34605 13:02:46 (0) ** ACEFlags: &h0
    34606 13:02:46 (0) ** ACEMask: &h1F
    34607 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34608 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34609 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34610 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34611 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34612 13:02:46 (0) **
    34613 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34614 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34615 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34616 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34617 13:02:46 (0) **
    34618 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34619 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
    34620 13:02:46 (0) ** - REMOVED ACE:
    34621 13:02:46 (0) ** ACEType: &h0
    34622 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34623 13:02:46 (0) ** ACEFlags: &h0
    34624 13:02:46 (0) ** ACEMask: &h1F
    34625 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34626 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34627 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34628 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34629 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34630 13:02:46 (0) **
    34631 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34632 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34633 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34634 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34635 13:02:46 (0) **
    34636 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
    34637 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
    34638 13:02:46 (0) ** - REMOVED ACE:
    34639 13:02:46 (0) ** ACEType: &h0
    34640 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
    34641 13:02:46 (0) ** ACEFlags: &h0
    34642 13:02:46 (0) ** ACEMask: &h1F
    34643 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
    34644 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
    34645 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
    34646 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
    34647 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
    34648 13:02:46 (0) **
    34649 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    34650 13:02:46 (0) ** Removing default security will cause some operations to fail!
    34651 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
    34652 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    34653 13:02:46 (0) **
    34654 13:02:46 (0) **
    34655 13:02:46 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
    34656 13:02:46 (0) ** DCOM security error(s) detected: .................................................................................... 14.
    34657 13:02:46 (0) ** WMI security warning(s) detected: ................................................................................... 0.
    34658 13:02:46 (0) ** WMI security error(s) detected: ..................................................................................... 0.
    34659 13:02:46 (0) **
    34660 13:02:46 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
    34661 13:02:46 (0) ** Overall WMI security status: ........................................................................................ OK.
    34662 13:02:46 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    34663 13:02:46 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
    34664 13:02:46 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    34665 13:02:46 (0) ** 'select * from MSFT_SCMEventLogEvent'
    34666 13:02:46 (0) **
    34667 13:02:46 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    34668 13:02:46 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
    34669 13:02:46 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    34670 13:02:46 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    34671 13:02:46 (0) ** - ROOT/SERVICEMODEL.
    34672 13:02:46 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    34673 13:02:46 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    34674 13:02:46 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    34675 13:02:46 (0) ** i.e. 'WMIC.EXE /NODE:"ISWDC2" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    34676 13:02:46 (0) **
    34677 13:02:46 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    34678 13:02:46 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    34679 13:02:46 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 32 ERROR(S)!
    34680 13:02:46 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34681 13:02:46 (0) ** MOF Registration: ''
    34682 13:02:46 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34683 13:02:46 (0) ** MOF Registration: ''
    34684 13:02:46 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34685 13:02:46 (0) ** MOF Registration: ''
    34686 13:02:46 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34687 13:02:46 (0) ** MOF Registration: ''
    34688 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34689 13:02:46 (0) ** MOF Registration: ''
    34690 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34691 13:02:46 (0) ** MOF Registration: ''
    34692 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34693 13:02:46 (0) ** MOF Registration: ''
    34694 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34695 13:02:46 (0) ** MOF Registration: ''
    34696 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34697 13:02:46 (0) ** MOF Registration: ''
    34698 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34699 13:02:46 (0) ** MOF Registration: ''
    34700 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34701 13:02:46 (0) ** MOF Registration: ''
    34702 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34703 13:02:46 (0) ** MOF Registration: ''
    34704 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34705 13:02:46 (0) ** MOF Registration: ''
    34706 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34707 13:02:46 (0) ** MOF Registration: ''
    34708 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34709 13:02:46 (0) ** MOF Registration: ''
    34710 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34711 13:02:46 (0) ** MOF Registration: ''
    34712 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34713 13:02:46 (0) ** MOF Registration: ''
    34714 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34715 13:02:46 (0) ** MOF Registration: ''
    34716 13:02:46 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34717 13:02:46 (0) ** MOF Registration: ''
    34718 13:02:46 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34719 13:02:46 (0) ** MOF Registration: ''
    34720 13:02:46 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34721 13:02:46 (0) ** MOF Registration: ''
    34722 13:02:46 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34723 13:02:46 (0) ** MOF Registration: ''
    34724 13:02:46 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34725 13:02:46 (0) ** MOF Registration: ''
    34726 13:02:46 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34727 13:02:46 (0) ** MOF Registration: ''
    34728 13:02:46 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34729 13:02:46 (0) ** MOF Registration: ''
    34730 13:02:46 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34731 13:02:46 (0) ** MOF Registration: ''
    34732 13:02:46 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34733 13:02:46 (0) ** MOF Registration: ''
    34734 13:02:46 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34735 13:02:46 (0) ** MOF Registration: ''
    34736 13:02:46 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34737 13:02:46 (0) ** MOF Registration: ''
    34738 13:02:46 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34739 13:02:46 (0) ** MOF Registration: ''
    34740 13:02:46 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34741 13:02:46 (0) ** MOF Registration: ''
    34742 13:02:46 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    34743 13:02:46 (0) ** MOF Registration: ''
    34744 13:02:46 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
    34745 13:02:46 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
    34746 13:02:46 (0) ** You can refresh the WMI class provider buffer with the following command:
    34747 13:02:46 (0) **
    34748 13:02:46 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
    34749 13:02:46 (0) **
    34750 13:02:46 (0) ** WMI MOF representations: ............................................................................................ OK.
    34751 13:02:46 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    34752 13:02:46 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    34753 13:02:46 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    34754 13:02:46 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
    34755 13:02:46 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    34756 13:02:46 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    34757 13:02:46 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
    34758 13:02:46 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    34759 13:02:46 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    34760 13:02:46 (0) **
    34761 13:02:46 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    34762 13:02:46 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    34763 13:02:46 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    34764 13:02:46 (0) ** WMI static instances retrieved: ..................................................................................... 1822.
    34765 13:02:46 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    34766 13:02:46 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    34767 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34768 13:02:46 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    34769 13:02:46 (0) ** DCOM: ............................................................................................................. 0.
    34770 13:02:46 (0) ** WINMGMT: .......................................................................................................... 0.
    34771 13:02:46 (0) ** WMIADAPTER: ....................................................................................................... 0.
    34772 13:02:46 (0) **
    34773 13:02:46 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    34774 13:02:46 (0) ** DCOM: ............................................................................................................. 0.
    34775 13:02:46 (0) ** WINMGMT: .......................................................................................................... 0.
    34776 13:02:46 (0) ** WMIADAPTER: ....................................................................................................... 0.
    34777 13:02:46 (0) **
    34778 13:02:46 (0) ** 32 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
    34779 13:02:46 (0) ** => This error is typically a WMI error. This WMI error is due to:
    34780 13:02:46 (0) ** - a missing WMI class definition or object.
    34781 13:02:46 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
    34782 13:02:46 (0) ** You can correct the missing class definitions by:
    34783 13:02:46 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
    34784 13:02:46 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
    34785 13:02:46 (0) ** (This list can be built on a similar and working WMI Windows installation)
    34786 13:02:46 (0) ** The following command line must be used:
    34787 13:02:46 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
    34788 13:02:46 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
    34789 13:02:46 (0) ** with WMI by starting the ADAP process.
    34790 13:02:46 (0) ** - a WMI repository corruption.
    34791 13:02:46 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
    34792 13:02:46 (0) ** to validate the WMI repository operations.
    34793 13:02:46 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
    34794 13:02:46 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
    34795 13:02:46 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
    34796 13:02:46 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
    34797 13:02:46 (0) ** the WMI repository must be reconstructed.
    34798 13:02:46 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
    34799 13:02:46 (0) ** otherwise some applications may fail after the reconstruction.
    34800 13:02:46 (0) ** This can be achieved with the following command:
    34801 13:02:46 (0) ** i.e. 'WMIDiag ShowMOFErrors'
    34802 13:02:46 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
    34803 13:02:46 (0) ** ALL fixes previously mentioned.
    34804 13:02:46 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
    34805 13:02:46 (0) **
    34806 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34807 13:02:46 (0) ** WMI Registry key setup: ............................................................................................. OK.
    34808 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34809 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34810 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34811 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34812 13:02:46 (0) **
    34813 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34814 13:02:46 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    34815 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    34816 13:02:46 (0) **
    34817 13:02:46 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\ABCDEF\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_ISWDC2_2014.05.22_12.49.13.LOG' for details.
    34818 13:02:46 (0) **
    34819 13:02:46 (0) ** WMIDiag v2.1 ended on Donnerstag, 22. Mai 2014 at 13:02 (W:89 E:52 S:1).
    There are a lot of error in the report and I don't know, whether they are relevant or how to solve them. To my current knowledge, I need to solve at least some of them so that I can access the local WMI repository again and get replication back working.
    But after hours of research I am stuck. Any hints are greatly appreciated.
    Regards,
    Oliver

    I don't know why, but soon after posting this, I found a solution to the problem. The WMI part was solved in this thread:
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/953be9ef-e9e3-4885-a5c4-47fc475ba562/dfs-is-not-working-anymore?forum=winserverfiles
    The relevant portion is this:
    Open a CMD prompt in %windir%\system32\wbem
    mofcomp dfsrprovs.mof
    net stop winmgmt
    net start winmgmt
    net start iphlpsvc
    net stop dfsr
    net start dfsr
    I don't know why recompiling of all mof did not solve the problem, but the solution above did. Restarting the DCs solved the communication issue. I don't know why the primary DC forgot about the WMI DFS provider or why communication failed. However, it is
    working again, it seems.

  • WMI Corruption - SCCM 2012 - Win7 SP1

    Hi all,
    So we are in the process of switching to Configuration Manager 2012 and we are now having MANY instances of WMI corruption on user workstations. The OS we are deploying is Win 7 SP1.
    Symptoms:
    -Keeping users from logging in (heavily delayed or not at all), spinning at the blue login screen.
    -Computer hangs at logoff/shutdown.
    -NIC lags on recognizing internet connection at startup.
    -Programs running slow and crashing (Includes MS Office and IE).
    -Windows crashing and getting black screens.
    Fixes we've tried:
    -Deleting all expired updates from Configuration Manager.
    -Consolidating software update groups. When originally installed, someone configured it so every update would create it's own update group. After fixing this, we saw a decrease in affected machines.
    -Reseting the repositroy. This is pretty much putting a band-aid on the problem. It get's users to be able to get functional again while we continue to troubleshoot the underlying problem. We've tried salavaging the repository, but it hardly if ever completes
    successfully.
    -Applying the following hotfixes from Microsoft, after the repository has been reset. This method is only on about 1% of the machines on our network and is still in testing phase.
    2705357      The WMI process stops sending events to
    WMI clients from a Windows 7-based or Windows Server 2008 R2-based server
    2692929      "0x80041001" error when the
    Win32_Environment WMI class is queried by multiple requestors in Windows 7 or in Windows Server 2008 R2
    2617858      Unexpectedly slow startup or logon process
    in Windows Server 2008 R2 or in Windows 7
    2465990      "0x80041002 (WBEM_E_NOT_FOUND)"
    error occurs when you try to open a WMI namespace on a computer that is running Windows 7 or Windows Server 2008 R2
    2492536      Msinfo32.exe takes a long time to display
    or export system information on a computer that has many MSI-X-supported devices and that is running Windows 7 or Windows Server 2008 R2
    2578159-
    When you log on to a computer that is running Windows Server 2008 R2 or Windows 7, the logon process stops responding and a blue swirl is shown on the Welcome screen indefinitely. After some time, the computer stops responding to any network-related commands.
    You must forcibly restart the computer to recover from this issue.
    This issue occurs because of a race condition between the Windows Event Log service and the Event Tracing for Windows
    (ETW) tracing functions. When the race condition occurs, it causes a deadlock situation. This deadlock situation then causes the Winlogon.exe process to become unresponsive.
    2639505- Assume that you run a service which queries the Win32_StartupCommand Windows
    Management Instrumentation (WMI) class on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2.
    In this situation, all loaded user profiles occasionally cannot be unloaded successfully after the WMI query is finished. If the number of unloaded user profiles keeps increasing, the system resources may be exhausted. For example,
    the virtual address control block (VACB) may be exhausted.
    2639077-
    Handle leak in Svchost.exe when a WMI query is triggered by using the Win32_PowerSettingCapabilities class in Windows 7 or in Windows
    Server 2008 R2
    2547244-The WMI service and the WMI providers stop responding
    when you use WMI performance classes to monitor performance on a computer that is running Windows 7 or Windows Server 2008 R2
    Thanks in advance for any help!

    -Fails to boot from NIC.
    Booting from NIC (are you talking about PXE boot?) has nothing to do with WMI at all. There's no OS involved. So *I* do not see a connection between WMI and PXE.
    Have you already tried excluding the WBEM directory from antivirus scans? How are the WMI memory limits configured? See
    http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx as a starting point.
    Torsten Meringer | http://www.mssccmfaq.de

  • Can CM12 hardware inventory get more information by calling a WMI Method

    Hello Everyone,
    i have a question for CM12 hardware inventory. here is my question
    i'm now have a powershell script which can lists all the shared folder permissions or NTFS permissions. This powershell get such information by calling a WMI Method in Win32_LogicalShareSecuritySetting.
    here is the powershell link http://gallery.technet.microsoft.com/scriptcenter/Lists-all-the-shared-5ebb395a
    i'm now trying to implement this in SCCM 2012 R2. In SCCM client settings you can add a BASIC WMI classes very simply. But i didn't find a way to calling WMI classes Method by SCCM hardware inventory which can help me get more information just like
    the powershell i posted.
    i'm really not familiar with WMI and not under what is WMI method very clearly.. just hope someone can give me a quick answer of my question
    Any help will be greatly appreciated
    Thanks
    MJQIAN

    What is your exact requirement?
    Creating a WMI provider is Hard. Really hard, but one created you will get real-time results.
    However creating a static WMI class is easy. But the results need to be refreshed every so often to ensure that the data is relevant.  I did a quick bing search and here is a PowerShell script to do it.
    http://social.technet.microsoft.com/Forums/scriptcenter/en-US/183b8b56-131c-4de7-80bc-08650daf7333/wmi-custom-class-with-powershell?forum=ITCG
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • WMI V2 equivalent of WMI V1

    Hi Guyz,
    Since in Hyper V 2012 R2 the support for WMI 1 is removed, Hence we are migrating our applications from WMI V1 to WMI V2, Is there is any table or something which can give me WMI V2 (Classes, Method and attrib) equivalent of WMI V1 (Classes, Method and attrib).
    Thanks

    All Hyper-V questions should be posted in the Hyper-V forum:
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverhyperv
    This forum is for Virtual Server 2005.  There's no relation between Hyper-V and Virtual Server.

  • RD640 power supply monitoring ( WMI) status

    hiFor RD640, if monitoring of the status of Power supply ( hot swap?)  need to be done, what is the WMI namespace/class/path that will return the status? I have already attempted to query by cim_powersupply but nothing returns.  wmic path cim_powersupply get *  Does easy manage monitors the power supply at all? Thanks     

    hiFor RD640, if monitoring of the status of Power supply ( hot swap?)  need to be done, what is the WMI namespace/class/path that will return the status? I have already attempted to query by cim_powersupply but nothing returns.  wmic path cim_powersupply get *  Does easy manage monitors the power supply at all? Thanks     

  • Application error happening at least twice a day. Faulting applicaiton name: wmiprvse.exe

    We're experiencing an issue with one of our Windows Server 2008R2 Standard Edition SP1 servers where an Application error occurs at least twice, and sometimes up to 5 or 6 times per day.  The following error is what we see.  Any help would be greatly
    appreciated, and I'll be checking back frequently to check for updates and provide more info whenever needed.  Thanks!
    General:
    Faulting application name: wmiprvse.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d42
    Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c8f9
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c40f2
    Faulting process id: 0x1bbc
    Faulting application start time: 0x01cd5d65dbeb2e7c
    Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Details:
    System
    Provider
    [ Name]
    Application Error
    EventID
    1000
    [ Qualifiers]
    0
    Level
    2
    Task
    100
    Keywords
    0x80000000000000
    TimeCreated
    [ SystemTime]
    2012-07-09T08:34:39.000000000Z
    EventRecordID
    6812
    Channel
    Application
    Computer
    {FQDN}
    Security
    EventData
    wmiprvse.exe
    6.1.7601.17514
    4ce79d42
    ntdll.dll
    6.1.7601.17514
    4ce7c8f9
    c0000374
    00000000000c40f2
    1bbc
    01cd5d65dbeb2e7c
    C:\Windows\system32\wbem\wmiprvse.exe
    C:\Windows\SYSTEM32\ntdll.dll
    ebe1621c-c9a0-11e1-a1d4-5cf3fce8cef6
    ETA:  I also ran the wmidiag.exe tool from Microsoft.  I saw it as a suggestion on another forum and ran it.  I don't know if it has any bearing here, but this is the log in case it's helpful
    show
    06604 14:51:25 (0) ** WMIDiag v2.1 started on Tuesday, July 10, 2012 at 14:40.
    06605 14:51:25 (0) ** 
    06606 14:51:25 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    06607 14:51:25 (0) ** 
    06608 14:51:25 (0) ** This script is not supported under any Microsoft standard support program or service.
    06609 14:51:25 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    06610 14:51:25 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    06611 14:51:25 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    06612 14:51:25 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    06613 14:51:25 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    06614 14:51:25 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    06615 14:51:25 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    06616 14:51:25 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    06617 14:51:25 (0) ** of the possibility of such damages.
    06618 14:51:25 (0) ** 
    06619 14:51:25 (0) ** 
    06620 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06621 14:51:25 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    06622 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06623 14:51:25 (0) ** 
    06624 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06625 14:51:25 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User {Username} on computer {ComputerName}.
    06626 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06627 14:51:25 (0) ** Environment: ........................................................................................................ OK.
    06628 14:51:25 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
    06629 14:51:25 (0) ** Drive type: ......................................................................................................... SCSI (IBM ServeRAID M5015 SCSI Disk Device).
    06630 14:51:25 (0) ** There are no missing WMI system files: .............................................................................. OK.
    06631 14:51:25 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    06632 14:51:25 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
    06633 14:51:25 (0) ** AFTER running WMIDiag:
    06634 14:51:25 (0) ** The WMI repository has a size of: ................................................................................... 90 MB.
    06635 14:51:25 (0) ** - Disk free space on 'C:': .......................................................................................... 75295 MB.
    06636 14:51:25 (0) **   - INDEX.BTR,                     15818752 bytes,     7/10/2012 2:38:58 PM
    06637 14:51:25 (0) **   - MAPPING1.MAP,                  242388 bytes,       7/10/2012 2:33:33 PM
    06638 14:51:25 (0) **   - MAPPING2.MAP,                  242388 bytes,       7/10/2012 2:38:58 PM
    06639 14:51:25 (0) **   - OBJECTS.DATA,                  77570048 bytes,     7/10/2012 2:38:58 PM
    06640 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06641 14:51:25 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
    06642 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06643 14:51:25 (0) ** DCOM Status: ........................................................................................................ OK.
    06644 14:51:25 (0) ** WMI registry setup: ................................................................................................. OK.
    06645 14:51:25 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
    06646 14:51:25 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    06647 14:51:25 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    06648 14:51:25 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    06649 14:51:25 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    06650 14:51:25 (0) **          this can prevent the service/application to work as expected.
    06651 14:51:25 (0) ** 
    06652 14:51:25 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    06653 14:51:25 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    06654 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06655 14:51:25 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    06656 14:51:25 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    06657 14:51:25 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    06658 14:51:25 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    06659 14:51:25 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    06660 14:51:25 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    06661 14:51:25 (2) !! WARNING: Some WMI providers EXE/DLL file(s) are missing: ............................................................ 18 WARNING(S)!
    06662 14:51:25 (0) ** - ROOT/QLOGIC_CMPI, QLogic_NIC_Provider, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{28A5F598-F699-4A6B-B9F9-8C7EB9B7359F}:QLogic_NIC_Provider
    06663 14:51:25 (0) ** - ROOT/QLOGIC_CMPI, QLogic_FCHBA_Provider, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{0AE588DD-D2E9-41EB-BCD1-8BF474187EC5}:QLogic_FCHBA_Provider
    06664 14:51:25 (0) ** - ROOT/IBMSD, ADPT_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{B007445E-6AF0-4CBD-9009-809F071FCE69}:ADPT_Module
    06665 14:51:25 (0) ** - ROOT/IBMSD, IBM_PA_Providers, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{2244E0FA-D37A-4F6E-82FB-92F1DB78716D}:IBM_PA_Providers
    06666 14:51:25 (0) ** - ROOT/IBMSD, EndpointRegistrationProviderModule, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{BF833E81-33AA-40ED-B74A-329F006DB4F8}:EndpointRegistrationProviderModule
    06667 14:51:25 (0) ** - ROOT/CIMV2, SBLIM_Data_Gatherer, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{0D03AF80-A160-44EF-9E8B-318201F41693}:SBLIM_Data_Gatherer
    06668 14:51:25 (0) ** - ROOT/ADPT, ADPT_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{B007445E-6AF0-4CBD-9009-809F071FCE69}:ADPT_Module
    06669 14:51:25 (0) ** - ROOT/PG_INTEROP, SBLIM_Data_Gatherer, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{0D03AF80-A160-44EF-9E8B-318201F41693}:SBLIM_Data_Gatherer
    06670 14:51:25 (0) ** - ROOT/PG_INTEROP, LSIESG_SMIS13_HHR_ProviderModule, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{E21064DD-757A-4F2D-B798-81CDFF03B48C}:LSIESG_SMIS13_HHR_ProviderModule
    06671 14:51:25 (0) ** - ROOT/PG_INTEROP, emulex_fc_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{27734403-1E6C-4BC7-B97D-1FE9657B35EC}:emulex_fc_provider_Module
    06672 14:51:25 (0) ** - ROOT/PG_INTEROP, emulex_ucna_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{68D3C192-F517-41CC-B852-BA74A8D05A85}:emulex_ucna_provider_Module
    06673 14:51:25 (0) ** - ROOT/IBMSE, emulex_fc_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{27734403-1E6C-4BC7-B97D-1FE9657B35EC}:emulex_fc_provider_Module
    06674 14:51:25 (0) ** - ROOT/IBMSE, IBM_PA_Providers, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{2244E0FA-D37A-4F6E-82FB-92F1DB78716D}:IBM_PA_Providers
    06675 14:51:25 (0) ** - ROOT/IBMSE, emulex_ucna_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{68D3C192-F517-41CC-B852-BA74A8D05A85}:emulex_ucna_provider_Module
    06676 14:51:25 (0) ** - ROOT/LSI_MR_1_3_0, LSIESG_SMIS13_HHR_ProviderModule, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{E21064DD-757A-4F2D-B798-81CDFF03B48C}:LSIESG_SMIS13_HHR_ProviderModule
    06677 14:51:25 (0) ** - ROOT/EMULEX, emulex_fc_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{27734403-1E6C-4BC7-B97D-1FE9657B35EC}:emulex_fc_provider_Module
    06678 14:51:25 (0) ** - ROOT/EMULEX, emulex_ucna_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{68D3C192-F517-41CC-B852-BA74A8D05A85}:emulex_ucna_provider_Module
    06679 14:51:25 (0) ** - ROOT/BROCADE, brcdprovider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{48898EFD-0F9A-4657-B03D-FF400A7D2CDE}:brcdprovider_Module
    06680 14:51:25 (0) ** => This will make any operations related to the WMI class supported by the provider(s) to fail.
    06681 14:51:25 (0) **    This can be due to:
    06682 14:51:25 (0) **    - the de-installation of the software.
    06683 14:51:25 (0) **    - the deletion of some files.
    06684 14:51:25 (0) ** => If the software has been de-installed intentionally, then this information must be
    06685 14:51:25 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
    06686 14:51:25 (0) **    the provider registration data.
    06687 14:51:25 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\BROCADE path __Win32Provider Where Name='brcdprovider_Module' DELETE'
    06688 14:51:25 (0) ** => If not, you must restore a copy of the missing provider EXE/DLL file(s) as indicated by the path.
    06689 14:51:25 (0) **    You can retrieve the missing file from:
    06690 14:51:25 (0) **    - A backup.
    06691 14:51:25 (0) **    - The Windows CD.
    06692 14:51:25 (0) **    - Another Windows installation using the same version and service pack level of the examined system.
    06693 14:51:25 (0) **    - The original CD or software package installing this WMI provider.
    06694 14:51:25 (0) ** 
    06695 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06696 14:51:25 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
    06697 14:51:25 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    06698 14:51:25 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    06699 14:51:25 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    06700 14:51:25 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    06701 14:51:25 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    06702 14:51:25 (0) ** 
    06703 14:51:25 (0) ** Overall DCOM security status: ....................................................................................... OK.
    06704 14:51:25 (0) ** Overall WMI security status: ........................................................................................ OK.
    06705 14:51:25 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    06706 14:51:25 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
    06707 14:51:25 (0) ** - ROOT/SUBSCRIPTION, CommandLineEventConsumer.Name="BVTConsumer".
    06708 14:51:25 (0) **   'SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99'
    06709 14:51:25 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    06710 14:51:25 (0) **   'select * from MSFT_SCMEventLogEvent'
    06711 14:51:25 (0) ** 
    06712 14:51:25 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    06713 14:51:25 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
    06714 14:51:25 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    06715 14:51:25 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    06716 14:51:25 (0) ** - ROOT/SERVICEMODEL.
    06717 14:51:25 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    06718 14:51:25 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    06719 14:51:25 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    06720 14:51:25 (0) **    i.e. 'WMIC.EXE /NODE:"{ComputerName}" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    06721 14:51:25 (0) ** 
    06722 14:51:25 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    06723 14:51:25 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    06724 14:51:25 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 30 ERROR(S)!
    06725 14:51:25 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06726 14:51:25 (0) **   MOF Registration: ''
    06727 14:51:25 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06728 14:51:25 (0) **   MOF Registration: ''
    06729 14:51:25 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06730 14:51:25 (0) **   MOF Registration: ''
    06731 14:51:25 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06732 14:51:25 (0) **   MOF Registration: ''
    06733 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06734 14:51:25 (0) **   MOF Registration: ''
    06735 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06736 14:51:25 (0) **   MOF Registration: ''
    06737 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06738 14:51:25 (0) **   MOF Registration: ''
    06739 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06740 14:51:25 (0) **   MOF Registration: ''
    06741 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06742 14:51:25 (0) **   MOF Registration: ''
    06743 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06744 14:51:25 (0) **   MOF Registration: ''
    06745 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06746 14:51:25 (0) **   MOF Registration: ''
    06747 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06748 14:51:25 (0) **   MOF Registration: ''
    06749 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06750 14:51:25 (0) **   MOF Registration: ''
    06751 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06752 14:51:25 (0) **   MOF Registration: ''
    06753 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06754 14:51:25 (0) **   MOF Registration: ''
    06755 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06756 14:51:25 (0) **   MOF Registration: ''
    06757 14:51:25 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06758 14:51:25 (0) **   MOF Registration: ''
    06759 14:51:25 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06760 14:51:25 (0) **   MOF Registration: ''
    06761 14:51:25 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06762 14:51:25 (0) **   MOF Registration: ''
    06763 14:51:25 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06764 14:51:25 (0) **   MOF Registration: ''
    06765 14:51:25 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06766 14:51:25 (0) **   MOF Registration: ''
    06767 14:51:25 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06768 14:51:25 (0) **   MOF Registration: ''
    06769 14:51:25 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06770 14:51:25 (0) **   MOF Registration: ''
    06771 14:51:25 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06772 14:51:25 (0) **   MOF Registration: ''
    06773 14:51:25 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06774 14:51:25 (0) **   MOF Registration: ''
    06775 14:51:25 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06776 14:51:25 (0) **   MOF Registration: ''
    06777 14:51:25 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06778 14:51:25 (0) **   MOF Registration: ''
    06779 14:51:25 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06780 14:51:25 (0) **   MOF Registration: ''
    06781 14:51:25 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06782 14:51:25 (0) **   MOF Registration: ''
    06783 14:51:25 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06784 14:51:25 (0) **   MOF Registration: ''
    06785 14:51:25 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
    06786 14:51:25 (0) **    a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
    06787 14:51:25 (0) **    You can refresh the WMI class provider buffer with the following command:
    06788 14:51:25 (0) ** 
    06789 14:51:25 (0) **    i.e. 'WINMGMT.EXE /SYNCPERF'
    06790 14:51:25 (0) ** 
    06791 14:51:25 (0) ** WMI MOF representations: ............................................................................................ OK.
    06792 14:51:25 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    06793 14:51:25 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    06794 14:51:25 (2) !! WARNING: WMI EXECQUERY operation errors reported: ................................................................... 2 WARNING(S)!
    06795 14:51:25 (0) ** - Root/CIMV2, 'Select * From Win32_PointingDevice WHERE Status = "OK"' did not return any instance while AT LEAST 1 instance is expected.
    06796 14:51:25 (0) ** - Root/CIMV2, 'Select * From Win32_Keyboard' did not return any instance while AT LEAST 1 instance is expected.
    06797 14:51:25 (0) ** 
    06798 14:51:25 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
    06799 14:51:25 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06800 14:51:25 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06801 14:51:25 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
    06802 14:51:25 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06803 14:51:25 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06804 14:51:25 (0) ** 
    06805 14:51:25 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    06806 14:51:25 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    06807 14:51:25 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    06808 14:51:25 (0) ** WMI static instances retrieved: ..................................................................................... 2072.
    06809 14:51:25 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    06810 14:51:25 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    06811 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06812 14:51:25 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    06813 14:51:25 (0) **   DCOM: ............................................................................................................. 0.
    06814 14:51:25 (0) **   WINMGMT: .......................................................................................................... 0.
    06815 14:51:25 (0) **   WMIADAPTER: ....................................................................................................... 0.
    06816 14:51:25 (0) ** 
    06817 14:51:25 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    06818 14:51:25 (0) **   DCOM: ............................................................................................................. 0.
    06819 14:51:25 (0) **   WINMGMT: .......................................................................................................... 0.
    06820 14:51:25 (0) **   WMIADAPTER: ....................................................................................................... 0.
    06821 14:51:25 (0) ** 
    06822 14:51:25 (0) ** 30 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
    06823 14:51:25 (0) ** => This error is typically a WMI error. This WMI error is due to:
    06824 14:51:25 (0) **    - a missing WMI class definition or object.
    06825 14:51:25 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
    06826 14:51:25 (0) **      You can correct the missing class definitions by:
    06827 14:51:25 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
    06828 14:51:25 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
    06829 14:51:25 (0) **            (This list can be built on a similar and working WMI Windows installation)
    06830 14:51:25 (0) **            The following command line must be used:
    06831 14:51:25 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
    06832 14:51:25 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
    06833 14:51:25 (0) **            with WMI by starting the ADAP process.
    06834 14:51:25 (0) **    - a WMI repository corruption.
    06835 14:51:25 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
    06836 14:51:25 (0) **      to validate the WMI repository operations.
    06837 14:51:25 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
    06838 14:51:25 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
    06839 14:51:25 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
    06840 14:51:25 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
    06841 14:51:25 (0) **      the WMI repository must be reconstructed.
    06842 14:51:25 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
    06843 14:51:25 (0) **          otherwise some applications may fail after the reconstruction.
    06844 14:51:25 (0) **          This can be achieved with the following command:
    06845 14:51:25 (0) **          i.e. 'WMIDiag ShowMOFErrors'
    06846 14:51:25 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
    06847 14:51:25 (0) **          ALL fixes previously mentioned.
    06848 14:51:25 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
    06849 14:51:25 (0) ** 
    06850 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06851 14:51:25 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
    06852 14:51:25 (0) ** INFO: Unexpected registry key value:
    06853 14:51:25 (0) **   - Current:  HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
    06854 14:51:25 (0) **   - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
    06855 14:51:25 (0) **     From the command line, the registry configuration can be corrected with the following command:
    06856 14:51:25 (0) **     i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
    06857 14:51:25 (0) ** 
    06858 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06859 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06860 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06861 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06862 14:51:25 (0) ** 
    06863 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06864 14:51:25 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    06865 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06866 14:51:25 (0) ** 
    06867 14:51:25 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\{Username}\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_{ComputerName}_2012.07.10_14.40.25.LOG' for details.
    06868 14:51:25 (0) ** 
    06869 14:51:25 (0) ** WMIDiag v2.1 ended on Tuesday, July 10, 2012 at 14:51 (W:103 E:51 S:1).

    Following might help
    A Wmiprvse.exe process crashes in Windows Server 2008 R2 when you use the WMI interface to query the hardware status on a computer that supports the IPMI standard
    http://support.microsoft.com/kb/2280777
    I do not represent the organisation I work for, all the opinions expressed here are my own.
    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
    I saw this in my googling.  Listed as the cause on the hotfix page is the following: "This
    problem occurs because the Ipmiprv.dll module leads the Wmiprvse.exe process to crash. This behavior depends on certain hardware sensor types when the sensor is enumerated."  The
    faulting module for that hotfix is ipmiprv.dll, and our faulting module is ntdll.dll.  I'm thinking that this hotfix isn't applicable, but I'm open to hearing why I'm incorrect if I am.
    Seth Johnson

  • Cannot connect to Session broker server, but can to other servers in Cluster

    Hi Everyone,
    Hopefully this is the right place to post. Have searched quite a bit through the forums (not all 19000+ pages though), and can't seem to find a similiar issue.
    I have also searched the internet and tried all solutions others with a similiar problem have.
    This is my problem:
    We have two servers running Server 2008 R2, set up as Remote Desktop Servers in a cluster setup.
    The session broker is located on the second server (This is an active server which has sessions load balanced to it). There is also a DNS round robin setup
    Problem: When sessions are allowed to be load balanced on Server2, then the users cannot connect to the cluster. The round robin seems to still send some sessions to the first server, and these seem to connect fine.
    I suspected the issue was with the WMI Respository, and so started. I found a lot of errors, but have been unable to fix them.
    I downlaoded the WMIDiag from Microsoft, and here is the report:
    48866 15:56:44 (0) ** WMIDiag v2.1 started on 15 April 2015 at 15:48.
    48867 15:56:44 (0) **
    48868 15:56:44 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    48869 15:56:44 (0) **
    48870 15:56:44 (0) ** This script is not supported under any Microsoft standard support program or service.
    48871 15:56:44 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    48872 15:56:44 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    48873 15:56:44 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    48874 15:56:44 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    48875 15:56:44 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    48876 15:56:44 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    48877 15:56:44 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    48878 15:56:44 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    48879 15:56:44 (0) ** of the possibility of such damages.
    48880 15:56:44 (0) **
    48881 15:56:44 (0) **
    48882 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48883 15:56:44 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    48884 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48885 15:56:44 (0) **
    48886 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48887 15:56:44 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'MIBCO\CONN.LOMBARD' on computer 'SSCRDS02'.
    48888 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48889 15:56:44 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
    48890 15:56:44 (0) ** INFO: => 3 possible incorrect shutdown(s) detected on:
    48891 15:56:44 (0) **          - Shutdown on 05 December 2014 22:55:28 (GMT-0).
    48892 15:56:44 (0) **          - Shutdown on 12 December 2014 06:43:00 (GMT-0).
    48893 15:56:44 (0) **          - Shutdown on 27 February 2015 05:19:26 (GMT-0).
    48894 15:56:44 (0) **
    48895 15:56:44 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
    48896 15:56:44 (0) ** Drive type: ......................................................................................................... SCSI (DELL PERC H700 SCSI Disk Device).
    48897 15:56:44 (0) ** There are no missing WMI system files: .............................................................................. OK.
    48898 15:56:44 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    48899 15:56:44 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
    48900 15:56:44 (0) ** AFTER running WMIDiag:
    48901 15:56:44 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
    48902 15:56:44 (0) ** - Disk free space on 'C:': .......................................................................................... 297281 MB.
    48903 15:56:44 (0) **   - INDEX.BTR,                     5513216 bytes,      2015/04/15 03:52:21 PM
    48904 15:56:44 (0) **   - MAPPING1.MAP,                  76804 bytes,        2015/04/15 03:50:51 PM
    48905 15:56:44 (0) **   - MAPPING2.MAP,                  76804 bytes,        2015/04/15 03:52:21 PM
    48906 15:56:44 (0) **   - OBJECTS.DATA,                  22036480 bytes,     2015/04/15 03:52:21 PM
    48907 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48908 15:56:44 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
    48909 15:56:44 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
    48910 15:56:44 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
    48911 15:56:44 (0) ** => This will prevent any WMI remote connectivity to this computer except
    48912 15:56:44 (0) **    if the following three inbound rules are ENABLED and non-BLOCKING:
    48913 15:56:44 (0) **    - 'Windows Management Instrumentation (DCOM-In)'
    48914 15:56:44 (0) **    - 'Windows Management Instrumentation (WMI-In)'
    48915 15:56:44 (0) **    - 'Windows Management Instrumentation (ASync-In)'
    48916 15:56:44 (0) **    Verify the reported status for each of these three inbound rules below.
    48917 15:56:44 (0) **
    48918 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' GROUP rule: ............................................. ENABLED.
    48919 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... ENABLED.
    48920 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ ENABLED.
    48921 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... ENABLED.
    48922 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. ENABLED.
    48923 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48924 15:56:44 (0) ** DCOM Status: ........................................................................................................ OK.
    48925 15:56:44 (0) ** WMI registry setup: ................................................................................................. OK.
    48926 15:56:44 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
    48927 15:56:44 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    48928 15:56:44 (0) ** - SMS Agent Host (CCMEXEC, StartMode='Automatic')
    48929 15:56:44 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    48930 15:56:44 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    48931 15:56:44 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    48932 15:56:44 (0) **          this can prevent the service/application to work as expected.
    48933 15:56:44 (0) **
    48934 15:56:44 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    48935 15:56:44 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    48936 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48937 15:56:44 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    48938 15:56:44 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    48939 15:56:44 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    48940 15:56:44 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    48941 15:56:44 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    48942 15:56:44 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    48943 15:56:44 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
    48944 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    48945 15:56:44 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
    48946 15:56:44 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
    48947 15:56:44 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
    48948 15:56:44 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
    48949 15:56:44 (0) **         selecting 'Run as Administrator'.
    48950 15:56:44 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
    48951 15:56:44 (0) **         in the Task Scheduler within the right security context.
    48952 15:56:44 (0) **
    48953 15:56:44 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    48954 15:56:44 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    48955 15:56:44 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    48956 15:56:44 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    48957 15:56:44 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    48958 15:56:44 (0) **
    48959 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
    48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
    48961 15:56:44 (0) **        - ACTUAL ACE:
    48962 15:56:44 (0) **          ACEType:  &h0
    48963 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    48964 15:56:44 (0) **          ACEFlags: &h4
    48965 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
    48966 15:56:44 (0) **          ACEMask:  &hB
    48967 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
    48968 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    48969 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    48970 15:56:44 (0) **        - EXPECTED ACE:
    48971 15:56:44 (0) **          ACEType:  &h0
    48972 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    48973 15:56:44 (0) **          ACEFlags: &h0
    48974 15:56:44 (0) **          ACEMask:  &h1F
    48975 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
    48976 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    48977 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
    48978 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    48979 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
    48980 15:56:44 (0) **
    48981 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
    48982 15:56:44 (0) **    This will cause some operations to fail!
    48983 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
    48984 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    48985 15:56:44 (0) **
    48986 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
    48987 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\INTERACTIVE' DOES NOT match corresponding expected trustee rights (Actual->Default)
    48988 15:56:44 (0) **        - ACTUAL ACE:
    48989 15:56:44 (0) **          ACEType:  &h0
    48990 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    48991 15:56:44 (0) **          ACEFlags: &h4
    48992 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
    48993 15:56:44 (0) **          ACEMask:  &hB
    48994 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
    48995 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    48996 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    48997 15:56:44 (0) **        - EXPECTED ACE:
    48998 15:56:44 (0) **          ACEType:  &h0
    48999 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    49000 15:56:44 (0) **          ACEFlags: &h0
    49001 15:56:44 (0) **          ACEMask:  &h1F
    49002 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
    49003 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
    49004 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
    49005 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
    49006 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
    49007 15:56:44 (0) **
    49008 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
    49009 15:56:44 (0) **    This will cause some operations to fail!
    49010 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
    49011 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    49012 15:56:44 (0) **
    49013 15:56:44 (0) **
    49014 15:56:44 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
    49015 15:56:44 (0) ** DCOM security error(s) detected: .................................................................................... 2.
    49016 15:56:44 (0) ** WMI security warning(s) detected: ................................................................................... 0.
    49017 15:56:44 (0) ** WMI security error(s) detected: ..................................................................................... 0.
    49018 15:56:44 (0) **
    49019 15:56:44 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
    49020 15:56:44 (0) ** Overall WMI security status: ........................................................................................ OK.
    49021 15:56:44 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    49022 15:56:44 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 5.
    49023 15:56:44 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    49024 15:56:44 (0) **   'select * from MSFT_SCMEventLogEvent'
    49025 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
    49026 15:56:44 (0) **   'SELECT * FROM __NamespaceCreationEvent'
    49027 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
    49028 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_EmbeddedObject"'
    49029 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
    49030 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_Config"'
    49031 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
    49032 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy"'
    49033 15:56:44 (0) **
    49034 15:56:44 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    49035 15:56:44 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
    49036 15:56:44 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    49037 15:56:44 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    49038 15:56:44 (0) ** - ROOT/SERVICEMODEL.
    49039 15:56:44 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    49040 15:56:44 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    49041 15:56:44 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    49042 15:56:44 (0) **    i.e. 'WMIC.EXE /NODE:"SSCRDS02" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    49043 15:56:44 (0) **
    49044 15:56:44 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    49045 15:56:44 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    49046 15:56:44 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 34 ERROR(S)!
    49047 15:56:44 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49048 15:56:44 (0) **   MOF Registration: ''
    49049 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49050 15:56:44 (0) **   MOF Registration: ''
    49051 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49052 15:56:44 (0) **   MOF Registration: ''
    49053 15:56:44 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49054 15:56:44 (0) **   MOF Registration: ''
    49055 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49056 15:56:44 (0) **   MOF Registration: ''
    49057 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49058 15:56:44 (0) **   MOF Registration: ''
    49059 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49060 15:56:44 (0) **   MOF Registration: ''
    49061 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49062 15:56:44 (0) **   MOF Registration: ''
    49063 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49064 15:56:44 (0) **   MOF Registration: ''
    49065 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49066 15:56:44 (0) **   MOF Registration: ''
    49067 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49068 15:56:44 (0) **   MOF Registration: ''
    49069 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49070 15:56:44 (0) **   MOF Registration: ''
    49071 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49072 15:56:44 (0) **   MOF Registration: ''
    49073 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49074 15:56:44 (0) **   MOF Registration: ''
    49075 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49076 15:56:44 (0) **   MOF Registration: ''
    49077 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49078 15:56:44 (0) **   MOF Registration: ''
    49079 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49080 15:56:44 (0) **   MOF Registration: ''
    49081 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49082 15:56:44 (0) **   MOF Registration: ''
    49083 15:56:44 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49084 15:56:44 (0) **   MOF Registration: ''
    49085 15:56:44 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49086 15:56:44 (0) **   MOF Registration: ''
    49087 15:56:44 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49088 15:56:44 (0) **   MOF Registration: ''
    49089 15:56:44 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49090 15:56:44 (0) **   MOF Registration: ''
    49091 15:56:44 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49092 15:56:44 (0) **   MOF Registration: ''
    49093 15:56:44 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49094 15:56:44 (0) **   MOF Registration: ''
    49095 15:56:44 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49096 15:56:44 (0) **   MOF Registration: ''
    49097 15:56:44 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49098 15:56:44 (0) **   MOF Registration: ''
    49099 15:56:44 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49100 15:56:44 (0) **   MOF Registration: ''
    49101 15:56:44 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49102 15:56:44 (0) **   MOF Registration: ''
    49103 15:56:44 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49104 15:56:44 (0) **   MOF Registration: ''
    49105 15:56:44 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49106 15:56:44 (0) **   MOF Registration: ''
    49107 15:56:44 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49108 15:56:44 (0) **   MOF Registration: ''
    49109 15:56:44 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49110 15:56:44 (0) **   MOF Registration: ''
    49111 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49112 15:56:44 (0) **   MOF Registration: ''
    49113 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    49114 15:56:44 (0) **   MOF Registration: ''
    49115 15:56:44 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
    49116 15:56:44 (0) **    a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
    49117 15:56:44 (0) **    You can refresh the WMI class provider buffer with the following command:
    49118 15:56:44 (0) **
    49119 15:56:44 (0) **    i.e. 'WINMGMT.EXE /SYNCPERF'
    49120 15:56:44 (0) **
    49121 15:56:44 (0) ** WMI MOF representations: ............................................................................................ OK.
    49122 15:56:44 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    49123 15:56:44 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    49124 15:56:44 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    49125 15:56:44 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
    49126 15:56:44 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    49127 15:56:44 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    49128 15:56:44 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
    49129 15:56:44 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    49130 15:56:44 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    49131 15:56:44 (0) **
    49132 15:56:44 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    49133 15:56:44 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    49134 15:56:44 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    49135 15:56:44 (0) ** WMI static instances retrieved: ..................................................................................... 6304.
    49136 15:56:44 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    49137 15:56:44 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 3.
    49138 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49139 15:56:44 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    49140 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
    49141 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
    49142 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
    49143 15:56:44 (0) **
    49144 15:56:44 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    49145 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
    49146 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
    49147 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
    49148 15:56:44 (0) **
    49149 15:56:44 (0) ** 34 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
    49150 15:56:44 (0) ** => This error is typically a WMI error. This WMI error is due to:
    49151 15:56:44 (0) **    - a missing WMI class definition or object.
    49152 15:56:44 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
    49153 15:56:44 (0) **      You can correct the missing class definitions by:
    49154 15:56:44 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
    49155 15:56:44 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
    49156 15:56:44 (0) **            (This list can be built on a similar and working WMI Windows installation)
    49157 15:56:44 (0) **            The following command line must be used:
    49158 15:56:44 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
    49159 15:56:44 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
    49160 15:56:44 (0) **            with WMI by starting the ADAP process.
    49161 15:56:44 (0) **    - a WMI repository corruption.
    49162 15:56:44 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
    49163 15:56:44 (0) **      to validate the WMI repository operations.
    49164 15:56:44 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
    49165 15:56:44 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
    49166 15:56:44 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
    49167 15:56:44 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
    49168 15:56:44 (0) **      the WMI repository must be reconstructed.
    49169 15:56:44 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
    49170 15:56:44 (0) **          otherwise some applications may fail after the reconstruction.
    49171 15:56:44 (0) **          This can be achieved with the following command:
    49172 15:56:44 (0) **          i.e. 'WMIDiag ShowMOFErrors'
    49173 15:56:44 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
    49174 15:56:44 (0) **          ALL fixes previously mentioned.
    49175 15:56:44 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
    49176 15:56:44 (0) **
    49177 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49178 15:56:44 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
    49179 15:56:44 (0) ** INFO: Unexpected registry key value:
    49180 15:56:44 (0) **   - Current:  HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
    49181 15:56:44 (0) **   - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
    49182 15:56:44 (0) **     From the command line, the registry configuration can be corrected with the following command:
    49183 15:56:44 (0) **     i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
    49184 15:56:44 (0) **
    49185 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49186 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49187 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49188 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49189 15:56:44 (0) **
    49190 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49191 15:56:44 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    49192 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    49193 15:56:44 (0) **
    49194 15:56:44 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\CONN.LOMBARD\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_SSCRDS02_2015.04.15_15.48.25.LOG' for details.
    49195 15:56:44 (0) **
    49196 15:56:44 (0) ** WMIDiag v2.1 ended on 15 April 2015 at 15:56 (W:110 E:41 S:1).
    This seems to be the biggest problem:
    48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
    This seems to be the second biggest error (and there are a few of them):
    0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    I have tried:
    winmgmt /resyncperf
    winmgmt /verifyrepository
    winmgmt /salvagerepository
    winmgmt /resetrepository
    I have also tried registering the mof files with
    MOFCOMP <FileName.mof>
    Lastly, I even disabled the WMI service, renamed the Repository folder, and had it rebuild the repository.
    I got stuck on re registering the 'NT AUTHORITY\SYSTEM' (I think it is in the Components section in Administrative tools), as I could not find clear instructions on exactly how to go about it.
    Chkdsk found no errors
    Sfc /scannow found no errors
    winmgmt /verifyrepository finds no errors.
    I'm hoping someone here might be able to steer me in the right direction to get this resolved, as I do not want to rebuild a server that hosts a connection broker and has over 100 user profiles on it, as well as some very annoying and finniky LOB apps installed,
    which will have to manually be reinstalled for each profile.

    Hi,
    Here is a blog regarding how to fix WMI issue might be useful to you:
    Fixing WMI issues Using Batch Script
    http://social.technet.microsoft.com/wiki/contents/articles/6887.fixing-wmi-issues-using-batch-script.aspx
    In addition, you mentioned Remote Desktop Servers are in a cluster setup, would you tell us how did you create the cluster?
    As far as I know, with RD Connection Broker, we don’t need to create a cluster but just add multiple RD session hosts into one collection, then RD connection Broker would redirect sessions automatically.
    Best Regards,
    Amy
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Windows 8.1 - Update 1

    In the SCCM 2012 R2 console, looking through All Software Updates, we can see KB2919355, but not the associated Features Packs shown below.  We do see other Feature Packs but not the ones required below.
    Feature Pack for Windows (KB2932046)
    Feature Pack for Windows (KB2934018)
    Feature Pack for Windows (KB2937592)
    Update for Windows (KB2919355)
    reference http://www.ghacks.net/2014/05/15/find-version-windows-8-running/
    Does anyone see the above Feature Packs under their All Software Updates ?  (I wonder if Microsoft has released these to software update servers)
    Thanks

    Feature Pack for Windows (KB2932046)
    Feature Pack for Windows (KB2934018)
    Feature Pack for Windows (KB2937592)
    these updates are not listed in MUcatalog website, so it's unlikely that they would appear in WSUS sync feed (which is used by ConfigMgr SUM)
    but, those updates article numbers do appear in the KB article describing 2919355 (File information section of the article), so, these 3 "feature pack" items seem to be bundled inside 2919355???
    https://support.microsoft.com/kb/2919355
    My laptop does have Win8.1u1 installed.
    On my laptop, these 3 "Feature pack" KBnumbers, are not listed in any of the "updates installed" displays:
    a) WMI quickfixengineering class (2919355 exists but not the other three)
    b) Modern PC Settings app, Update history/View your update history (2919355 exists but not the other three)
    c) classic control panel/windows updates/installed updates (2919355 exists but not the other three)
    So, I think you are looking for something which doesn't exist as a separate download/update file.
    You get these three update packages, only as part of applying KB2919355.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Failed to Run Task Sequence 0x80040154

    I have been looking all over for some help with this one.
    I am pretty new to SCCM, but I setup a SCCM 2012 SP1 CU4 server.  I am using it for Endpoint Protection and Windows Updates.
    I have been reading on how to use PXE and have followed several guides to get this working.  Right now my workstation will successfully boot using PXE.  My problem is that the machine reboots immediately after "Preparing Network Connections." 
    I do get an IP address when I push F8 so it is not a network driver issue.  I can ping other devices on my network by name and by IP address so it is not a DNS problem either.
    There are 4 error lines in red, but I cannot figure out how to fix this. 
    Coult not create WMI locator class (80040154)
    Failed to connect to WMI namespace \\.\ROOT\CIMV2 (Code 0x80040154)
    RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence
    GetTsRegValue() failed. 0x80070002.
    Screen-shot:
    Here is the full log:
    <![LOG[LOGGING: Finalize process ID set to 752]LOG]!><time="12:00:59.369+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="756" file="tslogging.cpp:1495">
    <![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="12:00:59.369+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="756"
    file="bootshell.cpp:1052">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="12:00:59.369+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="756" file="util.cpp:963">
    <![LOG[Debug shell is enabled]LOG]!><time="12:00:59.369+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="756" file="bootshell.cpp:1063">
    <![LOG[Waiting for PNP initialization...]LOG]!><time="12:00:59.416+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:60">
    <![LOG[RAM Disk Boot Path: NET(0)\SMSIMAGES\PDC00019\BOOT.PDC00019.WIM]LOG]!><time="12:00:59.416+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="configpath.cpp:186">
    <![LOG[Booted from network (PXE)]LOG]!><time="12:00:59.416+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="configpath.cpp:201">
    <![LOG[Network(PXE) path: X:\sms\data\]LOG]!><time="12:00:59.416+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="configpath.cpp:203">
    <![LOG[Found config path X:\sms\data\]LOG]!><time="12:00:59.416+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:545">
    <![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="12:00:59.416+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:579">
    <![LOG[X:\sms\data\WinPE does not exist.]LOG]!><time="12:00:59.416+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:596">
    <![LOG[X:\_SmsTsWinPE\WinPE does not exist.]LOG]!><time="12:00:59.416+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:610">
    <![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="12:00:59.447+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:857">
    <![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="12:01:01.583+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="756" file="bootshell.cpp:857">
    <![LOG[The command completed successfully.]LOG]!><time="12:01:01.583+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="756" file="bootshell.cpp:939">
    <![LOG[Successfully launched command shell.]LOG]!><time="12:01:01.583+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="756" file="bootshell.cpp:430">
    <![LOG[The command completed successfully.]LOG]!><time="12:01:09.466+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:939">
    <![LOG[Starting DNS client service.]LOG]!><time="12:01:09.466+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:663">
    <![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="12:01:09.988+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760"
    file="bootshell.cpp:857">
    <![LOG[The command completed successfully.]LOG]!><time="12:01:09.988+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:939">
    <![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="12:01:10.066+480" date="04-14-2014" component="TSMBootstrap" context="" type="1" thread="848"
    file="tsmbootstrap.cpp:1129">
    <![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="12:01:10.066+480" date="04-14-2014" component="TSMBootstrap" context="" type="0" thread="848"
    file="tsmbootstrap.cpp:1130">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="12:01:10.066+480" date="04-14-2014" component="TSMBootstrap" context="" type="1" thread="848" file="util.cpp:963">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="12:01:10.066+480" date="04-14-2014" component="TSMBootstrap" context="" type="1" thread="848" file="resourceutils.cpp:169">
    <![LOG[Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH]LOG]!><time="12:01:10.066+480" date="04-14-2014" component="TSMBootstrap" context="" type="0" thread="848"
    file="tsmbootstrap.cpp:963">
    <![LOG[PXE Boot with Root = X:\]LOG]!><time="12:01:10.066+480" date="04-14-2014" component="TSMBootstrap" context="" type="1" thread="848" file="tsmbootstrap.cpp:1062">
    <![LOG[Executing from PXE in WinPE]LOG]!><time="12:01:10.066+480" date="04-14-2014" component="TSMBootstrap" context="" type="1" thread="848" file="tsmbootstrap.cpp:1077">
    <![LOG[Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll]LOG]!><time="12:01:10.066+480" date="04-14-2014" component="TSMBootstrap" context="" type="0" thread="848" file="tsmbootstraputil.cpp:1320">
    <![LOG[TsPxe.dll loaded]LOG]!><time="12:01:10.082+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tsmbootstraputil.cpp:1330">
    <![LOG[Device has PXE booted]LOG]!><time="12:01:10.082+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspxe.cpp:122">
    <![LOG[Variable Path: \SMSTemp\2014.04.14.11.56.52.0001.{003FC085-A2AB-4BDA-84A6-11CF9C5CDC95}.boot.var]LOG]!><time="12:01:10.082+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848"
    file="tspxe.cpp:134">
    <![LOG[Variable Key Len: 69]LOG]!><time="12:01:10.082+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspxe.cpp:141">
    <![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="12:01:10.082+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="fwopen.cpp:123">
    <![LOG[Executing: X:\sms\bin\x64\smstftp.exe -i 10.1.1.216 get \SMSTemp\2014.04.14.11.56.52.0001.{003FC085-A2AB-4BDA-84A6-11CF9C5CDC95}.boot.var X:\sms\data\variables.dat]LOG]!><time="12:01:10.082+480" date="04-14-2014" component="TSPxe"
    context="" type="0" thread="848" file="tspxe.cpp:177">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="12:01:10.145+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="commandline.cpp:228">
    <![LOG[Set command line: "X:\sms\bin\x64\smstftp.exe" -i 10.1.1.216 get \SMSTemp\2014.04.14.11.56.52.0001.{003FC085-A2AB-4BDA-84A6-11CF9C5CDC95}.boot.var X:\sms\data\variables.dat]LOG]!><time="12:01:10.145+480" date="04-14-2014"
    component="TSPxe" context="" type="0" thread="848" file="commandline.cpp:731">
    <![LOG[Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 10.1.1.216 get \SMSTemp\2014.04.14.11.56.52.0001.{003FC085-A2AB-4BDA-84A6-11CF9C5CDC95}.boot.var X:\sms\data\variables.dat]LOG]!><time="12:01:10.145+480" date="04-14-2014"
    component="TSPxe" context="" type="1" thread="848" file="commandline.cpp:827">
    <![LOG[Process completed with exit code 0]LOG]!><time="12:01:10.176+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="commandline.cpp:1123">
    <![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="12:01:10.176+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="fwopen.cpp:146">
    <![LOG[Successfully downloaded pxe variable file.]LOG]!><time="12:01:10.176+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tspxe.cpp:187">
    <![LOG[we are booted using PXE]LOG]!><time="12:01:10.176+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:2629">
    <![LOG[we are booted using PXE and we use a generated password]LOG]!><time="12:01:10.176+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:2634">
    <![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="12:01:10.176+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsremovablemedia.cpp:322">
    <![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\qfe\nts\sms\framework\smscrypt\windes.cpp,165)]LOG]!><time="12:01:10.176+480" date="04-14-2014" component="TSPxe" context=""
    type="0" thread="848" file="windes.cpp:165">
    <![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\qfe\nts\sms\framework\tscore\tsremovablemedia.cpp,387)]LOG]!><time="12:01:10.176+480"
    date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tsremovablemedia.cpp:387">
    <![LOG[Verifying media password.]LOG]!><time="12:01:10.176+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:271">
    <![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="12:01:10.176+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsremovablemedia.cpp:322">
    <![LOG[Found network adapter "Intel(R) 82567LM-3 Gigabit Network Connection" with IP Address 10.1.1.63.]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="0"
    thread="848" file="tsmbootstraputil.cpp:474">
    <![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsremovablemedia.cpp:322">
    <![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\qfe\nts\sms\framework\smscrypt\windes.cpp,165)]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context=""
    type="0" thread="848" file="windes.cpp:165">
    <![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\qfe\nts\sms\framework\tscore\tsremovablemedia.cpp,387)]LOG]!><time="12:01:10.191+480"
    date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tsremovablemedia.cpp:387">
    <![LOG[Entering TSMediaWizardControl::GetPolicy.]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tsmediawizardcontrol.cpp:527">
    <![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00']LOG]!><time="12:01:10.191+480"
    date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="environmentscope.cpp:284">
    <![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848"
    file="environmentscope.cpp:659">
    <![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00']LOG]!><time="12:01:10.191+480"
    date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="environmentscope.cpp:284">
    <![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848"
    file="environmentscope.cpp:659">
    <![LOG[Setting LogMaxSize to 1000000]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:555">
    <![LOG[Setting LogMaxHistory to 1]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:556">
    <![LOG[Setting LogLevel to 0]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:557">
    <![LOG[Setting LogEnabled to 1]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:558">
    <![LOG[Setting LogDebug to 1]LOG]!><time="12:01:10.191+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:559">
    <![LOG[UEFI: false]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:569">
    <![LOG[Loading variables from the Task Sequencing Removable Media.]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:584">
    <![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsremovablemedia.cpp:322">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="util.cpp:963">
    <![LOG[Setting SMSTSMP TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSMediaGuid TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSBootMediaPackageID TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSHTTPPort TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSHTTPSPort TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSIISSSLState TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSLaunchMode TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSMediaPFX TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSPublicRootKey TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSSiteCode TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSSiteSigningCertificate TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSUseFirstCert TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSx64UnknownMachineGUID TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Setting _SMSTSx86UnknownMachineGUID TS environment variable]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:604">
    <![LOG[Root CA Public Certs=]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:615">
    <![LOG[Missing root CA environment variable from variables file]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:621">
    <![LOG[Support Unknown Machines: 0]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:632">
    <![LOG[Custom hook from X:\\TSConfig.INI is ]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:675">
    <![LOG[No hook is found to be executed before downloading policy]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:699">
    <![LOG[Authenticator from the environment is empty.]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:838">
    <![LOG[Need to create Authenticator Info using PFX]LOG]!><time="12:01:10.207+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:850">
    <![LOG[Initialized CStringStream object with string: {16863E43-476B-4EE9-8E12-00F504776669};2014-04-14T20:01:10Z.]LOG]!><time="12:01:10.238+480" date="04-14-2014" component="TSPxe" context="" type="0"
    thread="848" file="stringstream.cpp:101">
    <![LOG[Set media certificate in transport]LOG]!><time="12:01:10.238+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libsmsmessaging.cpp:9418">
    <![LOG[Set authenticator in transport]LOG]!><time="12:01:10.238+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libsmsmessaging.cpp:7751">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SCCM-Corp.pdcarea.lcl:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA]LOG]!><time="12:01:10.254+480" date="04-14-2014" component="TSPxe" context="" type="1"
    thread="848" file="libsmsmessaging.cpp:8621">
    <![LOG[Request was succesful.]LOG]!><time="12:01:10.270+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libsmsmessaging.cpp:8956">
    <![LOG[Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider]LOG]!><time="12:01:10.270+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libcrypt.cpp:1914">
    <![LOG[Default CSP Type is 24]LOG]!><time="12:01:10.270+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libcrypt.cpp:1915">
    <![LOG[New settings:]LOG]!><time="12:01:10.270+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:925">
    <![LOG[    site=PDC,PDC, MP=http://SCCM-Corp.pdcarea.lcl, ports: http=80,https=443]LOG]!><time="12:01:10.270+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848"
    file="tsmediawizardcontrol.cpp:927">
    <![LOG[    certificates are received from MP.]LOG]!><time="12:01:10.270+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:931">
    <![LOG[Unknown machine GUIDs: 99572c96-584f-4c19-bd8b-fc4409608be6 29a3e6d5-a627-4e52-b02c-f09c8acaba5c]LOG]!><time="12:01:10.270+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848"
    file="tsmediawizardcontrol.cpp:986">
    <![LOG[Getting MP time information]LOG]!><time="12:01:10.270+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:1021">
    <![LOG[Set authenticator in transport]LOG]!><time="12:01:10.270+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libsmsmessaging.cpp:7751">
    <![LOG[Requesting client identity]LOG]!><time="12:01:10.285+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="libsmsmessaging.cpp:5760">
    <![LOG[Setting message signatures.]LOG]!><time="12:01:10.285+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libsmsmessaging.cpp:1297">
    <![LOG[Setting the authenticator.]LOG]!><time="12:01:10.285+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libsmsmessaging.cpp:1327">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SCCM-Corp.pdcarea.lcl:80  CCM_POST /ccm_system/request]LOG]!><time="12:01:10.301+480" date="04-14-2014" component="TSPxe" context="" type="1"
    thread="848" file="libsmsmessaging.cpp:8621">
    <![LOG[Request was succesful.]LOG]!><time="12:01:10.301+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libsmsmessaging.cpp:8956">
    <![LOG[::DecompressBuffer(65536)]LOG]!><time="12:01:10.301+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="ccmzlib.cpp:739">
    <![LOG[Decompression (zlib) succeeded: original size 432, uncompressed size 2540.]LOG]!><time="12:01:10.316+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="ccmzlib.cpp:651">
    <![LOG[-60 -60]LOG]!><time="12:01:10.316+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="libsmsmessaging.cpp:5956">
    <![LOG[Server time zone info: 360, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60]LOG]!><time="12:01:10.316+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848"
    file="libsmsmessaging.cpp:6055">
    <![LOG[Client Identity: ]LOG]!><time="12:01:10.316+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="libsmsmessaging.cpp:6140">
    <![LOG[Netbios name: ]LOG]!><time="12:01:10.316+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="libsmsmessaging.cpp:6156">
    <![LOG[Current time: 2014-04-14 20:01:10.316 TZ:Pacific Standard Time Bias:0480]LOG]!><time="12:01:10.316+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:1090">
    <![LOG[Current time zone info: 480, Pacific Standard Time, [0 0 0 0 0 0 0 0], 0, , [0 0 0 0 0 0 0 0], 0]LOG]!><time="12:01:10.316+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848"
    file="tsmediawizardcontrol.cpp:1118">
    <![LOG[Adjusting the system time: -10800.340 seconds]LOG]!><time="12:01:10.316+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:1120">
    <![LOG[Time zone info set to: 360, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60]LOG]!><time="15:01:10.316+300" date="04-14-2014" component="TSPxe" context="" type="1" thread="848"
    file="tsmediawizardcontrol.cpp:1156">
    <![LOG[New time: 2014-04-14 17:01:09.975]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:1172">
    <![LOG[Current time: 2014-04-14 17:01:09.973 TZ: Bias:0360]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:1178">
    <![LOG[Downloading policy from http://SCCM-Corp.pdcarea.lcl.]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmediawizardcontrol.cpp:1185">
    <![LOG[Initializing HTTP transport.]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:817">
    <![LOG[   Setting URL = http://SCCM-Corp.pdcarea.lcl.]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:818">
    <![LOG[   Setting Ports = 80,443.]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:821">
    <![LOG[   Setting CRL = false.]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:824">
    <![LOG[   Setting Server Certificates.]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:841">
    <![LOG[Set authenticator in transport]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="libsmsmessaging.cpp:7751">
    <![LOG[   Setting Media Certificate.]LOG]!><time="12:01:09.973+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:849">
    <![LOG[Preparing Client Identity Request.]LOG]!><time="12:01:09.987+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:583">
    <![LOG[    Setting transport.]LOG]!><time="12:01:09.987+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:586">
    <![LOG[    Setting SourceID = {16863E43-476B-4EE9-8E12-00F504776669}.]LOG]!><time="12:01:09.987+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848"
    file="tspolicy.cpp:590">
    <![LOG[    Setting site code = PDC.]LOG]!><time="12:01:09.987+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:595">
    <![LOG[Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.]LOG]!><time="12:01:09.987+300" date="04-14-2014" component="TSPxe" context="" type="1"
    thread="848" file="utils.cpp:1314">
    <![LOG[spLocator.createInstance( ((bUseAdminLocator == true) ? CLSID_WbemAdministrativeLocator : CLSID_WbemLocator ) ), HRESULT=80040154 (e:\qfe\nts\sms\framework\core\ccmcore\wminamespace.cpp,260)]LOG]!><time="12:01:09.987+300" date="04-14-2014"
    component="TSPxe" context="" type="0" thread="848" file="wminamespace.cpp:260">
    <![LOG[Could not create WMI locator class (80040154)]LOG]!><time="12:01:09.987+300" date="04-14-2014" component="TSPxe" context="" type="3" thread="848" file="wminamespace.cpp:260">
    <![LOG[spNamespace.Open(c_szCIMv2Namespace), HRESULT=80040154 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,605)]LOG]!><time="12:01:09.987+300" date="04-14-2014" component="TSPxe" context="" type="0"
    thread="848" file="tspolicy.cpp:605">
    <![LOG[Failed to connect to WMI namespace \\.\ROOT\CIMV2 (Code 0x80040154)]LOG]!><time="12:01:09.987+300" date="04-14-2014" component="TSPxe" context="" type="3" thread="848" file="tspolicy.cpp:605">
    <![LOG[TS::Policy::GetClientIdentity (&m_oHttpTransport, m_sSiteCode, sMediaGuid.c_str(), m_sClientGUID, m_sNetbiosName, bUnknown, sServerName, sServerRemoteName, sImportedClientIdentity), HRESULT=80040154 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,868)]LOG]!><time="12:01:09.987+300"
    date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tspolicy.cpp:868">
    <![LOG[m_pPolicyManager->init( sMP, nHttpPort, nHttpsPort, sSiteCode, bUseCRL, L"", sMediaPfx, sMediaGuid, sEnterpriseCert, sServerCerts, sSiteSigningCert, sAuthenticator), HRESULT=80040154 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1198)]LOG]!><time="12:01:10.002+300"
    date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tsmediawizardcontrol.cpp:1198">
    <![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSPxe" context="" type="0" thread="848" file="tsmediawizardcontrol.cpp:1378">
    <![LOG[GetPolicy(), HRESULT=80040154 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2448)]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSPxe" context=""
    type="0" thread="848" file="tsmediawizardcontrol.cpp:2448">
    <![LOG[RunWizardForPXE(), HRESULT=80040154 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2790)]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSPxe" context=""
    type="0" thread="848" file="tsmediawizardcontrol.cpp:2790">
    <![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80040154 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078)]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSPxe"
    context="" type="0" thread="848" file="tsmbootstrap.cpp:1078">
    <![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80040154 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1183)]LOG]!><time="12:01:10.002+300" date="04-14-2014"
    component="TSPxe" context="" type="0" thread="848" file="tsmbootstrap.cpp:1183">
    <![LOG[Exiting with return code 0x80040154]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSPxe" context="" type="1" thread="848" file="tsmbootstrap.cpp:1195">
    <![LOG[Execution complete.]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:690">
    <![LOG[hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell" context="" type="0"
    thread="760" file="environmentscope.cpp:515">
    <![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell" context="" type="0"
    thread="760" file="environmentlib.cpp:337">
    <![LOG[this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell" context="" type="0"
    thread="760" file="environmentlib.cpp:549">
    <![LOG[::RegOpenKeyExW (HKEY_LOCAL_MACHINE, c_szSMSTSKey, 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,258)]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell"
    context="" type="0" thread="760" file="utils.cpp:258">
    <![LOG[RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:258">
    <![LOG[GetTsRegValue() failed. 0x80070002.]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:279">
    <![LOG[End program: ]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:722">
    <![LOG[Finalizing logging from process 752]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="12:01:10.002+300" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
    <![LOG[LOGGING: Setting log directory to "D:\SMSTSLog".]LOG]!><time="12:01:10.067+300" date="04-14-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1808">
    Any help would be great!
    Thanks in advance!

    Hi,
    Please try to update the boot image.
    For more information:http://social.technet.microsoft.com/Forums/en-US/d2806294-97c7-4aa3-849b-3c176d9a9ce1/pxe-fails-to-boot?forum=configmanagerdeployment
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for

  • Error in Installation of SAP R/3 4.7 - Urgent Help Pls !!!

    Hi All, I have a problem while installing SAP R/3 4.7. The Central instance has been successfully installed. Error occurred while installing the database instance. I am using SAPDB as the database. The error I get is the following: **INFO 2008-03-01

  • Problem with SLD in XI Configuration

    Hi, I am getting the error like "Role Assignment Failed" while trying to do post installation activities in XI.when we go to SLD Data Supplier Bridge and required inputs are provided in the fields and click on "assign application roles to user groups

  • Acconts payable Flow

    Hi Experts, 1.       From purchase to Vendor payment flow which one is correct  ...   PR ->PO (ME23N) -> GRN (MIGO) -> Invoice verification (MIRO) -> AP Vendor invoice (FB60) -> Payment clearance (F-53)                                                

  • Oracle session creation takes long time

    Hi , I am getting the below mentioned error continously in the alert log file. I am unable login through sqlplus on my remote database server from clients . Where as i am able connect locally on the server. some times i am able to connect from client

  • Mixed platform installation for XI

    Hi, Does anyone know if it is possible to install the DB component for XI on One platform say HPUX / Solaris and application layer on Wintel? Thanks in advance. Sagar Aparajit