>After more research on this, it seems this is possible:
>
>1. Only have one copy of the executable residing in the same location as it is now
>2. Create a many service entries as needed from various servers to point to that share drive executable file
>3. Some services will be on one server, other on another on so on
>4. In order to let the executable know what to do, we will do as we do now by passing a parameter to the executable
>
>So, basically, this would be exactly as it is now except that it would be Windows Service. The Windows Service can point to a share drive executable and can use a domain controller account to execute.
>
>Anyone has done something like this before or can confirm the viability of such infrastructure?

I would look at "launcher" technology. I think there are examples in Downloads here.

I don't like the idea of a Windows Service relying on the availability of an executable on a network share.

What do you perceive as the advantages of a service over the scheduled tasks you have working now?