Summary

A general methodology for investigating issues with Nomad server components and 1E Client, as well as identifying key issues and their resolutions.

For known issues relating to specific components please refer to their troubleshooting pages:

1E Support contact details

Support Web portal

Maintenance support customers can log onto the 1E Support Web Portal at http://1eportal.force.com using their login details provided with their maintenance contract. This provides issue tracking, product hotfixes and knowledge base articles related to each product.

Telephone support

Maintenance support customers can contact the technical support department at 1E through the following support numbers for the US and UK. Just phone the relevant number for your area so your call can be routed quickly and efficiently to the correct support group:

US: 1-866-349-4032

UK: 0208 326 3499

Email support

Maintenance customers can use the following email for additional support:

support@1e.com

For customers evaluating Nomad

If you are evaluating Nomad, please contact 1E Support by email on support@1e.com

The technical support process

  1. Read through the Troubleshooting pages to see if there are known issues, or quick resolutions to any problems you may have encountered. 
  2. Maintenance support customers can use the 1E Support Web Portal to review knowledge base articles and download hotfixes. 
  3. If still encountering problems, create a technical report (log files and details) and then contact the 1E technical support team.

Creating a technical report

If possible, please obtain the following details and log files before contacting 1E, to include in your technical report.

Version details

  • The OS, version number and patch level for:

    • Tachyon Servers

    • 1E Client

    • Configuration Manager - if used

    • Other 1E Server software, for example Shopping, Nightwatchman and WakeUp

  • For Nomad and Shopping, please provide OS, version number and patch level for:
    • Configuration Manager DPs
    • Nomad extensions used on Configuration Manager Consoles
    • ActiveEfficiency Server

Environmental details

  • If there were any recent changes made to your configuration
  • The name of the machines, Configuration Manager Application and/or Package IDs for when the issue occurred

Problem details

  • When did the issue occur, ensure log files cover this period
  • The scope of the issue – did it affect a particular geographical location, group of users or client machines
  • Details of any self-help troubleshooting steps you carried out
  • In the event of a service crash or if you are experiencing high CPU or memory usage, provide us with the dump file, event viewer logs, traces. We will provide you with FTP details to upload these files.


Log files

1E needs details of the recorded time when the issue took place. To ensure logs contain relevant details, please try to rerun the steps to replicate the issue. The table below details the log files we require:

For issues relating toRequired log filesLocation of log files
1E Client
  • 1E.Client.log
  • NomadBranchUninstall-YYY-MM-DDThh_mm_ss_000Z.log
Default location: %ALLUSERSPROFILE%\1E\Client\
Nomad client
  • NomadBranch.log

Default location: %ALLUSERSPROFILE%\1E\NomadBranch\

Optional location if installed using 1E Client Deployment Assistant (CDA): C:\WINDOWS\CCM\Logs\

1E Client Deployment Assistant (CDA) was previously known as 1E Endpoint Agent Installation Solution Accelerator (EAISA) or Endpoint Agent Installer (EAI).

OS deployment
  • NomadPackageLocator.log
  • NBCacheActions.log
  • All Configuration Manager logs including SMSTS.log
The path changes at different stages of an OS deployment
Nomad and ActiveEfficiency integration
  • Services.log
%ALLUSERSPROFILE%\1E\ActiveEfficiency\