# xWebsite PhysicalPath not accepting network path
**URL:** https://forums.powershell.org/t/xwebsite-physicalpath-not-accepting-network-path/7918
**Category:** DSC
**Created:** [January 25, 2017, 2:03pm UTC](https://forums.powershell.org/t/xwebsite-physicalpath-not-accepting-network-path/7918 "2017-01-25T14:03:25Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@chris-liquori](https://forums.powershell.org/u/chris-liquori)
#### Post date: [January 25, 2017, 2:03pm UTC](https://forums.powershell.org/t/xwebsite-physicalpath-not-accepting-network-path/7918/1 "2017-01-25T14:03:25Z")
Hello,
I am having a hard time pointing the physical path of the website to a network path. Can this be done? Or does the physical path have to point to a local path?
Error:
```
VERBOSE: [ComputerName]: LCM: [End Set] [[xWebsite]WebsiteName] in 0.1090 seconds.
PowerShell DSC resource MSFT_xWebsite failed to execute Set-TargetResource functionality with error message: Failure to successfully create the
website "WebsiteName". Error: "Parameter 'PhysicalPath' should point to existing path.".
+ CategoryInfo : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName : ComputerName
```
The website name and computer name have been changed. The physical path does exist, but pointing to a network location, not a local path.
---
### Author:  [@donj](https://forums.powershell.org/u/donj)
#### Post date: [January 26, 2017, 12:04pm UTC](https://forums.powershell.org/t/xwebsite-physicalpath-not-accepting-network-path/7918/2 "2017-01-26T12:04:13Z")
There’s some validation in the resource that bombs for a UNC. If you get into the gitHub repo for that resource, I’m fairly sure it’s been logged as an issue before.
---
### Author:  [@chris-liquori](https://forums.powershell.org/u/chris-liquori)
#### Post date: [January 26, 2017, 3:09pm UTC](https://forums.powershell.org/t/xwebsite-physicalpath-not-accepting-network-path/7918/3 "2017-01-26T15:09:29Z")
Thanks. It may be something else causing the issue, I was thinking it could be the double hop scenario as I cannot use a unc path using Powershell remoting. But, enabling CredSSP temporarily did not work. I can create the website using a unc path on the local server, but not remotely.
---
### Author:  [@dotnVo](https://forums.powershell.org/u/dotnVo)
#### Post date: [May 16, 2024, 9:16pm UTC](https://forums.powershell.org/t/xwebsite-physicalpath-not-accepting-network-path/7918/4 "2024-05-16T21:16:46Z")