Strategy supports the use of Windows Terminal Services with Strategy 9.x and newer products. However, Strategy Technical Support does not recommended performing an installation of the Strategy products through Terminal Services.
It is technically "possible," in that users may run the Strategy installer on a remote machine using Terminal Services (Remote Desktop) and the installation could possibly complete without error, and most of the components of the Strategy product suite might function as expected. However, it is likely that some components will exhibit erratic behavior.
It is always safer to install Strategy directly on the server machine's physical interface, or by using a remote connection tool that takes full control of the server machine's interface (such as NetMeeting, VPN or pcAnywhere).
When a user logs into a machine using Windows Terminal Services, a virtual session is created on the host machine. The virtual session runs in the background and is not visible in the user interface on the physical machine.
Because this virtual session does not have primary control over the machine's resources, processes like installation that add or modify system components are at risk of otherwise unexplainable failures. Strategy Technical Support has observed symptoms such as the following in connection with installations performed through Terminal Services:
Symptoms are not limited to this small sampling.
Users should also be aware of the following issues when using Terminal Services with a successful installation:
Third Party Software Installation
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
