This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 67%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
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!
If the device is reachable from the ConfigMgr server then it could be a case of not having adequate permissions to access the client’s drive remotely. Are you using a client push account? Have you tried installing the client manually on the machine?
@Rahul Jindal [MVP] , yes, we are using client push account, account has full administrator permissions on sccm. When we failed to deploy client from sccm console to target machine, then only we manually installed the client once, but somehow our test lab environment is hosted in Azure and we want to test some configuration that we implemented, it works fine with Azure virtual machines, but for physical laptop, we have observered, waiting for hours client didn't installed on the laptop which domain-joined. Can you please elaborate, it could be a case of not having adequate permissions to access the client’s drive remotely.
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:
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".