Remoting and UNC paths RRS feed

  • Question

  • This may be by design, so just confirming, and then looking for alternative methods. Thanks in advance

    Have a powershell script "Master" that uses invoke-command to run powershell script "Worker" on a remote server.  (The "Worker" script resides on  a network share and is referenced by a unc path)

    This much works fine as long as the "worker" script is executing commands that reside on the server on which it is running. The problem occurs as soon as the "Worker" script attempts to call another powershell script that is located on the networkshare via a UNC path. The error is "xyz is not a commandlet...etc"

    Outside of only calling local scripts/programs/commands is there any other alternative to this nested type of call. My desire is to have all the called scripts in a central location

    Tuesday, February 14, 2012 11:23 PM


All replies