Exercise Overview:

Configuring Experience

Here we will learn how to configure Experience. In Experience we think about 3 personas, they are:

End User Computing Manager
Level 3 Helpdesk Analyst – An Escalation Engineer typically working on wide spread issues and proactive maintenance
Level 1/Level 2 Helpdesk

Configuring Tachyon for Experience

This section will show you how to configure Tachyon to use Experience. 

Confirm Permissions to use Experience

Earlier we assigned a number of roles to different users, in this section we will add the additional role for Experience.

Due to the set up of users in these labs additional roles have been given to our users. you will need to think about what you want your users to be able to do. The roles we are talking about are:

A user who only needs to view Experience so should be assigned (Possibly End User Computing Manager):-
Experience Viewer role

A user who needs to be able to explore devices and issue questions and actions to resolve issues should be assigned (Possibly Level 3 Helpdesk Analyst):-
Experience Viewer
Global Actioner
Global Viewer

A user who needs to be able to explore devices and issue questions to find issues should be assigned (Possibly Level 1/Level 2 Helpdesk):
Experience Viewer
Global Viewer

1ETRNAP
  1. Navigate to Settings – Permissions – Roles.
  2. Click on Experience Viewers then the Members tab
  3. Add the group: Tachyon_Admins

Verify the Installation

In this section we will verify that Experience has successfully installed

1ETRNAP
  1. Open Explorer and navigate to C:\ProgramData\1E\Tachyon

Open Tachyon.Experience.log and note the lines:
Starting experience Server
Processing database 'TachyonExperience'
Cube processing complete

It is possible to increase the frequency with which the Coordinator initiates cube processing by modifying %programfiles%\1E\Tachyon\Coordinator\Tachyon.Server.Coordinator.exe.config to reduce the value and restarting the Tachyon Coordinator service:
<add key="ExperienceCubeProcessingIntervalMinutes" value="10" />

In our lab environment, we will change this value to 10 minutes, the default is 1440 and we do not want to wait a full day for the updates

  1. Open Explorer and navigate to C:\Program Files\1E\Tachyon\Coordinator and open Tachyon.Server.Coordinator.exe.config search for ExperienceCubeProcessingIntervalMinutes and set the Value to 10
  2. Open the Services Applet and restart the 1E Tachyon Coordinator service

Deploy Policies

In order for the clients to report back to Experience, they need to have policies deployed to the environment. 

These are the steps you would need to take in your environment if you are not implementing or using Guaranteed State, although we have installed Guaranteed State we have yet to carry out any configuration, so we will carry out these steps
1ETRNW72
  1. Still logged into 1ETRNW72 as 1ETRN\Manager1
  2. Open the Tachyon Portal and Launch Guaranteed State
  3. Navigate to Administration – Policies.
  4. Click Deploy, and click Yes to the pop up showing the changes since the last deployment

Confirm that Experience has Populated

1ETRNAP
    As part of the installation of Experience a new Cube is created and is used to populate the Experience Data.
  1. From Start open SQL Server Management Studio, and connect to Analysis Services
  2. Expand Databases and confirm TachyonExperience is listed

1ETRNW101
  1. Log on as User
  2. Open the Tachyon Portal in Chrome (if not already open)
  3. Open Experience, either from a tile or via switch app
  4. The page should open on Overview if it has not navigate there
  5. Confirm that data is displayed, The data and how to use the screens is covered in the Using Experience training. (You may need to wait 10 mins since the Coordinator Service restart)
If data is not displayed then carry out the Generate Experience Data section below. BUT only if Data is not displayed

Generate Experience Data

The following steps are not required in a production environment, the data will generate and populate Experience automatically, however the data is bundled and reported back once per day just after midnight, that is not practical for us in the Lab Environment so we will force the update to suit us. This should not be done in a Production Environment, as it would cause duplicated data.
1ETRNAP
  1. Open SkyTap Shared Drive shortcut on the desktop and navigate to 1E Tachyon - Course Content\Tachyon 5.1 Course Content\ download 1ETRN_Code_Signing_cert.pfx files to c:\temp Extract the contents of the ZIP file, also download and copy 1ETRN-GeneratePerfData.xml to c:\temp
  2. From the start menu, type certificate, and click on Manage Computer Certificates
  3. In the Certificates console, right-click on Trusted Publishers. Select All Tasks>Import
  4. On the Welcome, ensure Local Machine is selected by default. Click Next
  5. On the File to Import page, click Browse
  6. Switch the file type to All Files (.)
  7. Navigate to c:\temp and double-click 1ETRN_Code_Signing_cert.pfx. Click Next
  8. On the Password page, input Passw0rd for the password and click Next
  9. On the Certificate Store, ensure Trusted Publishers is populated. Click Next
  10. On the final page, click Finish. Click OK
  11. In the Certificates console, expand Trusted Publishers>Certificates and validate that the code signing cert issued to SCCM Admin is present
  12. From a cmd prompt, run IISRESET to bounce IIS
  13. Running IISRESET will ensure the web service recognizes the certificate we just added to the server
  1. In the Tachyon Portal navigate to Settings – Instructions – Instruction Sets
  2. Click on Upload in the upper right
  3. In the Open dialog box select C:\Temp\1ETRN-GeneratePerfData.xml click Open
  4. Click Add new set on the right to create a New Instruction Set
  5. In the Name field type in 1E-PerformanceGeneration click Add
  6. Click on the Unassigned instruction set – Select all the instruction that you just imported and click move in the far right. Select 1E-PerformanceGeneration in the move instructions popup.
  7. Click Move
1ETRNW71


  1. You should still be logged in as 1ETRN\Tachyon_Admin1
  2. Launch the Tachyon Portal if it is not already open, with Google Chrome. If the Portal is already opened – click on Switch app at the bottom and select Explorer
  3. Click on All Instructions. It will now display the Instruction Sets which we added to Tachyon, and the associated questions and actions.
  4. Select 1E-PerformanceGeneration and choose the GeneratePerfData instruction
  5. Click the Ask this question button
  6. Ensure all 7 machines are reporting inventory back
  7. Remember these steps are not required in a production environment, and is only included here to facilitate the course

Configuring Tachyon for Patch Success

This exercise will show you how to configure Tachyon to use Patch Success. We have already configured our connector to use Tachyon Powered Inventory. We have also already imported the Instruction Set 1E Inventory used by Tachyon Powered Inventory and created the Tachyon Role required and assigned it to the All Devices Management Group.

If we used stand-alone WSUS for Security Updates in our environment we would configure a WSUS connector instead of a Config Man Connector. In order to be used for Patch Success WSUS has to be configured to use SQL (instead of the Windows Internal Database). We also require either patch approvals for WSUS or Deployments for SCCM. This information will be what Patch Success evaluates to determine if a device is fully patched.

Create A Custom Role for Patch Success

We need to create a Patch Success user and role and assign to our All Devices Management Group. We also need to assign permissions to our Patch Success Instruction Set which we imported earlier.

1ETRNW102
  1. Navigate to Settings – Permissions – Roles. Click on Add
  2. In the Add Role dialog box Name field type in 1E Patch Success
  3. Click Add. You will then see the Role in the listing of Roles
  4. Click on 1E Patch Success
  5. In the Role: 1E Patch Success page Permissions tab click on Add in the far right
  6. In the Add Permissions dialog box Type field select Instruction Set. In the Name field choose Patch Success from the drop-down listing. Check the boxes for ActionerApprover, and Questioner. Click Add
  7. If you do not want to trigger a deployment of the patches via Patch Success, then do not add the Actioner and Approver permissions to the role. This will prevent the Deploy button from being enabled in the Patch Success Application.
  8. Click Add again and select Repository:Patch in the type field. Select the box next to Read. Click Add
  9. Click the Management Group tab. Click Add in the far right. Select All Devices. Click Add
  10. Click the Members tab. Click Add in the far right. Start typing in Manager and select Manager1 from the list. Click Add
  11. Navigate to Users and select Manager1 to see that the 1E Patch Success role has been added to that user
  12. Also add the following roles to our Manager1 account to use for Patch Success
  13. Connector Administrators
    Inventory Administrators
    Log Viewers
    Permissions Administrators
  14. Add the 1E Patch Success role to the Tachyon Connector account
  15. If the Patch Success role is not added to our Tachyon Connector account the cube data will not populate the Patch Success Overview page with the Device information. To check this after doing an ETL Sync. Look at the SLA-BI DB EventLog Table on the Tachyon server for the Patch Device Table message (you should see another number than 0 devices).

Tachyon License File Details

To use Patch Success your Tachyon License file must have the Inventory and Patch Success consumers enabled. The license file must also include the pattern for 1E-Inventory* and 1E-PatchSuccess* as these are the names of the instructions that will use for Patch Success. We will look at our lab license file in this task to make sure we are set up correctly.

1ETRNW102
  1. In the Settings application navigate to Configuration – License Information
  2. Within Customer Licence expand Products – expand Features and expand Item 7 and notice that we have PatchSuccess
  3. Expand Consumers expand Item 1 and notice that we are also licensed for the PatchSuccess consumer

Lab Summary

In this lab, we learned how to configure and populate the Experience and Patch Success applications, how to use these applications is covered in the Using - Using Experience and Using - Using Patch Success courses


Next Page

Ex 8 - Tachyon v5.1 - Install and Configure - Post installation optional configuration