Hi we are running 2008 r2 64 bit OS on server A and Windows Server 2003 STD SP2 (I believe this is a 32 bit OS) on server B. I am attempting to run powershell with the following syntax from the command line on A after remoting in to A as domain administrator.. xxx-yyyyyyy is server B.
powershell invoke-command -ComputerName xxx-yyyyyyy -ScriptBlock {'C:\aaaaa\bbbbbbbbbbb\ccccccccccccImport.vbs'}
from a directory on A called c:windows\winsxs\wow64_microsoft-windows-powershell-exe_somethingthatlookslikeaguid_6.1.nnnn.mmmmm._none_somethingelsethatlookslikeaguid.
the n's and m's in the path represent some digits whose meaning I don't know. And I'm not sure what the guids represent.
The reason I'm doing this is to simulate an issue I'm having doing the same thing from an app that runs on server A. That app seems to reach and execute the vb script thru powershell. But running from the command line doesn't even reach or execute the vb script. There are no errors in the dos window. The cmd prompt returns shortly (not immediately) after I hit return . Can someone help me just to get the cmd line to work?
I think what I am going to find once this works from the cmd line is that as in my app, logging in the vbscript works fine but execution of a 3rd party import function after preliminary logging and before final logging returns a return code of 0 but does nothing.