I am trying to push client from SCCM on of my lab machine (Win7) but Getting error in CCM.log that not able to connect to remote WMI.
m trying to push client from SCCM on of my lab machine (Win7) but Getting error in CCM.log that not able to connect to remote WMI.
I am able to connect to admin share of client from Server and also able to ping machine but not able to install Client from Server.Below is CCM log error.
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 5/26/2020 11:56:32 AM 3768 (0x0EB8)
Getting a new request from queue “Incoming” after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 5/26/2020 11:56:32 AM 3768 (0x0EB8)
Waiting for change in directory “C:Program FilesMicrosoft Configuration Managerinboxesccr.box” for queue “Incoming”, (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 5/26/2020 11:56:32 AM 3768 (0x0EB8)
—> Unable to connect to WMI on remote machine “WIN7”, error = 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 5/26/2020 11:57:14 AM 3368 (0x0D28)
—> Deleting SMS Client Install Lock File ‘\WIN7admin$SMSClientInstall.IND’ SMS_CLIENT_CONFIG_MANAGER 5/26/2020 11:57:14 AM 3368 (0x0D28)
Execute query exec [sp_CP_SetLastErrorCode] 2097152003, -2147023174 SMS_CLIENT_CONFIG_MANAGER 5/26/2020 11:57:14 AM 3368 (0x0D28)
Stored request “2097152003”, machine name “WIN7”, in queue “Retry”. SMS_CLIENT_CONFIG_MANAGER 5/26/2020 11:57:14 AM 3368 (0x0D28)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152003, 2 SMS_CLIENT_CONFIG_MANAGER 5/26/2020 11:57:14 AM 3368 (0x0D28)
Execute query exec [sp_CP_SetLatest] 2097152003, N’05/26/2020 06:27:14′, 9 SMS_CLIENT_CONFIG_MANAGER 5/26/2020 11:57:14 AM 3368 (0x0D28)
Answers ( 17 )
Thanks for all the help i was able to push the Client on machine successfully.
The problem was with the Networking of VM machine which i configured as i configured two
Adapter to access the Physical internet as a result the IP was not coming properly now i have changed the setting and able to install. So this can mrked as solved
Hello Mayank, Validate whether you had allowed the listed firewall port for communication, added inbound firewall rules for both “File and Printer Sharing” & “Windows Management Instrumentation (WMI)”
Hello JItesh as this is my lab so i have disabled firewall on both server and test client and also i have created inbound firewall rules for both “File and printer sharing and Windows management instrumentation” .I am able to ping and able to access the admin share of client from Server but only WMI is not accessible
Not able to connect means you need Admin$ access
Have you already checked the same from server side to access client\admi$?
hello Anoop i was able to access the Client admin share from Server
Thanks for the update, Are you getting this issue only with Windows 7 Client or tried with other also.
– Is Boundaries configured properly!
If possible Please share the complete log by attaching to https://snipboard.io/ that helps to identify the issue
At the moment i have only one Test machine and that is Win 7 and
I am beginer in SCCM so according to me boundaries are configured correctly..You only want CCM log or any other log which i can attach.
Yes! ccmsetup logs only –
+ You’d already verified all mentioned point, If possible please review settings once.
The wbemtest connect with machine if we are using IP but when i am using machine name is not connecting gives error as RPC server not available ..Any suggestion
Have you tried to connect that machine via wbemtest ? If not try it.
Check for the firewall settings there are specific inbound and outbound rules which needs to be in place if not create them and then try.
Check this below article from Prajwal and Anoop.
tried with Wbemtest it aslo giving me error that RPC is unavailable …
I have created Inbound and outbound rules as per the Anoop blog but still not able to connect to WMI..i am able to ping client from server and server from client also able to access Admin share on client machine from Server as well.
Check if you are able to telnet below ports which are required for RPC from server to client machine.
TCP Ports 135 and 445 Inbound – This is needed for Windows Management Instrumentation (WMI)
Do we need to create inbound and out bound rules only on client machine or on SCCM server as well as i have created on Client only
I tried doing telnet on Server to Client both ports are open
I tired last day wbemtest and i was able to connect to machine using IP but not with name can you suggest something on this why hostname is not working
Mayank if you are setting up your lab then lot of considerations needs to be taken.Which article you have followed to setup the lab.
If you are not able to connect machine with hostname then it could be DNS.
Are you able to ping the machine with hostname?
Ensure that SCCM Client push account should have admin rights on remote computer. then only it will allow to connect the remote machine WMI provide to trigger the client installation remotely.
User is already part of Local Adim group so same id is having admin access on Client machine