To run these tests you need:
- Tachyon Server installed
- Remote workstation with a supported browser
- The name and password for the server installation account
- the AD account must be enabled
- the account may already be assigned to other Tachyon roles either directly or via membership of an AD group role.
- Two AD User accounts, Test User 1 and 2
- must not be existing Tachyon users because they will be assigned specific roles for the purpose of these tests.
- must have email addresses and be able to read emails.
- The 1E-TachyonPlatform.zip product pack file containing the Tachyon Verification instructions, if not already installed. In these tests this file is referred to as the Tachyon Verification product pack.
- At least one test device on which the Tachyon Agent will be installed
- Tachyon Agent installation source files and configuration details required by your Tachyon implementation
Verify Server Installation
To run the following tests you need:
- Tachyon Server installed
- The name and password for the server installation account, the account must also be enabled
Ref | Test | Expected | Remediation | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
TCNI01 |
| Programs and Features displays 1E Tachyon Server with correct 3 part version number. If an MSP update has been installed, the Installed Updates displays 1E Tachyon Server Update (Qnnnnn). The following Windows services exist and are running.
The Switch Host service has a delayed start. | If any of the Tachyon services is not running, then check the corresponding log(s). The Switch Host service will stop after several seconds if it is unable to start any Switches. The ConsumerAPI log is not created until a user (the server installation account) successfully connects to the Explorer portal. The BackgroundAPI log is not created until an Agent attempts to download an Agent resource. The Tachyon Verification Product Pack can be used to trigger this. | ||||||||||||||||||
TCNI02 |
|
The default location for all Tachyon Server logs is the folder Please refer to Services and NTFS Security if changing the location of log files. In this version of Tachyon Server, the installer does not support the LOGPATH property and the logs folder is not configurable during installation. Each component has a configuration file in the Tachyon Server installation folder structure, which contains log configuration details. Defaults are:
Switch logs have the following names:
Tachyon server components use the log4net RollingFileAppender class. Details can be found in http://logging.apache.org/log4net. |
Verify IIS Security of the Tachyon Web site
To run the following tests you need:
- Tachyon Server installed
- The name and password for the server installation account, the account must also be enabled
- Remote workstation with a supported browser
Ref | Test | Expected | Remediation |
TCNI03 |
| Successful connection to the Tachyon Explorer portal. The ability to navigate around the Explorer portal will depend on which Tachyon roles have been assigned to the logged-on account. The server installation account is able to view the following Administration menu pages:
| Ensure the server installation account is enabled to do this test. It has the necessary rights to access Tachyon as well as NTFS rights on the Tachyon Server. 401 'Unauthorized' Typically, the website also prompts you to provide an account and password. This may occur if you are using invalid credentials or an account in a domain that is not trusted by the Tachyon Server. 403 'Access denied' When you use a browser to connect to the Tachyon Explorer you will see Server Error 403 - Forbidden: 'Access denied' if your AD account does not have read access to the Tachyon web application folders:
This can happen if Tachyon is installed in a non-default location and the NTFS permissions on the installation folder are not correct. To remedy the issue, you should review and correct NTFS permissions as described in Services and NTFS Security. 404 'File or directory not found' Is the URL you entered correct, and have the correct spelling? Is the corresponding web application installed? For example, the Registration Service may not be installed. Contact system administrator to get access When you use a browser to connect to the Tachyon Explorer and you see a message Contact system administrator to get access, it means your AD account is not a Tachyon user. Try using an AD account that you know is a Tachyon user that is assigned to a Tachyon system role or custom role. For example, use the server installation account which is automatically installed as a Tachyon user. For a new installation, the server installation account must be used to add other Tachyon users before their AD accounts can be used to access the Tachyon Explorer. This process is described in The Permissions page and is used in the following TCNU verification tests. |
TCNI04 |
| The web browser will respond with the Version number of the Tachyon server (IE will download as a JSON file, other browsers will display a response in XML format). Confirm the Version number is as expected. | |
TCNI05 |
| The web browser will respond with 'You have reached Tachyon background API.' (IE will download as a JSON file, other browsers will display a response in XML format). | |
TCNI06 |
| The web browser will respond with 'You have reached Tachyon Registration Service.' (IE will download as a JSON file, other browsers will display a response in XML format). | |
TCNI07 |
| The expected response is 'Server Error 403 - Forbidden: Access is denied'. For security reasons, access to the these web applications are allowed for local users and services only, and denied to remote devices. If the response is 'You have reached Tachyon Core API' then there is an issue with IIS configuration. Or, you are using a browser on the actual Tachyon Server, and should do the test on a remote workstation. | Access Allowed It should not be possible for a remote web browser to have access to the following web applications:
If access is possible then it is probable that the IIS role feature IP Address and Domain Restrictions is not installed on the Tachyon Server. This version of the Tachyon Server installer does not check for this prerequisite. You must ensure this IIS feature is installed, as described in the troubleshooting IIS Issues page. |
TCNI08 |
| ||
TCNI09 |
| When accessed from a server on which the Registration Service is installed the web browser will respond with the Version number of the Tachyon server (IE will download as a JSON file, other browsers will display a response in XML format). When accessed from any other device the expected response is 'Server Error 403 - Forbidden: Access is denied'. | Access Allowed In order for the Registration service to access the Authentication service, the Authentication web application requires its IP Address and Domain Restrictions to be configured with the IP address(es) of the Registration server. |
Verify User Rights Assignment
To run the following tests you need:
- Tachyon Server installed and above TCNI verification tests passed
- The name and password for the server installation account, the account must also be enabled
- Two AD User accounts, Test User 1 and 2
- must not be existing Tachyon users because they will be assigned specific roles for the purpose of these tests.
- must have email addresses and be able to read emails.
- The Tachyon Platform product pack, if not already installed
1E is oftne asked why the Verification
Ref | Test | Expected Response | Remediation |
TCNU01 |
| For a new Tachyon installation, the Instruction sets page will not contain any instruction definitions. After adding the Tachyon Verification product pack, the two instructions contained in the product pack will be displayed on the Product packs page. After creating the Tachyon Verification instruction set this will appear in the Instruction sets list. After moving the verification instructions from Unassigned to the Tachyon Verification instruction set, the instruction count for the Tachyon Verification instruction set will go up by 2. | If the server installation account is not able to add instructions from a product pack, then the installation account is not assigned to the Instruction Set Administrators role. You can confirm if this is the case by viewing the rights of the server installation account in the Administration Permissions page. You may have upgraded Tachyon from a previous version where the server installation account was not automatically assigned to this role. Contact 1E for advice on how to fix this. |
TCNU02 |
| Searching returns lists of user and groups. Selecting a group and viewing its members shows the Name and Email of each member. | The purpose of this step is to confirm the system is capable of searching Active Directory. You do not need to add the group; you will add users in the next step. The ability to search and find different types of AD security group depends on the search method selected during installation of the Tachyon Server, as described in Design considerations - Active Directory Security Groups.
|
TCNU03 |
| The following custom role exists:
The following users are included in the list of Users.
| |
TCNU04 |
| Each Test User is able to view the following menu pages:
| Contact system administrator to get access When you use a browser to connect to the Tachyon Explorer and you see a message Contact system administrator to get access, it means your AD account is not a Tachyon user. Try using an AD account that you know is a Tachyon user that is assigned to a Tachyon system role or custom role. For example, use the server installation account which is automatically installed as a Tachyon user. For a new installation, the server installation account must be used to add other Tachyon users before their AD accounts can be used to access the Tachyon Explorer. This process is described in The Permissions page. 403 'Access denied' When you use a browser to connect to the Tachyon Explorer you will see Server Error 403 - Forbidden: 'Access denied' if your AD account does not have read access to the Tachyon web application folders:
This can happen if Tachyon is installed in a non-default location and the NTFS permissions on the installation folder are not correct. To remedy the issue, you should review and correct NTFS permissions as described in Services and NTFS Security. |
Verify Agent Installation
To run the following tests you need:
- Tachyon Server installed and above TCNI verification tests passed
- Two AD User accounts, Test User 1 and 2 and above TCNU verification tests passed
- At least one test device on which the Tachyon Agent will be installed
- Tachyon Agent installation source files and configuration details required by your Tachyon implementation
Ref | Test | Expected Response | Remediation |
TCNA01 |
| Tachyon Agent installed. Programs and Features displays 1E Tachyon Agent.
If an MSP update has been installed, the Installed Updates displays 1E Agent Update (Qnnnnn). | The first Agents can be installed manually or using a script. You should repeat this set of tests when you have deployed a few Agents using your organization's preferred deployment method. You may need to edit the Agent configuration file after installation, to suit the requirements of your implementation, and restart the Agent service. |
TCNA02 |
| The following Windows services exist and are running.
| If the 1E Tachyon Agent service is not running, then check the Agent log. |
TCNA03 |
| No errors. | Check the Switch setting in the Agent configuration file is using the correct DNS Alias for the Tachyon Server, and correct port for the Switch. If errors in the Agent log relate to certificates then see Configuration issues. |
TCNA04 |
| Each Test Device is listed in the Tachyon Devices Table page. The device details shows information about the device's system, activity, certificate and configuration settings. | If you cannot use the Test User 1 or 2 accounts then use another Tachyon user account. All Tachyon users are able to view the Tachyon Devices Table page. Check the configuration of the Agent and review the Switch setting in the Agent configuration file. |
Verify Agent Server Communications
To run the following tests you need:
- Tachyon Server installed and above TCNI verification tests passed
- At least one test device has Tachyon Agent installed and above TCNA verification tests passed
- Two AD user accounts configured as Tachyon users and above TCNU verification tests passed
To run the following tests you need to logon to a workstation with a user account that is assigned to at least one of the Tachyon administration roles.
Ref | Test | Expected Response | Remediation |
TCNA01 | See TCNA01 above. | Each Test Device is listed in the Tachyon Explorer Devices page. | |
TCNA05 |
| When the Tachyon Platform verification stage 1 question is asked, the Explorer view changes to the Instruction History Responses page. The Instruction History Responses page lists the software products installed on each Test Device. Contents are shown for online Devices that have the Tachyon Agent installed and running. If you view other Explorer pages and want to get back to the Instruction History Responses page, then you should select Instruction History from the navigation menu on the left side, and you should see a list of the instructions that have been run. You may then click on the name of the instruction to view its responses. The Agent log indicates:
| You may need to refresh the Instruction History Responses page. Verification stage 1 tests communication between the Agent and Switch. Any issues will appear in the Agent log. Check each test device has the Tachyon Agent running and is online. |
TCNA06 |
| If Two-Factor authentication (2FA) is enabled then Explorer will prompt for an authentication code, and Test User 1 should receive an authentication code by email, and on their mobile device if the Tachyon App has been installed and correctly registered. The Explorer view changes to Instruction pending approval. Test User 2 should receive an email asking for approval. | This stage of the Verification tests communication between the Tachyon Server and the SMTP relay/gateway. If 2FA is enabled and Test User 1 does not receive an email with the authentication code, then:
If Test User 2 does not receive an email, then:
|
TCNA07 |
| When clicking on the link in the request for approval email, a browser should open automatically and take you to the Notifications page. You can view notifications and approval request at any time by clicking on the notification icon. The icon will show the number of actions pending approval by the logged on user. When the request is approved by Test User 2:
| If Test User 2 is unable to approve the request, then:
|
TCNA08 |
| Response details show a list of devices and their Agent configuration details. You may need to refresh the Details page. This stage of the Verification tests the Agent's connection to the Background Channel. Successful execution of the action will cause the following to appear in the Agent log:
You may have to wait up to 5 minutes for the action to complete on each device. This is because the default Agent setting for DefaultStaggerRangeSeconds=300. | Check the BackgroundChannelUrl setting in the Agent configuration file is using the correct URL for the Background Channel on the Tachyon Server. Repeat test TCNI05 using a browser on the test device. |
Verify Extended Features
To run the following tests you need:
- all the above tests completed
- to logon to a workstation with a user account that is assigned to at least one of the Tachyon administration roles
Ref | Test | Expected Response | Remediation |
TCNX01 |
| This test verifies BCP has been installed on the Tachyon Server, and an Export share is correctly configured, as described in Tachyon Server post-installation tasks - Configure the Tachyon Server to support the Export all responses feature. When you stop the question or wait for the question to complete its gather duration, then the Export all results button will be enabled. TSV is a tab-delimited text file. | If you see a popup error initiating export operation after clicking on the Export All results button, then
|