Asked by:
Since SP1 upgrade seeing a lot of these errors when trying to deploy through the console

Question
-
Did the SP1 install a week ago, and now I can't seem to push the client out through the console. I keep getting this:======>Begin Processing request: "2097152047", machine name: "COR-1D5N3M1" SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
Execute query exec [sp_IsMPAvailable] N'FR1' SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
---> Attempting to connect to administrative share '\\COR-1D5N3M1\admin$' using account 'FRIVER\SCCM_CIA' SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
---> The 'best-shot' account has now succeeded 318 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
---> Connected to administrative share on machine COR-1D5N3M1 using account 'FRIVER\SCCM_CIA' SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
---> Attempting to make IPC connection to share <\\COR-1D5N3M1\IPC$> SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
---> Searching for SMSClientInstall.* under '\\COR-1D5N3M1\admin$\' SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
---> Unable to connect to WMI on remote machine "COR-1D5N3M1", error = 0x8007007e. SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
---> Deleting SMS Client Install Lock File '\\COR-1D5N3M1\admin$\SMSClientInstall.FR1' SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
Execute query exec [sp_CP_SetLastErrorCode] 2097152047, -2147024770 SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
Stored request "2097152047", machine name "COR-1D5N3M1", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152047, 2 SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
Execute query exec [sp_CP_SetLatest] 2097152047, N'01/31/2013 14:12:24', 52 SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
<======End request: "2097152047", machine name: "COR-1D5N3M1". SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
I go to the client machine to look at the CCMSetup.log only to find out there isn't one.
- Moved by Alexey Zhuravlev - G14 Thursday, January 31, 2013 2:49 PM
Thursday, January 31, 2013 2:41 PM
All replies
-
---> Unable to connect to WMI on remote machine "COR-1D5N3M1", error = 0x8007007e. SMS_CLIENT_CONFIG_MANAGER 1/31/2013 9:12:24 AM 3100 (0x0C1C)
Torsten Meringer | http://www.mssccmfaq.de
Thursday, January 31, 2013 3:05 PM -
*** Check this Post in the forum ***
http://social.technet.microsoft.com/Forums/is/configmanagerdeployment/thread/0e4b7fd1-9fd4-4d06-8eb9-27f0c44c9a64Seems like a similar problem...
- Edited by Miguel FS Oliveira Thursday, January 31, 2013 3:10 PM
Thursday, January 31, 2013 3:07 PM -
They are a mix of both. But seem to be mostly XP machines from what I am noticing. I'll be doing the WBemtest tonight after the users leave for the day.Thursday, January 31, 2013 3:18 PM
-
Why do you have to wait to the users leave? You can try to connect using wbemtest remotely as a start.
Jason | http://blog.configmgrftw.com
Thursday, January 31, 2013 3:35 PM