FactoryTalk View SE and ThinManager

From ThinManager Knowledge Base
Jump to: navigation, search

FactoryTalk View® Site Edition (SE) is a supervisory human machine interface (HMI) software package for enterprise solutions. It has a distributed and scalable architecture that supports distributed-server/multi-user applications, giving maximum control over information where you want it. View SE is composed of the following primary components:

  • FactoryTalk View Studio: Configuration software for developing and testing HMI applications.
  • FactoryTalk View SE Server: HMI Server that stores HMI project components and serves these components to clients.
  • FactoryTalk View SE Client: HMI Client for viewing and interacting with supervisory-level applications developed with FactoryTalk View Studio.

These components can be installed on a single server, or distributed across multiple servers. For smaller, less critical applications, these components can be located on a single server.

This is not a substitute for official FactoryTalk View SE documentation but is provided as a courtesy to our customers.

Here are some references to additional FactoryTalk View SE documentation:


Versions

This article will focus on the deployment of FactoryTalk View SE version 7.0 within a ThinManager version 7.0 environment, running within Windows Server 2008 R2.

View SE version 7.0 supports the following server class operating systems:

  • Windows Server 2008 R2 Standard Edition (with and without Service Pack 1) – 64 Bit Only
  • Windows Server 2008 R2 Enterprise Edition with Service Pack 1 – 64 Bit Only
  • Windows Server 2008 Standard Edition with Service Pack 2 – 32 Bit or 64 Bit
  • Windows Server 2003 R2 Standard Edition with Service Pack 2 – 32 Bit or 64 Bit


ThinManager 7.0 supports the following server class operating systems:

  • Windows Server 2012 R2 – 64 Bit Only
  • Windows Server 2012 – 64 Bit Only
  • Windows Server 2008 R2 with Service Pack 1 – 64 Bit Only
  • Windows Server 2008 with Service Pack 2 – 32 Bit or 64 Bit
  • Windows Server 2003 R2 with Service Pack 2 – 32 Bit or 64 Bit


Therefore, if ThinManager is to be co-located with View SE components, the following operating systems would be supported by both:

  • Windows Server 2008 R2 Standard Edition (with and without Service Pack 1) – 64 Bit Only
  • Windows Server 2008 R2 Enterprise Edition with Service Pack 1 – 64 Bit Only
  • Windows Server 2008 Standard Edition with Service Pack 2 – 32 Bit or 64 Bit
  • Windows Server 2003 R2 Standard Edition with Service Pack 2 – 32 Bit or 64 Bit

NOTE: ThinManager can also be installed on workstation operating systems like Windows XP, Windows Vista, and Windows 7.



NOTE: All steps should be performed while logged in as the local Administrator.


Reference Architectures

To be added.


NOTE: The steps that follow should be performed on each Remote Desktop/Terminal Server in your environment.


Configure Firewall, UAC and DEP

For testing purposes, it is advised to turn off the Windows Firewall, User Account Control (UAC) and Data Execution Prevention (DEP). If these security measures are required in your environment, they should be re-enabled after successful testing, preferably one at a time (in order to pinpoint any issues).

Windows Firewall

  1. The Windows Firewall can be accessed from Server Manager.
  2. From the Server Manager tree, select Server Manager | Configuration | Windows Firewall with Advanced Security.
  3. Click the Windows Firewall Properties link.
  4. Set the Firewall State to Off on the Domain Profile, Private Profile and Public Profile tabs.

UAC

  1. Open the Control Panel.
  2. Click the System and Security link.
  3. Click the Change User Account Control settings link.
  4. From the User Account Control Settings window, drag the vertical slider down to Never Notify. A restart will be required to apply the change. It can be postponed until DEP is disabled next.

DEP

  1. Within the Windows Start Menu, locate the Command Prompt shortcut. Right click it and select Run as administrator.
  2. Execute the following command, then restart the server.
bcdedit /set nx AlwaysOff

Name Resolution

Subsequent steps will utilize server names as examples instead of IP addresses. As such, name resolution is required. This can be accomplished using a Domain Name Server (DNS), the configuration of which is beyond the scope of this article. If a DNS Server is unavailable or not preferred, the HOSTS file can be utilized. The HOSTS file is a local lookup table that must exist on each server in your environment. It maps IP addresses to names and is located in the folder: c:\windows\system32\drivers\etc. To verify name resolution is functioning as expected, simply open a command prompt and attempt to ping by computer name.

Install Remote Desktop Services Role

Microsoft recommends that the Remote Desktop Services role be installed before any other applications. For example, it is not recommended to add the Remote Desktop Services role to a server after View SE has already been installed.

  1. Open Server Manager.
  2. From the Server Manager tree, select Server Manager | Roles.
  3. Click the Add Roles link.
  4. Click the Next button.
  5. Select the Remote Desktop Services role checkbox and click Next twice.
  6. Select the Remote Desktop Session Host and Remote Desktop Licensing checkboxes, then click Next twice.
  7. Select the Do not require Network Level Authentication radio button, then click Next. Network Level Authentication is only supported with WinTMC terminals.
  8. Select the Per User radio button, then click Next three times.
  9. Select the Configure a discovery scope for the license server. The "This workgroup" radio button will be selected by default if your server is in a Workgroup, which this article will assume. Click Next.
  10. Click the Install button.
  11. Once the first stage of the installation is completed, click the Close button. Restart the server if prompted to do so.
  12. When the server restarts, log back in as the local Administrator and allow the installation to finish. When finished, click the Close button.
  13. Close the Server Manager.

Activate Remote Desktop Services Licensing Server

  1. From the Windows Start Menu select, Administrative Tools | Remote Desktop Services | Remote Desktop Licensing Manager.
  2. From the RD Licensing Manager window, right click the server from the right side and select Activate Server.
  3. Click the Next button from the Activate Server Wizard.
  4. Select Automatic connection (recommended) from the drop down list. This option requires the server to have a connection to the Internet. If it does not, the Web Browser or Telephone options are valid options as well. They will require some additional manual interaction in order to activate the licensing server. Click the Next button.
  5. Enter/select the First name, Last name, Company and Country or Region fields. Click the Next button.
  6. Optionally enter the remaining fields and click the Next button.
  7. From the Completing the Activate Server Wizard window, uncheck the Start Install Licenses Wizard now checkbox.
  8. Click the Finish button. You can return to the RD Licensing Manager to add Remote Desktop Services Client Access Licenses (RDSCALs) at a later time.
  9. The Activation Status should now indicate "Activated".

Configure Remote Desktop Services

  1. Open Server Manager.

Specifying a Remote Desktop Licensing Server

  1. From the Server Manager tree, select Server Manager | Roles | RD Session Host Configuration: {SERVERNAME}.
  2. On the right hand side, locate the Licensing heading and double click the Remote Desktop license servers entry underneath it.
  3. If a warning dialog box is presented, click Close.
  4. The Licensing tab should be selected in the Properties popup. Click the Add button.
  5. Select the local server from the Known license servers list, and click the Add button to move it to the Specified license servers list. Click OK twice.

Access to Unlisted Programs

ThinManager's AppLink feature enables a user to configure a specific program to launch. This is a simple and effective way of securing a terminal by not even delivering a desktop. In order for this to work with Server 2008 R2, the initial program must either be enabled as an initial program using the RemoteApp settings, or RemoteApp must be configured to allow listed as well as unlisted programs on initial connection. To allow unlisted programs, follow these steps:

  1. From the Server Manager tree, select Server Manager | Roles | Remote Desktop Services | RemoteApp Manager.
  2. To the right of the tree, locate the RD Session Host Server Settings heading. Click the Change link.
  3. The RD Session Host Server tab should open within the RemoteApp Deployment Settings window. Click the "Allow users to start both listed and unlisted programs on initial connection" radio button in the Access to unlisted programs frame. Click OK.

Install FactoryTalk View SE Client

  1. Open the Control Panel.
  2. From the Control Panel, click the Programs link.
  3. From the Programs window, click the Install Application on Remote Desktop... link. This method should be used to install all applications on a Remote Desktop Server.
  4. From the Install Program From Floppy Disk or CD-ROM window, click the Next button.
  5. Click the Browse button and locate the View SE setup.exe application.
  6. Once the setup.exe application is selected, click the Next button.
  7. If a Security Warning is presented, click the Run button.
  8. From the FactoryTalk View Setup window, select the Site Edition Client option from the drop down list. Click the Next button.
  9. If a Security Warning is presented, click the Run button.
  10. From the FactoryTalk View Site Edition Client Setup window, click the Next button three times.
  11. Enter the User Name and Organization and click the Next button.
  12. Click the Accept all button.
  13. Click the Next button.
  14. Choose the Complete radio button and then click the Next button.
  15. Finally, click the Install button.
  16. When the installation is complete, check the "Activate products using FactoryTalk Activation" checkbox.

Configure FactoryTalk Activation

The article will assume the FactoryTalk Activation Server is located on a separate server. If it is not then you must install your View SE client licenses on each Remote Desktop Server that will run the View SE Client.

  1. If the FactoryTalk Activation Manager is not already open from the previous section, open it from the Windows Start Menu - All Programs | Rockwell Software | FactoryTalk Activation | FactoryTalk Activation Manager.
  2. Click the Manage Activations tab.
  3. Click the Update Activation Search Path link.
  4. Click the Add Server button.
  5. Enter the computer name of the FactoryTalk Activation server.
  6. Click the Up button to move the FactoryTalk Activation server to the top of the list.
  7. Click the Save button.
  8. Click the Refresh Activations button. The installed activations on the FactoryTalk Activation server specified should populate the Available activations list box.
  9. Close the FactoryTalk Activation Manager.
  10. If this was the continuation of the FactoryTalk View SE Client install, you will be presented with a Restart confirmation dialog box. Click No for now.
  11. Click the Finish button on the Finish Admin Install window. Then Restart the server.

NOTE: It is very important to keep the View SE servers at the same patch level. So if you are applying a patch rollup to one server, make sure you apply that same patch rollup to all servers (i.e.: HMI Servers as well as Remote Desktop Server running View SE Client).


Add View SE Terminal Servers to the FactoryTalk Directory

This article will assume that the FactoryTalk Directory is on a server separate from the Remote Desktop Server (recommended). As such, the steps that follow demonstrate how to point the Remote Desktop Server to a separate server that is hosting the FactoryTalk Directory.

  1. From the Windows Start Menu, select All Programs | Rockwell Software | FactoryTalk Tools | Specify FactoryTalk Directory Location.
  2. From the FactoryTalk Directory Server Location Utility, click the ellipsis button.
  3. Enter the credentials for your local Administrator account (on the server you are currently on) and click the OK button.
  4. From the FactoryTalk Directory Server Configuration window, select the Remote Server radio button.
  5. In the Remote Server text box, enter the name of the remote computer on which the FactoryTalk Directory is installed. Click the OK button.
  6. Click the OK button again, and yet again when the notification of restart dialog is presented.
  7. Enter the credentials for your local Administrator account (these are the credentials for the local Administrator account on the remote server where the FactoryTalk Directory resides). Click the OK button.
  8. Restart the server.

Creation of View SE Client File(s)

  1. From the Windows Start Menu, select All Programs | Rockwell Software | FactoryTalk View | FactoryTalk View Site Edition Client.
  2. From the FactoryTalk View SE Client Wizard window, click the New button.
  3. On the FactoryTalk View SE Client Configuration Name page, enter the name of the new configuration file. Click the Next button.
  4. From the FactoryTalk View SE Client Application Type page, select the Network Distributed radio button. Click the Next button.
  5. From the FactoryTalk View SE Client Application Name page, select the desired application from the application drop down list.
  6. Select English from the language drop down list. Click the Next button.
  7. From the FactoryTalk View SE Components page, click the ellipsis button for the Area.
  8. From the Area Browser window, click the area in which the desired HMI Server resides. Click the OK button.
  9. Select the desired components and then click the Next button.
  10. Select the desired Window Properties for the View SE client and click the Next button.
  11. Choose to enable/disable Auto Logout and click the Next button.
  12. Select the "Save configuration and open FactoryTalk View SE Client now" radio button and click the Finish button. It is always a good test to launch the newly created SE Client file to ensure it displays properly.

NOTE: Each client file created needs to exist in the same place on all Remote Desktop Servers where the View SE application could be run.


ThinManager Installation

ThinManager will request a local Administrator account during its installation.

ThinManager Local Administrator Account

  1. Open Server Manager.
  2. From the Server Manager tree, select Server Manager | Configuration | Local Users and Groups.
  3. Right click the Users folder and select New User.
  4. From the New User window, enter thinman as the username and an appropriate password.
  5. Uncheck the "User must change password at next logon" checkbox.
  6. Check the "Password never expires" checkbox.
  7. Click the Create button, followed by the Close button.
  8. Right click the new thinman user and select Properties.
  9. Select the Member Of tab.
  10. Click the Add button.
  11. Enter Administrators in the text box. Click the OK button.
  12. Click the OK button.

NOTE: The same local account should be created on all the Remote Desktop Servers utilized by ThinManager. This will enable ThinManager to properly communicate with all of the Remote Desktop Servers and provide the ability to manage the resulting Remote Desktop sessions from within ThinManager (i.e.: Reset Sessions, etc.)


Installation

  1. Open the Control Panel.
  2. Click the Programs link.
  3. Click the "Install Application on Remote Desktop..." link.
  4. From the "Install Program From Floppy Disk or CD-ROM" window, click the Next button.
  5. From the "Run Installation Program" window, click the Browse button.
  6. Navigate to the ThinManager install and click the Open button, followed by the Next button.
  7. If a File Security Warning is generated, click the Run button.
  8. From the ThinManager installation wizard, click the Install button to install the Visual C++ 2010 SP1 Redistributable Package.
  9. Once the Visual C++ Redistributable is installed, click the Next button.
  10. After reading the entire licensing agreement, click the Yes button to accept its terms.
  11. From the Applications to Install page of the ThinManager installation wizard, accept the defaults and click the Next button.
  12. From the Select Directory to Install to page of the ThinManager installation wizard, click the Next button.
  13. From the Login for ThinServer Service page of the ThinManager installation wizard, enter the thinman user credentials created in the previous section. Click the Next button.
  14. Click the Finish button.
  15. After several seconds, the Finish button will become available on the Finish Admin Install window. Once it does, click it.

ThinManager Activation

  1. From the Windows Start Menu, select All Programs | ACP | ThinManager.
  2. Upon first launching ThinManager, a message box indicating there are no valid terminal connection licenses will appear. Click OK.
  3. If you do not already have a license, a fully functional 30 day demo can be downloaded from www.thinmanager.com by clicking on the License Activation link, followed by the Demo Code button.
  4. Once you have a valid product license key, click the Windows Start Menu and select All Programs | Internet Explorer (or your preferred browser).
  5. Enter www.thinmanager.com in the IE URL bar.
  6. Click the License Activation link.
  7. If you do not have ThinManager activation account, click the New User link and follow the prompts.
  8. Once finished, click the Login button.
  9. Click the Create Master License link.
  10. Fill in the master license fields and click the Submit button. Pay special attention to the License Redundancy radio button selection and choose the correct redundancy type based on the license purchased.
  11. Click the Add Product License link.
  12. Click the newly created Master License Number link.
  13. Enter the Product License Number in the text box and click the Submit button.
  14. Click the Activate link.
  15. Once again, click the Master License Number link.
  16. To acquire the Installation ID, return to ThinManager, click the Install ribbon bar, followed by the Licenses toolbar icon.
  17. The Installation ID will be listed at the bottom and can be copied and pasted back to Internet Explorer. If you are activating either a Mirrored or Full Redundancy license, you will also need to provide the Secondary Installation ID at this time, which can be acquired in the same way, but from the server that will act as the Secondary ThinManager.
  18. Click the Submit button.
  19. If successful, a license file download link will be presented. Click it to download the license file.
  20. To install the license file, copy it to a location on the server where ThinManager has been installed.
  21. If not already open, click the Install ribbon bar, followed by the Licenses toolbar icon.
  22. Click the Install License button.
  23. Browse to the location of the license file just downloaded and click the Open button.
  24. If successful, a License successfully installed message box should appear. Click the OK button.
  25. Click the Done button.

NOTE: The Installation ID that is shown on the Licensing window is based on the MAC address of the machine. If the MAC address changes for any reason, the license will require re-activation. As an alternative, you may consider using an Installation ID that is generated based on the Operating System (OS). The OS Installation ID can be viewed by clicking the Show All button on the Licensing window. In practice, it has been noted that some Stratus servers sometimes report a different MAC address upon restart. When this happens, re-activation is required. To avoid this, the OS Installation ID can be used. In order to ensure the OS Installation ID is unique across cloned images, it is important that Microsoft's Sysprep is performed on each cloned image, which will ensure a unique SID is generated.


ThinManager Configuration

Automatic Synchronization

If your environment utilizes Mirrored or Full Redundancy ThinManager licensing, it is recommended that the configurations between these redundant partners be automatically synchronized. If you are not using either Mirrored or Full Redundancy ThinManager licensing, this section can be skipped.

  1. From ThinManager, select the Manage ribbon bar.
  2. Click the ThinManager Server List toolbar icon. This will launch the ThinManager Server List Wizard.
  3. Click the Next button on the first page of the wizard.
  4. Check the Automatic Synchronization checkbox.
  5. Click the Next button.
  6. From the Auto-synchronization Configuration page of the ThinManager Server List Wizard, click the Edit button for the Primary ThinManager Server.
  7. Enter in the computer name of the Primary ThinManager Server in the ThinManager Server text box.
  8. Click the Discover button. If ThinManager can resolve the name to its IP address, the server's IP address should be populated in the ThinManager Server IP text box.
  9. Click the OK button.
  10. From the Auto-synchronization Configuration page of the ThinManager Server List Wizard, click the Edit button for the Secondary ThinManager Server.
  11. Enter in the computer name of the Secondary ThinManager Server in the ThinManager Server text box.
  12. Click the Discover button. If ThinManager can resolve the name to its IP address, the server's IP address should be populated in the ThinManager Server IP text box.
  13. Click the OK button.
  14. Click the Finish button.
  15. The synchronization status can be viewed by:
    1. Click the ThinManager icon from the ThinManager tree on the left hand side of ThinManager.
    2. Select the Primary ThinManager Server from the ThinManager tree.
    3. Click the Synchronization tab on the right hand side.
    4. The synchronization state should indicate Synchronized.

Display Servers

Within ThinManager, Display Servers can be viewed as the sources of the content to be applied to your ThinManager terminals. Display Servers are either Terminal Servers or Cameras. Each Terminal Server that will be utilized within your ThinManager environment must be added as a Display Server to ThinManager.

  1. From ThinManager, click the Display Servers icon on the ThinManager tree toolbar. Depending on the state of the button bar, either collapsed or expanded, it may either be an icon (if the button bar is collapsed), or a button unto itself (if the button bar is expanded).
  2. In the Display Servers tree, right click the Terminal Servers item and select Add Terminal Server.
  3. From the Introduction page of the Terminal Server Wizard, click the Next button.
  4. From the Terminal Server Name page of the Terminal Server Wizard, enter the name of the Terminal Server you are adding into the Terminal Server Name text box.
  5. Click the Discover button and ThinManager will attempt to resolve the name to an IP address. If successful, the IP address will be filled in the Terminal Server IP text box.
  6. In the Log In Information section, enter a set of credentials that is a member of the local Administrators group on the terminal server being added. We recommend using the "thinman" account created in the section: ThinManager Local Administrator Account.
  7. Click the Next button.
  8. From the Terminal Server Capabilities page of the Terminal Server Wizard, ensure that Microsoft Remote Desktop Protocol is checked.
  9. You may also consider checking the "Available for Display Clients using SmartSession". See the note below describing SmartSession.
  10. From the Data Gathering page of the Terminal Server Wizard, accept the defaults and click the Finish button.
  11. Repeat these steps for each additional Terminal Server in your environment.

NOTE: SmartSession will automatically launch new Terminal Server sessions on the most available terminal server when a terminal boots up. It bases this on CPU utilization, RAM utilization and currently active sessions. The weighting of these factors is configurable. SmartSession also serializes connections to terminal servers, thereby preventing a boot storm when multiple terminals are attempting to boot simultaneously.


Display Clients

As noted in the previous section, Display Servers are the sources of the content managed by ThinManager, while Display Clients are the actual content running from the Display Servers. The example below will show how to configure the InstantFizz demo View SE application as a Display Client. This example will demonstrate how to configure the AppLink feature. Once a Display Client is created, it can be applied and consumed by a thin client terminal, a mobile device using the iTMC iOS application, or a PC using the WinTMC application. In order to enable this Display Client to be utilized by any terminal type (thin client, iOS device via iTMC or PC via WinTMC), we will create a Windows Batch file to launch the View SE application.

  1. From the Windows Start Menu, select All Programs | Accessories | Notepad.
  2. In the Notepad document, enter the following:
    start "" "c:\Program Files (x86)\Rockwell Software\RSView Enterprise\DisplayClient.exe" "c:\Users\Public\Documents\RSView Enterprise\SE\Client\InstantFizz.cli"
  3. Click the File menu item, followed by the Save As menu item.
  4. Navigate to the location where you would like to save the batch file. In this example: "c:\Users\Public\Documents\RSView Enterprise\SE\Client\InstantFizz.bat".
  5. Click the Save button.
  6. Close Notepad.
  7. As a test, launch the newly created InstantFizz.bat file to ensure it opens the application properly.
  8. After confirmation, hit ALT-F4 on the keyboard to close the application.
  9. From ThinManager, click the Display Client button bar from the ThinManager Tree toolbar.
  10. From the Display Client tree, right click the Terminal Services item and select Add Display Client.
  11. On the Client Name page of the Display Client wizard, enter InstantFizz in the Client Name field and click the Next button.
  12. On the Display Client Options page of the Display Client Wizard, accept the defaults and click the Next button.
  13. If your activation includes a Relevance license, you will be presented with the Relevance Options page of the Display Client Wizard. Accept the defaults and click the Next button.
  14. From the Terminal Services Display Client Type page of the Display Client Wizard, accept the defaults and click the Next button.
  15. From the Terminal Services and Workstation Options page of the Display Client Wizard, check the Application Link check box. Click the Next button (only the Allow Auto-Login checkbox should also be checked in this example).
  16. From the Display Client Members page of the Display Client Wizard, first select the desired terminal server on which the Display Client is to run from the Available Terminal Servers list box.
  17. With the desired terminal server selected, click the right arrow button to move it from the Available Terminal Servers list to the Selected Terminal Servers list. Click the Next button.
  18. Since we clicked the Application Link check box earlier in the wizard, we are now presented with the AppLink page of the Display Client Wizard. Click the Browse button.
  19. Explore to the location of the InstantFizz.bat batch file we created earlier in this example. Select it and click the Open the button.
  20. The path to the InstantFizz.bat file should be displayed in the Program Path and Filename field. Click the Finish button.

NOTE: The same batch filename and path needs to be created on each Remote Desktop Server in your environment from where the Display Client could be run.



NOTE: It should be noted that a batch file like this is not always required. In fact, it is probably the exception when it is used. In this case, it was utilized because the path to launch the InstantFizz.cli file has a space between it and the DisplayClient.exe path. This alone could be handled by the AppLink Path specification in the Display Client Wizard, but the location of the double quotes in this compound path generates different results depending on whether the Display Client is deployed to a terminal, a PC running WinTMC, or an iPad running iTMC. (i.e.: placing double quotes around each path with a space between them will work for a terminal, but not for a PC running WinTMC). If you are only using one of these platforms in your environment, you do not have to use the batch file approach. Similarly, if your Display Client does not require any Command Line options, and you have a single path (i.e.: you are just delivering “c:\Windows\System32\calc.exe”), then a batch file is not required regardless of the combination of terminal types you are using.


Terminals

With a Display Client created, it can now be applied to a terminal. ThinManager supports 2 types of thin client hardware. Both terminal types support all of the ThinManager feature set.

  1. ThinManager Ready - purchased from our hardware partners. These terminals have the ThinManager BIOS extension image already installed in their BIOS, making them ThinManager Ready right out of the box. These terminals will have an ACP sticker applied to them from the manufacturer.
  2. ThinManager Compatible - are hardware compatible with ThinManager and can perform a PXE boot. ThinManager can be configured to act as a PXE Server. This allows ThinManager to deliver its firmware, or operating system, over the network to a PXE Client device. If you would like to know if a specific terminal has been tested by ACP, please consult the Supported Hardware article. It is important to note that if your device is not listed, there is still a good chance that it may be compatible. You may need to specify PXE as a boot option in the device’s BIOS.

An iPad can function as a ThinManager terminal by downloading the free iTMC application from the Apple App Store. A PC can also function as a ThinManager terminal by installing the WinTMC, Windows-based application. The WinTMC application is included in the ThinManager installation media, or can be downloaded from www.thinmanager.com.

ThinManager Compatible Terminal

The following example will demonstrate how to configure a ThinManager Compatible terminal. The terminal will be configured to automatically login to the terminal server(s). As such, Windows credentials must first be created on the terminal server(s).

  1. Open Server Manager.
  2. From the Server Manager tree, select Server Manager | Configuration | Local Users and Groups.
  3. Right click the Users folder and select New User.
  4. Enter the new user credentials.
  5. Uncheck the "User must change password at next logon" checkbox.
  6. Check the "Password never expires" checkbox.
  7. Click the Create button.
  8. Click the Close button.
  9. Right click the newly created user and click the Properties menu item.
  10. From the User Properties window, select the Member Of tab.
  11. Click the Add button.
  12. Enter "Remote Desktop Users" (without the quotes) in the text box. Click the OK button.
  13. With the Remote Desktop Users group added to the Member of list box, click the OK button. Without a domain controller, the same user credentials need to be created on each terminal server in your environment.
  14. Close Server Manager.
  15. From ThinManager, click the Terminals button bar.
  16. Right click the Terminals tree item.
  17. Click Add Terminal from the context menu.
  18. From the Terminal Name page of the Terminal Configuration Wizard, enter the desired name as the Terminal Name. Click the Next button.
  19. From the Terminal Hardware page of the Terminal Configuration Wizard, select GENERIC from the Make / OEM drop down list.
  20. Select PXE from the Model drop down list. Click the Next button.
  21. From the Terminal Options page of the Terminal Configuration Wizard, accept the defaults and click the Next button.
  22. From the Terminal Mode Selection page of the Terminal Configuration Wizard, accept the defaults and click the Next button.
  23. From the Display Client Selection page of the Terminal Configuration Wizard, click the InstantFizz Display Client in the Available Display Clients list box to select it.
  24. Click the right arrow button to move the InstantFizz Display Client item from the Available Display Clients to the Selected Display Clients.
  25. With the InstantFizz Display Client in the Selected Display Clients list, click the Next button.
  26. From the Terminal Interface Options page of the Terminal Configuration Wizard, accept the defaults and click the Next button.
  27. From the Hotkey Configuration page of the Terminal Configuration Wizard, accept the defaults and click the Next button.
  28. From the Log In Information page of the Terminal Configuration Wizard, enter the Windows credentials that will be used by this terminal to automatically login to the terminal server(s). If no credentials are provided, the terminal user will be prompted to enter credentials. Click the Next button.
  29. Select the video Resolution, Color Depth and Refresh Rate for the terminal. Click the Next button.
  30. From the Module Selection page of the Terminal Configuration Wizard, click the Next button.
  31. From the Monitoring Configuration of the Terminal Configuration Wizard, accept the defaults and click the Finish button.
  32. The new terminal should now be added to the Terminals tree. It will show a red icon next to it, since it is not powered on yet.
PXE Server

Since we are configuring a PXE terminal, the ThinManager PXE Server must first be configured before attempting to power on the terminal.

  1. From ThinManager, click the Manage ribbon bar.
  2. From the Manage ribbon bar, click the PXE Server icon.
  3. From the PXE Server Configuration page of the PXE Server Wizard, check the Enable PXE Server checkbox. Click the Next button.
  4. From the Network Interface Configuration page of the PXE Server Wizard, first select the correct network interface card to use on the primary ThinManager server. If your server has multiple network interface cards, make sure you select the correct one. The associated IP address of the selected network interface will be displayed below.
  5. If ThinManager is configured for automatic synchronization between Primary and Secondary, the network interface for the Secondary must also be selected. Again, ensure the correct network interface is selected the Secondary.
  6. For PXE Server Mode, select the "Not using standard DHCP server radio button. This mode should be selected if you do not have an existing DHCP server that you want to use. In this mode, ThinManager will act as a DHCP server for your PXE clients. Click the Next button.
  7. Since ThinManager will act as the DHCP Server in our configuration, an IP address range must be configured. Click the Add button from the IP Address Range Configuration page of the PXE Server Wizard.
  8. From the IP Address Range window, enter in the Starting IP Address, Ending IP Address, Subnet Mask and Router IP Address.
  9. With the new IP Address range added, click the Finish button.
  10. Power up the terminal. It should receive an IP address via the PXE Server's DHCP Server, as well as the ThinManager firmware via TFTP (the progress bar will fill from left to right).
  11. Since the terminal has not been associated with a terminal configuration previously, the terminal configuration selection menu will appear at the terminal. Select the previously created terminal configuration and hit enter. The terminal should then receive its configuration and launch its configured Display Clients.

NOTE: It is recommended that only one PXE Server reside on a single subnet. If this is not possible, please refer to the Multiple PXE Servers section.



NOTE: The PXE Server Modes section provides additional details on the PXE Server Mode options.


Auto Login to FactoryTalk Directory

In order to automatically login to the View SE application, the Windows account that is used to automatically log the terminal in to the terminal server must be added to the FactoryTalk security model. The example that follows assumes your terminal servers are in a workgroup.

  1. From each terminal server, click on the Windows Start menu and select All Programs | Rockwell Software | FactoryTalk Administration Console.
  2. When presented with the Select FactoryTalk Directory window, select the Network radio button and click the OK button.
  3. If prompted for a login, enter the credentials for the local Administrator account on the server where the FactoryTalk Directory resides.
  4. From the FactoryTalk Administration Console, select the following from the tree Network | System | Computers and Groups.
  5. Right click the Computers folder and select New Computer.
  6. From the New Computer window, enter the terminal name that you configured in the Terminals section as the Computer name here. The Description is optional. Click the OK button.
  7. From the the FactoryTalk Administration Console tree, select Network | System | Users and Groups.
  8. Right click the Users folder and select New | Windows-Linked User.
  9. From the New Windows-Linked User window, click the Add button.
  10. From the Selec-t Users window, enter the Windows user created for the terminal in the previous section. Click the OK button.
  11. With the Windows-Linked User in the list box, click the OK button.
  12. To see the result of the changes, it is necessary to reset the terminal server session running View SE on the terminal. Open ThinManager.
  13. From ThinManager, select the Display Servers button bar from the ThinManager tree toolbar.
  14. From the Display Servers tree, select Display Servers | Terminal Servers.
  15. Select the terminal server in the tree.
  16. Click the Sessions tab on the right hand side.
  17. Locate the session that is running the InstantFizz Display Client. Right click it and select Reset Session.
  18. The session should restart and the InstantFizz display client should launch and automatically login to FactoryTalk Security.

NOTE: Adding the terminal name as a Computer account is required because of the FactoryTalk Security Policy called "Require computer accounts for all client machines", which is enabled by default.


RSView32

This example configuration will demonstrate how virtualized workstations can be utilized to deliver content to a terminal. ThinManager is very much a transitionary technology that can support mixed use environments that include thin clients, mobile devices and PCs. This use case describes how a legacy PC running RSView32 on Windows XP can be virtualized and then its content delivered to a thin client. The steps that follow assume that the Windows XP image has already been virtualized and has been added to a VMWare ESXi host that has been registered with ThinManager. In addition, it is assumed that Remote Desktop has been enabled on the Windows XP virtual machine.

  1. From ThinManager, click the Display Clients button bar from the ThinManager tree toolbar.
  2. From the Display Client tree, right click Workstation and select Add Display Client.
  3. From the Client Name page of the Display Client Wizard, enter the desired name in the Client Name text box. Click the Next button.
  4. From the Display Client Options page of the Display Client Wizard, check the Start Virtual Machine if necessary check box. Click the Next button.
  5. If you have a Relevance license activated, the Relevance Options page of the Display Client Wizard will be presented. Click the Next button.
  6. From the Terminal Services and Workstation Options page of the Display Client Wizard, check the Application Link check box, and leave the Allow Auto-Login checkbox checked.
  7. From the AppLink page of the Display Client Wizard, enter the path to the RSView32 application. In this example, enter the following:
    "c:\Program Files\Rockwell Software\RSView\rsview32.exe" "c:\Program Files\Rockwell Software\Samples\RSView\SAMPLES\samples.rsv" /r
  8. Click the Finish button.
  9. With the new Workstation Display Client created, it can now be added to a terminal. Click the Terminals button bar from the ThinManager tree toolbar.
  10. Double click the desired terminal to which you would like to apply the new Workstation Display Client. This will launch the Terminal Configuration Wizard.
  11. From the Terminal Name page of the Terminal Configuration Wizard, click the Next button.
  12. From the Terminal Hardware page of the Terminal Configuration Wizard, click the Next button.
  13. From the Terminal Options page of the Terminal Configuration Wizard, click the Next button.
  14. From the Terminal Mode Selection page of the Terminal Configuration Wizard, click the Next button.
  15. From the Display Client Selection page of the Terminal Configuration Wizard, select the new Workstation Display Client from the Available Display Clients list box.
  16. Click the Right Arrow button to move the new Workstation Display Client from the Available Display Clients list box to the Selected Display Clients list box. Click the Next button.
  17. Since a Workstation Display Client was added to this Terminal, the Complete the Workstation Display Client Configuration page is displayed. And since the Workstation we are going to use is hosted on an ESXi host that has been added to ThinManager’s vCenter Servers tab, the Add Virtual Workstation button can be clicked to browse to the desired virtual workstation.
  18. From the Add Virtual Workstation dialog box, select the item that is hosting the desired Windows XP image. Click the Add button.
  19. From the Complete the Workstation Display Client Configuration page of the Terminal Configuration Wizard, click the Finish button.
  20. If the terminal is already powered up (indicated by a green terminal icon), right click it and select Restart Terminal to apply the terminal changes.
  21. Once the new configuration has been applied to the terminal, the RSView32 Workstation Display Client should now be displayed.

NOTE: Because the Allow Auto-Login option was checked for the Workstation Display Client, it will attempt to automatically login to the Windows XP virtual machine using the credentials defined for the terminal (in the Log In Information page of the Terminal Configuration Wizard). To work properly, these credentials must be valid on the Windows XP virtual machine. If you would prefer to use a different set of credentials for this Workstation Display Client, you can alter this behavior by clicking the Override button in Step 16 above.



NOTE: Workstation Operating Systems like Windows XP Pro, Windows 7 Pro and Windows 8 Pro all support remote desktop, but unlike a server class OS with the Remote Desktop Services role enabled, only a single connection can be made to these operating systems. Therefore a Workstation Display Client can only be applied to a single terminal for this reason.


Multiple Monitors within Same Session

Multiple View SE instances and applications can be launched within the same session while only consuming a single View SE license. With multiple monitors connected, it is desirable to automatically locate each View SE instance to a specific monitor. ThinManager’s MultiMonitor feature makes managing the content deployed to multiple monitors simple; however, MultiMonitor depends on creating unique sessions for each of the applications. For View SE, this would require multiple View SE licenses. Therefore, MultiMonitor is not a solution for this scenario. In order to position applications across multiple monitors within the same session, an additional tool is required. As such, this configuration example utilizes a tool from Realtime Soft called UltraMon along with ThinManager. With UltraMon, it is possible to position multiple instances of View SE within the same session. Please read the comments within the script to get a better understanding of what the script is doing so that you can make the proper modifications for your environment.


NOTE: This solution will only work on Terminal Servers that support Microsoft Extended Desktop. At the time the script referenced below was created, that includes Server 2008 R2, Server 2012 and Server 2012 R2.


  1. On the terminal server, download and install the latest version of UltraMon. Be sure to use the Control Panel, and the "Install Application in Remote Desktop..." utility for the install.
  2. Next, a VBScript file needs to be created. Click the Windows Start Menu and select All Programs | Accessories | Notepad.
  3. Copy and paste the VBScript snippet below into the Notepad window.
  4. Click the File menu item, then the Save As menu item.
  5. Name the file Launch.vbs.
  6. Select All Files (*.*) from the Save as type drop down list. If this step is not taken, the file will be saved as Launch.vbs.txt, which is not correct.
  7. Click the Save button.
  8. Close Notepad.
  9. From ThinManager, click the Display Clients button bar from the ThinManager tree toolbar.
  10. From the Display Client tree, right click the Terminal Services item and select Add Display Client.
  11. On the Client Name page of the Display Client wizard, enter the desired client name in the Client Name field and click the Next button.
  12. On the Display Client Options page of the Display Client Wizard, accept the defaults and click the Next button.
  13. If your activation includes a Relevance license, you will be presented with the Relevance Options page of the Display Client Wizard. Accept the defaults and click the Next button.
  14. From the Terminal Services Display Client Type page of the Display Client Wizard, accept the defaults and click the Next button.
  15. From the Terminal Services and Workstation Options page of the Display Client Wizard, check the Application Link check box. Leave the Allow Auto-Login checkbox checked. Click the Next button.
  16. From the Display Client Members page of the Display Client Wizard, select the desired terminal server where the Display Client will run.
  17. With the desired terminal server selected, click the right arrow button to move it from the Available Terminal Servers list to the Selected Terminal Servers list. Click the Next button.
  18. Since the Application Link check box was checked earlier in the wizard, we are now presented with the AppLink page of the Display Client Wizard. Enter the following in the Program Path and Filename text box:
    "c:\windows\system32\wscript.exe c:\RAOTM\Launch.vbs"
  19. Replace c:\RAOTM with your path to the Launch.vbs file. Click the Finish button.
  20. With the new UltraMon Display Client created, it now needs to be applied to a multi-monitor capable terminal. Click the Terminals toolbar from the ThinManager tree toolbar.
  21. Double click the terminal to which the new Display Client will be applied. This will launch the Terminal Configuration Wizard.
  22. From the Terminal Name page of the Terminal Configuration Wizard, click the Next button.
  23. From the Terminal Hardware page of the Terminal Configuration Wizard, click the Next button.
  24. From the Terminal Options page of the Terminal Configuration Wizard, click the Next button.
  25. From the Terminal Mode Selection page of the Terminal Configuration Wizard, click the Next button. Do not check Enable MultiMonitor.
  26. From the Display Client Selection page of the Terminal Configuration Wizard, remove any existing Display Clients on the terminal by selecting them from the Selected Display Clients list box and clicking the left arrow.
  27. Select the newly created Display Client from the Available Display Clients list box and click the right arrow to move it to the Selected Display Clients list box.
  28. Click the Finish button.
  29. Right click the terminal and select Restart Terminal to apply the changes.
' The purpose of this VBScript is to demonstrate one way to programmatically position 
' applications on multiple monitors using a single, spanned desktop.  It utilizes an application
' called UltraMon (www.realtimesoft.com/ultramon).  This script was tested with the x64
' version of UltraMon (v3.2.2) on a [[Windows Server 2008 R2]] with SP1 image.  

' The use case of this VBScript is using ACP's ThinManager with Rockwell's View SE and
' a multi-monitor thin client to launch multiple instances of View SE within the same
' terminal server/remote desktop session, and position each of those instances on
' different monitors at startup.  Rockwell's licensing model supports launching multiple
' instances of View SE within the same session while only consuming a single View SE
' client license.

' There is a timing element to the script.  The WScript.Sleep command is used to pause
' the execution of the script for a long enough time period to allow View SE to fully
' launch.  This script uses a 40 second delay, but this may need to change in other
' environments.

' To utilize this script on a [[multimonitor]] thin client in ThinManager:
' 1. Create a [[Display Client]] with Application Link checked.
' 2. Specify a Terminal Server with UltraMon installed on it for the new [[Display Client]].
' 3. For the Application Link Program Path and Filename, specify:
'    c:\windows\system32\wscript.exe c:\RAOTM\Launch.vbs
'    where c:\RAOTM\Launch.vbs is the path and filename to this VBScript.
' 4. Create a new Terminal with [[MultiMonitor]] enabled.
' 5. Specify the number of monitors to use (2 in this example).
' 6. Choose a Spanned screen layout (so we have 1 logical monitor as in this example).
' 7. Apply the new [[Display Client]] to the screen.
' 8. On the Screen Options page, click the Screen Option button.
' 9. Check the use Microsoft Extended Desktop.

' NOTE: This solution will only work on Terminal Servers that support Microsoft Extended
' Desktop.  At the time this script was created, that includes Server 2008 R2, Server
' 2012 and [[Server 2012]] R2.

' Set constants for use in script.
Const SHOWSTATE_HIDDEN = 0
Const SHOWSTATE_MINIMIZED = 1
Const SHOWSTATE_NORMAL = 2
Const SHOWSTATE_MAXIMIZED = 3
Const SHOWSTATE_MAXIMIZED_DESKTOP = 4

Const ViewSEPath = "c:\Program Files (x86)\Rockwell Software\RSView Enterprise\DisplayClient.exe"

' Paths to CLI files to launch.  Only the first 2 are used in this example.
Const ViewSECLIPath_1 = "c:\RAOTM\InstantFizz\IF_CLIENT1.cli"
Const ViewSECLIPath_2 = "c:\RAOTM\InstantFizz\IF_CLIENT2.cli"
Const ViewSECLIPath_3 = "c:\RAOTM\InstantFizz\IF_CLIENT3.cli"
Const ViewSECLIPath_4 = "c:\RAOTM\InstantFizz\IF_CLIENT4.cli"
Const ViewSECLIPath_5 = "c:\RAOTM\InstantFizz\IF_CLIENT5.cli"

' Instantiate UltraMon objects.
Set util = CreateObject( "UltraMon.Utility" )
Set wnd = CreateObject( "UltraMon.Window" )

' Launch first instance of View SE Client.
If util.Run( ViewSEPath & " " & ViewSECLIPath_1 ) = True Then

	' Give the application time to fully launch.  May have to experiment here.
	' Example here provides a 40 second delay.
	WScript.Sleep 40000

	' Determine the window handle of the newly launched View SE client.
	If wnd.GetAppMainWindow( util.ProcessID, 5000 ) = True Then

		' Set the monitor number and maximize it.
		wnd.Monitor = 1
		wnd.ShowState = SHOWSTATE_MAXIMIZED
		wnd.ApplyChanges 0

	End If

End If

' Launch second instance of View SE Client.
If util.Run( ViewSEPath & " " & ViewSECLIPath_2 ) = True Then


	' Give the application time to fully launch.  May have to experiment here.
	' Example here provides a 40 second delay.
	WScript.Sleep 40000

	' Determine the window handle of the newly launched View SE client.
	If wnd.GetAppMainWindow( util.ProcessID, 0 ) = True Then

		' Set the monitor number and maximize it.
		wnd.Monitor = 2
		wnd.ShowState = SHOWSTATE_MAXIMIZED
		wnd.ApplyChanges 0

	End If

End If

' #############################################
' Uncomment this block to enable a 3rd monitor.
' #############################################

' Launch third instance of View SE Client.
'If util.Run( ViewSEPath & " " & ViewSECLIPath_3 ) = True Then

	' Give the application time to fully launch.  May have to experiment here.
	' Example here provides a 40 second delay.
	'WScript.Sleep 40000

	' Determine the window handle of the newly launched View SE client.
	'If wnd.GetAppMainWindow( util.ProcessID, 0 ) = True Then

		' Set the monitor number and maximize it.
		'wnd.Monitor = 3
		'wnd.ShowState = SHOWSTATE_MAXIMIZED
		'wnd.ApplyChanges 0

	'End If

'End If

' #############################################
' Uncomment this block to enable a 4th monitor.
' #############################################

' Launch fourth instance of View SE Client.
'If util.Run( ViewSEPath & " " & ViewSECLIPath_4 ) = True Then

	' Give the application time to fully launch.  May have to experiment here.
	' Example here provides a 40 second delay.
	'WScript.Sleep 40000

	' Determine the window handle of the newly launched View SE client.
	'If wnd.GetAppMainWindow( util.ProcessID, 0 ) = True Then

		' Set the monitor number and maximize it.
		'wnd.Monitor = 4
		'wnd.ShowState = SHOWSTATE_MAXIMIZED
		'wnd.ApplyChanges 0

	'End If

'End If

' #############################################
' Uncomment this block to enable a 5th monitor.
' #############################################

' Launch fifth instance of View SE Client.
'If util.Run( ViewSEPath & " " & ViewSECLIPath_5 ) = True Then

	' Give the application time to fully launch.  May have to experiment here.
	' Example here provides a 40 second delay.
	'WScript.Sleep 40000

	' Determine the window handle of the newly launched View SE client.
	'If wnd.GetAppMainWindow( util.ProcessID, 0 ) = True Then

		' Set the monitor number and maximize it.
		'wnd.Monitor = 5
		'wnd.ShowState = SHOWSTATE_MAXIMIZED
		'wnd.ApplyChanges 0

	'End If

'End If

' Clean up.
Set wnd = Nothing
Set util = Nothing

Stratix Switches

If you are using Allen Bradley Stratix managed switches in your environment, you may need to experiment with the Ethernet port profiles assigned to your terminal connections as well as your terminal servers. In one case, assigning the Desktop for Automation profile to a PXE client and assigning None to the terminal server ports worked. In another case, where the Stratix switch was acting as a DHCP Server, the option for DHCP Snooping on the switch had to be disabled (to use the Stratix switch as a DHCP Server, the PXE Server configuration within ThinManager must be set to Use standard DHCP server). If you are having trouble booting a thin client (PXE or otherwise) and you have managed Stratix switches in your environment, you may want to use a standard unmanaged switch just to verify that the your ThinManager configuration is correct. If you can boot the terminal using an unmanaged switch, then you can focus on troubleshooting the Stratix switch configuration.