You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Jordan,
I'm wondering if you have considered creating a batch file specific to the service instance that uses PAExec.exe internally? Services would then call their respective service batch file instead. This would require that an instance of PAExec.exe be already on the host; however, the initial connection could check for this and during the service creation, it could be delivered if required ( as is done currently). This reduces considerably the bandwidth and also the size of orphaned instances on the C:\Windows folder. Just a thought for improvement.
The text was updated successfully, but these errors were encountered:
Hi Jordan,
I'm wondering if you have considered creating a batch file specific to the service instance that uses PAExec.exe internally? Services would then call their respective service batch file instead. This would require that an instance of PAExec.exe be already on the host; however, the initial connection could check for this and during the service creation, it could be delivered if required ( as is done currently). This reduces considerably the bandwidth and also the size of orphaned instances on the C:\Windows folder. Just a thought for improvement.
The text was updated successfully, but these errors were encountered: