With Microsoft Server 2008, it is now possible to run OASIS on a remote server without installing OASIS - AND without seeing a remote desktop background.
The configuration of this solution is best performed by a certified Microsoft technician. The setup of Terminal Services for windows is not supported by Ingen Software.
A similar option is to use products by Citrix.
One nice advantage is that the administrator must only manage the server and not a number of remote installations of OASIS. Upgrades, security, and downtime are better managed through the centralized server.
In low bandwidth scenarios and locations where the Internet is not always stable, Terminal server allows the user's session to be maintained, even if the Internet fails. Granted, Terminal Services does not ensure that the user is connected when the Internet is down; however, Terminal Services will ensure the user's session with OASIS continues while the Internet connection is recovered.
The more users operating from the server may require the server to be expanded.
Printer drivers can be an issue when run from a terminal service session. The best option is to ensure a current copy of all the drivers to be utilized by the users is properly installed on the server.
All programs to be utilized by OASIS attachments must be installed on the server. This normally includes Adobe's PDF reader and any office applications (e.g. Microsoft Office). Please verify licensing with the appropriate company(s).
Drag and drop between other applications and the user's local desktop is not possible.
The user must be running a supported Windows platform which does include Vista and Windows 7 (see Microsoft support for Windows XP and other operating systems).
From the Terminal Server, a website is published, containing an icon for each published application. Often, the user must supply a login to get to this website. The default view with just the OASIS application published is shown here:
Double-clicking on the OASIS icon will present the user with a confirmation window:
Next, the server login is shown. This dialog may be skipped in the future if the "Remember my credentials" is selected.
Next, the OASIS login will show, unless the OASIS auto login feature is properly configured:
From here, OASIS operates on your desktop much like OASIS would if it were installed and run on the local PC:
(Note OASIS is running on the server - the icon in the Windows 7 task bar is the remote desktop icon and not the OASIS icon: )
In OASIS 271, the setup for remote applications is a little different, allowing for different configurations. In OASIS 271, a command file is created to contain the start up information for OASIS (giving the administrator more control over OASIS). The default start up command file is both shown and attached below:
Please note that 512 may be changed to 1024 to allow OASIS to use more memory on the server. The installation path may also be changed to conform to a different installation directory. Please call if you have any questions about altering the command file.
The file must be stored in a location where most users have access. The example here is showing the command file stored on the root C: drive:
Next, open the administrative tools under control panel. Some users may have to search for the administrative tools as shown below:
Click on "Administrative Tools":
Then select "Terminal Services" (please note, if you do not have Windows Server Standard or Enterprise, you may not have access to these features):
Click "Add RemoteApp Program":
Press "Browse ..."
Locate and select the OASIS271.cmd file and press "Open".
At this point, OASIS is ready to use.
An easy way to deploy the file to other computers is to create a .rdp file. To do this, select "OASIS271.cmd" and then select "Create .rdp File":
(You may need to change the server if the server will have a different name from the Internet. This example shows OASIS being used from a VPN connection and the name of the server will remain the same when in the office and when remotely connected using a VPN. Consult a LAN specialist if you need help with this setting.)
Copy the .rdp file to another computer running Windows XP or later. Just double click on the .rdp file to run: