January 12, Prepared by Dina Borisov, Product manager Jetro Platforms. All rights reserved.

Transcription

1 January 12, 2016 Prepared by Dina Borisov, Product manager 2015 Jetro Platforms. All rights reserved.

2 Contents acockpit5 RDP Android Client... 3 Setting Two factor Authentication... 5 Configuring Two Factor Authentication...5 The Login Process...6 Spatial configurations...6 URL Redirection... 8 Session Reconnection... 9 Session Control Log off Mechanism Connections' details Client Log report was upgraded CPU & Memory Control Print Screen redirection

3 acockpit5 RDP Android Client acockpit5 is an RDP Android Client that allows you to connect via RDP to your remote COCKPIT desktop in the cooperate environment. acockpit5 is a part of Jetro COCKPIT5 client-server infrastructure for centralizing application deployment and management using Windows Terminal Services. End users can connect to their COCKPIT farm using their Android device over LAN (Direct) and/or over 3G, 4G, and Wifi, LAN (Direct) - To provide users the ability to connect over organizational network, COCKPIT5i Secure Connector must be configured. For more information, read the Secure Connector user guide. 3G, 4G and Wifi To enable users to connect using any other network then LAN, an organizational Wifi should be configured. For more information, contact our support team JetroSupport@jetroplatforms.com To publish an application to Mobile device, please open the Admin Console and make the following configurations: 1. Choose which existing COCKPIT5 Terminal Server will be also your Mobile server, and simply check the Mobile check box on a Host mode, like in figure 1: Figure 1 2. To enable an application to published also to Mobile, simply check the Mobile check box on the Application 3

4 Figure 2 Note, that In Mobile mode (for Mobile servers only), the Load Balancing will be made based on the Load Balancing policy you defined, and not based the Delivery Configuration. Please read the complete user guide acockpit5 about how to use RDP Android Client. 4

5 Setting Two factor Authentication An additional security layer has been added in order to allow users to add combination of two different components upon login to Cockpit Client. In order to set the two factor authentication, an organizational mail server must be configured and the account should be configured in the Administration Console: the account should be added into the Mail From and the Mail User fields in and Event Log settings Section (Server Settings, Alert Settings) as shown on Fig 2: Figure 3 Configuring Two Factor Authentication This feature is optional and can be defined in Client Login Policy in the Admin Console. To configure Two Factor Authentication, from the Login Provider list choose the User Name, Password option. Then, from the Two Factor Authentication list, select the By option and click the Save button as shown on Fig 4. Figure 4 5

6 The Login Process The following process shows the two factor authentication process when user is logging into COCKPIT5 site: Step 1: The user enters their username, password and domain into the Login screen and clicks OK Figure 5 The COCKPIT5 server sends a numeric code to user s organizational account or to user s mobile phone, based on the configuration in the Active Directory. Step 2: At the same time, the second authentication screen appears, prompting the user to add the code he got in order to complete the authentication process: Figure 6 Spatial configurations User's By default, the code will be sent to user's address in the Active Directory General tab. However, this is possible to send the code to user s mobile device, by using organizational SMS server that allows to send SMS by . To enable this option, in addition to other TFO configurations, an Pattern text filed should be populated: 6

7 . Figure 7 Code validity period - By default, the Code will expire after 2 min, however the validation period can be modified by changing the registry settings on the Controller: HKLM\SOFTWARE\Jetro Platforms\Secure Browsing\SB Server\Client (DWORD) TicketUpdatePeriod = 60 Auto Login functionality - allows users to automatically login. To configure this functionality, in the Admin Console, in Client Login Policy Two Factor Authentication a None option should be chosen and the Auto Logon check box should be checked: Figure 8 7

8 URL Redirection The URL redirection enhances the security by providing system administrators to disable IE access on Terminal Servers with applications published on without actually preventing from users to browse the IE. This is a security layer that enables users to browse the IE despite the URL was accessed from inside the application that were published on Terminal Server without IE access. This happens because any URL is configured to automatically be redirected to a dedicated Terminal Server with Internet access. To configure the new URL Redirection: On all Clients stations create a new Registry entry "TS Redirection" and set it to 1 ("TS Redirection"=dword: ) For 64 bit: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Jetro Platforms\JDsClient] For 32 bit: [HKEY_LOCAL_MACHINE\SOFTWARE\ Jetro Platforms\JDsClient] On a Controller, run the PublishIE.exe utility Open the Admin Console and make the following configurations: a. In the Content Redirection policy, check the URL Redirection check box. Figure 9 b. Publish a new application with the following parameters and add the destination host under the Delivery Configuration tab. 8

9 Figure 10 On the Destination Terminal Server, IE should be enabled and the JDsCockpitBHO.dll in the Bin folder should be renamed. Session Reconnection A new policy has been added allowing to restrict users to one workstation login in order to prevent from more the one session to be running for one user. This can be done by checking the new Restrict users to one workstation login in the General Tab on the Client Policy screen: 9

10 Figure 11 Now, when a user will log into his COCKPIT5 farm from a second work station while an active session is still running on his first work station, the client on a second station will be automatically reconnected to an existing session. At the same time, the client on the first station will be closed. 10

11 Figure 12 Session Control Now, all Cockpit sessions can be controlled from the Sessions screen. Right clicking on the session will display a Session menu with the following options: Disconnect - allows to disconnect the session remotely Send Message - allows to disconnect the session remotely. Session Information displays the Session Information screen Session Printers displays a list of all printers in this session. Session Mirror allows session mirroring. Log off allows to log off a session. Lunch Process allows to lunch processes in the session. Show Screen allows to take a snap shot of user's screen. 11

12 Figure 13 Log off Mechanism The Log Off mechanism has been redesigned to display the list of all modified applications with unsaved data upon attempt to log off: Figure 14 In addition, a new Force log off on Exit Client policy has been added into the Client Policies screen, that forces logging off Client without notification for unsaved changes when the user clicks Exit. 12

13 Figure 15 Connections' details The OS and SP parameters were added to the Controller's Connections screen: Figure 16 This will allow to navigate from the Central Management Screen to the Connections screen by simply double clicking the Connected Users in the Controllers panel: 13

14 Figure 17 Client Log report was upgraded New indicators have been added into the Client Log: MAC indicates the MAC number address of the user's work station. OS indicates the operation system installed on user's work station. SP indicates which the service pack is installed on user's work station. 32/64 bit indicates which the bit version is installed on user's work station. SC will be checked in case when the user client is connected via Secure Connector. 14

15 Figure 18 CPU & Memory Control Processes CPU and Memory can now be controlled per session and per user in the new Limit CPU & Memory screen. To display this screen, first double click the relevant Terminal Server in the Central System Management screen, and then double click the required user to display all process currently running. Right click any process and from the menu displayed, choose the Limit Process or CPU optionl the Limit Processes Memory & CPU screen opens; 15

16 Figure 19 In this screen you can limit the CPU and Memory parameters. Once limited, these parameters will be indicated in the Session Processes screen: Figure 20 16

17 Print Screen redirection An ability to define weather to include the Print Screen function in Jetro Clipboard or not has been added. To configure it, select the include Print screen in the Redirection screen: Figure 21 17