Contents
-
Introducing Tachyon
-
Quick Start
-
Implementing Tachyon
-
Using Settings
-
Using Explorer
-
Using Guaranteed State
-
Using Inventory
-
Using Experience
-
Using Patch Success
-
Troubleshooting
-
Extending Tachyon
-
Training
-
Tachyon Operator v5.0 Lab Guide
-
Ex 1 - TCN Opr v5.0 - Installing and Configuring Tachyon Prerequisites
-
Ex 2 - TCN Opr v5.0 - Installing Tachyon
-
Ex 3 - TCN Opr v5.0 - Exploring the Settings Application
-
Ex 4 - TCN Opr v5.0 - Instruction Sets and Management Groups
-
Ex 5 - TCN Opr v5.0 - Working with Instructions
-
Ex 6 - TCN Opr v5.0 - Working with Patch Success
-
Ex 7 - TCN Opr v5.0 - Working with Inventory
-
Ex 8 - TCN Opr v5.0 - Using Guaranteed State
-
Ex 9 - TCN Opr v5.0 - Microsoft Configuration Manager Integration
-
Ex 10 - TCN Opr v5.0 - Creating Instructions and Fragments Using TIMS
-
Ex 11 - TCN Opr v5.0 - Working with Experience
-
Ex 1 - TCN Opr v5.0 - Installing and Configuring Tachyon Prerequisites
-
Tachyon Advanced v5.0 Lab Guide
-
Tachyon - Nomad as Content Provider Lab Guide
-
Tachyon Operator v5.0 Lab Guide
-
Reference
Installing Tachyon
In this lab, we will install all Tachyon components onto the same server which we have prepared with the prerequisites, 1ETRNAP. This includes the roles and features required for the Tachyon installation. In addition, we will deploy the Tachyon clients once the server components have been installed.
Installing Tachyon components
Install Tachyon components
In this task, you will install Tachyon components on the Application server (1ETRNAP).
- On 1ETRNAP Launch the SkyTap Shared Drive shortcut from the desktop and download 1E Tachyon - Course Content\Tachyon 5.0 Course Content\Tachyonplatform.v5.0.0.592.zip to C:\Temp (if a password window is shown the password is Passw0rd)
- Also download tachyon.lic and Q21355-tachyonserver.v5.0.0.592.msp from 1E Tachyon - Course Content\Tachyon 5.0 Course Content\ to c:\temp
- Navigate to c:\temp and right click on TachyonPlatform.v5.0.0.592.zip and choose Extract All
- From C:\Temp\TachyonPlatform.v5.0.0.592 double click Tachyon.Setup.exe
- On the Welcome page click Next
- On the Documentation page, click Next
- On the License Agreement page select I accept the terms of the license agreement and click Next
- On the License file page, click browse and select tachyon.lic in c:\temp. Click Open. Click Next
- Review the properties of the license file to get a feel for what it entails. Specifically, the MaxCount value as well as the thumbprints for the different Features
- On the Select Configuration page, change the install location to be C:\Program Files\1E and Click Next
- On the Check prerequisites page click Start checking
- Click Install missing prereqs
- Once all the prerequisites are installed, click on Check Again to revalidate. Click Next
- On the Server certificate page Select Tachyon tachyon.1etrn.local Certificate, note that all the available Computer Certificates enrolled on this server are displayed. Click Next
- On the Client certificates page, Click Next
- On the Database server page, ensure that (local) is in each field. Click Validate. On the validation passed box, click Ok. Click Next
- On the BI SSAS database settings page, in the BI SSAS User (domain account) section enter 1ETRN\svc_BI in Username and Passw0rd in the password fields. ensure that (local) is in the SSAS server field. Click Validate. Click Ok on the Validation passed box. Click Next
- On the Number of Devices page, ensure the Number of devices is set to 1500. Click Next
- On the Switch configuration page, click validate. There are two warnings these can be looked at, but do not need remediation. Click Next
- On the Website Configuration page, leave the default settings. Click Next
- On the Active Directory and email Configuration page, enter the following and Click Validate, close the validation check. Click Next
- On the SLA and 1E Catalog page, DO NOT Check the Enable AI-based auto-curation. Click Next
- On the Nomad synchronisation page, click Next
- On the Ready to Install page, click Install. It will take a few minutes to finish the install. You can see the install log scrolling
- On the Installation results, click Next
- On the Post-installation Checks, Click Start Checking.
- On the first warning – Configuration of loopback-check security feature. Click on Warning in the Info column. In the Warning box click on Fix this issue for me. In the Done box click Ok
- If there are any other errors or warnings click on them to investigate
- Click close
- Following the step to fix the loopback-check a reboot was prompted to be carried out prior to continuing with the install, restart the server at this point
- Log back into 1ETRNAP after the reboot and open c:\temp Right click on Q21355-tachyonserver.v5.0.0.592.msp and choose apply
- Click Open and Update. When the process completes click finish. Click yes to restart the server
SMTP Server: 1ETRNDC.1ETRN.LOCAL
Mail From: Tachyon@1etrn.local
Enable two-factor authentication: Checked
We could at this stage decide to invoke the Tachyon Product Pack Deployment Tool to automatically import any product packs and move them into instruction sets (named the same as the .zip file). There is already a folder called ProductPacks in the same location as the Tachyon.Setup.exe (which we have just downloaded and extracted). The ProductPacks folder contains by default the files for the Tachyon Product Pack Deployment Tool and the Classic and Integrated folders with some 1E Product Packs you may want to bulk import into Tachyon. You can also add any additional product pack.zip files you have created or downloaded and wish to import.
We will use the bulk import feature later as a stand-alone to learn how it works.
The option to Deploy is shown at the bottom of the page, we will not do that here.
Review the installation
In this task, you will observe the changes made by the Tachyon server installation
- After the reboot log back into the server as 1ETRN\AppInstaller
- Launch Google Chrome and navigate to https://tachyon.1etrn.local/tachyon
- The Tachyon Portal should open and display the 6 Applications that are available – Experience, Explorer, Guaranteed State, Inventory, Patch Success, and Settings. They should all have a green check mark as our license allows us to have all of the Applications
- Browse to C:\Program Files\1E\Tachyon and note the following folders:
- Open Internet Information Services (IIS) Manager from the start menu. Navigate down to the websites and expand Tachyon
- Note the different web applications running under Tachyon
- With the Tachyon website selected, click on Bindings in the Actions pane on the right, select the https type, and click Edit
- Note that the web certificate we enrolled is bound to the website on https port 443. Exit out of bindings
- With the Tachyon website selected, double click on IP Address and Domain Restrictions in the middle pane. Note nothing is configured here
- Click on each individual application beneath the Tachyon website and double click each of the Authentication, SSL Settings and IP Address and Domain Restrictions and confirm they are set as shown. Note that some have Requestors configured, while others do not
- Open the Services applet from the start menu. Validate the 2 Tachyon services running, 1E Tachyon Coordinator and 1E Tachyon Switch Host, as well as the 1E Catalog Update Service, and the 3 SLA Platform services
- Browse to C:\ProgramData\1E\Licensing. Note the files in here
- Browse to C:\ProgramData\1E\Tachyon. There are multiple folders and logs here associated with different Tachyon components
- Open the Tachyon.Switch.Host.log. Search for NumberofSwitches. Note that the log shows the 1 switch we installed
- Open Tachyon.Switch_A.log. Note the configuration information and the application of the certificate
- Open the Tachyon.Coordinator.log. Search for AnalyzeCertificate: Note our thumbprint and the details on our certificate. Note the next lines in the log shows our license being checked and becoming active and the date that it will expire
- Note the 4 folders under C:\ProgramData\1E\Tachyon: Content, Installers, PolicyDocuments and Updates, each with a web.config file
- From the Start screen, start SQL Server 2014 Management Studio, connect to the local Database Engine, and navigate to the Databases node. Expand the TachyonMaster database. Note that the installer has created objects (tables, stored procedures etc.)
- Expand the TachyonResponses database. Expand tables, and note that there are a very small number of objects created
- Expand the SLA-BI database. Look at the tables that are created
- Expand the BI.Event Log table. This table holds the Business Intelligence event log date
- Right click the BI.Event Log table and choose Select Top 1000 rows. Notice the columns
- From the Task Bar, open Google Chrome and browse to https://tachyon.1etrn.local
- Go back to Google Chrome and Browse to https://tachyon.1etrn.local/tachyon
- From the Tachyon Portal click on the Settings Application
- Explore the other nodes that are available. Instructions will be empty. We will add some instructions sets later
- Click on Switch app and select Explorer
- In the Settings Application and navigate to Permissions - Users
- Note the only user displayed is the user we installed Tachyon with (aside from Network Service and the app server machine account)
- Click on 1ETRN\Appinstaller and review the permissions
- Navigate to Monitoring - Infrastructure Log and Audit Information log to review the different actions taken within Tachyon since install
- Spend a few minutes looking around. We will get into the finer details of the platform in the next lab
Folder | Description |
Background | Binaries associated with the Background Channel, which is used to download content to clients |
ConfigurationViewer | Binaries used for validation and troubleshooting. The Configuration tool also allows for exporting of configuration to disk. |
Consumer | Binaries associated with the Consumer API. It provides access to the Tachyon platform via IIS |
Coordinator | Binaries associated with the Workflow and Instrumentation services |
Core | Binaries associated with the Core component and its APIs |
Database | Binaries associated with the configuration of the Master and Response databases |
Experience | Binaries associated with the configuration of the Experience component |
Portal | Binaries for the Portal to display the Applications that are available to launch. |
Switch | Binaries associated with the Switch service used to provide real time communication between Tachyon agents and the Platform |
TachyonExternal | Folder defining the Tachyon website. Also, used to manage redirection |
Application | Authentication | SSL Settings | IP Address and Domain Restrictions |
Tachyon* | Windows | Require SSL | Not Configured |
ActiveEfficiency | Anonymous and Windows | Not Configured | Not Configured |
Admin | Windows | Not Configured | Not Configured |
Background | Anonymous and Windows | Require SSL | Not Configured |
CatalogWeb | Anonymous and Windows | Not Configured | Not Configured |
Consumer | Windows | Require SSL | Not Configured |
Core | Anonymous | Require SSL | Local IP addresses |
CoreExternal | Anonymous | Not configured | Not Configured |
CoreInternal | Anonymous | Not Configured | Local Addresses |
Experience | Windows | Require SSL | Not Configured |
Platform | Windows | Not Configured | Not Configured |
Service | Description |
1E Tachyon Coordinator | This service is a central component that manages all the components other than the switch. |
1E Tachyon Switch Host | This service is used to control all the switch processes configured to run. It automatically starts each Switch process, restarting them if they terminate, and allowing them to be stopped gracefully via the Service Control Manager. |
Installing the 1E Client
Now that the back end has been installed, it is time to get some clients reporting into our environment. In this exercise, we will install the 1E Client manually on a single machine, and then deploy the client to the rest of our environment via ConfigMgr. As of this version of Tachyon the 1E Client has replaced the Tachyon Agent.
Copy the 1E Client Install to the Config Mgr Server
- Log into 1ETRNDC as 1ETRN\Administrator
- Launch the skytap shortcut from the desktop. Download and copy 1E Tachyon - Course Content\Tachyon 5.0 Course Content\1EClient.v5.0.0.745.zip to c:\temp then right click and extract all
- copy the 1EClient.v5.0.0.745 folder to E:\ConfigMgrSource\software
Install the 1E Client Manually
- Ensure all workstations are powered on
- Log onto 1ETRNW101 as 1ETRN\User
- From the start menu, type Certificate and click on Manage computer certificates to launch the certificates mmc console
- In the console, right click Personal, and select All Tasks>Request New Certificate
- Click Next
- On the Select Certificate Enrollment Policy click Next
- Note there is only one certificate available for enrollment. Select the Computer certificate and click Enroll
- Once enrolled, click Finish
- From the ConfigMgr Content Source folder on the desktop, navigate down to \software\1EClient.v5.0.0.745
- Copy 1E.Client-x86.msi to c:\sources
- From the taskbar, run the command prompt
- Switch to the c:\sources directory and run the following command line to start the 1E Client installation wizard
- On the Welcome to the 1E Client Installer screen click Next
- On the License Agreement screen select I accept the terms of the license agreement and click Next
- On the Installation Folder screen accept the default location and click Next
- On the Tachyon screen, enter TACHYON.1ETRN.local:4000 for the Switch
- On the Background Channel URL, enter https://tachyon.1etrn.local/Background for the Background Channel. Click Next
- On the Nomad screen, click Next
- On the Shopping screen, Click Next
- On the WakeUp screen, click Next
- On the Ready to Install the 1E Client screen, Click Install. On the User Account Control pop-up click OK. When install is completed, click Finish
msiexec /i 1E.Client-x86.msi /l*v 1EClient.log
Validate the 1E Client Install
- On the client machine, launch the Services applet from the desktop
- Confirm the 1E Client service has been installed and is running
- Navigate to c:\programdata\1E\Client
- Note there are DBs and Persist folders and a log file present
- Double- click the 1E.Client.log file and review the log
- Note upon service startup, the client is setting the Switch to tachyon.1etrn.local:4000 as defined in the installer
- Review the other settings in the log
- The 2 subfolders: DBs and Persist
- Navigate to c:\program files\1E\Client and review the content
- Right-click 1E.Client.conf and select Open With and open with Notepad
- Review the different sections of the config file, ensuring you do not make any changes. Note that the settings displayed in the log file are all defined here
- Close the config file, ensuring no changes were made. If asked to save it, click NO
Installing the 1E Client using the 1E Client Deployment Assistant via ConfigMgr
In most enterprises, there will be a Systems Management platform to manage devices in the environment. In our lab we will use ConfigMgr, but the concept of deploying the 1E Client as a piece of software will apply to any Systems Management platform.
- Log into 1ETRNCM as 1ETRN\SCCMADMIN
- Launch the SkyTap Shared Drive shortcut on the desktop. Download 1E Tools\1EClientDeploymentAssistant.v1.4.100.9.zip to c:\temp
- Extract the zip file to c:\temp
- Launch the 1EClientDeploymentAssistant.exe
- On the Welcome page click Next
- On the License Terms page check I accept the license terms. Click Next
- On the Configuration Manager Connection page click connect. Once it connects click Next
- On the General settings page 1E License File field click browse and select the licenses.txt file in the 1EClientDeploymentAssistant folder
- In the 1E ActiveEfficiency Server URL change default to http://1etrnap/ActiveEfficiency
- On the Application and Package Content Sources fields type in \\1etrndc\ConfigMgrSource\Software
- Check the Distribute Content box and select All Distribution Points from the drop-down. Click Next
- On the Agent selection page Uncheck all the boxes except for the 1EClient 5.0.0.745. Click Next
- On the 1E Client 5.0.0.745 page Change the Limiting Collection to All Desktop and Server Clients Click Next
- On the Tachyon and other client settings page Switch field type in Tachyon.1etrn.local:4000
- In the Background Channel field type in https://tachyon.1etrn.local:443/Background click Next
- On the Nomad Client Settings page click Next
- Once the Summary page activates the Create button click Create
- Once that completes click Next
- Click Finish
- Launch the ConfigMgr console from the taskbar
- Navigate to Software Library – Application Management – Applications
- Select the 1EClient 5.0.0.745 and click Deployment Types tab at the bottom
- Right Click the 1E Client x64 deployment type and choose Properties
- Click the Requirements tab. Click the Operating System requirement type and click the edit button
- Scroll down and select all the x64 Server Operating Systems also. Click Ok. Click Apply. Click Ok
- Navigate to Assets and Compliance and click on Devices
- Multi-select all the devices in the Lab except for 1ETRNDC and add them to an existing collection – 1EClient 5.0.0.745 – Required
- Once the collection membership shows 7
- Right Click on the 1EClient 5.0.0.745 – Required collection and choose Client Notification – Download Computer Policy
- Repeat the client validation steps from above on any of the workstations to ensure the client has installed correctly
Lab Summary
In this lab, we installed Tachyon on a single server. We used components from the prereqs we installed/configured in the previous lab required by Tachyon. Once installed, we validated the install by evaluating the binaries, the web components, the services, and the databases. Once validated, we launched the Tachyon Portal, and reviewed the console.
We then installed a 1E Client manually on one workstation. We validated the install on the client, then configured a package for deployment of the 1E Client agent via ConfigMgr. Once the package was created, we deployed it to our 1E Client collection for install.
Next Page
Ex 3 - TCN Opr v5.0 - Exploring the Settings Application