Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, July 13, 2012 9:51 AM
Hi,
I have a one-site SCCM 2012 installation on a Windows Server 2008 R2 Standard SP1 server with 16 GB of RAM.
I am currently upgradering our MS Forefront to MS Endpoint, and during this process I install the SCCM agent on all our servers.
On many servers (>50) there has been no problems, but on a few I get the error: "Last Installation Error: 2147942405" in the SCCM console.
It is on Windows server 2008 R2 standard, 2003 standard SP2 and even on a XP Pro SP3 computer I get the error.
All servers/workstations are joined to the domain and I have added the SCCM installation account to the local administrator group on each server.
Our Active Directory schema has been succesfull extended with the SCCM attributes.
The eventlog does not say anything on the failed servers/computers.
The only thing I can find on the error number is http://myitforum.com/myitforumwp/2011/10/27/sccm-client-install-error-codes/ and the windows firewall is disabled on all the failed servers/computers.
I have been through the http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_ClientInstallLog site, but I cannot find any logfiles than can help me locate the error more precisely from the SCCM server.
Can you help me?
Kind regards,
Carl-Marius
All replies (18)
Wednesday, July 18, 2012 9:21 AM âś…Answered
Have you tried to install cm12 client on the server manually?
Monday, July 16, 2012 8:31 AM
I am guessing you are talking about push installation. Did you check the CCM.log file on the CM12 Server? What abou ccmsetup.log and client.msi.log files on the client? Is there any error message?
Wednesday, July 18, 2012 6:59 AM
Hi dekac99,
There is no log files on the server (MS 2008 R2 standard), but it says the following in the CCM.log on the server:
======>Begin Processing request: "2097154063", machine name: "GIZZ1"
Execute query exec [sp_IsMPAvailable] N'PRI'
> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)
> Attempting to connect to administrative share '\GIZZ1\admin$' using account 'zzz\yyy'
> The 'best-shot' account has now succeeded 76 times and failed 0 times.
> Connected to administrative share on machine GIZZ1 using account 'zzz\yyy'
> Attempting to make IPC connection to share \GIZZ1\IPC$
> Searching for SMSClientInstall.* under '\GIZZ1\admin$\
CWmi::GetFirstObjectFromQuery(): ExecQuery() failed. - 0x80070005
> Unable to get Win32_OperatingSystem object from WMI on remote machine "GIZZ1", error = 0x80070005.
> Deleting SMS Client Install Lock File '\GIZZ1\admin$\SMSClientInstall.PRI'
Execute query exec [sp_CP_SetLastErrorCode] 2097154063, -2147024891
Stored request "2097154063", machine name "GIZZ11", in queue "Retry".
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154063, 2
Execute query exec [sp_CP_SetLatest] 2097154063, N'07/17/2012 11:18:56', 350
<======End request: "2097154063", machine name: "GIZZ1".
Wednesday, July 18, 2012 7:11 AM
I have run a WMIDiag.exe on the "GIZZ1" server in a elevated command prompt and this gave the following result:
35991 09:08:42 (0) ** WMIDiag v2.1 started on 18. juli 2012 at 09:01.
35992 09:08:42 (0) **
35993 09:08:42 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
35994 09:08:42 (0) **
35995 09:08:42 (0) ** This script is not supported under any Microsoft standard support program or service.
35996 09:08:42 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
35997 09:08:42 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
35998 09:08:42 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
35999 09:08:42 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
36000 09:08:42 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
36001 09:08:42 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
36002 09:08:42 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
36003 09:08:42 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
36004 09:08:42 (0) ** of the possibility of such damages.
36005 09:08:42 (0) **
36006 09:08:42 (0) **
36007 09:08:42 (0) **
36008 09:08:42 (0) ** WMI REPORT: BEGIN
36009 09:08:42 (0) **
36010 09:08:42 (0) **
36011 09:08:42 (0) **
36012 09:08:42 (0) ** Windows Server 2008 R2 - No Service Pack - 64-bit (7600) - User 'xxx\yyy' on computer 'GIZZ1'.
36013 09:08:42 (0) **
36014 09:08:42 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
36015 09:08:42 (0) ** INFO: => 1 possible incorrect shutdown(s) detected on:
36016 09:08:42 (0) ** - Shutdown on 09 December 2011 18:30:56 (GMT-0).
36017 09:08:42 (0) **
36018 09:08:42 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
36019 09:08:42 (0) ** Drive type: ......................................................................................................... SCSI (VMware Virtual disk SCSI Disk Device).
36020 09:08:42 (0) ** There are no missing WMI system files: .............................................................................. OK.
36021 09:08:42 (0) ** There are no missing WMI repository files: .......................................................................... OK.
36022 09:08:42 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
36023 09:08:42 (0) ** AFTER running WMIDiag:
36024 09:08:42 (0) ** The WMI repository has a size of: ................................................................................... 21 MB.
36025 09:08:42 (0) ** - Disk free space on 'C:': .......................................................................................... 7381 MB.
36026 09:08:42 (0) ** - INDEX.BTR, 5128192 bytes, 18-07-2012 09:04:18
36027 09:08:42 (0) ** - MAPPING1.MAP, 56108 bytes, 17-07-2012 23:41:48
36028 09:08:42 (0) ** - MAPPING2.MAP, 56108 bytes, 18-07-2012 09:04:18
36029 09:08:42 (0) ** - OBJECTS.DATA, 16646144 bytes, 18-07-2012 09:04:18
36030 09:08:42 (0) **
36031 09:08:42 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
36032 09:08:42 (0) **
36033 09:08:42 (0) ** DCOM Status: ........................................................................................................ OK.
36034 09:08:42 (0) ** WMI registry setup: ................................................................................................. OK.
36035 09:08:42 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
36036 09:08:42 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
36037 09:08:42 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
36038 09:08:42 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
36039 09:08:42 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
36040 09:08:42 (0) ** this can prevent the service/application to work as expected.
36041 09:08:42 (0) **
36042 09:08:42 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
36043 09:08:42 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
36044 09:08:42 (0) **
36045 09:08:42 (0) ** WMI service DCOM setup: ............................................................................................. OK.
36046 09:08:42 (0) ** WMI components DCOM registrations: .................................................................................. OK.
36047 09:08:42 (0) ** WMI ProgID registrations: ........................................................................................... OK.
36048 09:08:42 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
36049 09:08:42 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
36050 09:08:42 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
36051 09:08:42 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
36052 09:08:42 (0) **
36053 09:08:42 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
36054 09:08:42 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
36055 09:08:42 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
36056 09:08:42 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
36057 09:08:42 (0) ** selecting 'Run as Administrator'.
36058 09:08:42 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
36059 09:08:42 (0) ** in the Task Scheduler within the right security context.
36060 09:08:42 (0) **
36061 09:08:42 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
36062 09:08:42 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
36063 09:08:42 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
36064 09:08:42 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
36065 09:08:42 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
36066 09:08:42 (0) **
36067 09:08:42 (0) ** Overall DCOM security status: ....................................................................................... OK.
36068 09:08:42 (0) ** Overall WMI security status: ........................................................................................ OK.
36069 09:08:42 (0) ** - Started at 'Root'
36070 09:08:42 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
36071 09:08:42 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
36072 09:08:42 (0) ** 'select * from MSFT_SCMEventLogEvent'
36073 09:08:42 (0) **
36074 09:08:42 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
36075 09:08:42 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
36076 09:08:42 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
36077 09:08:42 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
36078 09:08:42 (0) ** - ROOT/SERVICEMODEL.
36079 09:08:42 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
36080 09:08:42 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
36081 09:08:42 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
36082 09:08:42 (0) ** i.e. 'WMIC.EXE /NODE:"GIZZ1" /AUTHLEVEL:Pktprivacy /NAMESPACE:\ROOT\SERVICEMODEL Class __SystemSecurity'
36083 09:08:42 (0) **
36084 09:08:42 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
36085 09:08:42 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
36086 09:08:42 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 32 ERROR(S)!
36087 09:08:42 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36088 09:08:42 (0) ** MOF Registration: ''
36089 09:08:42 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36090 09:08:42 (0) ** MOF Registration: ''
36091 09:08:42 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36092 09:08:42 (0) ** MOF Registration: ''
36093 09:08:42 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36094 09:08:42 (0) ** MOF Registration: ''
36095 09:08:42 (0) ** - Root/CIMV2, Win32_PerfFormattedData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36096 09:08:42 (0) ** MOF Registration: ''
36097 09:08:42 (0) ** - Root/CIMV2, Win32_PerfRawData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36098 09:08:42 (0) ** MOF Registration: ''
36099 09:08:42 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36100 09:08:42 (0) ** MOF Registration: ''
36101 09:08:42 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36102 09:08:42 (0) ** MOF Registration: ''
36103 09:08:42 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36104 09:08:42 (0) ** MOF Registration: ''
36105 09:08:42 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36106 09:08:42 (0) ** MOF Registration: ''
36107 09:08:42 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36108 09:08:42 (0) ** MOF Registration: ''
36109 09:08:42 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36110 09:08:42 (0) ** MOF Registration: ''
36111 09:08:42 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36112 09:08:42 (0) ** MOF Registration: ''
36113 09:08:42 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36114 09:08:42 (0) ** MOF Registration: ''
36115 09:08:42 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36116 09:08:42 (0) ** MOF Registration: ''
36117 09:08:42 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36118 09:08:42 (0) ** MOF Registration: ''
36119 09:08:42 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36120 09:08:42 (0) ** MOF Registration: ''
36121 09:08:42 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36122 09:08:42 (0) ** MOF Registration: ''
36123 09:08:42 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36124 09:08:42 (0) ** MOF Registration: ''
36125 09:08:42 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36126 09:08:42 (0) ** MOF Registration: ''
36127 09:08:42 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36128 09:08:42 (0) ** MOF Registration: ''
36129 09:08:42 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36130 09:08:42 (0) ** MOF Registration: ''
36131 09:08:42 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36132 09:08:42 (0) ** MOF Registration: ''
36133 09:08:42 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36134 09:08:42 (0) ** MOF Registration: ''
36135 09:08:42 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36136 09:08:42 (0) ** MOF Registration: ''
36137 09:08:42 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36138 09:08:42 (0) ** MOF Registration: ''
36139 09:08:42 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36140 09:08:42 (0) ** MOF Registration: ''
36141 09:08:42 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36142 09:08:42 (0) ** MOF Registration: ''
36143 09:08:42 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36144 09:08:42 (0) ** MOF Registration: ''
36145 09:08:42 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36146 09:08:42 (0) ** MOF Registration: ''
36147 09:08:42 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36148 09:08:42 (0) ** MOF Registration: ''
36149 09:08:42 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
36150 09:08:42 (0) ** MOF Registration: ''
36151 09:08:42 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
36152 09:08:42 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
36153 09:08:42 (0) ** You can refresh the WMI class provider buffer with the following command:
36154 09:08:42 (0) **
36155 09:08:42 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
36156 09:08:42 (0) **
36157 09:08:42 (0) ** WMI MOF representations: ............................................................................................ OK.
36158 09:08:42 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
36159 09:08:42 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
36160 09:08:42 (2) !! WARNING: WMI EXECQUERY operation errors reported: ................................................................... 1 WARNING(S)!
36161 09:08:42 (0) ** - Root/CIMV2, 'Select * From Win32_USBController' did not return any instance while AT LEAST 1 instance is expected.
36162 09:08:42 (0) **
36163 09:08:42 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
36164 09:08:42 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
36165 09:08:42 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
36166 09:08:42 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
36167 09:08:42 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
36168 09:08:42 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
36169 09:08:42 (0) **
36170 09:08:42 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
36171 09:08:42 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
36172 09:08:42 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
36173 09:08:42 (0) ** WMI static instances retrieved: ..................................................................................... 2477.
36174 09:08:42 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
36175 09:08:42 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
36176 09:08:42 (0) **
36177 09:08:42 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
36178 09:08:42 (0) ** DCOM: ............................................................................................................. 0.
36179 09:08:42 (0) ** WINMGMT: .......................................................................................................... 0.
36180 09:08:42 (0) ** WMIADAPTER: ....................................................................................................... 0.
36181 09:08:42 (0) **
36182 09:08:42 (0) ** # of additional Event Log events AFTER WMIDiag execution:
36183 09:08:42 (0) ** DCOM: ............................................................................................................. 0.
36184 09:08:42 (0) ** WINMGMT: .......................................................................................................... 0.
36185 09:08:42 (0) ** WMIADAPTER: ....................................................................................................... 0.
36186 09:08:42 (0) **
36187 09:08:42 (0) ** 32 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
36188 09:08:42 (0) ** => This error is typically a WMI error. This WMI error is due to:
36189 09:08:42 (0) ** - a missing WMI class definition or object.
36190 09:08:42 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
36191 09:08:42 (0) ** You can correct the missing class definitions by:
36192 09:08:42 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
36193 09:08:42 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
36194 09:08:42 (0) ** (This list can be built on a similar and working WMI Windows installation)
36195 09:08:42 (0) ** The following command line must be used:
36196 09:08:42 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
36197 09:08:42 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
36198 09:08:42 (0) ** with WMI by starting the ADAP process.
36199 09:08:42 (0) ** - a WMI repository corruption.
36200 09:08:42 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
36201 09:08:42 (0) ** to validate the WMI repository operations.
36202 09:08:42 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
36203 09:08:42 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
36204 09:08:42 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
36205 09:08:42 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
36206 09:08:42 (0) ** the WMI repository must be reconstructed.
36207 09:08:42 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
36208 09:08:42 (0) ** otherwise some applications may fail after the reconstruction.
36209 09:08:42 (0) ** This can be achieved with the following command:
36210 09:08:42 (0) ** i.e. 'WMIDiag ShowMOFErrors'
36211 09:08:42 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
36212 09:08:42 (0) ** ALL fixes previously mentioned.
36213 09:08:42 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
36214 09:08:42 (0) **
36215 09:08:42 (0) **
36216 09:08:42 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
36217 09:08:42 (0) ** INFO: Unexpected registry key value:
36218 09:08:42 (0) ** - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
36219 09:08:42 (0) ** - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
36220 09:08:42 (0) ** From the command line, the registry configuration can be corrected with the following command:
36221 09:08:42 (0) ** i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
36222 09:08:42 (0) **
36223 09:08:42 (0) **
36224 09:08:42 (0) **
36225 09:08:42 (0) **
36226 09:08:42 (0) **
36227 09:08:42 (0) **
36228 09:08:42 (0) **
36229 09:08:42 (0) ** WMI REPORT: END
36230 09:08:42 (0) **
36231 09:08:42 (0) **
36232 09:08:42 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\YYY\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.RTM.64_GIZZ1_2012.07.18_09.00.58.LOG' for details.
36233 09:08:42 (0) **
36234 09:08:42 (0) ** WMIDiag v2.1 ended on 18. juli 2012 at 09:08 (W:66 E:36 S:1).
Wednesday, July 18, 2012 7:12 AM
I have tried to run the following command in a elevated command prompt:
winmgmt /verifyrepository
This returns the message: "WMI repository is consistent"
Do you know any way to fix this strange WMI access denied problem?
Kind regards,
Carl-Marius
Wednesday, July 18, 2012 7:35 AM
Are you able to make a WMI connection from the SCCM server to the client with the account used for Client push installation (You can use WbemTest and try connecting to <a href="file://\\root\cimv2">\<Clientname>\root\cimv2)?
Wednesday, July 18, 2012 7:44 AM
I have just tried to run a "WMIDiag.vbs writeinrepository" in a elevated command prompt, but to no avail.
The result is stille the same.
Kind regards,
Carl-Marius
Wednesday, July 18, 2012 7:58 AM
Hi dekac99,
I can log on to the SCCM server with the service user account and I can succesfully connect to the remote server (GIZZ1).
If I run the WQL query: "Select * from win32_Process", I get 52 objects back.
Kind regards,
Carl-Marius
Wednesday, July 18, 2012 8:14 AM
What do you mean with "service user account"!? Is this the client push install account?
Wednesday, July 18, 2012 8:15 AM
Yes, this is the client push install account.
Kind regards,
Carl-Marius
Wednesday, July 18, 2012 8:16 AM
Any error message in %systemdrive%\WINDOWS\CCM\Logs\EndpointProtectionAgent.log on the client?
Wednesday, July 18, 2012 8:22 AM
There is no CCM folder, the server does first get the Endpoint Proctection agent installed when the SCCM agent is installed.
Currently the server runs the MS Forefront client security.
Kind regards,
Carl-Marius
Wednesday, July 18, 2012 8:26 AM
What about ccmsetup.log and client.msi.log?
Wednesday, July 18, 2012 8:39 AM
There is no file on the server by that name.
There is no info in the eventlog viewer on the server, except for the security log, where the client push install account has made a succesfull logon (EventID 4624) and 12 seconds later it has made a succesfull logoff (EventID 4634).
The "Application" and "System" eventlog does not contain any information.
Kind regards,
Carl-Marius
Wednesday, July 18, 2012 8:49 AM
Is there anything in ccm.log on the sccm server?
Wednesday, July 18, 2012 9:02 AM
Only the information I posted earlier in the post number 3 from the top in this thread :-)
Kind regards,
Carl-Marius
Wednesday, July 18, 2012 9:38 AM
No.
I will report back when I have tried that.
Kind regards,
Carl-Marius
Thursday, July 19, 2012 6:38 AM | 1 vote
Hi Dekac99,
It works when I install the SCCM agent manually.
After a reboot the agent is registered correctly up against the SCCM server, so I will say it works.
But I do not understand why the push installation does not work.
Thank you for your help!
Kind regards,
Carl-Marius