We have an application which runs multiple parallel process tasks on a multi-cpu Windows 2012R2 Server.
We want the executive program which launches these tasks to also startup process tasks on another similar server located in the domain.
What is the best practice for an executive process on Server A to startup process tasks to run on Server B?
We know by experience that running \\ServerB\C:\ProgramName.exe from ServerA will use the resource from ServerB but execute it on ServerA. Which is not what we want.
Glenn Barber