Verifying
Links to other 1E product documentation to verify or troubleshoot their features that are dependent on the 1E Client.
1E platform: Verifying.
Content Distribution: Troubleshooting.
PXE Everywhere: Verifying.
Shopping: For customers with a maintenance contract.
NightWatchman Enterprise: For customers with a maintenance contract.
General verification of the 1E Client
Confirm the 1E Client service is running.
Ensure you know which client features are enabled - review the <INSTALLDIR>\1E\Client\1E.Client.conf file.
Review the log files for errors.
1E Client logs on Windows%ALLUSERSPROFILE%\1E\Client\1E.Client.log (used by 1E Client and Tachyon features, and Shopping client) %ALLUSERSPROFILE%\1E\Client\NomadBranchUninstall-YYYY_MM_HHTMM_HH_SS_000Z.log 1E Client logs on macOS/Library/Logs/1E.Client.Daemon.log (shows any service start errors) /Library/Logs/1E.Client.log (shows the current operation of the 1E Client) 1E Client logs on other non-Windows platforms/var/log/1E/Client/1E.Client.log |
Nomad client log%ALLUSERSPROFILE%\1E\NomadBranch\LogFiles\NomadBranch.log |
PXE Everywhere Agent log%ALLUSERSPROFILE%\1E\PXEEverywhere\PXEEverywhere.log |
Shopping WSA client log%ALLUSERSPROFILE%\1E\Client\WSA.log |
WakeUp client log%ALLUSERSPROFILE%\1E\Agent\WakeUpAgt.log |
Note
By default, Windows resolves %ALLUSERSPROFILE% as C:\ProgramData\
Verify 1E Client installation
To run the following tests you need:
1E Server installed and TCNI verification tests passed, refer to Verify 1E Server installation for details.
Two user accounts, Test User 1 and 2 , and above TCNU verification tests passed, refer to ??? for details.
At least one test device on which the 1E Client will be installed.
1E Client installation source files and configuration details required by your 1E implementation.
Ref | Test | Expected Response | Remediation | ||||||||
TCNA01 |
| 1E Client installed. Programs and Features display 1E Client.
If an MSP update has been installed, the Installed Updates displays 1E Client Update (Qnnnnn). | The first clients can be installed manually or using a script. You should repeat this set of tests when you have deployed a few clients using your organization's preferred deployment method. You may need to edit the 1E Client configuration file after installation, to suit the requirements of your implementation, and restart the 1E Client service. | ||||||||
TCNA02 |
| The following Windows services exist and are running.
| If the 1E Client service is not running, then check the Client log. | ||||||||
TCNA03 |
| No errors. To view LOG file locations for each OS platform, click to expand... 1E Client logs on Windows%ALLUSERSPROFILE%\1E\Client\1E.Client.log (used by 1E Client and Tachyon features, and Shopping client) %ALLUSERSPROFILE%\1E\Client\NomadBranchUninstall-YYYY_MM_HHTMM_HH_SS_000Z.log 1E Client logs on macOS/Library/Logs/1E.Client.Daemon.log (shows any service start errors) /Library/Logs/1E.Client.log (shows the current operation of the 1E Client) 1E Client logs on other non-Windows platforms/var/log/1E/Client/1E.Client.log | Check the Switch setting in the Client configuration file is using the correct DNS Alias for the 1E Server, and the correct port for the Switch. If errors in the Client log relate to certificates, then see Client issues. | ||||||||
TCNA04 |
| Each Test Device is listed on the Tachyon Devices Table page. The device details show 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 1E user account. All 1E users are able to view the Devices Table page. Check the configuration of the client and review the 1E client settings in the 1E Client configuration file. To view CONF file locations for each platform, click to expand... The 1E Client is controlled via the 1E Client configuration file 1E.Client.conf which resides in the installation folder along with the 1E Client executable. The default installation location used for the different OS supported by the 1E Client are given in the following table:
NoteThe configuration file uses ASCII encoding. A comment line starts with the # symbol. |
Verify 1E client-platform communications (stage 1 and 2 instructions)
To run the following tests you need:
1E Server installed and above TCNI verification tests passed, refer to Verify 1E Server installation.
At least one test device has 1E Client installed and above TCNA verification tests passed, refer to Verify 1E Client installation.
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 1E administration roles. 1E Tachyon Platform Product Pack describes the purpose of each of its verification instructions.
Ref | Test | Expected Response | Remediation |
TCNA01 | See TCNA01 above. | Each Test Device is listed on the Endpoint Troubleshooting Devices page. | |
TCNA05 |
| When the Tachyon Platform verification stage 1 question is asked, the 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 1E Client installed and running. If you view other Endpoint Troubleshooting 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 Client log indicates:
| You may need to refresh the Instruction History Responses page. Verification stage 1 tests communication between the 1E Client and Switch. Any issues will appear in the Client log. Check each test device has the 1E Client running and is online. |
TCNA06 |
| If Two-Factor authentication (2FA) is enabled, then Endpoint Troubleshooting will prompt for an authentication code, and Test User 1 should receive an authentication code by email. Endpoint Troubleshooting 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 1E 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 requests 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 Client configuration details. You may need to refresh the Details page. This stage of the Verification tests the Client's connection to the Background Channel. Successful execution of the action will cause the following to appear in the Client log:
You may have to wait up to 5 minutes for the action to complete on each device. This is because the default 1E Client setting for DefaultStaggerRangeSeconds=300. | Repeat test TCNI05 using a browser on the test device to confirm the Background Channel has been configured correctly, refer to Verify IIS security of the 1E website. A common error is an incorrect value for the BackgroundChannelUrl setting in an 1E Client configuration file. If you deployed the 1E Client using a software deployment tool like Microsoft's ConfigMgr then look to see if similar devices have the same issue. Check the 1E Client configuration file on problem devices to see if the setting has the correct URL for the Background Channel. Check to see if the Background Channel has the scripts used by the Stage 2 instruction. Review the contents of C:\ProgramData\1E\Tachyon\Content folder on the server hosting your Background Channel. The Content folder should contain a folder named 1E Tachyon Platform-VerificationStage2 which contains a sub-folders with a PowerShell file, and another subfolder containing a bash and a perl files. |