In an effort to create a more unified support experience, we have moved support of our Knowledgebase to Rockwell Automation Tech Support.

If you would like to speak with one of our engineers, please Submit a Question or give us a call at the phone number here. In North America, To route your phone support request directly to a technical support engineer, call toll free 1-888-382-1583 or 1-440-646-3434, select Option 3 (Technical Support), then select Option 5 (More Options). When prompted, enter the ThinManager Direct Dial Code 201.

Difference between revisions of "Upgrade Procedure: Mirrored/Redundant Systems"

From ThinManager Knowledge Base
Jump to: navigation, search
Line 3: Line 3:
 
Upgrading ThinManager is relatively simple task where most of the heavy lifting is done via InstallShield. Upgrades can be done during on hours depending on your implementation, but there are special circumstances that must be taken into consideration before an upgrade:
 
Upgrading ThinManager is relatively simple task where most of the heavy lifting is done via InstallShield. Upgrades can be done during on hours depending on your implementation, but there are special circumstances that must be taken into consideration before an upgrade:
 
*For the purposes of this article, it is assumed that you are running a either a Mirrored or Redundant Setup and the Primary server is named "Server1" and the Secondary is "Server2".  For a standalone system, see [[Upgrade Procedure: Standalone System]]
 
*For the purposes of this article, it is assumed that you are running a either a Mirrored or Redundant Setup and the Primary server is named "Server1" and the Secondary is "Server2".  For a standalone system, see [[Upgrade Procedure: Standalone System]]
*If ThinManager and your Terminal Servers are running on the same machine (either physical or virtual) and you attempt the steps outlined in this article, <b>you may be required to reboot the ThinManager server and your thin clients will lose connection to the RDS server</b>. In this instance, it is recommended that you schedule a down time to perform the upgrade.
+
*If your ThinManager Server is also an RDS Server (either physical or virtual) and you attempt the steps outlined in this article, <b>you may be required to reboot the ThinManager/RDS server and your thin clients will lose connection to the RDS server</b>. In this instance, it is recommended that you schedule a down time to perform the upgrade.
*If ThinManager and Terminal Services are on two separate machines (either physical or virtual), thiclients may not be able to boot during the upgrade. However, <b>existing connections will remain intact</b>.
+
*If ThinManager Server and RDS Services are on two separate machines (either physical or virtual), thiclients may not be able to boot during the upgrade. However, <b>existing connections will remain intact</b>.
  
 
==Version Specific Considerations==
 
==Version Specific Considerations==

Revision as of 18:41, 28 June 2018

Overview

Upgrading ThinManager is relatively simple task where most of the heavy lifting is done via InstallShield. Upgrades can be done during on hours depending on your implementation, but there are special circumstances that must be taken into consideration before an upgrade:

  • For the purposes of this article, it is assumed that you are running a either a Mirrored or Redundant Setup and the Primary server is named "Server1" and the Secondary is "Server2". For a standalone system, see Upgrade Procedure: Standalone System
  • If your ThinManager Server is also an RDS Server (either physical or virtual) and you attempt the steps outlined in this article, you may be required to reboot the ThinManager/RDS server and your thin clients will lose connection to the RDS server. In this instance, it is recommended that you schedule a down time to perform the upgrade.
  • If ThinManager Server and RDS Services are on two separate machines (either physical or virtual), thiclients may not be able to boot during the upgrade. However, existing connections will remain intact.

Version Specific Considerations

  • If you are upgrading from 3.3 and below, you will need to create a new Master License to hold your existing Product Licenses, populate the Master License with your Product Licenses. This can be done via the Licensing Website.

See the License Activation article for in depth detail on licensing.

Upgrade Prep

It is always a good idea to backup your configuration before any system upgrade.

Configuration

Your ThinManager Configuration can be backed up from ThinManager by clicking:
Manage > Backup Configuration
and specifying a safe location for the file.

License

When upgrading Major or Minor versions of the software, the upgrade process requires that ThinManager be re-licensed for the new version. Service Packs are exempt from this licensing requirement. To begin to re-license the software you will have to contact ACP Technical Support at +1.877.239.4282 option 2 or email and request an additional activation on your license. If you choose to contact us via email, please include your Master License Number. After re-activating on the Licensing Website, you will be able to import the new license into ThinManager via Install > Licenses.
For further details on the Licensing Process, see the License Activation Article.

Installation

Required Materials:

  • Logged in as an Administrator.
  • ACP Installation Media or Downloaded Executable with applicable Service Pack.

Server 1

  • Break Synchronization:
    • From ThinManager: Manage > ThinManager Server List > Next > Uncheck Automatic Synchronization > Finish
  • Close any open ThinManager Windows.
  • Stop the ThinServer Service on Server 1 in the Services Snap-in:
    • Start > Run > Services.msc > Scroll down until you find "ThinServer", right click and stop.
  • Install ThinManager from either the media provided or from the executable located at the the ThinManager Downloads Page.
    • Verify ThinServer is installed and running via the Services Snap-in on Server 1.

Server 2

  • Stop the ThinServer Service on Server 2 in the Services Snap-in:
  • Close any open ThinManager Windows.
    • Start > Run > Services.msc > Scroll down until you find "ThinServer", right click and stop.
  • Install ThinManager from either the media provided or from the executable located at the the ThinManager Downloads Page.
    • Verify ThinServer is installed and running via the Services Snap-in on Server 2.
  • Open ThinManager and re-enable synchronization.

After synchronization is re-enabled, verify that you configuration was migrated correctly by shadowing your thin clients.