Remote Execution of a script with Get-Child Item cannot find path

Question

Hello!
I have been tackling this problem for a few days now and I just can't find the answer.
I want to execute scripts remotely in parallel so that each of remote machine will run the script with their own resources.
Below is just the simple script in the local machine server1
$Folder = \\server1\folder\subfolder
GCI $folder
It works fine it I call that through my client with this I am using in my client
invoke-command -computername server -scriptblock {powershell.exe C:\filepath\script.ps1}
But if I change the script inside to look at another machine server 2 and do
$folder = \\server2\folder\subfolder
It generates an error that it cannot find that path when trying to call GCI remotely. Note that it still works if the script is run locally.
I did some research and I see about the double-hop using credssp but I just can't get it to work.
Any help would be appreciated.

Answer 1

Each system that you're remoting into (or calling Invoke-Command against) will need to have the WSManCredSSP server role enabled. You can do this through group policy, or you can do it on a per-machine basis. Here's what you would run on a computer if you
want to only enable it on certain computers (you should be able to run this remotely):
Enable-WSManCredSSP -Role Server
The system that you're running everything from will be the CredSSP client. You'll need to run this from it:
Enable-WSManCredSSP -Role Client -DelegateComputer *.yourdomain.com
You'll need to change the 'yourdomain.com' to your domain name (or, you could simply put a * for the delegate computer, just be aware that this will allow your computer to pass credentials along to any computer when you tell a cmdlet to use CredSSP authentication).
Now, to use Invoke-Command, do this:
$cred = Get-Credential
Invoke-Command -computername server.yourdomain.com -scriptblock {"Commands go here"} -Authentication CredSSP -Credential $cred
Notice that the -ComputerName parameter is using a fully qualified domain name. If your -DelegateComputer parameter above used a domain name, you'll have to have the FQDN here.
Let me know if that works for you. If you want more information, you can check out the Enable-WSManCredSSP and Disable-WSManCredSSP help topics.
Hi Rohn,
I tried doing your instruction but it gives me this error
Connecting to remote server failed with the following error message : The WinRM client cannot process the request because the server name cannot be resolved. For more information, see the about_Remote_Troubleshooting Help topic.
After enabling the client and server with the wsmancredssp
Here is the command I executed that produced the error
invoke-command -computername server01.domain01 -scriptblock {get-process} -authentication credssp -credential $cred.
Thank you very much for all the help.