Exercise Overview:

Enabling AI Powered Auto-curation after installation of Tachyon

Using the AI Powered Auto-curation feature you'll be able to increase the total amount of normalized software in your Inventory repositories. This is done using AI that integrates with the inventory consolidation process. By using AI your organization will benefit from significant numbers of normalized software and a reduced manual effort needed to normalize software. You can enable AI Powered Auto-curation either during Tachyon Setup or after you've installed Tachyon. During set up we did not select enable AI. We will do that in this exercise.

Confirm Memory requirements

Use the Memory requirements section of the page AI Powered Auto-curation to calculate the physical memory required for AI Powered Auto-curation, the requirement is calculated on the basis of the number of records the AI has to process. In this lab we have already installed Tachyon and so we will use the query listed in the SLA-Data database query section, if we had not installed Tachyon, and we intended to enable AI during Tachyon set up we would use the SCCM Database Query

1ETRNAP
  1. Open SQL Server Management Studio, select the SLA-Data database (expand databases → SLA-Data)
  2. Right click and select New Query, paste and run the following query:
  3. /*SLA query to get number of distinct software titles from SLA-Data database*/
    USE [SLA-Data]
    CREATE TABLE #Software
           (
                  [SoftwareID]                      INT IDENTITY(1,1) PRIMARY KEY,
                  [DataSource]                      NVARCHAR(255) COLLATE DATABASE_DEFAULT,
                  [SoftwareIdent]                   NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
                  [SoftwareIdent_Hash]              VARBINARY(128),
                  [Vendor]                          NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
                  [Vendor_Hash]                     VARBINARY(128),
                  [Title]                           NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
                  [Title_Hash]                      VARBINARY(128),
                  [Version]                         NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
                  [Version_Hash]                    VARBINARY(128),
                  [ColloquialVersion]               NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
                  [ColloquialVersion_Hash]          VARBINARY(128),
                  [Edition]                         NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
                  [Edition_Hash]                    VARBINARY(128),
                  [NormalizedProductID]             INT
           );
    SELECT * FROM #Software
    EXEC [usp_ReportDataEx_se] 1, N'Software', N'#Software';
       
    SELECT count(*) AS 'Distinct Software Titles'
    FROM
    (
    SELECT DISTINCT [Title] FROM #Software
    ) a
     
    DROP TABLE #Software
  4. Read the number of Distinct Software Titles
  5. On the AI Powered Auto-curation page, read off the Extra GB RAM for AI engine information for the number of Distinct Software Titles (it should be 15GB)
  6. The minimum total disk space required for the downloaded AI Package ZIP is approximately 12.5 GB at installation. This includes:

    • Binary and support files for AI and the directory structure is 8 GB
    • AIPackage ZIP file is 4 GB

    While the downloaded AI Package is 5 GB, the unzipped contents are approximately 12.5 GB and are extracted to C:\ProgramData\1E\SLA Platform\AI\

    Please note, the required disk space reduces to 8.2 GB after the first Catalog sync with the cloud. During the sync a check is made for any newer AI packages. If there is one, it's downloaded and a hash check of the ZIP file is made to make sure it's not corrupted. Once all checks are complete, the AI Package ZIP is deleted from C:\ProgramData\1E\SLA Platform\AI\ leaving an 8 GB disk space requirement.


    In your own environment you would now need to follow whatever process exists to add the additional RAM, and any additional disk space this has already been done in the Lab environment

Enable AI Powered Auto-curation

We have confirmed the pre requisites and now we will enable AI

1ETRNW102

  1. Log onto 1ETRNW102 as Tachyon_AdminPP
  2. Open the Tachyon Portal and navigate to: Settings → Configuration → Components
  3. On the row with an entry in the Name field of AIEngine, slide the slider to enable it
  4. A message will be displayed to confirm this has been enabled
  5. Enabling AI will now cause the download of the AI model file from the Catalog Cloud server. This will take some time to complete. To speed up the download in the lab env restart the 1E Catalog Update Service

Verify AI Auto-curation is working

Once enabled the following steps should be followed to verify that AI is working. 

The AI feature consists of an 1E-AIEngine.exe and AI model files contained in an AIPackage_<version>.zip. The 1E-AIEngine.exe uses the associated AI package files to run the AI. Because of the size of the package, it initially resides on the Catalog cloud to reduce the installer size. 

When the AI feature is enabled:

  • 1E Catalog checks that it has the latest AI package synced from the 1E Catalog cloud. This is downloaded and saved in: C:\ProgramData\1E\Catalog\CatalogSynchronization\PredictionModel
  • Tachyon Inventory checks with 1E Catalog that it has the latest AI package ZIP which is then unzipped to:  C:\ProgramData\1E\SLA Platform\AI

1ETRNAP
  1. Logged in as 1etrn\Appinstaller
  2. Navigate to C:\ProgramData\1E\Catalog\
  3. Open the Catalog.UpdateService.log

  1. The log file will have entries that looks like the text highlighted, in particular confirm that there are entries for: Syncing AI Package with cloud, Downloading AI Package, Download Complete and Successfully Synced AI Package
  2. The version numbers may be different in your example

[Info] T13 2020-08-10 10:57:22.519: Pulling records from url https://catalog.1e.com/ for memberGuid 65335867-97A8-4006-B0C1-EAB20C4894C0 with lastPullTime 17-06-2020 11:56:41
[Info] T14 2020-08-10 10:58:05.369: No content recieved for ApiVersion 6.
[Info] T14 2020-08-10 10:58:05.376: Getting queue API versions.
[Info] T14 2020-08-10 10:58:05.416: No sync content was processed.
[Info] T13 2020-08-10 10:58:05.732: Pull operation ended, took 43288 ms
[Info] T13 2020-08-10 10:58:05.741: Push operation started
[Info] T14 2020-08-10 10:58:42.362: MemberGuid 65335867-97a8-4006-b0c1-eab20c4894c0, Sent 3 entries for ProductMatch
[Info] T10 2020-08-10 10:58:43.927: Successfully pushed 3 site defined records.
[Info] T10 2020-08-10 10:58:46.773: Updated last push time to 07-08-2020 14:33:24.373
[Info] T13 2020-08-10 10:58:46.790: Push operation ended, took 41048 ms
[Info] T13 2020-08-10 10:58:46.810: Syncing AI Package with cloud
[Info] T13 2020-08-10 10:58:47.043: Started Executing SQL
[Info] T13 2020-08-10 10:58:47.056: Completed Executing SQL
[Info] T13 2020-08-10 10:58:47.060: Downloading AI Package version 1.3.0.701 with cloud of size 4804669391 from url api/sync/aiengine?Version=1.3.0.701
[Info] T13 2020-08-10 10:58:47.090: Indexes re-creation started after Sync.
[Info] T3 2020-08-10 11:02:39.775: Download complete. Comparing file hash..
[Info] T3 2020-08-10 11:03:28.849: Successfully synced AI Package version 1.3.0.701 with cloud
[Info] T3 2020-08-10 11:03:28.860: Model ID for which prediction result data to be deleted :1
[Info] T3 2020-08-10 11:03:28.860: Started Executing SQL
[Info] T3 2020-08-10 11:03:28.872: Completed Executing SQL
[Info] T3 2020-08-10 11:10:31.023: Indexes are created successfully after Sync.

  1. Navigate to C:\ProgramData\1E\Catalog\CatalogSynchronization\PredictionModel and confirm a file exists in the format AIPackage_x.x.x.xxx.zip

When enabled, a new action called Process AIEngine is created. This is automatically run after the Sync Data action for a supported connector. The sync time for the Process AIEngine  action depends on the number of distinct software records being processed, hardware and environment configuration. We will now confirm that the action exists and run a sync.


1ETRNW102
  1. Log onto 1ETRNW102 as Tachyon_AdminPP
  2. Open the Tachyon Portal and navigate to: Monitoring → Process Log 
  3. Click on Execute
  4. On the Execute action, select the following and click Execute:

    Repository: Default Inventory
    Action: Sync Data - Config Mgr
    Run AI action:  check
  5. The Sync will now take place, monitor, and confirm that an action: Process AI Engine is now listed and runs (this may take some time)

Telemetry Configuration/Reconfiguration

The feature is enabled by default but may be disabled using Tachyon Setup during installation or upgrade. 1E encourages customers to enable sending telemetry, to help us build better products. By default, Tachyon collects data continuously and sends a compressed and encrypted summary by email to 1E every Friday at 23:40 UTCIf you have disabled the Tachyon email feature then telemetry will not be sent to 1E.

There are two types of Telemetry, Server and User Interface, 

Server telemetry reports how the platform is used and data is compressed, encrypted and sent to 1E through email on a configurable schedule. Tachyon stores its automated Telemetry configuration in the <INSTALLDIR>\Tachyon\Coordinator\Tachyon.Server.Coordinator.exe.config file. After any changes reboot the server or restart the 1E Tachyon Coordinator service. Changes to the Telemetry configuration do not affect the data exported into an unencrypted CSV file by the Export Telemetry button on the Settings → System information screen

User Interface telemetry reports how the user interface is used and data is sent directly from administrator browsers to the 1E Cloud.

Export Telemetry data

The Export telemetry button triggers a telemetry collection process and exports a CSV file. The contents of the file are not encrypted. Details of 1E product usage statistics gathered by Tachyon to help with 1E's continued product improvement initiative. Tachyon will periodically send summarized, statistical information about usage of the product to 1E. This enables 1E to improve your experience with Tachyon as it helps us understand how features are being used, focus future development, ensure we continue to support the Operating Systems you currently use, spot early warning signs of potential issues and identify instructions that may be causing issues or could be improved. No personally identifiable data is collected. The data is compressed, encrypted and sent to 1E through email.

1ETRNW102
  1. Still logged on as Tachyon_AdminPP open the Tachyon Portal and navigate to Settings →  System information
  2. Click the Export telemetry button in the top right of the screen.
  3. Open the downloaded TachyonTelemetry-yyyy-mm-dd.csv in WordPad and review the data listed.

  4. At a high level, the following data is collected:

    • Instruction usage (by Instruction Definition and by day), and statistics on the type of resources attached to Instruction Definitions
    • 1E Client configuration details, versions, operating system variants, device types, age of installation, last connected time and status, and time zones
    • Registered Tachyon Portal applications and Tachyon Consumers
    • Database table sizes
    • Tachyon server component information and basic configuration
    • (Anonymized) Management Group information (number of devices)
    • Tachyon upgrade history

Change Server Telemetry email frequency

The time and frequency of when Telemetry is sent to 1E is changed by editing the Telemetry line.

1ETRNAP
  1. Open the C:\\Program Files\1E\Tachyon\Coordinator\Tachyon.Server.Coordinator.exe.config file search for: Telemetry
  2. Replace the 40 23 and the 5 in the string below:
  3. <add key="Telemetry" value="40 23 * * 5 SendTelemetryStats" />
    The numbers that you see after value is a crontab schedule expression. The schedule. 40 23 * * 5 means "at 23:40 hours on every day of the month, every month of the year, and on the 5th day of the week (Friday)". In other words, this configuration sends the telemetry data once per week on Friday nights.
  4. Having read the point above change the data to make the schedule run in the next 10 minutes, so if the current time is 09:45 on Tuesday then the line would read: <add key="Telemetry" value="55 09 * * 2 SendTelemetryStats" />
  5. Save and close the file
  6. Open the Services applet and restart the Tachyon Coordinator service

Disable/Enable Server Telemetry

Telemetry emails can be disabled by changing "Telemetry" to "DISABLED". To enable them, change it back to "Telemetry".

1ETRNAP
  1. Open the C:\\Program Files\1E\Tachyon\Coordinator\Tachyon.Server.Coordinator.exe.config file search for: Telemetry
  2. Replace the word Telemetry with DISABLED in the following line:
  3. <add key="Telemetry" value="40 23 * * 5 SendTelemetryStats" />
  4. Save and close the file
  5. Open the Services applet and restart the Tachyon Coordinator service

Enable/Disable User interface Telemetry

The User interface Telemetry is configured in the Tachyon Master database. 

1ETRNAP
  1. Open SQL Server Management Studio, select the TachyonMaster database (expand databases → TachyonMaster)
  2. Expand Tables and navigate to GlobalSetting
  3. Right click and select edit top 200 rows
  4. Locate the entry whose Name is UITelemetryLevel, it is currently set to 0 (as we left it to Off during Tachyon Setup), To choose what data is sent to 1E change the value to one of the below.
  5. 0 - Off
    1 - Anonymous
    2 - License Name 
    3 - License Name and Unique user ID

    The change takes effect for each user when they close and reopen their browser to connect to the Tachyon Portal.

    License Name is Customer name as it appears in the Tachyon license file and License information page.

    Unique user ID is a random ID number representing an individual user.

Direct based Management Groups

Direct based Management Groups

These use scripts to create management groups by importing lists of devices using FQDN names only - once created these appear in the Management groups page marked with a DB icon.

This type of Management group has no associated rules and cannot be edited and evaluated from the Management groups page.

Create Direct-based management groups from a file


1ETRNW102
  1. Create a folder in C:\temp named DeviceFolder
  2. Launch the SkyTap Shared Drive shortcut from the desktop and download from 1E Tachyon - Course Content\Tachyon v5.2 - Course Content\ the file Create-DirectManagementGroupUsingFile.ps1 to C:\Temp\DeviceFolder
  3. Create a text file in c:\temp\DeviceFolder named ManagementGroup - From File.txt
  4. The file name should be the same as the management group name, and if a management group already exists with the same name, the script will delete and recreate it, only with the new devices provided.
  5. Opent the txt file and enter some text to act as the Management Group Description in first line
  6. Enter the following Device FQDN from line two onwards, one device per line, then save the file:

    1ETRNW71.1etrn.local
    1ETRNW73.1etrn.local
    1ETRNW101.1etrn.local

  7. Optionally add more files if you want to create multiple management groups
  8. Open Powershell and navigate to c:\temp\DeviceFolder and execute the following command line
  9. .\Create-DirectManagementGroupUsingFile.ps1 -TachyonApiBaseUrl https://tachyon.1etrn.local -FolderPath C:\Temp\DeviceFolder
    There is an additional parameter -UseCustomCredentials, we are not using this here as this user has the rights to create Management Groups in Tachyon
  10. The management group is then created, from what you learned earlier confirm the group contains the correct members

Create Direct-based management groups from a Configuration Manager collection

1ETRNCM
  1. Log onto 1ETRNCM as SCCMAdmin
  2. Create a folder in C:\temp named CollectionFolder
  3. Launch the SkyTap Shared Drive shortcut from the desktop and download from 1E Tachyon - Course Content\Tachyon v5.2 - Course Content\ the file Create-DirectManagementGroupUsingCmCollection.ps1 to C:\Temp\CollectionFolder
  4. Create a text file named CollectionData.txt which will be passed as a parameter in PowerShell script.
  5. In the file enter the following as a comma separated single line: Collection name, Management Group Name, Management Group Description. Use the following data:
    Windows 7 Devices, Windows 7 Devices from CM Collection, All the Windows 7 devices in the Windows 7 Devices CM Collection
  6. You could optionally enter more lines in the same format if you want to create multiple management groups 
  7. Open Powershell and navigate to c:\temp\CollectionFolder and execute the following command line
  8. .\Create-DirectManagementGroupUsingCmCollection.ps1 -TachyonApiBaseUrl https://tachyon.1etrn.local -FilePath C:\Temp\CollectionFolder\CollectionData.txt -UseCustomCredentials
  9. You will be prompted for credentials, as SCCMAdmin does not have the rights in Tachyon to create Management Groups, enter Tachyon_Adminpp and Passw0rd in the credentials popup
  10. The management group is then created, from what you learned earlier confirm the group contains the correct members

Confirming Creation of Management Groups

Confirm Management Group Creation

After running the script you will find a log file is created in the same directory where the  Create-DirectManagementGroupUsingFile.ps1 is located. Additionally, when the direct-based management groups are added to Tachyon some reports will run to enable the management groups to be used.

If more than one direct-based management groups are being added you will see two Management Group Evaluation reports run on the default Inventory repository. You will also see an additional Management Group Evaluation report run on each additional non-default inventory repositories you have in your system.

If you have Application Migration installed you will also see two Application Migration Consolidation reports run on the default ApplicationMigration repository.

1ETRNW102
  1. Open the log file in the C:\Temp\DeviceFolder and view the entries, there should be no errors
  2. Open the Tachyon Portal and navigate to the Settings Application, and then to Monitoring → Process Log
  3. Confirm that entries exist for Management Group Evaluation against the Default Inventory Repository and also as Application Migration is installed an entry for Management Group Evaluation against the Default Application Migration Repository



Changing the Branding

Change Values

The Branding page lets you customize the appearance of the Tachyon Portal and emails to match your corporate style. 

1ETRNW102
  1. Still logged on as Tachyon_AdminPP open the Tachyon Portal and navigate to Settings → Configuration → Branding
  2. Set the Company name to be: ACME
  3. Amend the Portal description to read: The corporation you can trust
  4. Launch the SkyTap Shared Drive shortcut from the desktop and download Company_Logo.png and Email_Logo.png from 1E Tachyon - Course Content\Tachyon v5.2 - Course Content\ to C:\Sources
  5. In the Company logo area, click Browse and navigate to C:\temp and select the Company_Logo.png
  6. In the Email banner area, click Browse and navigate to C:\temp and select the Email_Logo.png
  7. Click Save and refresh the browser, navigate to the landing page you will see the new logo and description applied,
  8. Choose an application, then click on Switch app, the new Company logo is shown next to the text
  9. Choose an application, then click on Switch app, the new Company logo is shown next to the text
  10. Choose an application, then click on Switch app, the new Company logo is shown next to the text
1ETRNW71
  1. Still logged on as Tachyon_Admin1 open the Tachyon Portal and navigate to Explorer
  2. Run the Tachyon Verification Stage 2 Instruction
  3. Enter the Password when prompted
  4. Open Windows Live Mail and view the Authentication email, confirm it has the email_logo.png showing
  5. This does not need to be approved, allow the instruction to time out, this was just to confirm the change of email logo

Reset to Default Branding

If at any time you want to revert Tachyon to using the default logos and text.

1ETRNW102
  1. Still logged on as Tachyon_AdminPP open the Tachyon Portal and navigate to Settings → Configuration → Branding
  2. Click on the Reset button to display the Update - Branding popup
  3. Clicking on Yes, Reset & Save resets the fields of the Branding page to their default 1E values.
  4. To view the reset you will need to refresh the browser again.
  5. Carry out the steps in the change values section to confirm the changes have reverted

Lab Summary

In this lab, we learned how to enable AI Powered Auto-curation post install of Tachyon, we checked the pre requisites, and enabled AI, we then checked the log files and the file location to confirm that the package had downloaded, if you take the Using Inventory module, you will see AI in operation. We also looked at the Telemetry data and how to amend the schedule and disable the sending of data. We also created Direct Based Management Groups, from both a file and a ConfigMgr Collection. Finally we re branded and then reset the branding.