Extending FactoryTalk View Site Edition with

ACP ThinManager and Relevance

For Classroom Use Only!

 Important User Information
This documentation, whether, illustrative, printed, “online” or electronic (hereinafter “Documentation”) is
intended for use only as a learning aid when using Rockwell Automation approved demonstration
hardware, software and firmware. The Documentation should only be used as a learning tool by qualified
professionals.

The variety of uses for the hardware, software and firmware (hereinafter “Products”) described in this
Documentation, mandates that those responsible for the application and use of those Products must satisfy
themselves that all necessary steps have been taken to ensure that each application and actual use meets
all performance and safety requirements, including any applicable laws, regulations, codes and standards
in addition to any applicable technical documents.

In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter
“Rockwell Automation”) be responsible or liable for any indirect or consequential damages resulting from
the use or application of the Products described in this Documentation. Rockwell Automation does not
assume responsibility or liability for damages of any kind based on the alleged use of, or reliance on, this
Documentation.

No patent liability is assumed by Rockwell Automation with respect to use of information, circuits,
equipment, or software described in the Documentation.

Except as specifically agreed in writing as part of a maintenance or support contract, equipment users are
responsible for:
• properly using, calibrating, operating, monitoring and maintaining all Products consistent with all
Rockwell Automation or third-party provided instructions, warnings, recommendations and
documentation;
• ensuring that only properly trained personnel use, operate and maintain the Products at all times;
• staying informed of all Product updates and alerts and implementing all updates and fixes; and
• all other factors affecting the Products that are outside of the direct control of Rockwell Automation.

Reproduction of the contents of the Documentation, in whole or in part, without written permission of
Rockwell Automation is prohibited.

Throughout this manual we use the following notes to make you aware of safety considerations:

Identifies information about practices or circumstances

that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property damage, or economic loss.

Identifies information that is critical for successful application and understanding of the
product.

Identifies information about practices or circumstances that can lead to personal injury or
death, property damage, or economic loss. Attentions help you:
• identify a hazard
• avoid a hazard
• recognize the consequence

Labels may be located on or inside the drive to alert people that dangerous voltage may be
present.

Labels may be located on or inside the drive to alert people that surfaces may be dangerous
temperatures.
Extending FactoryTalk View Site Edition with ACP ThinManager

Contents
Before you begin .......................................................................................................................................... 6
About this lab ...................................................................................................................................................7
New to ThinManager 9! ...................................................................................................................................9
Tools & prerequisites .....................................................................................................................................10
Additional References ...................................................................................................................................11
Section 1: Defining ThinManager Display Servers, Display Clients and Terminals .................................. 12
Overview........................................................................................................................................................12
Create Display Servers..................................................................................................................................14
Create a Display Client ..................................................................................................................................18
Create a Terminal ..........................................................................................................................................21
Configure PXE Server ...................................................................................................................................25
Assign the Terminal Configuration to a Thin Client .......................................................................................28
Shadow Thin Client from ThinManager .........................................................................................................30
Section 2: Configuring ThinManager Application Link and Failover for FactoryTalk View SE .................. 31
Overview........................................................................................................................................................31
Add Terminal Names to FactoryTalk Directory..............................................................................................32
Create a New ThinManager Display Client Using Application Link ...............................................................35
Apply New Display Client to Terminal ...........................................................................................................40
Add Automatic Remote Desktop Server Failover ..........................................................................................46
Section 3: Deploying Additional Content Using MultiSession and Tiling ................................................... 52
Overview........................................................................................................................................................52
Create InstantFizz Display Client ..................................................................................................................53
Create FactoryTalk View ME Display Client ..................................................................................................56
Create Studio 5000 Display Client.................................................................................................................60
Apply Display Clients to Terminal and Enable Tiling .....................................................................................62
Section 4: MultiMonitor, Virtual Screens and Session Scaling .................................................................. 71
Overview........................................................................................................................................................71

3 of 207
Split Content across Multiple Monitors ..........................................................................................................72
Create Virtual Screen Display Client .............................................................................................................82
Apply Virtual Screen to Terminal ...................................................................................................................95
Remove Virtual Screen Display Client...........................................................................................................99
Cleanup Disconnected Sessions .................................................................................................................101
Section 5: Terminal Replacement in under 2 Minutes ............................................................................. 103
Overview......................................................................................................................................................103
Power Down ThinXXA .................................................................................................................................104
Replace Thin Client XXA with Thin Client XXB ...........................................................................................105
Section 6: Terminal to Terminal Shadowing ............................................................................................ 110
Overview......................................................................................................................................................110
Create Terminal Shadow Display Client ......................................................................................................111
Create a Second Terminal Configuration ....................................................................................................114
Assign Second Terminal Configuration .......................................................................................................116
Section 7: User Based Content Delivery ................................................................................................. 118
Overview......................................................................................................................................................118
Create a Maintenance User Group..............................................................................................................119
Create a Maintenance User.........................................................................................................................122
Create an Operator Relevance User Group ................................................................................................126
Create an Operator User .............................................................................................................................127
Enable User Services for Terminal ..............................................................................................................128
Login as Maintenance User .........................................................................................................................129
Section 8: Event Notification and Firewall Compatible TFTP .................................................................. 133
Overview......................................................................................................................................................133
Enable E-Mail and SMS Event Notifications................................................................................................134
Modify Configuration to Generate Event Notifications .................................................................................141
Enable Firewall Compatible TFTP ...............................................................................................................147
Section 9: Relevance – Location Based Content Delivery ...................................................................... 149
Overview......................................................................................................................................................149
Create Terminal Configuration for Mobile Device........................................................................................152
Create Resolvers from ThinManager ..........................................................................................................155
Create Access Groups ................................................................................................................................157
Create Locations .........................................................................................................................................161
Assign the Location to a Terminal ...............................................................................................................169

4 of 207
Section 10: (Optional) Relevance with Actual Mobile Device .................................................................. 172
Overview......................................................................................................................................................172
Download and Install iTMC from the App Store ..........................................................................................173
Configure and Connect iTMC ......................................................................................................................175
User Based Content Delivery to iTMC Part 1 ..............................................................................................180
Modify Display Servers for Mobile Content .................................................................................................181
User Based Content Delivery to iTMC Part 2 ..............................................................................................196
Location Based Content Delivery to iTMC...................................................................................................198

5 of 207
Before you begin

At its core, ThinManager is a thin client management platform for the plant floor. Centralizing the
applications required by the plant floor with Remote Desktop Services makes architectural sense, and
offers a tremendous amount of savings over the life span of the system. Instead of maintaining potentially
dozens of plant floor PCs, migrate the plant floor applications to a set of Remote Desktop Servers.
ThinManager enhances Remote Desktop Services deployments by simplifying the configuration and
management of the thin clients and mobile devices requiring plant floor content. If a virtualized desktop
infrastructure (VDI) is preferred, ThinManager supports this architecture as well or even a combination of
both RDS and VDI. As this lab will demonstrate, ThinManager is a solution that IT departments can
embrace but does not require them to deploy or support, allowing Engineering and Maintenance to still own
the critical plant floor content.
This lab is broken up into smaller segments and should be performed sequentially. It is expected that each
section be completed before moving on to the next section or some labs steps may not be doable.
In the event of being prompted for logins, please use the following:
• If the Log On To Windows dialog is active, use the username ‘tmlab\labuser’ and ‘rw’ for the
password.
• Use the same login information if prompted to log on to FactoryTalk Directory.

6 of 207
About this lab
In this lab, you will complete an example deployment utilizing FactoryTalk View Site Edition with Remote
Desktop Services (RDS). The thin client and content delivered to it will be managed using ThinManager.
Along the way, you will have an opportunity to work with some of the unique capabilities of ThinManager.
The basic architecture being utilized is shown in the figure below:
Domain Controller
HMI Server
FactoryTalk View SE Server
RSLinx Enterprise
FactoryTalk Alarms & Events
FactoryTalk Network Directory
FactoryTalk Activation Server
RSLogix Emulate 5000
HMI

HM I

Remote Desktop Server Failover

Remote Desktop Server
ACP ThinManager
Remote Desktop Session Host
Remote Desktop Session Host FactoryTalk Services Platform
Remote Desktop Licensing Server FactoryTalk View SE Client
FactoryTalk Services Platform FactoryTalk Activation Client
FactoryTalk View SE Client
FactoryTalk Activation Client
RDP

RDP

Virtual Thin Client Virtual Thin Client

This lab utilizes 7 different VMWare images running in the Amazon Elastic Cloud (EC2). You will perform
tasks on 3 of them. The five images are:
1. Domain Controller – Windows Server 2012 R2 – hostname DC, domain name TMLAB.LOC
2. HMI Server – Windows Server 2012 R2 - hostname HMI82
3. ME Runtime – Windows Server 2012 R2 – hostname ME82
4. RDS Server – Windows Server 2012 R2 - hostname RDSXX (where XX is your assigned attendee
number)
5. RDS Server Failover – Windows Server 2012 R2 – hostname RDSF
6. Virtual Thin Client A (THINXXA local to your RDS Server – RDSXX)
7. Virtual Thin Client B (THINXXB local to your RDS Server – RDSXX)

7 of 207
The HMI server and an application for this lab are already built for your convenience and should not require
any modifications.
The ME Runtime server exists just to demonstrate VNC Server connectivity. As a sidebar, the ME Runtime
is not supported on a Remote Desktop Server (only one instance of the ME Runtime can be hosted on a
single machine). This server will be shared by all lab attendees for their VNC connections.
RDSXX is a virtual machine with the Microsoft’s Remote Desktop Services role, the FactoryTalk View SE
Client and ThinManager installed.
RDSF is essentially a clone of RDSXX, without ThinManager installed. It will be used to demonstrate the
automatic Remote Desktop Server failover capabilities of ThinManager for high availability environments. It
will be the failover Remote Desktop Server for each person attending.
This lab will be performed by utilizing 2 virtualized thin clients, Thin Client 1 and Thin Client 2. A virtualized
thin client can be generated quite easily with VMWare Player or Workstation by just creating a new virtual
machine without installing an Operating System (OS) on it, which is the essence of a zero client – no OS
stored at the client, and therefore easier to manage. These virtualized thin clients will then receive the
ThinManager firmware and terminal configuration utilizing PXE (Pre-Boot Execution Environment). While a
virtual thin client may not have much practical use in a production environment, it is ideal for demonstration
and training purposes.
All of the work required by this lab will be performed on a single image, RDSXX. Within RDSXX, you will
launch the 2 virtual thin clients.
This lab is broken up into 10 separate sections which must be completed in sequence. In this lab, you will
specifically gain experience with the following topics:
• Section 1: Defining ThinManager Display Servers, Display Clients and Terminals
• Section 2: Configuring ThinManager Application Link and Failover for FactoryTalk View SE
• Section 3: Deploying Additional Content Using MultiSession and Tiling
• Section 4: MultiMonitor, Virtual Screens and Session Scaling
• Section 5: Terminal Replacement in Under 2 Minutes
• Section 6: Terminal to Terminal Shadowing
• Section 7: User Based Content Delivery
• Section 8: Event Notification and Firewall Compatible TFTP
• Section 9: Relevance - Location Based Content Delivery
• Section 10: (Optional) Relevance with Actual Mobile Device

This lab takes approximately 2 hours to complete.

8 of 207
New to ThinManager 9!
Here is a summary of the new features added in ThinManager 9, on which this Hands on Lab is based.
The summary also includes references within the lab manual where the feature is discussed and/or used.
• Virtual Screening -> Section 4
o Create customizable screen layouts that behave like physical screens in ThinManager.
• Session Scaling -> Section 4 and Section 8
o Dynamically scale sessions into different size screens – physical and virtual.
• SMS Messaging -> Section 8
o Notify users of ThinManager events utilizing SMS Messaging.
• Authenticated E-mail -> Section 8
o Notify users of ThinManager events utilizing standard SMTP server sources like Gmail.
• VNC Display Servers -> Section 3
o VNC-enabled devices, like the PanelView Plus, can now be shadowed with ThinManager
and delivered in all of the unique ways ThinManager can deliver and visualize content.
• Firewall Compatible TFTP -> Section 8
o ThinManager uses TFTP to transfer its firmware to thin/zero clients at boot time.
o TFTP generally utilizes a wide, dynamic range of network ports, which can present
challenges with Firewalled environments.
o With this new implementation of TFTP, ThinManager can utilize a single network port to
transfer the firmware greatly simplifying Firewall deployments.
• Expanded Mouse Button Mapping - Section 3 and Section 4
o New actions can be assigned to Left, Middle, Right, Scroll Up and Scroll Down Mouse
events.
o Actions: Calibrate Touchscreen, Tile, Swap, Full Screen, Display Client Switching, Logon,
Main Menu, Virtual Keyboard and Disable Button.
• Remote Desktop Server Groups – Section 10
o Group Remote Desktop Servers together to make it quicker to assign multiple Remote
Desktop Servers to a Display Client
• USB Camera Support -> not utilized in this lab.
o USB Cameras can now be connected to thin/zero clients and that video stream can be
delivered not only to the client to which the camera is connected, but to other terminals as
well.
• Support for 4K Monitors -> not utilized in this lab.
o Included in ThinManager 8.1: 3840x2160 resolution.
o Combined with Virtual Screening can really change the way Control Rooms are
constructed.

9 of 207
Tools & prerequisites
This hands on lab utilizes virtualized thin clients; although, physical thin clients could certainly be used
instead. Similarly, a ControlLogix processor may be used in place of the Logix Emulate 5000, which is
used to drive the FactoryTalk View SE demo applications.

Software
§ FactoryTalk Services Platform v2.80.00 (CPR 9 SR 8)
§ FactoryTalk View Site Edition v8.20 (CPR 9 SR 8)
§ FactoryTalk View ME Runtime v8.20 (CPR 9 SR 8)
§ RSLinx Enterprise v5.80.00 (CPR 9 SR 8)
§ FactoryTalk Alarms and Events v2.80.00 (CPR 9 SR 8)
§ FactoryTalk Diagnostics v2.80.00 (CPR 9 SR 8)
§ FactoryTalk Activation Manager v4.00.00 (CPR 9 SR 8)
§ RSLinx Classic v3.74.00 (CPR 9 SR 7.4)
§ Studio 5000 Logix Designer v24.01 (CPR 9 SR 7.4)
§ RSLogix Emulate 5000 v24.01.00 (CPR 9 SR 7.1)
§ Internet Explorer 11
§ Adobe Reader XI
§ ACP ThinManager v9.00 SP2 (Build 9006)
§ iTMC for ThinManager Platform 8 (8.0.803)
§ TightVNC v2.7.10

Operating Systems
• Windows Server 2012 R2
• iOS 8.0 or Later

10 of 207
Additional References
For additional information on FactoryTalk View Site Edition and Remote Desktop Services, you can review
the following Rockwell Automation Knowledge Base article:
AID 554813 - Using FactoryTalk View SE with Remote Desktop Services - References TOC.
For additional information on Remote Desktop Services and its various components, you can review the
following:
Microsoft TechNet Windows Server site for Remote Desktop Services
Remote Desktop Services Component Architecture Poster
For guidance on how to evaluate and size a Remote Desktop Services solution, you can review the
following Microsoft whitepaper:
Capacity Planning for RD Session Host and Microsoft RemoteFX in Windows Server 2008 R2 with SP1
For ACP’s ThinManager and FactoryTalk View SE Deployment Guide:
http://www.thinmanager.com/rockwell/images/guides/FTViewSE_70_DeploymentGuide.pdf

11 of 207
Section 1: Defining ThinManager Display Servers, Display Clients and Terminals

Overview
In this section, you will create the 3 primary building blocks of ThinManager:
• Display Servers
• Display Clients
• Terminals
In ThinManager, Display Servers are the server sources of content that you want to deliver to your endpoint
devices. A Display Server is typically a Remote Desktop Server, but can also be an IP Camera or a VNC
Server (like a PanelView Plus).
Display Clients, not to be confused with the FactoryTalk View SE executable DisplayClient.exe, represent
the actual content you will be delivering to your endpoint devices, which are referred to as Terminals in
ThinManager. There are 6 types of Display Clients supported in ThinManager: (1) Remote Desktop
Services, (2) Camera, (3) Terminal Shadow, (4) Workstation, (5) VNC and (6) Virtual Screen. Within this
lab, you will have an opportunity to create several of these Display Client types.
Terminals are the thin or zero clients, mobile devices and/or PCs that you will be managing with
ThinManager. You apply the Display Clients created to the terminals to deliver the desired content to your
endpoint device.
A zero client may look very similar to a thin client physically, but it has no operating system. A thin client,
on the other hand, has an operating system - maybe a scaled down version of Linux capable of connecting
to a Remote Desktop Server, or maybe even Windows Embedded. ThinManager treats each of these
devices the same because the same ThinManager firmware is delivered to either device type. The
ThinManager firmware should be viewed as the operating system for ThinManager terminals. So if a
device has no operating system like a zero client or has an operating system like a thin client, it will receive
the ThinManager firmware when it boots up.
In this section, you will register your RDSXX (where XX is your assigned attendee number) virtual machine
as a Display Server within ThinManager. With this Display Server created, you will create a Display Client
to deliver a desktop session from RDSXX. You will then create a Terminal to which you will assign the
newly created Display Client. Lastly, you will start the THINXXA (where XX is your assigned attendee
number) virtual thin client and assign the new terminal configuration to it in order to see the results. To do
this, you will be performing the following tasks:
1. Create a Display Server
2. Create a Display Client
3. Create a Terminal
4. Configure PXE Server
5. Assign the Terminal Configuration to a Virtual Thin Client
6. Shadow Terminal from ThinManager

12 of 207
ThinManager is primarily composed of 2 components – the ThinServer service and the
ThinManager user interface.
The ThinServer service is a Windows based service that is the engine of ThinManager. It
delivers the terminal’s firmware and configuration, and therefore is essential in order for a
terminal to boot. The ThinServer is also the licensed component of ThinManager.
The ThinManager user interface, on the other hand, is not licensed, and is the interface
from which you manage the entire ThinManager environment. It can be installed and run
as many times as needed.
While these 2 components do not have to be co-located or installed on a Remote Desktop
Server, they often are due to the benefits of the Remote Desktop Services architecture.

13 of 207
Create Display Servers
Register both RDSXX (where XX is your assigned attendee number) and RDSF as Display Servers in
ThinManager.
1. Launch the ThinManager user interface from the desktop of RDSXX.

2. Click the Display Servers icon in the ThinManager tree selector.

The tree selector can be expanded or collapsed using the bar above directly above it.

3. From the Display Servers tree, right click the RDS Servers branch and select Add Remote
Desktop Server. This will launch the Remote Desktop Server Wizard.

14 of 207
4. From the Introduction page of the Remote Desktop Server Wizard, click the Next button.
5. From the Remote Desktop Server Name page of the wizard, type RDSXX (where XX is your
assigned attendee number) in the Name field, and 192.168.XX.20 in the IP Address field (where
XX is your assigned attendee number). NOTE: Do not use the Discover button, as it may return
one of the IP addresses from the several virtual network adapters utilized by the cloud image.
6. Type [email protected] in the User Name field.
7. Type thin in the Password field.
8. Click the Finish button.

The Remote Desktop Server name and the IP address field will most likely not match your
image. As previously noted, please substitute your attendee number for the XX in RDSXX.
Similarly, the third octet of the Remote Desktop Server IP address you will use will match
your attendee number. For example, attendee number 07 would see RDS07 with a
Remote Desktop Server IP address of 192.168.7.20.

15 of 207
9. RDSXX should now be added to the Remote Desktop Servers group. You may have to click the
Display Servers branch to refresh the Remote Desktop Servers group.
10. Repeat steps 3 through 8, but this time register RDSF. Enter 192.168.101.20 as the IP Address,
[email protected] as the User Name and thin as the Password. Click the Finish button.

11. Click the Remote Desktop Servers branch and note the status of RDSXX and RDSF on the right
hand side. It should indicate a Value of OK for each. This indicates that the IP address and
credentials provided for the Remote Desktop Servers are in fact valid.

16 of 207
The credentials entered when configuring a Remote Desktop Server must have
Administrative rights on the Remote Desktop Server. This is required for SmartSession
and to populate the User, Sessions and Process tabs of the details pane, which are
available when you click on the Remote Desktop Server of interest. SmartSession is
ThinManager’s load balancing solution. With SmartSession, Remote Desktop Server
sessions will be started on the least loaded Remote Desktop Server based on CPU
Utilization, RAM Utilization and Number of Sessions. Once a session is started on a
Remote Desktop Server, the session will not be moved dynamically.

In order for ThinManager to connect to a Remote Desktop Server (like RDSXX in the
example above), the provided Administrative credentials for that Remote Desktop Server
in ThinManager should also be used as the ThinServer service credentials. The
ThinServer service credentials on RDSXX are in fact configured as thinman with password
of thin, which are the same credentials entered for the RDSXX Remote Desktop Server.

In addition to Remote Desktop Servers and Cameras, the version 9 release of

ThinManager introduces support for VNC Servers as Display Servers. This will enable a
remote connection to be established with PanelView Plus terminals that support VNC (or
any other device offering a VNC connection). The VNC session could then be delivered to
a thin client or a mobile device, or even based on user login using TermSecure or location
using Relevance. TermSecure and Relevance will be introduced in subsequent sections
of this lab.

17 of 207
Create a Display Client

1. Click the Display Clients icon from the ThinManager tree selector.

2. From the Display Clients tree, right click the Remote Desktop Services branch and select Add
Display Client. This will launch the Display Client Wizard.

18 of 207
3. Type Desktop as the Client Name on the Client Name page of the wizard. Click the Next button.

4. Click the Next button on the Display Client Options page of the wizard.
5. Click the Next button on the Remote Desktop Services and Workstation Options page of the
wizard.
6. Click the Next button on the Screen Resolution / Scaling Options page of the wizard.

19 of 207
7. Select RDSXX (where XX is your assigned attendee number) from the Available Remote
Desktop Servers list and click the Right Arrow button to move it to the Selected Remote
Desktop Servers list. This is the Remote Desktop Server on which this Display Client will run.
Click the Finish button.

8. You should see the Desktop Display Client under the Remote Desktop Services branch. You
may have to click the Display Clients node for the branch to refresh.

20 of 207
Create a Terminal

1. Click the Terminals icon from the ThinManager tree selector.

2. From the Terminals tree, right click the Terminals node and select Add Terminal. This will
launch the Terminal Configuration Wizard.

21 of 207
3. Type ThinXXA (where XX is your assigned attendee number) as the Terminal Name on the
Terminal Name page of the wizard. Click the Next button.

Clicking the Description button on the Terminal Name page of the wizard will not only
allow you to enter a Description for the terminal, but also allow you to create Custom
Variables for the terminal. Custom Variables were added in ThinManager 8.1. The
Custom Variable can be used in the Display Client command line or by the TermMon
ActiveX. This would allow you to create a single Display Client in ThinManager that
utilizes a Custom Variable and it would receive direct that Display Client to different
content based on the terminal to which it was assigned. For instance, if you have several
FactoryTalk View SE Client configuration files (CLIs) that you need to deploy, you could
create a Custom Variable on each terminal that would include the name of the CLI file to
deliver to it. You would then create a single Display Client that references the path to the
CLI files and appends the Custom Variable to it in the command line. In addition to
Terminals, Custom Variables can also be created and assigned to Relevance Users
and Locations.

22 of 207
4. Select Generic from the Make/OEM drop down list and PXE from the Model drop down list. Click
the Next button.

5. Click the Next button on the Terminal Options page of the wizard.
6. Click the Next button on the Terminal Mode Selection page of the wizard.
7. Select Desktop from the Available Display Clients list and click the Right Arrow button to move
it to the Selected Display Clients list. This is the Display Client that will be delivered to this
Terminal.
8. Click the Finish button.

23 of 207
9. You should see the ThinXXA terminal under the Terminals node.

You can also create Terminal Groups in ThinManager. Terminal Groups provide 2 key
capabilities: (1) terminal organization and (2) property inheritance. With terminal
organization, you can create Terminal Groups much like folders in Windows Explorer,
and then add Terminals to the Terminal Group. The other key benefit of Terminal
Groups is that you can assign Terminal properties at the Terminal Group level and
choose to make these settings a Group Setting. By doing so, each Terminal member of
the Terminal Group would receive that setting as defined in the Terminal Group. In both
cases, nested Terminal Groups are support as well.

24 of 207
Configure PXE Server
ThinManager supports 2 types of thin or zero clients:
• ThinManager Ready
• ThinManager Compatible
ThinManager Ready terminals have ACP’s BIOS extension image embedded in them by the manufacturer.
When these terminals are powered on, they know how to find a ThinManager Server right out of the box.
Once found, the ThinServer service delivers the terminal’s firmware and configuration.
ThinManager Compatible terminals do not have ACP’s BIOS extension image. However, the ThinManager
firmware is hardware compatible with the majority of thin clients on the market. This is because the
ThinManager firmware is compiled for the x86 platform, and the majority of thin clients are x86-based. In
order to deliver the ThinManager firmware to these devices, PXE is utilized. Preboot eXecution
Environment (PXE) is an Intel standard whereby an operating system can be delivered over the network.
Functionally, there is no difference between a ThinManager Ready terminal and a ThinManager compatible
terminal.
Since this lab is utilizing Virtual Thin Clients, we will need to boot them via PXE. Therefore, the
ThinManager PXE Server must be configured.
1. Select the Manage ribbon and click the PXE Server icon. This will launch the PXE Server
Wizard.

25 of 207
2. Click the Enable PXE Server checkbox. Click the Next button.

26 of 207
3. Ensure the AWS PV Network Device #0 is selected and select the Using standard DHCP server
radio button selection in the PXE Server Mode frame. Click the Finish button.

PXE requires a DHCP server. The Using standard DHCP server option will result in
utilizing the built-in DHCP server of the Amazon Elastic Cloud and ThinManager providing
the additional boot related items (like boot filename).

27 of 207
Assign the Terminal Configuration to a Thin Client
1. Minimize ThinManager, and double click the ThinXXA (where XX is your assigned attendee
number) shortcut on the desktop of RDSXX.
NOTE: Do not use the VMWare Full Screen option, as it has proven to be somewhat unstable in
the cloud. It is ok to maximize the window.
Upon starting, the Virtual Thin Client will recognize that it has no operating system installed and will
therefore attempt to contact a PXE Server. The ThinManager PXE Server will respond to the PXE
request and deliver the ThinManager firmware via TFTP.
Since VMWare Tools cannot be installed within the virtual thin clients, the mouse pointer
will get locked within each virtual machine when one of the virtual thin clients is active. To
return the mouse pointer to the host, hit the CTRL+ALT key sequence.
2. Once the firmware has been delivered and since this is the first time the thin client has been
booted, the Choose the Terminal to Replace window will appear. Hit the Down arrow on the
keyboard to highlight the ThinXXA (where XX is your assigned terminal number) terminal
configuration that we created in the earlier lab section, followed by the Enter key.

28 of 207
3. Once the thin client receives the ThinXXA terminal configuration, you should be presented with a
Windows login screen for the new session running on RDSXX. Enter tmlab\userXX (where XX is
your assigned attendee number) as the username, and z as the password. You should now be
presented with a Windows desktop on RDSXX.

29 of 207
Shadow Thin Client from ThinManager
1. Return to the desktop of RDSXX, by minimizing VMWare Player.

2. Click the Terminals icon from the ThinManager tree selector.

3. Expand the Terminals node in the Terminals tree and select the ThinXXA (where XX is your
assigned terminal number) terminal.
4. Select the Shadow tab from the Details Pane. You should see a shadow of the terminal from
within ThinManager. Notice that the shadow is fully interactive. Also notice that the ThinXXA
terminal icon is green indicating that it is powered up and ThinManager has connectivity to it.

Each ThinManager terminal has a shadowing setting that determines if the terminal can be
shadowed or not. This setting is available by double clicking the terminal to open the
Terminal Configuration Wizard and navigating to the Terminal Options page of the
wizard. The available shadowing options are Yes, No, Ask, Warn, and a checkbox for
enabling Interactive Shadow or not. If you choose to experiment with these settings,
remember that a terminal must be restarted for configuration changes to be applied to it.
To perform a terminal restart, right click the terminal and select Restart Terminal.

30 of 207
Section 2: Configuring ThinManager Application Link and Failover for FactoryTalk View SE

Overview
In the last lab section, you successfully delivered a Windows Desktop to ThinXXA (where XX is your
assigned attendee number) using ThinManager. Typically, we go through great lengths to actually prevent
access to the Windows Desktop from the plant floor, which is another reason why VDI is not always the
best option for plant floor deployments – since delivering desktops is one of the strengths of VDI. This
section will use ThinManager Application Link to deliver the FactoryTalk View SE Cookie Factory demo to
the virtual thin client without a desktop. In addition, this lab will demonstrate how easy it is to configure
automatic Remote Desktop Server failover for your ThinManager terminals. To do this, you will be
performing the following tasks:
1. Add Terminal Names to FactoryTalk Directory
2. Create a New ThinManager Display Client with Application Link
3. Apply New Display Client to Terminal
4. Add Automatic Remote Desktop Server Failover

31 of 207
Add Terminal Names to FactoryTalk Directory
By default, every Computer connecting to the FactoryTalk Directory must be added as a Computer Account
– ThinManager terminals are no different. This section will add the ThinManager terminal names to the
FactoryTalk Directory as Computer Accounts.
1. Click the Windows Start button.

2. Click the search button ( ) in the upper right.

3. Type in admin
4. Click on the shortcut for the FactoryTalk Administration Console.

5. On the Select FactoryTalk Directory dialog, make sure Network is selected and click the OK
button.

32 of 207
6. In the Explorer view, browse to Network (HMI82) àSystemàComputers and
GroupsàComputers, right click Computers and select New Computer… from the menu.

7. In the Computer textbox, enter THINXXA (where XX is your assigned attendee number) and click
the OK button.

33 of 207
8. Repeat the previous 2 steps but this time add THINXXB. When finished, you should have
THINXXA and THINXXB (where XX is your assigned attendee number) added to the Computers
folder.

9. Close the FactoryTalk Administration Console and return to ThinManager.

In addition to adding the terminal name as a Computer Account to the FactoryTalk

Directory, you will typically have to add the Windows user account that is assigned to the
terminal, and therefore launching the session, to the FactoryTalk Directory as well. This
step was handled for you by adding a Windows linked group to the LAB\Domain Users
group, of which the userXX users are members.

34 of 207
Create a New ThinManager Display Client Using Application Link

1. Click the Display Clients icon from the ThinManager tree selector.
2. From the Display Clients tree, right click the Remote Desktop Services branch and select Add
Display Client. This will launch the Display Client Wizard.

3. Type CookieDemo as the Client Name on the Client Name page of the wizard. Click the Next
button.

35 of 207
4. Click the Next button on the Display Client Options page of the wizard.
5. Check the Application Link checkbox on the Remote Desktop Services and Workstation
Options page of the wizard. Click the Next button.

36 of 207
6. From the Screen Resolution / Scaling Options page of the wizard, check the box for Don’t Use
Screen Resolution, and select 1280x1024 from the Resolution drop down list. This is a setting
that will come into play during the Virtual Screen section of the lab. Click the Next button.

If a Session Resolution is NOT specified at the Display Client level like above, then the
session will be launched at the Screen Resolution set for the terminal on which it is being
delivered. By setting the Session Resolution here at the Display Client level, we are
relying on ThinManager to dynamically scale the Display Client to whatever Screen
Resolution to which its is assigned.

37 of 207
7. Select RDSXX (where XX is your assigned attendee number) from the Available Remote
Desktop Servers list and click the Right Arrow button to move it to the Selected Remote
Desktop Servers list. This is the Remote Desktop Server on which this Display Client will run.
Click the Next button.

38 of 207
8. From the AppLink page of the wizard, enter the following path for the Program Path and
Filename text box, noting the double quotes and the space between the paths (you can also copy
and paste this path from the LabPaths.txt file by right clicking the Notepad icon pinned to the start
bar and selecting LabPaths.txt):
"C:\Program Files (x86)\Rockwell Software\RSView
Enterprise\DisplayClient.exe" "C:\Lab Files\CookieDemo.cli"
9. Click the Finish button.

Remote Desktop Services considers any program configured to run initially - like the ones
configured with AppLink in this section - an “Initial Program.” By default, Windows Server
2012 Remote Desktop Services requires that each Initial Program be added to the
published RemoteApp list, or you will receive an Access Denied message when the
Display Client attempts to launch. While it is recommended that this default security
measure be maintained, it has been disabled through Group Policy of this lab (from the
Group Policy Editor: Default Domain Policy | Computer Configuration | Policies |
Administrative Templates | Windows Components | Remote Desktop Services | Remote
Desktop Session Host | Connections | Allow remote start of unlisted programs). With
Server 2012, the RemoteApp list is managed through Session Collections.

39 of 207
Apply New Display Client to Terminal

1. Click the Terminals icon from the ThinManager tree selector.

2. From the Terminals tree, double click the ThinXXA (where XX is your assigned attendee number)
terminal to launch the Terminal Configuration Wizard.
3. Click the Next button on the Terminal Name page of the wizard.
4. Click the Next button on the Terminal Hardware page of the wizard.
5. Click the Next button on the Terminal Options page of the wizard.
6. Click the Next button on the Terminal Mode Selection page of the wizard.
7. Select CookieDemo from the Available Display Clients list and click the Right Arrow button to
move it to the Selected Display Clients list.
8. Select Desktop from the Selected Display Clients list and click the Left Arrow button to move it
to the Available Display Clients list. Click the Next button.

9. Click the Next button on the Terminal Interface Options page of the wizard.
10. Click the Next button on the Hotkey Configuration page of the wizard.

40 of 207
11. On the Log In Information page of the wizard, enter [email protected] (where XX is your
assigned attendee number) as the Username and z as the Password. The terminal will use these
credentials to login to the Remote Desktop Server for those Display Clients applied to it that have
the Allow Auto Login property enabled. Click the Next button.

12. From the Video Resolution screen of the wizard, select 1280x1024 as the Screen Resolution,
64K Colors as the Color Depth and 60Hz as the Refresh Rate. Click the Next button.

41 of 207
13. Click the Next button on the Module Selection page of the Terminal Configuration Wizard.
14. Click the Next button on the ThinManager Server Monitor List page of the Terminal
Configuration Wizard.
15. From the Monitoring Configuration page of the wizard, select the Custom radio button within the
Monitor Interval. Keep the defaults for Monitor Interval, Monitor Timeout and Monitor Retry.
Enter a value of 1 for the Primary Up Delay Multiplier. This will speed up the Remote Desktop
Server fail back time in a later section. Click the Finish button.

42 of 207
16. Right click the ThinXXA (where XX is your assigned attendee number) terminal from the
Terminals tree and select Restart Terminal to apply the changes. Click Yes to restart the
terminal.

You may notice a small red exclamation icon appear in the bottom of the terminal icon.
This indicates that a change has been made to the terminal’s configuration that has not
been published to the terminal yet. Restarting the terminal will republish the terminal’s
configuration, including any recent changes.

If you need to apply a change to a terminal’s configuration, simply right click the terminal of
interest from the Terminals tree and select Restart Terminal. Restarting a terminal simply
reapplies the terminal’s configuration – unless ThinManager automatically detects a
configuration change that requires a terminal reboot, in which case a reboot is performed.
Reboot Terminal, available from the Tools ribbon bar, is equivalent to cycling power to
the terminal, and therefore resends the firmware as well as the configuration. It is
important to note that in both of these cases the sessions running on the Remote Desktop
Servers are not restarted by default. You need to perform a Reset Session in this case.
To reset a session, return to the Display Servers tree segment, and select the Remote
Desktop Server on which the session of interest is running. Select the Sessions tab from
the Details Pane. A list of all of the sessions running on the selected Remote Desktop
Server will be displayed. Right click the session desired and select Reset Session.

43 of 207
17. With the ThinXXA (where XX is your assigned attendee number) terminal still selected, click on the
Shadow tab in the Details Pane of ThinManager. If the Shadow does not start, click the
Configuration tab, then the Shadow tab to reactive the shadow.

18. This can also be confirmed by selecting the ThinXXA (where XX is your assigned attendee
number) virtual machine from the Windows task bar.

44 of 207
19. If you click the red “X” in the top right corner of FactoryTalk View SE application, it will close,
leaving an empty black screen without a desktop.

Once the application closes, you will see the desktop background with no Start menu bar
for about 45 seconds before you are automatically logged out. When using AppLink, the
user does not have access to any other programs or the desktop when connecting and
once that application terminates, the user is automatically logged off. The logoff delay is
due to the FactoryTalk View Site Edition client continuing to shut down in the background
after the display is closed.

If you hit the CTRL+ALT+DEL keyboard sequence while the empty black screen is active,
you will be presented with the Task Manager, from which Windows File Explorer could
certainly be launched. With ThinManager, this is easily rectified by adding the Key Block
Module to your terminal(s), which is a simple way to block common keyboard sequences
like CTRL+ALT+DEL, CTRL+ESC, etc.

A module is a small driver that can be applied to a terminal to provide additional

capabilities. For example, ThinManager includes 15 unique Touch Screen Modules, a
Redundant Ethernet Module for thin clients with dual Ethernet ports (provides automatic
failover of network interfaces connected to the thin client) as well as a MultiSession Screen
Saver Module (each Display Client applied to a thin client is automatically cycled on a
configurable time basis as a screen saver) – just to name a few. Modules are added to a
terminal using the Terminal Configuration Wizard.

45 of 207
Add Automatic Remote Desktop Server Failover
1. Return to ThinManager.
2. From the Terminals tree, expand the ThinXXA (where XX is your assigned attendee number)
terminal. Double click the CookieDemo Display Client under the ThinXXA terminal to launch the
Display Client Wizard.

3. Click the Next button on the Client Name page of the wizard.
4. Click the Next button on the Display Client Options page of the wizard.
5. Check the Enforce Primary checkbox on the Remote Desktop Services and Workstation
Options page of the wizard. Click the Next button.

46 of 207
6. Click the Next button on the Screen Resolution / Scaling Options page of the wizard.
7. Select RDSF from the Available Remote Desktop Servers list and click the Right Arrow button
to move it to the Selected Remote Desktop Servers list. Click the Finish button.

By adding more than 1 Remote Desktop Server to the Selected Remote Desktop
Servers list, you have added automatic Remote Desktop Server failover for this Display
Client. The order of the servers listed determines the order of failover. In this case,
RDSXX would be the primary and RDSF would be the secondary. There is no limit to how
many Remote Desktop Servers you can add, the terminal will just keep failing to the next
available server in the list.

47 of 207
8. Right click the ThinXXA terminal and select Restart Terminal to apply the changes. Click Yes on
the confirmation dialog box. If you expand the ThinXXA terminal, and then expand the
CookieDemo Display Client, you will now see both RDSXX and RDSF are listed. The green
lightning bolt next to RDSXX indicates that the session being delivered to the terminal is running on
RDSXX. Notice that RDSF has a red lightning bolt next to it.

48 of 207
9. To force a failover to occur, we can manually disable the RDSXX Remote Desktop Server from
ThinManager. This will disconnect all Remote Desktop Server sessions to RDSXX. From the
Terminals tree, expand the ThinXXA terminal, and then expand the CookieDemo Display Client.
Select the RDSXX Remote Desktop Server under the CookieDemo Display Client. With RDSXX
selected, click the Tools ribbon, followed by the Disable icon.

49 of 207
10. If you quickly shadow ThinXXA you will see the new FactoryTalk View SE session launching on
RDSF. To shadow, simply select ThinXXA from the Terminals tree and then click the Shadow
tab from the Details Pane. With the RDSXX Remote Desktop Server disabled, its icon has
changed from a green lightning bolt to a red lightning bolt with an X, while the RDSF Remote
Desktop Server has changed from a red lightning bolt to green.

50 of 207
11. To re-enable RDSXX, select RDSXX from the Terminals tree and then click the Enable button in
the Tools ribbon. Notice that the green lightning bolt returns to RDSXX, while RDSF returns to
red. The active session on the terminal has returned to the primary, RDSXX. This is because we
checked the Enforce Primary option of the Display Client Wizard in a previous step.

There are actually 2 types of automatic Remote Desktop Server failover supported by
ThinManager. The one demonstrated above is called Standard Failover. With Standard
Failover, the failover session is started on-demand. The other type is called Instant
Failover, which differs by keeping sessions running on each Remote Desktop Server – the
active one, and a hot standby one. Each Instant Failover session running would require a
FactoryTalk View SE Client license. Instant Failover is a great option for deployments
that cannot be without visualization for any length of time. Otherwise, Standard Failover
is perfectly suitable. To enable Instant Failover in our example above, we would have
additionally checked the Instant Failover checkbox in Step 5 above.

51 of 207
Section 3: Deploying Additional Content Using MultiSession and Tiling

Overview
To this point, we have only delivered a single ThinManager Display Client to ThinXXA. First, the Desktop
Display Client, then the CookieDemo Display Client. This lab will focus on applying multiple Display
Clients as well as the options to visualize and switch between them from a terminal. When more than one
Display Client is applied to a terminal, it is referred to as MultiSession. The Display Clients applied to a
terminal can be run from the same Remote Desktop Server, or from multiple Remote Desktop Servers –
even on different networks. In addition to Remote Desktop Services Display Clients, IP Cameras, VNC and
Terminal Shadow Display Clients can be delivered with MultiSession. This makes it possible to deliver a
very diverse set of content to a single terminal. The Display Clients can be visualized as tiles on a display
so that multiple Display Clients can be monitored at the same time and/or spread out across multiple
monitors – or a combination. This lab section is composed of the following tasks:
1. Create InstantFizz Display Client
2. Create FactoryTalk View ME Display Client
3. Create Studio 5000 Display Client
4. Apply Display Clients to Terminal and Enable Tiling

52 of 207
Create InstantFizz Display Client
We are going to copy the CookieDemo Display Client to create another View SE Display Client, but this
time to launch the InstantFizz demo. We won’t need Automatic Remote Desktop Failover, so we will
disable this from the copied terminal profile.

1. From ThinManager, click the Display Clients icon from the ThinManager tree selector.
2. From the Display Clients tree, expand the Remote Desktop Services branch and right click the
CookieDemo item and select Copy.

3. Type InstantFizz in the Enter new Display Client Name text box and click the OK button.

53 of 207
4. Double click the InstantFizz Display Client item.

5. From the Client Name page of the wizard, click the Next button.
6. From the Display Client Options page of the wizard, click the Next button.
7. From the Remote Desktop Services and Workstation Options page of the wizard, uncheck the
Enforce Primary checkbox and click the Next button.

54 of 207
8. From the Screen Resolution / Scaling Options page of the wizard click the Next button.
9. From the Display Client Members page of the wizard, select RDSF from the Selected list and
click the Left arrow button to remove it. Click the Next button.

10. From the AppLink page of the wizard, replace CookieDemo in the path with InstantFizz like below
(you can also copy and paste this path from the LabPaths.txt file by right clicking the Notepad
icon pinned to the start bar and selecting LabPaths.txt):
"C:\Program Files (x86)\Rockwell Software\RSView
Enterprise\DisplayClient.exe" "C:\Lab
Files\InstantFizz.cli"
11. Click the Finish button.

55 of 207
Create FactoryTalk View ME Display Client
For the FactoryTalk View ME Display Client, we will utilize a VNC Display Client.

1. Click the Display Servers icon in the ThinManager tree selector.

The tree selector can be expanded or collapsed using the bar above directly above it.

2. From the Display Servers tree, right click the VNC Servers branch and select Add VNC Server.
This will launch the VNC Server Configuration Wizard.

56 of 207
3. From the VNC Server Name page of the VNC Server Configuration Wizard, enter the following
and click the Finish button:
VNC Server Name = ME82
VNC Server IP Address = 192.168.100.21
Port = 5900
Password = z

4. Click the Display Clients icon from the ThinManager tree selector.
5. From the Display Clients tree, right click the VNC branch and select Add Display Client.

57 of 207
6. From the Client Name page of the Display Client Wizard, enter ME82 in the Client Name field.
Click the Next button.

7. Click the Next button on the Display Client Options page of the wizard.
8. From the VNC Display Client page of the wizard, un-check the All VNC Servers Available
checkbox, and click the Add button.

58 of 207
9. From the Select VNC Server or Group dialog box, select the ME82 terminal and click the OK
button. Click the Finish button.

59 of 207
Create Studio 5000 Display Client
1. From the Display Clients tree, expand the Remote Desktop Services branch and right click the
InstantFizz item and select Copy.

2. Type Studio5000 in the Enter new Display Client Name text box and click the OK button.

60 of 207
3. Double click the Studio5000 Display Client item.

4. From the Client Name page of the wizard, click the Next button.
5. From the Display Client Options page of the wizard, click the Next button.
6. From the Remote Desktop Services and Workstation Options page of the wizard, click the Next
button.
7. From the Screen Resolution / Scaling Options page of the wizard click the Next button.
8. From the Display Client Members page of the wizard, click the Next button.
9. From the AppLink page of the wizard, replace the path with the path below (you can also copy and
paste this path from the LabPaths.txt file by right clicking the Notepad icon pinned to the start bar
and selecting LabPaths.txt):
"C:\Program Files (x86)\Rockwell Software\Studio 5000\Logix
Designer\ENU\v24\Bin\LogixDesigner.Exe"
10. Click the Finish button.

While the above sections utilized Remote Desktop Services and VNC Display Clients,
ThinManager also supports IP and USB Cameras as server sources of content. The
camera’s video stream can be delivered as its own Display Client, or as an overlay to an
existing Display Client. ThinManager supports real time streaming protocols (RTSP) like
H.264. RTSP can be decoded by the terminal’s CPU or for certain Intel graphics chipsets,
by the on-board graphics.

61 of 207
Apply Display Clients to Terminal and Enable Tiling

1. Click the Terminals icon from the ThinManager tree selector.

2. From the Terminals tree, double click the ThinXXA (where XX is your assigned attendee number)
terminal to launch the Terminal Configuration Wizard.
3. Click the Next button on the Terminal Name page of the wizard.
4. Click the Next button on the Terminal Hardware page of the wizard.
5. Click the Next button on the Terminal Options page of the wizard.
6. Click the Next button on the Terminal Mode Selection page of the wizard.
7. Select InstantFizz from the Available Display Clients list and click the Right Arrow button to
move it to the Selected Display Clients list.

62 of 207
8. Repeat the previous step for the ME82 and Studio5000 Display Clients. Click the Next button.

63 of 207
9. On the Terminal Interface Options page of the wizard, make sure Show Selector on Terminal,
Enabled Tiling and Screen Edge Display Client Selection are checked. Click the Selector
Options button.

10. Click on the Selector Options button. Uncheck Auto-hide Selector and click the OK button.

64 of 207
11. Back on the Terminal Interface Options page of the wizard, click the Tiling Options button.

12. Make sure Show Grid is checked, and also check Tile Display Clients at startup. Click the OK
button.

13. Click the Next button when you return to the Terminal Interface Options page of the wizard.

65 of 207
14. From the Hotkey Configuration page of the wizard, make sure Enable Display Client Hotkeys
and Enable Tiling Hotkey are both checked. Click the Mouse Button Mapping button.

15. From the Mouse Button Mapping dialog box, select Tile from the Button 3 (Right Mouse) drop
down list. Click the OK button followed by the Next button.

ThinManager 9 introduced more mouse button mapping options, including all mouse
button types to a number of new mouse button actions like Swap and Full Screen, both of
which are applicable to Virtual Screens.

66 of 207
16. From the Log In Information page of the wizard, click the Next button.
17. From the Video Resolution page of the wizard, click the Next button.
18. From the Module Selection page of the wizard, click the Add… button.

19. From the Attach Module to Terminal dialog box, scroll down and select the RDP Experience
Module and click the OK button.

67 of 207
20. Back on the Module Selection page of the wizard, select the RDP Experience Module and click
the Configure button.

21. From the Module Properties dialog box, select 3 from the Duplicate Server Connect Delay
(seconds). Click the Done button.
22. Back on the Module Selection page of the wizard, click the Finish button.

The RDP Experience Module enables configuration of how the RDP session is rendered at
the terminal, including if the Desktop Background or Themes are delivered, if Network
Level Authentication (NLA) is enabled, etc. It is typically used with MultiSession because it
also staggers the starting of the sessions on the Remote Desktop Server. Without
staggering the starting of the sessions, the Remote Desktop Server can respond with a
warning message that it is busy.

68 of 207
23. Right click the ThinXXA (where XX is your assigned attendee number) terminal from the
Terminals tree and select Restart Terminal to apply the changes. Click Yes to the confirmation
dialog.
24. Select the ThinXXA virtual machine from the Windows taskbar.

25. ThinXXA should show the 4 Display Clients in a 2x2 grid referred to as Tile Mode.

The ME82 VNC Session may take several seconds to connect. You may have to
actually click the ME82 tile to activate it. Keep in mind that all attendees are sharing
this VNC Server connection as well, so you may experience some mouse fighting.

69 of 207
 In addition to using Tile Mode to switch between the Display Clients, the Display Client
Selector at the top of the thin client can be used. To use the Display Client Selector,
click and hold the selector to expand the menu. While still holding the mouse button, point
to the desired Display Client and release the mouse button to select it. You can also
return to Tile Mode from the Display Client Selector.

26. By default, the hotkeys CTRL-PAGE UP and CTRL-PAGE DOWN will also cycle through the
Display Clients. We also enabled the Screen Edge Selector which allows you to move the pointer
to the edge of the screen and shift the next Display Client into view. Experiment with each of
these. Similarly, the hotkey CTRL-t will return to Tile Mode.

You can deploy up to 25 (a 5x5 Grid) Display Clients using Tiling Mode to a single
monitor. If you are not using Tiling Mode, there is no limit to the number of Display
Clients that can be applied to a single monitor. All of the processing required for this
content is not occurring at the terminal, but at the server.

70 of 207
Section 4: MultiMonitor, Virtual Screens and Session Scaling

Overview
To this point, we have delivered content, or Display Clients, to a single display. ThinManager supports
multiple monitors as well – up to 5 on a physical terminal. The release of ThinManager 9 has also
introduced the concept of a Virtual Screen Display Client. The Virtual Screen Display Client will enable you
to carve up a physical display in completely configurable areas, to which you can assign Display Clients.
You can also overlay Virtual Screens to create a picture-in-picture effect with the ability to swap content
in/out. Prior to ThinManager 9, the concept of overlays was supported, but only for IP cameras. Now, any
type of Display Client can be applied to a Virtual Screen, and it can be automatically scaled to the size of
the Virtual Screen. This section will introduce you to MultiMonitor and Virtual Screens and will be
composed of the following tasks:
1. Split Content across Multiple Monitors
2. Disable MultiMonitor
3. Create Virtual Screen Display Client
4. Apply Virtual Screen to Terminal
5. Remove Virtual Screen Display Client
6. Cleanup Disconnected Sessions

71 of 207
Split Content across Multiple Monitors
Instead of applying all 4 Display Clients to a single monitor, let’s split the content across 2 monitors using
ThinManager’s MultiMonitor.

1. Return to ThinManager.

2. Click the Terminals icon from the ThinManager tree selector.

3. From the Terminals tree, double click the ThinXXA (where XX is your assigned attendee number)
terminal to launch the Terminal Configuration Wizard.
4. Click the Next button on the Terminal Name page of the wizard.
5. Click the Next button on the Terminal Hardware page of the wizard.
6. Click the Next button on the Terminal Options page of the wizard.
7. From the Terminal Mode Selection page of the wizard, check Enable MultiMonitor. Click the
Next button.

72 of 207
8. From the MultiMonitor Video Settings page of the wizard, make sure the following is selected: 2
Monitors radio button, 64K Colors Color Depth, 1280x1024 Resolution for each monitor, 60Hz
Refresh Rate for each monitor, Video Port 1 for Monitor 1, and Video Port 2 for Monitor 2. Click
the Next button.

The Use Session Size Limits for drop down list allows you to specify either Server 2012
or Server 2008 R2 session size limits. Prior to Windows Server 2012, the maximum
screen resolution for an RDP session was 4096 x 2048. Windows Server 2012 has
increased this maximum to 8192 x 8192.

9. From the Monitor Layout wizard, accept the defaults. This is where you tell ThinManager how
your monitors are physically oriented via the Monitor Layout section, as well as how to treat each
individual monitor via the Screen Layout section. Click the Next button.
Screens are treated individually by default, which is referred to as Screening. Or the screens can
be combined logically, which is referred to as Spanning.

73 of 207
10. Select CookieDemo from the Available Display Clients list and click the Right Arrow button for
Screen A to move it to the Selected Display Clients list. Repeat this step to move the
InstantFizz Display Client to Screen A as well.
11. Select ME82 from the Available Display Clients list and click the Right Arrow button for Screen
B to move it to the Selected Display Clients list. Repeat this step to move the Studio5000
Display Client to Screen B as well. Click the Next button.

12. On the Screen Options page of the wizard, click the Screen Options button for Screen A.

74 of 207
13. Make sure Show Display Client Selector, Enable Tiling, Allow Display Clients to move
to/from screen and Screen Specific Mouse Button Mapping checkboxes are checked. Click
the Selector Options button.

14. From the Display Client Selector Options popup, uncheck Auto-hide Selector and click the OK
button.

15. Back on the Screen Options popup, now click the Tiling Options button.

75 of 207
16. From the Tile Options popup, check the Tile Display Clients and startup check box. Click the
OK button on the Tile Options popup.

17. Click the Mouse Button Mapping button on the Screen Options popup.

18. From the Mouse Button Mapping dialog box, select Tile from the Button 3 (Right Mouse) drop
down list. Click the OK button.

76 of 207
19. Click the OK button on the Screen Options popup.
20. Back on the Screen Options page of the wizard, click the Screen Options button for Screen B.

21. Make sure Show Display Client Selector, Enable Tiling, Allow Display Clients to move
to/from screen and Screen Specific Mouse Button Mapping checkboxes are checked. Click
the Selector Options button.

22. From the Display Client Selector Options popup, uncheck Auto-hide Selector and click the OK
button.

77 of 207
23. Back on the Screen Options popup, now click the Tiling Options button.

24. From the Tile Options popup, check the Tile Display Clients and startup check box. Click the
OK button on the Tile Options popup.

25. Click the Mouse Button Mapping button on the Screen Options popup.

78 of 207
26. From the Mouse Button Mapping dialog box, select Tile from the Button 3 (Right Mouse) drop
down list. Click the OK button.

27. Click the OK button on the Screen Options popup.

28. Click the Finish button.
29. Right click the ThinXXA (where XX is your assigned attendee number) terminal from the
Terminals tree and select Restart Terminal to apply the changes. Click Yes to the confirmation
dialog.

79 of 207
30. The virtual thin client may only attempt to display Screen A or provide a scroll bar to scroll between
Screens A and B, so it is best to see the result with the setup of this lab by shadowing ThinXXA
from ThinManager. To do so, simply select the ThinXXA terminal and then click the Shadow tab
in the Details Pane.

80 of 207
31. Experiment with the Display Client Selector of each monitor while Shadowing. You can move
Display Clients from one monitor to the other and back again. This behavior is fully configurable.
32. You can also shadow an individual monitor, as opposed to both at the same time. Expand the
ThinXXA terminal and select Screen A. Now click the Shadow tab in the Details Pane to shadow
just Screen A.

MultiMonitor combined with Tiling are extremely powerful tools that really elevate the user
experience at the terminal. They are especially valuable in Control Room settings, or
anywhere centralized monitoring is desired. Some thin clients can support up to 5
monitors. ThinManager also includes a Shared Keyboard and Mouse Module that can be
applied to a group of thin clients. The Shared Keyboard and Mouse Module allows you to
control several thin clients using a single keyboard and mouse. As an example, you could
have three 5 monitor thin clients in your Control Room driving a total of 15 displays all
being controlled by a single keyboard and mouse. The Virtual Screen section will show
you an alternative way to accomplish similar content delivery while using a single physical
screen.

81 of 207
Create Virtual Screen Display Client

1. Click the Display Clients icon from the ThinManager tree selector.

2. Right click the Virtual Screen branch and select the Add Display Client item.

3. From the Client Name page of the wizard, enter Overview as the Client Name. Click the Next
button.

82 of 207
4. From the Display Client Options page of the wizard, click the Next button.
5. From the Select or Create the Virtual Screen Layout page of the wizard, select 1920x1080 from
the Screen Resolution drop down list and then click the Add button.

6. From the Custom Overlay dialog box, enter Main as the Overlay Name, 0 in the Left field, 0 in the
Top field, 1280 in the Width field and 1024 in the Height field. Click the OK button.

7. Back at the Select or Create the Virtual Screen Layout page of the wizard, click the Add button
again to add another overlay.

83 of 207
8. From the Custom Overlay dialog box, enter Top as the Overlay Name, 1280 in the Left field, 0 in
the Top field, 640 in the Width field and 360 in the Height field. Click the OK button.

9. Back at the Select or Create the Virtual Screen Layout page of the wizard, click the Add button
again to add another overlay.

10. From the Custom Overlay dialog box, enter Middle as the Overlay Name, 1280 in the Left field,
360 in the Top field, 640 in the Width field and 360 in the Height field. Click the OK button.

84 of 207
11. Back at the Select or Create the Virtual Screen Layout page of the wizard, click the Add button
again to add another overlay.

12. From the Custom Overlay dialog box, enter Bottom as the Overlay Name, 1280 in the Left field,
720 in the Top field, 640 in the Width field and 360 in the Height field. Click the OK button.

13. Note the completed Virtual Screen layout and click the Next button.

85 of 207
14. We will now assign content to each of the overlays created, starting with the Main overlay. Click the
Add button in the Selected Display Clients frame.

15. Select the CookieDemo item from the list and click the OK button.

86 of 207
16. Back at the Virtual Screen Configuration page of the wizard, click the Next button.

17. Now for the Top overlay, click the Add button.

87 of 207
18. Select the InstantFizz item from the list and click the OK button.

19. Back at the Virtual Screen Configuration page of the wizard, click the Screen Options button.

88 of 207
20. From the Virtual Screen Options dialog, check the Virtual Screen Specific Mouse Button
Mapping checkbox, and select Main from the Swap Destination drop down list. Click the Mouse
Button Mapping button.

21. From the Mouse Button Mapping dialog, select Swap from the Button 3 (Right Mouse) drop down
list. Click the OK button twice, followed by the Next button.

89 of 207
22. Now for the Middle overlay, click the Add button.

23. Select the ME82 item from the list and click the OK button.

90 of 207
24. Back at the Virtual Screen Configuration page of the wizard, click the Screen Options button.

25. From the Virtual Screen Options dialog, check the Virtual Screen Specific Mouse Button
Mapping checkbox, and select Main from the Swap Destination drop down list. Click the Mouse
Button Mapping button.

91 of 207
26. From the Mouse Button Mapping dialog, select Swap from the Button 3 (Right Mouse) drop down
list. Click the OK button twice, followed by the Next button.

27. Now for the Bottom overlay, click the Add button.

92 of 207
28. Select the SuperJuice item from the list and click the OK button.

29. Back at the Virtual Screen Configuration page of the wizard, click the Screen Options button.

93 of 207
30. From the Virtual Screen Options dialog, check the Virtual Screen Specific Mouse Button
Mapping checkbox, and select Main from the Swap Destination drop down list. Click the Mouse
Button Mapping button.

31. From the Mouse Button Mapping dialog, select Swap from the Button 3 (Right Mouse) drop down
list. Click the OK button twice, followed by the Finish button.

94 of 207
Apply Virtual Screen to Terminal

1. Click the Terminals icon from the ThinManager tree selector.

2. From the Terminals tree, double click the ThinXXA terminal to launch the Terminal
Configuration Wizard.
3. Click the Next button on the Terminal Name page of the wizard.
4. Click the Next button on the Terminal Hardware page of the wizard.
5. Click the Next button on the Terminal Options page of the wizard.
6. From the Terminal Mode Selection page of the wizard, un-check the Enable MultiMonitor
checkbox. Click the Next button.

95 of 207
7. Remove CookieDemo, InstantFizz, ME82, and Studio5000 from the Selected Display Clients
list. Select the Overview Display Client from the Available Display Clients list and click the
Right Arrow button to move it to the Selected Display Clients list. Click the Next button.

8. Click the Next button from the Terminal Interface Options page of the wizard.
9. Click the Next button from the Hotkey Configuration page of the wizard.
10. Click the Next button from the Log In Information page of the wizard.
11. Select 1920x1080 from the Resolution drop down list, keeping the same Color Depth and
Refresh Rate. Click the Finish button.

96 of 207
12. Right click the ThinXXA (where XX is your assigned attendee number) terminal from the
Terminals tree and select Restart Terminal to apply the changes. Click Yes to the confirmation
dialog.
13. Select the Shadow tab to see the results. Right click on each of the Display Clients on the right
to see how they Swap with the Main Virtual Screen.

If right-clicking the Display Clients on the right does not result in a Swap action, you
may need to return to your Virtual Screen Display Client and re-assign the Main
Virtual Screen as the Swap Destination for the Top, Middle and Bottom Virtual
Screens (appears to be an anomaly with this version of ThinManager).

Like MultiMonitor Display Clients, Virtual Screen Display clients can be configured to be
moveable from one Virtual Screen to another. You can also enable Tiling within a Virtual
Screen. You can also select any of the Virtual Screens to go Full Screen from their
respective Display Client Selector, and then return to Virtual Screen mode. Virtual
Screening allows you to take the concept of digital signage to the plant floor and deliver a
wide range of content in virtually an unlimited number of ways.

97 of 207
ThinManager 8.1 added support for 4K monitors. For thin clients with the graphics
horsepower to drive a 4K display (3840x2160), you will be able to carve up the 4K display
into 4 separate 1920x1080 quadrants and treat them as individual displays within
ThinManager using Virtual Screening.

98 of 207
Remove Virtual Screen Display Client

1. Click the Terminals icon from the ThinManager tree selector.

2. From the Terminals tree, double click the ThinXXA (where XX is your assigned attendee number)
terminal to launch the Terminal Configuration Wizard.
3. Click the Next button on the Terminal Name page of the wizard.
4. Click the Next button on the Terminal Hardware page of the wizard.
5. Click the Next button on the Terminal Options page of the wizard.
6. Click the Next button on the Terminal Mode Selection page of the wizard.
7. Remove the Overview Display Client from the Selected Display Clients list, and add the
CookieDemo. Click the Next button.

8. Click the Next button from the Terminal Interface Options page of the wizard.
9. Click the Next button from the Hotkey Configuration page of the wizard.
10. Click the Next button from the Log In Information page of the wizard.

99 of 207
11. Select 1280x1024 from the Resolution drop down list, keeping the same Color Depth and
Refresh Rate. Click the Finish button.

12. Right click the ThinXXA (where XX is your assigned attendee number) from the Terminals tree
and select Restart Terminal to apply the changes. Click Yes to the confirmation dialog.

100 of 207
Cleanup Disconnected Sessions
Since the RDSXX cloud server has minimal resources, let’s reset the Remote Desktop Server sessions we
are no longer using.

1. Click the Display Servers icon in the ThinManager tree selector.

2. From the Display Servers tree, expand the Display Servers tree item and Remote Desktop
Servers tree item. Select the RDSXX (where XX is your assigned attendee number) tree item.
Click the Sessions tab.

101 of 207
3. Right click each userXX (where XX is your assigned attendee number) Disconnected session,
and select Reset Session. Each session will take a few seconds to be removed from the list.

102 of 207
Section 5: Terminal Replacement in under 2 Minutes

Overview
A ThinManager terminal can be replaced in under 2 minutes. When a terminal does fail, replacement starts
by disconnecting the failed terminal and connecting the new terminal in its place. The replacement terminal
does not even need to be the same make or model. When the new terminal is powered up for the 1st time,
ThinManager will recognize that it has not been associated with a ThinManager terminal configuration
previously and prompt you to assign one to it. One of the available terminal configurations will be the
configuration for the failed terminal, since it is no longer in service. Once that terminal configuration is
selected, ThinManager will create an association between the terminal and terminal configuration based on
the MAC address of the terminal, and will therefore not prompt for this assignment on subsequent reboots
of the terminal. Once assigned, the new terminal will essentially assume the identity of the failed terminal
and even reconnect to the failed terminal’s sessions (Remote Desktop Server, VDI, etc.), which typically
are configured to run uninterrupted on the server during this process.
This lab section is composed of the following tasks:
1. Power Down ThinXXA
2. Replace ThinXXA with ThinXXB

103 of 207
Power Down ThinXXA

1. Click the Terminals icon from the ThinManager tree selector.

2. Under the Terminals node, select the ThinXXA terminal.
3. Select the Tools ribbon, and then click the Power Off icon. This will remotely power down the
virtual thin client. To confirm, the ThinXXA (where XX is your assigned attendee number) terminal
icon in the Terminals tree should be Red before continuing.

104 of 207
Replace Thin Client XXA with Thin Client XXB
1. Double click the Thin Client XXB (where XX is your assigned attendee number) virtual machine
from the desktop of RDSXX, and click the full screen mode icon. Thin Client XXB will boot and
receive its firmware from ThinManager. However, because ThinManager does not have an
existing terminal configuration that matches the MAC address of Thin Client XXB, you will be
prompted to either Create new Terminal or select an existing terminal configuration that is
currently not active, ThinXXA.

105 of 207
2. Select ThinXXA from the list using the Down Arrow of your keyboard and hit Enter. By doing so,
you will reassign the ThinXXA terminal configuration to ThinXXB.

106 of 207
3. You have now successfully replaced ThinXXA with ThinXXB. Notice when ThinXXB received the
ThinXXA terminal configuration it was automatically reconnected to the Remote Desktop Server
sessions that ThinXXA had been running – literally, a bumpless transfer.

4. Return to the ThinManager by minimizing the ThinXXB virtual machine.

5. To reassign the ThinXXA configuration back to the ThinXXA virtual thin client, click the Terminals

icon from the ThinManager tree selector.

6. Under the Terminals node, select the ThinXXA terminal.

107 of 207
7. Select the Tools ribbon, and then click the Power Off icon. This will remotely power down the
ThinXXB virtual thin client. To confirm, the ThinXXA terminal icon in the Terminals tree should be
Red before continuing.

.
8. Launch the ThinXXA virtual thin client from the desktop of RDSXX.

108 of 207
9. Select ThinXXA from the list using the Down Arrow of your keyboard and hit Enter. By doing so,
you will reassign the ThinXXA terminal configuration back to ThinXXA.

If you were to select Create new Terminal in Step 2, the Terminal Replacement Wizard
would automatically launch within the ThinManager user interface. This wizard will then
launch you into the Terminal Configuration Wizard to create a new terminal
configuration.

You can control whether a terminal’s configuration is available to other terminals when the
owning terminal is offline. This setting can be found in the Terminal Options page of the
Terminal Configuration Wizard. It is called Allow replacement at terminal if off line.

109 of 207
Section 6: Terminal to Terminal Shadowing

Overview
Throughout the lab you have shadowed terminals from the ThinManager user interface. One of the more
unique features of ThinManager is the ability to not just shadow terminals from the administrative console
of ThinManager, but also from another terminal, or terminals. Terminal to terminal shadowing is a very
powerful feature that can be configured for interactive access or non-interactive access to the shadowed
session. It is most commonly used to provide centralized monitoring of terminals from either a Control
Room or Manager’s Office setting.
This lab section is composed of the following tasks:
1. Create Terminal Shadow Display Client
2. Create a Second Terminal Configuration
3. Assign Second Terminal Configuration

110 of 207
Create Terminal Shadow Display Client

1. Click the Display Clients icon from the ThinManager tree selector.
2. From the Display Clients tree, right click the Terminal Shadow branch and select Add Display
Client. This will launch the Display Client Wizard.

3. Type Shadow as the Client Name on the Client Name page of the wizard. Click the Next button.

111 of 207
4. Click the Next button on the Display Client Options page of the wizard.
5. From the Terminal Shadow Display Client page of the Display Client Wizard, uncheck the All
Terminals Shadow checkbox, then click the Add button.

6. Select ThinXXA (where XX is your assigned attendee number) from the Select Terminal or
Group popup, followed by the OK button.

112 of 207
7. Click the Finish button.

113 of 207
Create a Second Terminal Configuration

1. Click the Terminals icon from the ThinManager tree selector.

2. From the Terminals tree, expand the Terminals node, right click the ThinXXA terminal and select

Copy.
3. From the New Terminal input box, enter ThinXXB (where XX is your assigned attendee number)
as the new terminal name. Click the OK button.

4. Double click the ThinXXB terminal to launch the Terminal Configuration Wizard.

114 of 207
5. Click the Next button on the Terminal Name page of the wizard.
6. Click the Next button on the Terminal Hardware page of the wizard.
7. Click the Next button on the Terminal Options page of the wizard.
8. Click the Next button on the Terminal Mode Selection page of the wizard.
9. Remove CookieDemo from the Selected Display Clients list.
10. Select Shadow from the Available Display Clients list and click the Right Arrow button to move
it to the Selected Display Clients list. Click the Finish button.

115 of 207
Assign Second Terminal Configuration
1. Double click the ThinXXB (where XX is your assigned attendee number) virtual machine shortcut
on your desktop.
2. Select ThinXXB from the list using the Down Arrow of your keyboard and hit Enter. By doing so,
you will assign the ThinXXB terminal configuration to ThinXXB.

3. Once ThinXXB receives its Terminal configuration from ThinManager, an interactive shadow of
ThinXXA will be delivered. Change screens within the FactoryTalk View SE CookieDemo
application from ThinXXB, then switch to the ThinXXA virtual machine to verify that the screen
change occurs there as well. Change screens from ThinXXA and then switch back to the
ThinXXB virtual machine to see the change in that direction.

116 of 207
4. From ThinManager, select the ThinXXB terminal. From the Tools ribbon, select the Power Off
ribbon icon to power down this virtual thin client. Click the Yes button from the ensuing
confirmation dialog box.

As previously mentioned, Terminal to Terminal Shadowing is not just a one to one

proposition. A single Terminal can be shadowed from several other terminals. The
processing required by shadowing resides on the Terminal that is being shadowed.
Therefore, if you plan on shadowing a single Terminal several times it is recommended
that the thin client hardware be specified with the necessary computing resources to
accommodate the additional loading provided by shadowing.

117 of 207
Section 7: User Based Content Delivery

Overview
Up to this point in the lab, you have assigned content to the terminal. In other words, the content is owned
by the terminal and is the same regardless of who is physically at the thin client. You can control a user’s
access within each application at the terminal by requiring them to login within the application and then
customizing their experience there – but this is completely separate from ThinManager. This lab section
will demonstrate how you can customize the actual content that a user receives at a terminal in addition to
the default content that are configured for the terminal. For instance, you may want to deliver additional
content to a Maintenance user that logs into the terminal using ThinManager security, such as the
Maintenance Work Order System, or possibly Logix Designer.
This lab section is composed of the following tasks:
1. Create a Maintenance User Group
2. Create a Maintenance User
3. Enable User Services for Terminal
4. Login as Maintenance User

118 of 207
Create a Maintenance User Group

1. Click the Users icon in the ThinManager tree selector.

2. From the Relevance Users tree, right click the Relevance Users node and select Add User
Group. This will launch the Relevance User Configuration Wizard.

3. From the Relevance User Group Information page of the wizard, enter Maintenance as the User
Name in the Group Name frame. Click the Next button.

119 of 207
 ThinManager 8 included much tighter integration with Active Directory. For example, a
Relevance User Group can be automatically synchronized with an Active Directory group.
In doing so, ThinManager would automatically create Relevance Users for each member
of the synchronized Active Directory group. It should be noted that only 1 AD Security
Group can be used to synchronize with Active Directory in ThinManager. This limitation is
because an Active Directory user can be a member of multiple Active Directory groups, but
ThinManager does not support this membership model (i.e.: a Relevance User can only
belong to one Relevance User Group). ThinManager can also synchronize with an
Organizational Unit and automatically create the associated Relevance users.

4. From the Display Client Selection page of the wizard, check the Group Setting checkbox.
Select Yes from the Add User-specific Display Clients radio button group. Click the Next button.

Clicking the Group Setting checkbox will pass the setting onto members of the group.

120 of 207
5. Select Logix from the Available Display Clients list and click the Right Arrow button to move it
to the Selected Display Clients list. Click the Group Setting checkbox and then click the Next
button.

6. From the Windows Log In Information page of the wizard, click the Next button.
7. From the Terminal Interface Options page of the wizard, note that you can override the default
Terminal settings by making changes here. Leave the default settings in place. Click the Next
button.
8. From the Terminal Hotkey Options page of the wizard, click the Next button. From the User
Group Options page of the wizard, click the Activate Display Client at Log In checkbox, as well
as its Group Setting checkbox. This setting will pull the user’s configured Display Clients to the
foreground at the Terminal when they login. Click the Finish button.

121 of 207
Create a Maintenance User
1. Expand the Relevance Users node.
2. Right click the newly created Maintenance User Group and select Add User. This will launch the
Relevance User Configuration wizard.

3. From the Relevance User Information page of the wizard, check the Active Directory User
checkbox if it is not already checked. Click the Search button.

4. From the Search for AD User dialog box, click the Search button.

122 of 207
5. Select userXX (where XX is your assigned attendee number) from the user list and then click the
OK button.

By linking to an Active Directory User, this Relevance user’s credentials will live in Active
Directory, not within ThinManager. This concept is very similar to creating Windows
Linked Accounts in the FactoryTalk Directory. You can also create non-linked Active
Directory users in ThinManager, in which case their credentials would reside in
ThinManager.

6. Back at the Relevance User Information page of the wizard, click the Next button.

123 of 207
7. From the Active Directory Password page of the wizard click the Next button.

Note that you can choose to store the Active Directory password for this user within
ThinManager. This is sometimes done when using badge readers or fingerprint scanners
so the user can either scan his/her badge or scan his/her fingerprint only to login (i.e.: no
password entry is required). If the Active Directory password were to change outside of
ThinManager, the user would be prompted to enter the new password upon their next login
attempt, which would then result in ThinManager storing the updated password. You can
also allow ThinManager to automatically rotate the user’s Active Directory password based
on pre-defined criteria, in which case, only ThinManager would know the active password.
Many times end users choose to have their terminals automatically login to the Remote
Desktop Servers with a service account, and then security is managed within the
application delivered. Prior to ThinManager 8, a service account with a non-expiring
password would have to be created in this scenario.

8. From the Card / Badge Information page of the wizard, click the Next button.
9. From the Relevance Resolver Selection page of the wizard, click the Next button.
10. From the Display Client Selection page of the wizard, notice that the selection is disabled. This is
because we chose Group Setting for this setting on the User Group. Click the Next button.

124 of 207
11. From the Display Client Specification page of the wizard, notice that the selection is disabled
here as well. Click the Finish button.

125 of 207
Create an Operator Relevance User Group
1. From the Relevance Users tree, right click the Relevance Users node and select Add User
Group. This will launch the Relevance User Configuration Wizard.

2. From the Relevance User Group Information page of the wizard, enter Operator as the User
Name in the Group Name frame. Click the Finish button.

126 of 207
Create an Operator User
1. Expand the Relevance Users node.
2. Right click the newly created Operator User Group and select Add User. This will launch the
Relevance User Configuration wizard.

3. From the Relevance User Information page of the wizard, un-check the Active Directory User
checkbox, enter oper as the User Name and z as the Password and Verify Password. Click the
Finish button.

127 of 207
Enable User Services for Terminal

1. Click the Terminals icon from the ThinManager tree selector.

2. Under the Terminals node, double click the ThinXXA (where XX is your assigned attendee
number) terminal to launch the Terminal Configuration Wizard.
3. Click the Next button on the Terminal Name page of the wizard.
4. Click the Next button on the Terminal Hardware page of the wizard.
5. Click the Next button on the Terminal Options page of the wizard.
6. From the Terminal Mode Selection page of the wizard, check Enable Relevance User Services.
Click the Finish button.

7. Right click ThinXXA terminal and select Restart Terminal to apply the change.

When deploying Relevance Users for the first time, Enabling Relevance User Services at
the Terminal is a commonly missed step. Without Enabling Relevance User Services at
the terminals where you want to enable Relevance User logins, the Login option will not be
available from the Display Client Selector menu. If you would like to Enable Relevance
User Services for all of your terminals, you can create a Terminal Group, enable it there,
and check the Group Setting checkbox. Each Terminal member of the Terminal Group
would then have it enabled.

128 of 207
Login as Maintenance User

1. From the Terminals icon in the ThinManager tree selector, select ThinXXA.
2. Click the Shadow tab from the Details Pane.
3. Click and hold the Display Client Selector at the top middle of the Shadow where it lists
CookieDemo. While holding down the mouse button, select the Main Menu entry from the
Display Client Selector.
You can also use the CTRL-m hotkey sequence to access the Main Menu.

129 of 207
4. From the Main Menu, click the Log In button.

130 of 207
5. From the Log In popup, enter userXX (where XX is your assigned attendee number) as the User
Name.
6. From the Password popup, enter z as the Password.
7. Once logged in, the Logix Display Client should be launched, activated and brought to the
foreground. Notice that there are now 2 Display Clients listed under the ThinXXA Terminal in the
Terminals tree. Also notice that the ThinXXA Terminal label now indicates that userXX is logged
in there.

8. Click the Display Client Selector within the Shadow and select the CookieDemo Display Client
to activate it.
9. Click the Display Client Selector again and select the Logix Display Client to activate it.
10. Click the Display Client Selector once more and this time select Main Menu.
11. From the Main Menu, click the Log Off button. UserXX (where XX is your assigned attendee
number) will be logged off, and the Logix Display Client will be removed.

There is an Inactivity Timeout setting available either at the User Group level or at the User
object itself that will automatically logoff the Relevance User after a period of inactivity.
The default is 120 seconds. It can be found on the last page of the User Configuration
Wizard.

If userXX were to leave ThinXXA and log into another Terminal (either terminal, PC or
tablet), his/her content would follow him/her. You can control what happens to a
Disconnected session in Domain Deployments with the Session Collection in Windows
Server 2012. For Workgroup Deployments, this is controlled through Group Policy only.

131 of 207
If you would prefer userXX to only receive content at a specific Terminal, you can use
ThinManager Access Groups to apply permissions to specific Display Clients. Access
Groups can be configured from the Manage ribbon. Once an Access Group is created, it
can then be associated with a Relevance User Group. The same Access Group can then
be applied as a Permission on the Display Client(s) that you want to restrict or provide
access to. When you apply these restricted Display Clients to a Terminal, they will only
become visible when a user assigned to that Access Group logs into the Terminal. We will
create Access Groups in Section 8.

ThinManager ships with the TermMon ActiveX control that can be utilized by any ActiveX
container, like the FactoryTalk View SE Client. The ActiveX extends most of the
ThinManager feature set to the ActiveX container, so you can then programmatically
control many elements of ThinManager right from the FactoryTalk View SE Client. As an
example, you can trigger a Touchscreen Calibration to launch from a button within
FactoryTalk View SE using the ActiveX control. You can also respond to ThinManager
events from within FactoryTalk View SE. So when a Relevance user logs into
ThinManager, an event is triggered in the ActiveX and FactoryTalk View SE that can be
configured to programmatically log that same user into FactoryTalk View SE. More details
on the ActiveX control can be found at:
http://www.thinmanager.com/kb/index.php/TermMon_ActiveX_Control

132 of 207
Section 8: Event Notification and Firewall Compatible TFTP

Overview
In this section, we are going to configure ThinManager event notification using both e-mail and text
messaging (SMS), as well as enabling Firewall Compatible TFTP.
This lab section is composed of the following tasks:
1. Enable E-Mail and SMS Event Notifications
2. Modify Configuration to Generate Event Notifications
3. Enable Firewall Compatible TFTP

133 of 207
Enable E-Mail and SMS Event Notifications

1. Click the ThinManager Server icon from the ThinManager tree selector.
2. Double click the RDSXX ThinManager Server to launch the ThinManager Server Configuration
Wizard.

1. Click the Next button from the Introduction page of the ThinManager Server Configuration
Wizard.
2. Click the Next button from the Unknown Terminals page of the wizard.
3. Click the Next button from the Terminal Replacement page of the wizard.
4. Click the Next button from the Historical Logging page of the wizard.
5. Click the Next button from the System Schedule page of the wizard.
6. Click the Next button from the ThinManager Security Groups page of the wizard.

With ThinManager Security Groups, you can control the permissions within the
ThinManager user interface based on their Windows User Group assignment. By default,
members of the Windows local Administrators group have permission to perform all tasks
within ThinManager. Several other groups have been pre-created within ThinManager
(i.e.: ThinManager Administrators, ThinManager Interactive Shadow Users, ThinManager
Power Users, ThinManager Shadow Users, ThinManager Users), each of which has their
own permission assignments. To utilize these groups, you would need to create the same
Windows group names on the PC on which ThinManager is installed and assign the
associated users to those groups.

134 of 207
7. From the Event Selection page of the ThinManager Server Configuration Wizard, select
Display Client Configuration Change Events from the Event Type drop down list, and check the
E-mail notification event type checkbox. Do not click the Next button yet.

135 of 207
8. Still from the Event Selection page of the ThinManager Server Configuration Wizard, select
Terminal Configuration Change Events from the Event Type drop down list, and check the SMS
Message notification event type checkbox. Click the Next button.

136 of 207
9. From the E-mail or Windows Message Recipients page of the ThinManager Server
Configuration Wizard, click the Settings button.

137 of 207
10. From the Email Server Settings dialog box, enter the follow details and click the OK button.
SMTP Server: smtp.gmail.com
SMTP Port: 25
Username: [email protected]
Password: thinman1
Use SSL: Checked
E-mail Return Address: [email protected]
Email Subject Prefix: ThinManager:

To use Gmail as an SMTP Server, the Allow less secure apps setting must be turned ON
within your Gmail settings. This setting was accessible through the Sign-in & Security
panel of the Gmail account being used for SMTP Authentication ([email protected]
in this example).

138 of 207
11. From the E-mail or Windows Message Recipients page of the ThinManager Server
Configuration Wizard, click the Add button from the E-Mail frame.

12. From the Enter the E-mail address dialog box, enter your e-mail address and click the OK button.

139 of 207
13. From the E-mail or Windows Message Recipients page of the ThinManager Server
Configuration Wizard, click the Add button from the SMS (Text Message) frame.

14. From the SMS Message Recipient dialog box, enter your Cell Phone Number, select your Cell
Phone Service Provider from the drop down list and then click the OK button. Click the Next
button, followed by the Finish button.

140 of 207
Modify Configuration to Generate Event Notifications
In the previous steps, you setup an E-mail notification for changes made to a Display Client and a Text
Message notification for changes made to a Terminal. In this section, you will make changes to a Display
Client and Terminal to generate the notifications.

1. From ThinManager, click the Display Clients icon from the ThinManager tree selector.
2. Double click the Studio5000 Display Client.

3. From the Client Name page of the wizard, click the Next button.
4. From the Display Client Options page of the wizard, click the Next button.
5. From the Remote Desktop Services and Workstation Options page of the wizard, click the Next
button.

141 of 207
6. From the Screen Resolution / Scaling Options page of the wizard, select 1024x768 from the
Resolution drop down list and click the Finish button.

142 of 207
7. Within a minute or so and you should receive an e-mail notification regarding this Display Client
change.

143 of 207
8. Click the Terminals icon from the ThinManager tree selector.
9. From the Terminals tree, double click the ThinXXA (where XX is your assigned attendee number)
terminal to launch the Terminal Configuration Wizard.

10. Click the Next button on the Terminal Name page of the wizard.
11. Click the Next button on the Terminal Hardware page of the wizard.
12. Click the Next button on the Terminal Options page of the wizard.
13. Click the Next button on the Terminal Mode Selection page of the wizard.
14. From the Display Client Selection page of the wizard, select the Studio5000 Display Client and
click the Right arrow button to add it to the Selected Display Clients list. Remove the
CookieDemo Display Client from the Selected list. Click the Finish button.

144 of 207
15. Right click ThinXXA (where XX is your assigned attendee number) and select Restart Terminal.
Click Yes to the ensuing confirmation dialog box.
16. Within a minute or so, you should receive a Text Message notifying you of the Terminal change
just made.

145 of 207
17. With ThinXXA (where XX is your assigned attendee number) selected within ThinManager, click
the Shadow tab. Notice that the Studio5000 Display Client is being delivered as a 1024x768
session and automatically scaled within the 1280x1024 screen.

146 of 207
Enable Firewall Compatible TFTP
In this section, we will enable the Firewall Compatible TFTP feature which is new to ThinManager 9.

1. Click the ThinManager Server icon from the ThinManager tree selector.
2. Double click the RDSXX ThinManager Server to launch the ThinManager Server Configuration
Wizard.

3. Click the Next button from the Introduction page of the ThinManager Server Configuration
Wizard.
4. Click the Next button from the Unknown Terminals page of the wizard.
5. Click the Next button from the Terminal Replacement page of the wizard.
6. Click the Next button from the Historical Logging page of the wizard.
7. Click the Next button from the System Schedule page of the wizard.
8. Click the Next button from the ThinManager Security Groups page of the wizard.
9. Click the Next button from the Event Selection page of wizard.
10. Click the Next button from the E-mail or Windows Message Recipients page of wizard.

147 of 207
11. From the Multicast Configuration page of the wizard, check the Enable Firewall Compatible
TFTP checkbox. Click the Finish button.

Why might this be important? Both ThinManager Ready and ThinManager Compatible
Terminals use TFTP (Trivial File Transfer Protocol) to transfer the ThinManager firmware
to thin/zero clients. The TFTP conversation starts at the client side on a specific port
(UDP4900 for ThinManager Ready terminals, UDP69 for ThinManager Compatible
terminals). By default, the ThinManager Server will respond on a random port per the
TFTP specification. The random nature of this response can make firewall configuration
(hardware and/or software) challenging. Most managed firewalls can be configured for
TFTP and intelligently handle the opening and closing of random ports. If not, then a fairly
broad range of ports must be opened, which is generally not desirable. By checking the
Enable Firewall Compatible TFTP, ThinManager will respond on the same port initiated by
the client (UDP4900 for ThinManager Ready terminals, UDP69 for ThinManager
Compatible terminals), making firewall configuration much simpler.

148 of 207
Section 9: Relevance – Location Based Content Delivery

Overview
So far we have assigned and delivered content to a terminal, as well as content to a user. The next level of
the content delivery model is to add Location into the equation. When talking about mobility on the plant
floor, providing access anywhere to applications that control moving processes may cause more problems
than solve. ThinManager Relevance provides the tools to safely provide access to these applications
because you can define a Location and associate Display Client(s) with that Location. When a mobile
device leaves a specified Location, the content associated with that Location will be no longer delivered to
the mobile device. Different users may receive different content from the same Location based on their
Access Groups in ThinManager.
So how does ThinManager determine a mobile device’s location? By using Location Resolver technologies
like:
1. Quick Response Codes (QR Codes)
2. Bluetooth Beacons
3. Wireless Access Points
4. Global Positioning Systems (GPS)
Relevance supports iOS, Android and Windows mobile devices. For iOS devices, ThinManager offers the
iTMC application which is available through the App Store, while for Android devices, ThinManager offers
the aTMC application which is available through the Google Play Store. For Windows tablets,
ThinManager offers WinTMC, which is a Windows based application that essentially emulates a
ThinManager terminal. In order to leverage all of the available Location Resolver technologies on a
Windows Tablet, it is recommended that Windows 10 be utilized.
Location Resolvers can be easily registered through iTMC, aTMC or WinTMC. For example, a QR Code
can be scanned within any of these apps, or a Bluetooth Beacon can be detected and registered.
Once you have registered your Location Resolvers, you can then assign them to Locations created within
ThinManager, and in turn, specific Display Clients can be associated with that Location.
As an example, let’s say we would like to apply laminated QR Codes to all of our process automation
assets, so that our Maintenance staff could walk up to an instrument with their iPad, scan a QR Code, and
instantly receive a series of documents and/or or applications that are assigned to that instrument. To do
so, we would first need to register each QR Code using iTMC from the iPad. Within ThinManager, we
would create the Display Clients necessary for the desired documentation. This might include a series of
Display Clients for Adobe Reader that open specific user manuals and/or standard operating procedures
located on a file share. With the Display Clients created, we would then create a new Location in
ThinManager, assign the Display Clients to it, and then associate the new QR Code Resolver to the
Location.

149 of 207
We can also assign a default Location to a Terminal, which would enable a mobile device to interact with
that Terminal in some very unique ways. Instead of applying Display Clients to a Terminal like we have
throughout the lab so far, we would assign the Display Client(s) to the Location and then assign the
Location to the Terminal. This extra level of indirection creates some very interesting possibilities. For
instance, we could allow a user to scan a QR Code at the terminal that would actually Transfer, or redirect,
the content from the terminal to the mobile device. We could also confine access to this content by
applying a Bluetooth Beacon to “geo-fence” the user. When the user walks outside of the range
established for the Bluetooth Beacon, the content would automatically be removed from the device, as it
would be returned to the terminal. In this example, the Transfer is considered a Resolver Action.
ThinManager Relevance supports 5 Resolver Actions:
1. Forced Transfer
2. Manual Transfer
3. Clone
4. View Only Shadow
5. Shadow

The Forced Transfer re-directs Display Client(s) from a terminal to a mobile device without requiring
approval at the terminal. Manual Transfer, on the other hand, would require a user’s acknowledgement at
the terminal to approve the Transfer request. Clone would spin up new, independent sessions of the
Display Clients assigned to the terminal, while View Only Shadow and Shadow would do just what you
would expect.

150 of 207
Since it is not possible to use wireless devices with our lab setup, we will walk through the configuration
steps, but will not be able to test out the configuration on an actual wireless device.
This lab section is composed of the following tasks:
1. Create Terminal Configuration for Mobile Device
2. Assign Terminal Configuration to Mobile Device
3. Create Resolvers from ThinManager
4. Create Access Groups
5. Create Locations
6. Assign the Location to a Terminal

QR Codes are essentially more robust alphanumeric versions of barcodes. QR Codes can
be generated and printed from several websites. Bluetooth Beacons are essentially
proximity sensors for mobile devices. They offer a tunable signal strength, and hence
range, from 0 to approximately 50 meters. ThinManager 8 introduced support for the
iBeacon, which utilizes Apple’s Bluetooth beacon protocol. There are numerous iBeacons
available in various forms. Wireless Access Points expose a unique identifier called a
BSSID which ThinManager can use to determine on which Access Point a mobile device is
connected. GPS offers accurate location resolution down to 5 feet, but is only for outdoor
applications.

Fencing (or geo-fencing) is defined as combining resolvers to limit access to specific

Display Clients based on Location. For instance, a Bluetooth Beacon can be used to geo-
fence in a QR Code so that a mobile device must be within range of the Bluetooth Beacon
when they scan the QR Code to actually resolve to the associated Location and receive its
content. Once the mobile device is outside the range of the Bluetooth Beacon, the Display
Clients associated with the Location would not be delivered to the mobile device.

151 of 207
Create Terminal Configuration for Mobile Device

1. Click the Terminals icon from the ThinManager tree selector.

2. From the Terminals tree, right click the Terminals node and select Add Terminal. This will
launch the Terminal Configuration Wizard.

3. Type iPad as the Terminal Name on the Terminal Name page of the wizard. Click the Next
button.

152 of 207
4. Select Apple from the Make/OEM drop down list and iOS Device from the Model drop down list.
Click the Next button.

5. Click the Next button on the Terminal Options page of the wizard.
6. Check the Use Display Clients, Enable Relevance User Services, and Enable Relevance
Location Services checkboxes on the Terminal Mode Selection page of the wizard. Click the
Next button.

7. Click the Next button on the Display Client Selection page of the wizard.
8. Click the Next button on the Terminal Interface Options page of the wizard.

153 of 207
9. Check the Enable QR Code Location Ids and Enable Bluetooth Locations checkboxes from the
Relevance Options page of the wizard. Click the Next button.

10. Click the Next button from the Log In Information page of the wizard.
11. From the Video Resolution screen of the wizard, select 1920x1080 as the Resolution, and 64K
Colors as the Color Depth. Click the Finish button.

154 of 207
Create Resolvers from ThinManager
At this point, you would typically connect the iPad to your wireless network with connectivity to
ThinManager, launch the iTMC application and then assign the new iPad terminal configuration to your
iPad. Once done, you would start to register your location resolvers from iTMC. Since we do not have an
actual iPad in this lab, we will instead register the location resolvers manually through ThinManager.
1. From ThinManager, click the Manage ribbon, followed by the Manage Resolvers icon.

2. Click the Add button from the Resolver Management popup. Typically, Resolvers are easily
registered and added through the mobile device, but will be done so manually in the lab.

3. From the Add New Resolver dialog, enter MixerQR as the Name, Mixer QR Code as the
Description, select QR Code from the Type drop down list and enter Mixer in the Data field. The
Data field represents the actual value of the QR Code. Click the OK button.

155 of 207
4. Click the Add button from the Resolver Management popup again.

5. Enter MixerBT as the Name, Mixer Beacon as the Description, select Bluetooth as the Type, and
enter ACP-0123456789AB as the Data. The Data field represents the unique identifier of the
Bluetooth Beacon. Click the OK button twice.

156 of 207
Create Access Groups
1. Click the Manage ribbon, followed by the Access Groups icon.

2. From the Access Groups popup, click the Add button.

3. Enter Maintenance as the Enter Group Name field. Click the OK button.

The Select Windows Security Group provides the ability to link an Access Group to a
Widows Security Group. Therefore, you could manage access to ThinManager resources
(Terminals, Display Clients, etc.) through Windows Security Groups as well. You could
also use the TermMon ActiveX within an ActiveX container, like View SE, to detect when a
ThinManager logon event occurs and then to determine that user’s Windows Security
Group membership to determine their appropriate access within the application.

4. Click the Add button again.

157 of 207
5. Enter Operator as the Enter Group Name field. Click the OK button.

6. With the new Maintenance and Operator Access Groups created, click the OK button.

7. Click the Relevance Users icon in the ThinManager Tree Selector.

8. Double click the Maintenance users group.

9. Click the Permissions button from the Relevance User Group Information page of the wizard.

158 of 207
10. Select the Maintenance Access Group from the Available list and click the Right Arrow to move
it to the Member Of list. Click the OK button, followed by the Finish button.

11. Double click the Operator users group.

12. Click the Permissions button from the Relevance User Group Information page of the wizard.

159 of 207
13. Select the Operator Access Group from the Available list and click the Right Arrow to move it to
the Member Of list. Click the OK button, followed by the Finish button.

160 of 207
Create Locations

1. Click the Locations icon in the tree selector. This icon will only be present if you have a
Relevance license activated.

2. From the ensuing Locations tree, right click the Locations tree node and select Add Location.

3. From the Location Name page of the Location Configuration Wizard, enter MixerZone as the
Location Name. Click the Next button.

161 of 207
4. From the Location Options page of the wizard, check Activate Display Client at Log In,
Enforce Location Fencing and Allow Local Access and uncheck the remaining options. Click
the Next button.

5. From the Display Client Selection page of the wizard, click the Next button.
6. From the Windows Log In information, click the Next button.

No Windows Credentials are required for this Location since we have not assigned any
Display Clients to it.

7. From the Relevance Resolver Location page of the wizard, click the Add button.

162 of 207
8. From the Choose a Relevance Resolver popup, select MixerBT from the Resolver Name
dropdown list, and No Action from the Choose Action dropdown list. Click the Permissions
button.

Clicking the Settings button for a Bluetooth Beacon resolver will enable you to set the
signal strength at the entrance point of the Location as well as the exit point of the
Location. The values displayed will show a 0 in the lab since we did not actually register
the beacon from a mobile device. Registering the Bluetooth Beacon through the mobile
device will automate this entry by asking you to stand at the entry point during the
registration process. If you clicked the Settings button, click the Cancel button.

9. Remove Unrestricted from the Member Of list, and add both Operator and Maintenance from
the Available list to the Member Of list. Click the OK button twice, followed by the Finish button.

At this point, you have created the MixerZone Location, which is associated with the MixerBT
Bluetooth Beacon. However, we assigned No Action to the Resolver Action. This is because
this Location will serve as a Fence only, which is why the Enforce Location Fencing checkbox
was checked as well. We have chosen not to deliver content by simply walking within range of the
beacon (although we could have).

163 of 207
10. Now we need to create a sub-location, so expand the Locations node, right click the MixerZone
location and select Add Location.

11. From the Location Name page of the Location Configuration Wizard, enter MixerHMI as the
Location Name. Click the Next button.

164 of 207
12. From the Location Options page of the wizard, check Activate Display Client at Log In and
Allow Local Access and uncheck the remaining options. Click the Next button.

13. Select CookieDemo from the Available Display Clients list and click the Right Arrow button to
move it to the Selected Display Clients list. Click the Next button.

165 of 207
14. From the Windows Log In information page of the wizard, enter [email protected] (where XX is
your assigned attendee number) for the Username, z for the Password field. Click the Next
button.

15. From the Relevance Resolver Selection, click the Add button.

166 of 207
16. From the Choose a Relevance Resolver popup, select MixerQR from the Resolver Name
dropdown list, and Force Transfer from the Choose Action dropdown list. Click the Permissions
button.

17. Remove Unrestricted from the Member Of list, and add Maintenance from the Available list to
the Member Of list. Click the OK button twice.

18. Back at the Relevance Resolver Selection, click the Add button again.

167 of 207
19. From the Choose a Relevance Resolver popup, select MixerQR from the Resolver Name
dropdown list, and Shadow from the Choose Action dropdown list. Click the Permissions
button.

20. Remove Unrestricted from the Member Of list, and add Operator from the Available list to the
Member Of list. Click the OK button twice

21. Back at the Relevance Resolver Selection page of the wizard, click the Finish button.

168 of 207
Assign the Location to a Terminal

1. Click the Terminals icon from the ThinManager tree selector.

2. Under the Terminals node, double click the ThinXXA (where XX is your assigned attendee
number) terminal to launch the Terminal Configuration Wizard.

3. Click the Next button on the Terminal Name page of the wizard.
4. Click the Next button on the Terminal Hardware page of the wizard.
5. Click the Next button on the Terminal Options page of the wizard.
6. From the Terminal Mode Selection page of the wizard, make sure Enable Relevance User
Services is checked. Also check the Enable Relevance Location Services. This is required to
use this Terminal with Relevance. Click the Next button.

169 of 207
7. Remove the CookieDemo Display Client from the Selected list, so that it is empty. Click the
Next button.

8. From the Terminal Interface Options page of the wizard, click the Next button.
9. From the Relevance Options page of the wizard, click the Change button.

170 of 207
10. From the Select Location popup, select LocationsàMixerZoneàMixerHMI. Click the OK
button.

11. Click the Finish button.

12. Right click ThinXXA (where XX is your assigned attendee number) and select Restart Terminal to
apply the change. Click Yes to the confirmation dialog.

After restarting the Terminal, you will notice that the CookieDemo application is still
delivered to ThinXXA. This is because we assigned the CookieDemo Display Client to the
MixerHMI Location and then assigned this Location to the ThinXXA Terminal. The more
interesting part of the configuration is how the MixerZone and MixerHMI Locations were
configured. Using a mobile device, the MixerQR QR Code can be scanned if and only if
the mobile device is within the defined range of the MixerBT Bluetooth Beacon AND the
user logged in is a member of either the Maintenance or Operator Access Groups. If the
user is a member of Maintenance, the CookieDemo Display Client would be transferred
from ThinXXA and redirected to the mobile device. If the user is a member of the Operator
Access Group, ThinXXA would be shadowed from the mobile device. In both cases, the
Display Client would remain on the mobile device as long as it stays within the range of the
Bluetooth Beacon, which is acting as a geo-fence. The user can also choose to manually
Leave the Location from the mobile device.

171 of 207
Section 10: (Optional) Relevance with Actual Mobile Device

Overview
In the previous section, you created Location Resolvers, Access Groups and Locations for use with
Relevance. However, you did not actually see Relevance in action. In this optional section, you will use
your own iOS device (iPhone or iPad) to deliver content from your Cloud Server to your iOS device. In
order to do so, your iOS device will require a connection to the Internet in order to download iTMC from the
iTunes App Store and to access your Cloud Server. If you do not have an iOS device, you can also
perform this section with an Android mobile device or a Windows mobile device, although the screen shots
will coincide with an iOS device. For the Android platform, you will need the aTMC application from the
Google Play Store (https://play.google.com/store/apps/details?id=com.thinmanager.atmc&hl=en), and for
the Windows platform, you will need the WinTMC application from the ThinManager downloads page
(https://downloads.thinmanager.com/Version/9).

This lab section is composed of the following tasks:

1. Download and Install iTMC from the App Store
2. Configure and Connect iTMC
3. User Based Content Delivery to iTMC Part 1
4. Modify Display Servers for Mobile Content
5. User Based Content Delivery to iTMC Part 2
6. Location Based Content Delivery to iTMC

172 of 207
Download and Install iTMC from the App Store
1. Launch the App Store from your iOS device.

173 of 207
2. In the Search field, enter iTMC for ThinManager Platform. Touch the Download icon.

3. Once the download is complete, touch the OPEN button.

174 of 207
Configure and Connect iTMC
1. Upon launching, iTMC will request access to your location while using the app. Touch the Allow
button.

iOS treats Bluetooth beacons as Location Services devices, so if you intend to use
beacons with an iOS device, you will need to enable Location Services for iTMC.

175 of 207
2. You will next be prompted to enter the Primary ThinServer Name or IP Address. Access the
Windows Desktop from your RDSXX (where XX is your assigned attendee number) connection
and note the Public IP Address.

176 of 207
3. Enter the Public IP Address into iTMC as your Primary ThinServer IP Address. Touch the OK
button.

4. Once iTMC connects to the Cloud ThinServer, you will be prompted for a Description for this
connection. Enter Cloud TM and touch the Save button.

Notice in the previous step you could also provide a Secondary ThinManager Server IP
address which iTMC would automatically use if the Primary ThinManager Server IP is
unavailable.

177 of 207
5. With ThinManager successfully registered within iTMC, you will now have a Cloud TM panel item
on the Main screen of iTMC. Touch the Cloud TM panel to connect.

6. The first time iTMC connects to ThinManager, it will require a Terminal Configuration assignment
(just like a new thin/zero client would). Touch the iPad profile, which you created in the previous
section.

178 of 207
7. If you do not have Bluetooth turned on and you want to use beacons, you will be prompted to do so
at this point. Touch the OK button. Turn Bluetooth on to avoid seeing this message in the future.

8. Returning to ThinManager, you should now see the iPad terminal icon in green from the
Terminals button bar, indicating that it is connected.

179 of 207
User Based Content Delivery to iTMC Part 1
1. From iTMC, touch the Login button from the upper right corner.

2. From the Relevance Username popup, enter userXX (where XX is your assigned attendee
number) and touch the OK button.

3. From the Relevance Password popup, enter z and touch the OK button.

4. You will see the iTMC attempt to receive the Studio5000 Display Client since you have
successfully logged in from iTMC, but it will be unable to connect to the 192.168.xx.20 (where XX
is your assigned attendee number) Display Server. This is because the 192.168.xx.0/24 subnet
exists only in the virtual private network in the cloud. We will address this in the next steps.

180 of 207
Modify Display Servers for Mobile Content
The following steps are being performed because our mobile device is connecting from outside our virtual
private network. These steps would not be required if the mobile device were simply connecting onsite
where ThinManager is deployed. We will use this opportunity to demonstrate the usage of Remote
Desktop Server Groups.
1. Return to ThinManager on your RDSXX (where XX is your assigned attendee number) server.

2. Click the Display Servers icon in the ThinManager tree selector.

The tree selector can be expanded or collapsed using the bar above directly above it.

3. Right click the RDS Servers branch and select Add Remote Desktop Server.

181 of 207
4. Click the Next button from the Introduction page of the Remote Desktop Server Wizard.
5. From the Remote Desktop Server Name page of the wizard, enter RDSXXP (where XX is your
assigned attendee number) as the Name, and the Public IP Address from the Desktop of your
RDSXX image as the IP Address. Leave the Log In Information section blank. Click the Finish
button.

6. Right click the RDS Servers branch again, but this time select the Add Remote Desktop Server
Group item.

182 of 207
7. Click the Next button from the Introduction page of the Remote Desktop Server Wizard.
8. Enter RDSXXGroup (where XX is your assigned attendee number) from the Remote Desktop
Server Name page of the wizard and click the Finish button.

9. Double click the RDSF RDS Server from the RDS Servers branch.

183 of 207
10. Click the Next button from the Introduction page of the Remote Desktop Server Wizard.
11. Click the Change Group button from the Remote Desktop Server Name page of the wizard.

12. Select the RDSXXGroup item from the Select Parent Terminal Server Group window and click
the OK button. Click the Finish button.

184 of 207
13. Double click the RDSXXP (where XX is your assigned attendee number) RDS Server from the
RDS Servers branch.

14. Click the Next button from the Introduction page of the Remote Desktop Server Wizard.
15. Click the Change Group button from the Remote Desktop Server Name page of the wizard.

185 of 207
16. Select the RDSXXGroup item from the Select Parent Terminal Server Group window and click
the OK button. Click the Finish button.

17. Double click the RDSXX (where XX is your assigned attendee number) RDS Server from the RDS
Servers branch.

186 of 207
18. Click the Next button from the Introduction page of the Remote Desktop Server Wizard.
19. Click the Change Group button from the Remote Desktop Server Name page of the wizard.

20. Select the RDSXXGroup (where XX is your assigned attendee number) item from the Select
Parent Terminal Server Group window and click the OK button. Click the Finish button.

187 of 207
21. Double click the RDSXXGroup (where XX is your assigned attendee number) item.

22. Click the Next button from the Introduction page of the Remote Desktop Server Wizard.
23. Click the Next button from the Remote Desktop Server Name page of the wizard.
24. Using the Up and Down buttons, arrange your Remote Desktop Servers to match the order
pictured below. Click the Finish button.

188 of 207
25. Click the Display Clients icon from the ThinManager tree selector.

26. Expand the Remote Desktop Services branch and double click the CookieDemo Display Client.

27. Click the Next button from the Client Name page of the Display Client Wizard.
28. Click the Next button from the Display Client Options page of the wizard.
29. Click the Next button from the Remote Desktop Services and Workstation Options page of the
wizard.
30. Click the Next button from the Screen Resolution / Scaling Options page of the wizard.

189 of 207
31. From the Display Client Members page of the wizard, select the RDSXX (where XX is your
assigned attendee number) item and click the Remove button.

32. Select the RDSF item and click the Remove button.

190 of 207
33. Click the Add button.

34. Select the RDSXXGroup (where XX is your assigned attendee number) item and click the OK
button. Click the Finish button.

191 of 207
35. Under the Remote Desktop Services branch, double click the Studio5000 Display Client.

36. Click the Next button from the Client Name page of the Display Client Wizard.
37. Click the Next button from the Display Client Options page of the wizard.
38. Click the Next button from the Remote Desktop Services and Workstation Options page of the
wizard.
39. Click the Next button from the Screen Resolution / Scaling Options page of the wizard.

192 of 207
40. From the Display Client Members page of the wizard, select the RDSXX (where XX is your
assigned attendee number) item and click the Remove button.

41. Click the Add button.

193 of 207
42. Select the RDSXXGroup item and click the OK button. Click the Finish button.

43. Click the Terminals icon from the ThinManager tree selector.

194 of 207
44. Right click the iPad terminal and select the Restart Terminal menu item. Click the Yes button to
confirm.

195 of 207
User Based Content Delivery to iTMC Part 2
1. From iTMC, touch the Login button from the upper right corner.

2. From the Relevance Username popup, enter userXX (where XX is your assigned attendee
number) and touch the OK button.

3. From the Relevance Password popup, enter z and touch the OK button.

196 of 207
4. You will see the iTMC attempt to receive the Studio5000 Display Client since you have
successfully logged in from iTMC, and it will first attempt to connect to the RDSXX Display Server
(since it is listed first in the priority order). This time it will automatically failover to RDSXXP since it
is next in the Remote Desktop Server Group and successfully launch the Display Client.

NOTE: The version of iTMC referenced in this Lab Manual (8.0.803) takes over a minute
to fail from the Primary to the Secondary Display Server. This is a bug that will be
addressed in the next release.

197 of 207
Location Based Content Delivery to iTMC
1. From iTMC, touch the LogOff button in the top right corner.

2. Touch the <Main button in the top left corner. Touch Yes to the confirmation popup.

3. Touch the Settings button at the bottom of the screen.

4. Touch the Manage a Server item from the Please Select popup.

5. Touch the Register QR Code item from the Relevance Resolvers section. Click the OK button
from the ensuing request for iTMC to access the camera. You may have to restart iTMC for this
change to take effect.

198 of 207
6. Using the popup camera window within iTMC, scan the QR Code below:

7. Enter MixerNew as the Enter Description field and touch the OK button.

8. Return to ThinManager, and select the Manage Ribbon, followed by the Manage Resolvers icon.

199 of 207
9. From the Resolver Management window, you should now see the MixerNew resolver show up.
Double click the MixerNew item.

10. From the Edit Resolver window, select the Data field (MixerNew) and copy it to the Clipboard.
This is the data represented by the QR Code we registered a few steps ago. Click the Cancel
button.

200 of 207
11. With MixerNew selected, click the Delete button. Click the Yes button to confirm.

12. Double click the MixerQR item.

13. From the Edit Resolver window, paste in the contents of the clipboard over the contents in the
Data field (should now have MixerNew as the Data). Click the OK button twice.

201 of 207
14. Click the Locations icon in the tree selector. This icon will only be present if you have a
Relevance license activated.

15. From the Locations tree, double click the MixerZone item.

16. Click the Next button from the Location Name page of the Location Configuration Wizard.

202 of 207
17. From the Location Options page of the wizard, un-check the Enforce Location Fencing
checkbox and click the Finish button.

Since we will not be using an actual beacon for this lab, we need to disable to the geo-
fence we setup in the previous section or we will not be able to access the MixerHMI
location.

18. Return to iTMC. Touch the <Settings button, followed by the <Main button in the top right corner.
19. Touch the Cloud TM panel to connect.

20. From iTMC, touch the Login button from the upper right corner.

203 of 207
21. From the Relevance Username popup, enter userXX (where XX is your assigned attendee
number) and touch the OK button.

22. From the Relevance Password popup, enter z and touch the OK button.

23. You should receive the Studio5000 Display Client after iTMC fails over to RDSXXP (where XX is
your assigned attendee number).

NOTE: The version of iTMC referenced in this Lab Manual (8.0.803) takes over a minute
to fail from the Primary to the Secondary Display Server. This is a bug that will be
addressed in the next release.

204 of 207
24. Touch the ScanID button in the top right corner. This will open a camera window within iTMC.

25. Scan the QR Code below (same one that we registered as MixerNew in an earlier step):

26. By scanning the QR Code, we have resolved to the MixerHMI Location, and as such will receive
the CookieDemo Display Client. It too will failover to RDSXXP (where XX is your assigned
attendee number) and the Display Client will be delivered.

NOTE: The version of iTMC referenced in this Lab Manual (8.0.803) takes over a minute
to fail from the Primary to the Secondary Display Server. This is a bug that will be
addressed in the next release.

This completes the Hands on Lab. Simply disconnect your Remote Desktop Session and it will be
reset momentarily (and you will no longer receive the automatic event notifications through e-mail
and text!) Sincerest thanks for your time and attention. We truly appreciate it!

205 of 207