SCCM Client Push Installation Error: Access Denied or Invalid Network Path

Question

Hi Team,

I hope you are doing well. I am currently facing a scenario where I am unable to proceed with my work, and I need your assistance.

We have a test lab environment that was created a few months ago. We now want to add a physical machine (laptop) to our test environment in Azure. We have done the necessary networking configurations, and the laptop is now domain-joined to abc.com (with the DC in Azure). The networking setup includes two network adapters on the laptop: one for the domain and another for internet access.

We have also configured a Site-to-Site (S2S) connection on one of our physical machines, which has Hyper-V enabled. We created a Hyper-V VM and configured the S2S connection on it. Our SCCM server is also in Azure, domain-joined to abc.com.

The issue arises with SCCM. Although everything appears to be functioning correctly, and the laptop is listed under the Devices tab in the Assets section of the SCCM console, the client installation is failing. We attempted to push the client to the laptop from SCCM by right-clicking on the machine and selecting Install Client, but the client fails to reach the laptop.

All machines, including the Azure-hosted DC and SCCM servers, are able to communicate with the laptop. We have added the necessary IPs in the routing table. Despite this, the client is not being installed on the laptop.

We reviewed the ccm.log in SCCM and found the following error:

"ERROR: Unable to access target machine for request: '2097152133', machine name: 'DESKTOP-xxxxxx', access denied or invalid network path."

This issue is a blocker, preventing me from proceeding with my work. Could you please help troubleshoot this problem?

Thanks!

Answer 1

Hi, @Prabhjot Singh

Thank you for posting in Microsoft Q&A forum.

It seems the client installation is unable to access the target machine due to access denied or invalid network path.

To troubleshoot this issue, you can try the following steps:

1. Verify that the user account used to install the SCCM client has administrative privileges to sign in through the primary domain of the target machine.
2. Ensure that the necessary ports are open on the target machine's firewall.
3. Ensure that the SCCM client push installation account has access to the network share where the SCCM client installation files are located
4. Verify that the SCCM client push installation account has the necessary permissions to access the SCCM server and domain controller.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".