Accops HyWorks Deployment Options

Accops HyWorks v3.4 can deliver applications, shared hosted desktops, or dedicated desktops in:

1. LAN - Users can directly reach the control layer and data layer

2. WAN - recommended when users have to access resources over the internet

Deployment in LAN Environment

Deployment of HyWorks in LAN, MPLS WAN or P2P WAN requires:

1. HyWorks Controller installed and available in the LAN

2. Firewall or third-party software should not be blocking HyWorks Controller.

3. HyDesk or HyWorks Clients are installed and running in the same network and should be able to:

   1. Detect and connect HyWorks Controller using UDP discovery method

   2. Connect to a HyWorks Controller through configured IP address

4. Dedicated Desktops:

   1. HyWorks Controller and Session Providers like VMware vCenter Server or Microsoft SCVMM Server and authentication servers like Microsoft Active Directory or LDAP must be in the same network and reachable.

   2. DVMs running on Session Providers must be reachable to HyDesk/HyWorks Client devices.

5. Shared Hosted or Desktops:

   1. HyWorks Session Host server must be installed on Microsoft RDS server and is configured in HyWorks.

   2. HyWorks Session Host server must be directly accessible from HyWorks/HyDesk client.

Below given deployment image shows the placement of Accops HyWorks. The device should be able to talk to the Accops HyWorks Controller on port 38866 and to the virtual machine on TCP port 3389.

Deployment in WAN Environment

To access applications, shared hosted desktops or dedicated desktops it is ncessary to connect with Accops HyWorks Controller, Session host and DVMs. This is not possible when users access resources over the internet (WAN) or are not part of your . To provide access in such scenarios HyWorks needs to be integrated with Accops HySecure. You can also use your own VPN but certain security features and single sign-on offered by HySecure will not be available.

Once HyWorks and HySecure are integrated:

1. HySecure acts as an gateway and users can connect to the VM through the HySecure gateway

2. Devices over the internet can directly access HySecure Gateway using Public IP address

3. HySecure Gateway is configured to have applications as

   1. HyWorks Controller (Port:38866). HyWorks Controller has pre-set configuration i.e. Session host Servers, Authentication servers, Session Teams, Applications, Desktop Pools, assignments etc.

   2. HyWorks Application Servers (3389) for applications and shared desktop access

Below given deployment diagram showing how HySecure and HyWorks can be integrated.