Does the server you are deploying to have the drive U mapped? Octopus packages and run everything on the target server, using the account that is used to configure the Tentacle. You may need to map U or specify a hostname/IP
If that is not the issue, would you be able to split the script from the package and add it individually to Octopus as a script step, then testing the deployment?
Everything is running on my desktop, the server and the tentacle are both just on my desktop pc. I had first tried to deploy as a script step before trying to package it up, I had the same error both ways though, can't find the file "U:\TFS Local2\....
Thanks for getting back! I'm sorry for the delay here. With the information provided here, I'm still not able to tell what could be going on here. It definitely looks like Powershell is having trouble finding that U:\ drive.
When you run this script locally, assuming the script is exactly the same, are there any error messages or warnings that are displayed in the script?
The next step in troubleshooting this would be to get a copy of this script. However, with the logs provided previously, the script may not give me much more relevant information. I believe it comes down to the Octopus Tentacle not being able to resolve the address: