OVD is not limited to publishing Linux programs to the Virtual Desktop. It also supports
publishing Windows applications. A Windows Application Server simply needs to be installed on the same LAN and registered as an active Application Server in your OVD Farm.
Inuvika OVD Windows Applications Server (OAS) can be run on Windows 2003 SP2/R2 (32 or 64 bit), Windows 2008 R2 SP1 and Windows 2012 R2.
Note: The Windows Application server cannot be a domain controller
Windows 2003 R2 SP1 must be running “Terminal Services” in application server mode
Windows 2008/2012 must have the Remote Desktop Session Host role deployed Note: A grace period runs from the first TS/RDS installation. In some scenarios, the TS/RDS licensing service will have to be installed and properly licensed for OVD to run with Windows OAS.
To avoid any unforeseeable complications, it is recommended that the Windows server be a fresh installation with no other services/roles installed other than those required by OVD.
4.1 DEPLOYING THE RDSH ROLE ON WINDOWS 2012 / 2008R2
Note: In this document, we will document using Windows Server 2008 R2 and 2012 R2 but not Windows 2003 server.
For all Windows operating systems, it is important that the Windows server is a fresh installation with only the default settings.
4.1.1 WINDOWS SERVER 2012
Follow the steps below to install the RDSH role on Windows Server 2012:
Run the “Server Manager” and select “Local Server”
From the “Manage” menu, select “Add Roles and Features”
Select “Role-based or feature-based installation” from the Installation option
Select “Remote Desktop Services” from Server Roles page
click “Next” from features page
Select ONLY “Remote Desktop Session Host” on the Role Services page
From the associated features page, accept all and click “Add Features”
Tick the box for server restart after role deployment and click “Install”
After completing the installation, the system will need rebooting.
After reboot
Run the “Server Manager” and select the “Local Server”
Click the “Windows Firewall”. From the Windows Firewall page:
o Click “Turn Windows Firewall on or off”
o Click “Turn off Windows Firewall” for “Private”, “Public” and “Domain (if apply) network settings
o Close Windows Firewall properties page
Click the “Remote Desktop” link
o Uncheck the box “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)”
o Press OK and close the Window
4.1.2 WINDOWS 2008 R2
Follow the steps below to install the RDSH role on Windows Server 2008:
Run “Server manager” if not already started.
Select “Roles” from the left pane. Then select “Add Roles” from the right pane.
Select only “Remote Desktop Services” then click “Next”
Select only “Remote Desktop Session Host” then click “Next”
Select “Do not require Network Level Authentication” and click “Next” in the Authentication method
Select “Configure later” then click “Next” in Licensing mode
Click “Next” on Users or Groups selection
Click “Next” on the clients experience
Click “Install”
“Restart” when prompted
After completing the installation, the system will need rebooting.
After Reboot
Run “start/control panel/system and security”
Then from the right pane “Windows Firewall” configuration,
“Check Firewall status” then “Turn Windows Firewall on or off” from the left pane”.
Turn off the Windows Firewall for any location then click OK.
4.2 INSTALLING THE OVD APPLICATION SERVER AGENT
To allow a Windows Server to become part of the OVD Evaluation Platform, the OVD Windows Application Server Agent must be installed. The steps below document the procedure to follow:
Download the agent (Inuvika-OVD-1.x.x-ApplicationServer.exe) from http://archive.inuvika.com/ovd/latest to the Windows server.
Run the installer on the Windows server
Accept the license agreement
Accept the default installation path
Enter the OSM IP address (in our scenario this will be “10.1.1.110”)
A security popup will show up regarding the Inuvika printer, click the Install button
Click Finish and allow it to restart the server. The OVD Agent service will automatically start and communicate with your OVD Farm. You can now set the new server as an active application server in your OVD Farm.
For more information, refer to the Installation and Configuration Guide available at http://archive.inuvika.com/ovd/latest/documentation
4.3 REGISTERING THE WINDOWS OAS
Once the Windows OAS has restarted with the Inuvika OVD agent installed, you must register the Windows OAS in the OVD Administration Console.
1. Connect to the OVD Administration Console at http://10.1.1.110/ovd/admin (using your own IP address) and enter admin as the login and password
2. Click the Servers page and then the Unregistered Servers tab
3. Click Register on the Windows server that is displayed. The system will now register the server and the applications available on the server.
4. When the registration is complete, the Servers page will be displayed. Click Switch to production to set the server to production mode
The Windows OAS is now ready for use.
4.4 INSTALLING AN APPLICATION ON THE WINDOWS OAS
Windows applications developed for end users of your system must be installed properly on one or more OAS servers so they can be accessed remotely.
To install an end-user application on a RD Session Host server, the RD Session Host server must first be switched into a special install mode called RD-Install to ensure that the application will
RD Session Host server, you must switch the server back into execution mode (RD-Execute) before users can remotely connect to your server. You can switch between the RD-install and RD-execute modes from the command line using these commands:
change user /install change user /execute
1. Open a cmd.exe window 2. Run the following command:
change user /install
3. Proceed with the application installation
4. When the application installation is finished and before rebooting the server (if required), run the command below:
change user /execute
5. Reboot server (if required)
4.5 PUBLISHING APPLICATIONS
1. Connect to the OVD Administration Console at http://10.1.1.110/ovd/admin (using your own IP address) and enter admin as the login and password
2. Navigate to the Applications page.
Note: If the newly installed application does not show up, press F5 on the keyboard to refresh the list of applications.
3. Click on the application link. The details for the application will be displayed similar to figure 27 below.
Figure 27: Application Details
4. Click the Add to this group button. This will publish the application to the some
applications Applications Group and make it available for users who have access to that Application Group which by default on the demo appliance is all the users.
5. Connect to OVD as a user and run the Windows application