kinook
10-29-2007, 11:37 AM
The VisBuildPro Project (http://www.visualbuild.com/Manual/visbuildprojaction.htm) and Run Program (http://www.visualbuild.com/Manual/runprogramaction.htm) actions support executing Visual Build and other programs on a remote computer via the Remote tab, and these actions use PsExec (https://docs.microsoft.com/en-us/sysinternals/downloads/psexec) for remote execution. This thread explains the minimum requirements for PsExec:
http://forum.sysinternals.com/forum_posts.asp?TID=15919
These pages explain additional requirements to enable remote execution on Windows Vista:
http://forum.sysinternals.com/forum_posts.asp?TID=9139
http://www.howtogeek.com/howto/windows-vista/enable-mapping-to-hostnamec-share-on-windows-vista/
Finally, there is apparently a bug (http://forum.sysinternals.com/forum_posts.asp?TID=12560) on Windows Vista in non-Aero Glass mode (common in virtual machines) which prevents GUI applications from launching properly when started remotely. To work around this problem, either:
1) Run it in the system account (check the 'Run in System account' checkbox on the Remote tab)
2) Use the Console app (VisBuildCmd.exe) instead of the GUI app (VisBuildPro.exe)
http://forum.sysinternals.com/forum_posts.asp?TID=15919
These pages explain additional requirements to enable remote execution on Windows Vista:
http://forum.sysinternals.com/forum_posts.asp?TID=9139
http://www.howtogeek.com/howto/windows-vista/enable-mapping-to-hostnamec-share-on-windows-vista/
Finally, there is apparently a bug (http://forum.sysinternals.com/forum_posts.asp?TID=12560) on Windows Vista in non-Aero Glass mode (common in virtual machines) which prevents GUI applications from launching properly when started remotely. To work around this problem, either:
1) Run it in the system account (check the 'Run in System account' checkbox on the Remote tab)
2) Use the Console app (VisBuildCmd.exe) instead of the GUI app (VisBuildPro.exe)