Contents
In-place upgrade of Tachyon
This scenario is for upgrading from an older version of Tachyon.
If your current Tachyon server already has ActiveEfficiency Server installed then please also read the following according to what it is currently used for.
- In-place upgrade of ActiveEfficiency Server for Nomad
- In-place upgrade of ActiveEfficiency Server for Shopping
Tachyon Setup is used to upgrade the following versions of Tachyon and its applications to Tachyon Platform 5.2.
Version | Features |
---|---|
Tachyon 5.0, 5.1 | Real-time and inventory features. Explorer, Guaranteed State, Patch Success, Application Migration, ActiveEfficiency, AppClarity, Experience. |
Tachyon 4.1 | Real-time and inventory features. Explorer, Guaranteed State, Patch Success, Application Migration, ActiveEfficiency. |
Tachyon 4.0 | Real-time and inventory features. Explorer, Guaranteed State, Patch Success. |
Tachyon 3.3 | Real-time features and Tachyon Explorer application. |
Tachyon Setup assumes you will keep existing applications when upgrading and optionally install additional applications. However, your Tachyon license ultimately determines which applications you can install and what you are able to use when you connect to the Tachyon Portal.
Tachyon Platform 5.2includes Real-time and inventory features. Explorer, Guaranteed State, Patch Success, Application Migration, AppClarity, Experience, Nomad.
Upgrade steps
- Upgrade server hardware as required - please refer to Server sizing
- If upgrading from versions older than Tachyon 5.0 you will need to import the Switch certificate files into Windows certificate store. Please refer to Moving Switch certificate files to the Windows Certificate Store below.
- Run Tachyon Setup on the Tachyon Master Stack server to upgrade to Tachyon Platform
- Run Tachyon Setup on remote Tachyon Response Stack servers (if used)
- Verify existing clients
- Run Tachyon Setup on remote Tachyon DMZ Server (if used)
- Verify existing Internet based clients
- Upgrade existing product packs, and install new ones
- Deploy new 1E Client to devices (with Tachyon enabled) and verify.
Tachyon Platform 5.2 onwards no longer allows the use of dots in role names, for example Questioners.Core, and they will no longer work after an upgrade. Therefore, please review your custom role names before upgrading. For more information about defining roles, please refer to Roles page.
Changing the Platform configuration when reinstalling or upgrading
Keep the DNS Names
Each server that has Tachyon platform components installed requires its own DNS Name.
Master Stack | The Master Stack is used by the following, therefore it helps users if it has a recognizable and convenient DNS Name such as tachyon - this is specified during installation of the Tachyon Server using Tachyon Setup.
Platform services also reside on the Master Stack, which non-Tachyon clients connect to, for example:
|
DMZ Server | The DMZ Server is a type of Response Stack used to provide Tachyon Real-time and Inventory services to Internet-based clients. It requires an external DNS Name - for example tachyonext - this is specified during installation of the DMZ Server using Tachyon Setup. The DNS Name is shared between the Switch network interfaces and Background Channel on the DMZ Server, and specified during installation of Tachyon clients, and stored in their configuration file. |
Response Stack | A Response Stack is used to provide Tachyon Real-time and Inventory services to clients on the internal (corporate) network. The choice of DNS Name is discussed in the table below. The DNS Name is shared between the Switch network interfaces and Background Channel on the Response Stack, and specified during installation of Tachyon clients, and stored in their configuration file. |
The number of DNS Names used by a system depend on the location of Tachyon and other Platform services. The table below describes options.
Single DNS Name | A Tachyon system can have a single DNS Name if all components are installed on the same server, for example tachyon - this is specified during installation of the Tachyon Server using Tachyon Setup. If the server has multiple Switches, and therefore multiple network interfaces, then the same DNS Name can be shared by all Switches, the Background Channel and Master Stack. If ActiveEfficiency Server is installed, it can share the same DNS Name provided the server supports less than 5,000 clients. ActiveEfficiency requires its own network interface and DNS Name if the server supports more than 5,000 clients, as described under |
Multiple client-facing DNS Names | Master and Response Stacks must have different DNS Names if they exist on different servers:
When a Response Stack is installed on the same server as the Master Stack, it will normally share the same DNS Name as the Master Stack as described under Single DNS Name above. However, if you have multiple Response Stacks and want them to share the same DNS Name, then the Master Stack must use a different DNS Name. This approach of all Response Stacks sharing the same DNS Name simplifies adding further Response Stacks at a later date. Only one client-facing DNS Name can be specified during installation, other HTTPS bindings are added manually after installation. If Master and Response Stack are on the same server and you want them to have different DNS Names, then specify the DNS Name for the Response Stack during installation, and manually add the HTTPS binding for the Response Stack after installation. You will need to seek guidance from 1E on how to configure Switches to use the second DNS Name. A simpler option is to put the Response Stack on its own server. Remote Response Stacks are recommended if the Master Stack is also hosting services for ActiveEfficiency Server, AppClarity Software Reclaimer or Application Migration. You can optionally have additional DNS Name(s) on the Master Stack server for other services such as ActiveEfficiency Server, AppClarity Software Reclaimer and Application Migration. These bindings would be added manually after installation, and do not require any further complex configuration. ActiveEfficiency Server requires its own network interface and DNS Name if it is installed on the same server as a Response Stack and supports more than 5,000 clients:
|
Internal DNS Names | A DMZ Server is a special example of a Response Stack. The DMZ Server itself requires two DNS Names:
Both DNS Names must be included in the web server certificate. The Response Stack also requires an additional DNS Name - for example tachyonalt - for internal communications with the DMZ Server. Please refer to Implementing a Tachyon DMZ Server for more detail about DMZ Servers. |
Tachyon Setup supports installation of one HTTP and one HTTPS binding, but you can manually add more bindings after installation. HTTPS bindings can share a web server certificate provided it includes all DNS Names, or each HTTPS binding can have its own certificate.
Each DNS Name used to access a Tachyon Server must be included as a DNS Name in the Subject Alternate Name (SAN) entry of the web server certificate, and the Switch certificate files.
A DNS Name can be a DNS alias, CNAME or Host (A) record.
Moving Server
Agents use the DNS Name FQDN to connect to the Switch and Background Channel. Provided the DNS Name FQDN remains the same, the server can be renamed or moved without having to re-configure clients.
If the server hosting a Tachyon Server is renamed or moved, then it will need a new certificate and Tachyon Server must be re-installed. The database can be kept. There is also a known issue where new website URLs do not get updated in the database tables.
Please contact 1E for advice if a new configuration is required when re-installing or upgrading a server.
In-place upgrade of ActiveEfficiency Server for Nomad
This scenario is for upgrading a server that has ActiveEfficiency Server installed and used by Nomad. If ActiveEfficiency is also being used for Shopping then please also read In-place upgrade of ActiveEfficiency Server for Shopping.
Tachyon Setup will do the following automatically, but only if your Tachyon license includes Nomad, and you choose to install Nomad, and a local installation of ActiveEfficiency Server is detected.
- replace ActiveEfficiency Server with Content Distribution to support to new Nomad clients
- create a virtual directory in the Tachyon website and use HTTP redirection to support legacy Nomad clients
- rename the ActiveEfficiency database as ContentDistribution if it exists on the SQL Server instance you selected for the ContentDistribution database (the database is renamed, but the database mdf and ldf filenames are not changed)
The last point means ActiveEfficiency data will be retained in the ContentDistribution database, to provide the following:
- Existing pre-cache jobs, and paused collections, are migrated so they are shared by old and new Nomad clients, and can be managed by upgraded installations of the Nomad Configuration Manager Console Extensions
- Locations and Single-site content registrations are not migrated, but retained in legacy database tables so they continue to be used by legacy Nomad clients - content registrations for new Nomad clients are created in new database tables, so that legacy and new clients function independently.
The ActiveEfficiency database will be retained, and no data migrated, if it is on a different SQL Server instance than the one you specified for your ContentDistribution database. To automatically migrate data during upgrade, you will need to copy the ActiveEfficiency database to the new location, and reconfigure ActiveEfficiency Server to use the copied database. Alternatively, you can Manually migrate data as described below.
If the installation of Content Distribution fails for whatever reason, the database changes are rolled back.
Although ActiveEfficiency Server is replaced by Content Distribution, the new Nomad client in 1E Client 5.2 does not connect directly to it. Instead, it connects to the same Tachyon Switch and Background Channel as the Tachyon client - the 5.2 version of the Background Channel contains a reverse proxy to forward API requests to Content Distribution. The Tachyon Switch and Background Channel may be on the same server as the Tachyon Master stack, or on a remote Response Stack. This means any remote Tachyon Response Stacks or DMZ Server (if used) must be upgraded also, before your Tachyon infrastructure can support new Nomad clients.
When upgrading Nomad clients, the new Nomad clients will no longer require an HTTP connection to the server that previously hosted ActiveEfficiency Server. However, if you are upgrading from a Tachyon or SLA server, then other 1E software (Application Migration and AppClarity Software Reclaimer) may still use HTTP to connect to SLA services on the server.
You should only upgrade to Tachyon Platform 5.2 if you are prepared to upgrade Nomad clients to 1E Client 5.2 (with Tachyon and Nomad clients enabled) and replace ActiveEfficiency with Nomad and Content Distribution on Tachyon Platform.
You cannot deploy 1E Client 5.2 and retain the older version of Nomad client, and the Nomad client in 1E Client 5.2 cannot use ActiveEfficiency. Therefore, if you are currently using Nomad with ActiveEfficiency, you must upgrade both.
Upgrade steps
- Review your requirements to determine which features you need of 1E Client and Tachyon Platform, please refer to Design Considerations, Requirements and Preparation pages
- Upgrade your server hardware as required- please refer to Server sizing
- Reconfigure Shopping Central (if used)
- Uninstall ActiveEfficiency Scout (if used) and disable associated Windows Task Scheduler job(s)
- Run Tachyon Setup on the ActiveEfficiency server to upgrade it to Tachyon Platform - please refer to Tachyon Setup
- Run Tachyon Setup on remote Tachyon Response Stack servers (if used) - please refer to Tachyon Setup
- Verify existing clients, to confirm Tachyon continues to function as before, with Nomad clients using HTTP redirection as described above
- Run Tachyon Setup on remote Tachyon DMZ Server (if used) - please refer to Implementing a Tachyon DMZ Server
- Verify existing Internet based clients
- Deploy new 1E Client to some test devices (with Tachyon and Nomad client enabled)
- Verify the test devices
- Upgrade Nomad tools - please refer to Nomad 7.1 - Upgrading Nomad
- Upgrade Nomad Admin Tools and server components
- Update OS Deployment Task Sequence actions to use the Tachyon Platform
- Review Automatically migrated data and configure Nomad Sites
- Deploy new 1E Client to remaining devices.
Do not reinstall ActiveEfficiency on the Tachyon Platform server.
Automatically migrated data
As stated above, the upgrade of ActiveEfficiency Server to Tachyon Platform automatically migrates details of pre-cache jobs, and paused collections, so they can be managed by upgraded installations of the Nomad Configuration Manager Console Extensions. You can review these in the Nomad app.
Locations, Single-site data, and content registrations are not migrated, but are retained in legacy database tables so they continue to be used by legacy Nomad clients. This data is not shared with new clients, so that legacy and new clients function independently. New clients will re-register their content automatically up to 24 hours later, or can be forced by using the NomadBranch command-line parameter -cdssync as described in NomadBranch.exe command-line switches. Old and new clients will perform master elections and peer-share content if they are the same subnet, but they will only use SSD with their own set of clients.
You will continue to maintain Nomad Sites (previously known as Locations) using one of the new versions of the example PowerShell scripts provided with the Nomad Admin Tools. Alternatively, you can use the examples to modify your existing script to use Content Distribution instead of ActiveEfficiency.
Side-by-side upgrade of ActiveEfficiency Server for Nomad
This scenario is for an existing Nomad and ActiveEfficiency installation, where Tachyon Platform is on a different server, either newly installed or upgraded from on earlier version of SLA Platform or Tachyon. The old ActiveEfficiency Server is eventually decommissioned. There is no requirement for HTTP redirection on the Tachyon server, because old Nomad clients will continue to use the ActiveEfficiency server, and new Nomad clients will use Content Distribution on the upgraded Tachyon Platform. Each set of clients functions independently. Some data is manually migrated from the ActiveEfficiency server, as described below.
If your Tachyon license includes Nomad, and you choose to install Nomad, and a local installation of ActiveEfficiency Server is detected, then you are doing an In-place upgrade of ActiveEfficiency Server for Nomad.
If a local installation of ActiveEfficiency Server is not detected, the ActiveEfficiency database is retained even if it is on the same SQL instance you specified for the ContentDistribution database.
Upgrade steps
- Review your requirements to determine which features you need of 1E Client and Tachyon Platform, please refer to Design Considerations, Requirements, and Preparation pages
- Upgrade your server hardware as required- please refer to Server sizing
- Run Tachyon Setup on the existing SLA Platform or Tachyon server to upgrade it to Tachyon Platform - please refer to Tachyon Setup
- Run Tachyon Setup on remote Tachyon Response Stack servers (if used) - please refer to Tachyon Setup
- Verify existing clients (if upgrading SLA Platform or Tachyon)
- Run Tachyon Setup on remote Tachyon DMZ Server (if used) - please refer to Implementing a Tachyon DMZ Server
- Verify existing Internet based clients (if upgrading Tachyon)
- Deploy new 1E Client to some test devices (with Tachyon and Nomad client enabled)
- Verify the test devices
- Upgrade Nomad Admin Tools and server components - please refer to Nomad 7.1 - Upgrading Nomad
- Upgrade Nomad Admin Tools and server components
- Update OS Deployment Task Sequence actions to use the Tachyon Platform
- Manually migrate data from ActiveEfficiency Server
- Configure Nomad Sites
- Deploy new 1E Client to remaining devices
- When all Nomad clients have been upgraded, then you can decommission the old ActiveEfficiency Server (unless you need to retain it for Shopping).
Manually migrate data
Use the following migration scripts to manually migrate sites, pre-cache jobs, and paused collections, from ActiveEfficiency, so they can be managed by upgraded installations of the Nomad Configuration Manager Console Extensions. After migration, you can review these in the Nomad app.
Locations, Single-site data, and content registrations are not migrated, but are copied to legacy database tables for reference only. This data is not shared with new clients, so that legacy and new clients function independently. New clients will re-register their content automatically up to 24 hours later, or can be forced by using the NomadBranch command-line parameter -cdssync as described in NomadBranch.exe command-line switches. Old and new clients will perform master elections and peer-share content if they are the same subnet, but they will only use SSD with their own set of clients.
You will maintain Nomad Sites (previously known as Locations) using the one of the new versions of the example PowerShell scripts provided with the Nomad Admin Tools. Alternatively, you can use the examples to modify your existing script to use Content Distribution instead of ActiveEfficiency.
You may continue to maintain Locations in ActiveEfficiency as before, to continue supporting old clients.
Click here to download - AE-CD Data Migration Scripts.zip
Prerequisites
- The ability to run PowerShell scripts and SQL script
- A SQL Login on each SQL Server instance for the user running the scripts
- db_datareader rights on the ActiveEfficiency database
- db_datawriter rights on the ContentDistribution database
Before running the scripts you will need to prevent clients, administrators, and scheduled jobs from updating ActiveEfficiency and Nomad.
- Stop IIS on the Tachyon Master Stack server (where Content Distribution is installed)
- Open command prompt in administrator mode and run iisreset /stop
- Stop IIS on the server where ActiveEfficiency Server is installed
- Open command prompt in administrator mode and run iisreset /stop
- Temporarily disable any Task Scheduler jobs related to ActiveEfficiency
- From the Start screen, start typing Task Scheduler then click on Task Scheduler in the search results
- Expand Task Scheduler Library → ActiveEfficiency
- Right-click on each job and select Disable
- If you have any custom jobs to run import scripts for Sites and Subnets then also disable these temporarily.
Create Tables
Open SQL Management Studio and connect to ContentDistribution database. Execute SQL script CreateTables.sql. This will create all the required legacy tables in the ContentDistribution database.
This script only needs to be executed once.
Export Data
Run the ExportData.ps1 script in a PowerShell admin command prompt using a command line similar to below.
.\ExportData.ps1 -AEServerName "AEServer" -AEDBName "ActiveEfficiency" -CDServerName "CDServer" -CDDBName "ContentDistribution" -folderPath "C:\migration" -logsPath "C:\migration\logs"
This command will create a series of CSV files that we will later import into the ContentDistribution database.
Import Data
Run the ImportData.ps1 script in a PowerShell admin command prompt using a command line similar to below.
.\importData.ps1 -CDServerName "CDServer" -CDDBName "ContentDistribution" -folderPath "C:\migration" -logsPath "C:\migration\logs"
This command will populate the tables from the CSV files exported earlier.
Restart IIS
- Restart IIS on the ActiveEfficiency Server and Tachyon Master Stack server (where Content Distribution is installed)
- Open command prompt in administrator mode and run iisreset /start
- Enable the Task Scheduler jobs again on the ActievEfficiency Server
Script parameters
Parameter | Description |
---|---|
AEServerName | Name of the SQL Server hosting ActiveEfficiency database. If the server is not running on the default instance, enter the server name and instance name separated by backslash, for example DBServer\DB |
AEDBName | Name of the ActiveEfficiency database. |
CDServerName | Name of the server hosting ContentDistribution database. If the sever is not running on the default instance, enter the server name and instance name separated by backslash, for example DBServer\DB |
CDDBName | Name of the ContentDistribution database. |
folderPath | Folder location to save CSV files. If the path doesn't exist, it will be created by the script. |
logsPath | Folder location to save log files. If the path doesn't exist, it will be created by the script. |
In-place upgrade of ActiveEfficiency Server for Shopping
This scenario is for upgrading a server that has ActiveEfficiency Server installed and used by 1E Shopping. If ActiveEfficiency is also being used for Nomad then please also read In-place upgrade of ActiveEfficiency Server for Nomad.
If your installation of ActiveEfficiency is being used by 1E Shopping, then before you replace ActiveEfficiency with Content Distribution you will need to do one of the following:
- install another instance of ActiveEfficiency Server and Scout and reconfigure Shopping to use that - this process is not described here
- reconfigure Shopping to synchronize directly with Configuration Manager (this method of synchronization is provided out-of-the-box in Shopping 6.1 onwards)
Shopping is not a Tachyon Platform application, and has no direct dependency on it, therefore it is not affected by Tachyon Setup, other than ActiveEfficiency being removed. Whilst Shopping has no direct dependency on Tachyon Platform, it can optionally integrate with Application Migration 3.1 which is a Tachyon application. The Shopping/WSA client is a module of the 1E Client. If this is interesting to you please refer to Shopping 6.0 - Integrating with Application Migration.
Reconfigure Shopping to synchronize directly with Configuration Manager
Execute the following SQL script on the Shopping database, then restart the Shopping Central service. A few minutes later the Central service will perform its usual synchronization processes with AD, and also synchronize with CM. You can monitor this process in C:\ProgramData\1E\ShoppingCentral\ShoppingCentral.log
The script changes preference settings in Shopping 6.0 - Shopping Admin Console settings: Central Service as shown in the table opposite. The script changes the description of the sync interval, it does not change its value, which is 1 day by default. If you change the value later it should be longer than the time it takes to complete all the syncs. You should not need to change the value of the sync interval because the SCCM sync should be approximately the same as the ActiveEfficiency Scout sync.
Click here to download - ReplaceActiveEfficiencySyncWithConfigMgrSync.sql
Preference name | Change made by the SQL script |
---|---|
Users and Machines, AD Sync Interval | Change description |
Users and Machines, AD Sync Units | Change description |
Sync Machines and Users From Active Efficiency | Set to 'False' (enables sync from SCCM instead) |
Sync Machines From Old Sccm | Hide as no longer required |
ActiveEfficiency ServerName | Hide as no longer required |
In-place upgrade of 1E Catalog 1.2 and SLA Platform 3.3
Tachyon Setup will upgrade 1E Catalog, SLA Platform and its applications to Tachyon Platform 5.2. If SLA and Catalog are installed on separate servers, then you have the following options:
- Use Tachyon Setup to upgrade SLA Platform and to install 1E Catalog on the same server
- Setup allows you to retain the SQL Server instance(s) their databases are on
- You can manually relocate the databases before running Setup.
- Use a custom option of Tachyon Setup that supports using a remote Catalog server
- This option is discouraged to avoid configuration and upgrade issues. Please contact 1E for details of how to use custom setup options.
SLA Platform 3.3 supports Application Migration 2.5.100 and AppClarity 6.1.100. Tachyon Setup will upgrade these applications to versions supported by Tachyon Platform 5.2.
Preparing for upgrade
Moving Switch certificate files to the Windows Certificate Store
From Tachyon 5.0 onward, the Tachyon Switch uses certificates in the Windows Certificate Store, whereas earlier versions used certificate files located on disk. When upgrading, you might still be using file-based certificates that don't exist in the certificate store. This is more likely if your server certificate (used for IIS components) is different to the certificate your switch (or switches) present. This certificate needs to be imported into the certificate store, preferably before upgrading.
If you don't have a .pfx file, you can assemble one from the existing switch certificate files and OpenSSL. If you do, skip this step:
openssl pkcs12 -export -out <outPfxFilePath> -inkey <keyFilePath> -in <cerFilePath> //example: openssl pkcs12 -export -out c:\mycerts\mypfx.pfx -inkey c:\mycerts\hello.cer -in c:\mycerts\hello.key
Import it into the Local Machine's Personal certificate store. This can also be done though mmc:
certutil -f -p <pfxPassword> -importpfx <pfxFilePath> //example: certutil -f -p Password -importpfx c:\mycerts\mypfx.pfx
In Tachyon Setup, select the certificate when it appears on the Server Certificate screen
This will set both the server (IIS) certificate and the Switch certificate. If your switch needs to use a different certificate, modify the Tachyon.Switch.Host.exe.config.
Backup first!
Before doing a re-installation or upgrade of the Tachyon Platfrom, make a backup of the following (but first see the note below about automatic backups):
TachyonMaster database
Backing up the Tachyon Responses database is not usually needed, unless there are instruction responses that you need to keep. Tachyon responses are not permanently held data and will naturally expire according to the settings specified when an instruction was run, typically in hours or possibly days. If in doubt, there is no harm in backing up the Tachyon Responses database as well.
- Tachyon Server installation directory
- including the config files, which may have been manually updated in the previous installation
- Switch certificate files
Earlier versions of Product Packs that have been modified
Tachyon Setup will automatically perform a backup of the following items:
- Tachyon Server installation directory. This is backed up to a subfolder named Tachyon.bak under the root installation folder for Tachyon. All files, including the .config files and certificate files, will be copied.
- IIS configuration. This is done by taking a copy of the applicationhost.config file from the Windows system folders. The backup file is placed at the same location, and is named like the original file with a suffix that indicates the date and time when the copy was taken.
- The following databases are backed up to the default location for backups that is configured in the database server. By default, this points to a subfolder named "Backups" under the folder where the executable for SQL Server is installed. Unless you are installing a small lab or proof-of-concept, this is usually not a good location for the backups, so make sure that you configure the backup location in SQL Server to an adequate folder before starting the Tachyon upgrade:
- 1ECatalog
- ActiveEfficiency (optional, required for Nomad)
- SLA-Data
- SLA-Shared
- SLA-Integrate
- SLA-BI (optional, required for Patch Success)
- TachyonMaster
- TachyonResponses
- TachyonExperience (optional, required for Experience)
The Product packs are not copied by themselves, but they are kept in a table within the TachyonMaster database, which is backed-up.
Upgrading to Tachyon Platform
Partial Upgrades
You may still be asked at some intermediate steps about configuration information for the components that will not be installed. You should still provide it, because it may be relevant for Tachyon Setup at the time of configuring other components that are being installed so that they can interact with the components that are not being installed but are already present in the system.
The following process is used when upgrading Tachyon 3.x, 4.x, 5.0 or 5.1 to Tachyon Platform 5.2 and keeping the same configuration and the TachyonMaster database.
Keeping the same configuration means using the same installer properties as the previous installation. If changing the configuration, please refer below to Changing the Platform configuration when re-installing or upgrading.
Ref | Step | Notes |
---|---|---|
1 | Ensure you have prerequisites ready for installation of the new version.
Review Known Issues for Upgrades. | Preparation for an in-place upgrade is not as complex compared to a new installation, provided the configuration remains the same. If changing the configuration, please refer below to Changing the Tachyon Server configuration when re-installing or upgrading. Determine if you will re-use the existing Web certificate or a new one. If re-using the certificate and upgrading from a version of Tachyon prior to 5.0 then ensure you make a copy of the certificate files in the Switch SSL folder. If using a new certificate then follow the guidance in Server Provisioning. If you are upgrading from Tachyon 5.0 the certificates will already be in the local Windows Computer Certificate Store so there is no need to backup. If in doubt about your configuration review each of the configuration in the Tachyon installation folder. A later step in this process asks you to make a backup copy of the installation folder. This allows you to review configuration settings and also retain a backup of the Switch certificate files. 1E recommends using the same server installation account as the original installation, but this is not mandatory provided the account is an existing Tachyon administrator user. You can check which is the original installation account by looking in the Permissions page and finding the user which does not have an edit or delete icon. For Tachyon 5.2 you will need a new license when upgrading. Please contact your 1E Sales account manager for license inquires. |
2 | Inform Tachyon users when you plan to upgrade the system. | You should notify Tachyon users about the impending upgrade. This includes users of external consumers such as the extension described in Using Tachyon in Configuration Manager. To help identify the users of the Tachyon system you can review the Tachyon Permissions. You can also review the Tachyon Consumers in order to remind yourself of any 3rd party systems that will be affected by the upgrade. Any instructions that are running or pending approval prior to the Platform and Agent upgrade will not be affected, other than be delayed by services being temporarily down. |
3 | Shutdown the existing Tachyon system.
| If you want to keep any instruction responses, review the notes in the next step before shutting down the system. Shutting down the system gracefully ensures there are no instructions in process and prevents access. The installer will internally shutdown the services if you do not stop them manually. Stopping them manually gives you a greater control about when they are stopped. The services will be restarted automatically after the upgrade. Both the Tachyon Switch Host and the Coordinator can take some time stopping their services. No other services for the applications associated with Tachyon need to be stopped. Do not stop or disable the Tachyon website or application pools. The installer needs them to be active in order to complete all installation tasks. |
4 | Close all active connections to the Tachyon databases. | To avoid a particular known issue when upgrading you must ensure there are no active connections to the databases. You can use the following SQL script to identify which programs have active connections to the Tachyon databases. SELECT DB_NAME(dbid) as [database], loginame, hostname, program_name FROM sys.sysprocesses WHERE DB_NAME(dbid) LIKE 'Tachyon%' AND program_name LIKE 'Tachyon%' ORDER BY DB_NAME(dbid), loginame, hostname, program_name; With the Tachyon services stopped, any open connections to the database, such as Tachyon Consumer and Tachyon Portal, should not cause the upgrade to fail and can be safely ignored. |
5 | Backup the databases. | If you use Tachyon Setup to perform the upgrade it backs up the following databases:
The following notes apply to the Responses database and whether you would need to create a backup of that database too: Backing up the Tachyon Responses database is not usually needed, unless there are instruction responses that you need to keep. Tachyon responses are not permanently held data and will naturally expire according to the settings specified when an instruction was run, typically in hours or possibly days. If in doubt, there is no harm in backing up the Tachyon Responses database as well. |
6 | Make a copy of the Tachyon Server installation folder. | The installation folder contains the following non-default files:
|
7 | Install Tachyon Server. | Install Tachyon Server using the same configuration as before. Do not drop the databases. Please refer to Tachyon Setup for more details. |
8 | Post-install tasks. | Repeat any Tachyon Server post-installation tasks that are relevant for an upgrade installation and are not performed automatically by Tachyon Setup. |
9 | Customizations. | Re-instate non-default settings.
|
10 | Verify. | See Verifying page. |
After upgrading to Tachyon Platform
After upgrading, you should perform a sync for all configured Connectors followed by the Basic Inventory Consolidation report.
The following points should be considered after upgrading from Tachyon 3.x, 4.x, or 5.0 to Tachyon 5.2:
- If you have previously configured any Schedules these will be converted to using UTC time. You will need to revisit these to ensure the time you want the Schedules to run is still correctly configured
- If you have previously configured any Schedules for Tachyon or Configuration Manager Connector syncs these will need to be deleted and re-created - as the sync process for both of these types of connector has been redefined. Please refer to Tachyon connector and System Center Configuration Manager connector for more details.
Tachyon 5.1 already uses UTC for Schedules, therefore no changes are required when upgrading to Tachyon 5.2.
Upgrading Instructions and Product Packs
Tachyon Instructions are designed as far as possible to be backwards compatible, but as a general rule we recommend that you update your Tachyon product packs to the latest version so that you can gain the benefit of newer features.
When upgrading you should be able to safely continue to use your existing Instructions. We recommend that newer versions of Instructions are verified in a test environment to ensure that they still behave as expected before updating in your production environment.
Your Tachyon license should retain any code signing certificates you may have registered. This means your custom instructions should continue to be licensed as normal following an upgrade of Tachyon. You may want to check the Writing Tachyon Instructions in the Tachyon SDK pages to check for any changes to the Tachyon SCALE language.