|Thanks for the help, ijack.|
Is yours a Win7 machine having the file written to it by a DC via a GP startup script? That's the exact problem I'm having. Yes, I too can key in the command line directly and copy the file across the network, but that's not the problem. It seems running the startup script from a command box from the server may be the issue?
Here are more details:
1. The batch file (Copy_File.bat) should run from a startup script in GP, which the target computer is a member of.
2. Because the batch file running from the server didn't do it's job (copy the file over,) I attempt to run the file myself on the target computer by viewing it and executing through Windows Explorer.
3. Upon execution of the file from the local computer I receive the following message:
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
C:\WINDOWS>xcopy "\\server\sharedfolder\file.xxx" "\\localcomputername\folder\folder"
Invalid drive specification
0 File(s) copied
* * *
The batch file contains only 1 command line:
xcopy "\\server\sharedfolder\file.xxx" "\\%computername%\folder\folder"
* * *
I've tried changing the format of the command to see if this would affect anything, but it had the same results:
(xcopy "file.xxx" "\\%computername%\folder\folder") <-- file.xxx is in the same folder as the batch file on the server
(xcopy "c:\folder\folder\file.xxx" "\\%computername%\folder\folder") <-- Using a proper path instead of UNC
Does this help?
If it's worth doing, it's worth doing right.