Client Installation Logs (Windows)
When users log in to a realm, the access methods available to them depend on a few different things:
The network access agents or clients that are permitted for a particular community, which is something that you specify when you set up a realm
The user’s environment: the operating system, browser, the availability of ActiveX or Java, and whether any clients or agents are already present
If something goes wrong during client or agent installation on a computer running Windows, the error is
recorded in a client installation log. These logs are automatically uploaded to the appliance and listed in AMC if
the user has Secure Endpoint Manager installed. See Client and Agent Provisioning (Windows) for details about
Secure Endpoint Manager.
To view the list of client logs for all users
In the AMC, navigate to Monitoring > Logging.
The View Logs page displays.
Select Client installation logs from the Log file drop-down menu.
You can sort the client installation logs by time or username; to download a log file, click on it. The log appends
information about each step in the provisioning process: bootstrapping, provisioning new components, and
interrogating the device (for device profile matching). The last set of information is probably where the
installation problem occurred.
When troubleshooting, first look at a user’s client installation log in AMC, and then (if necessary) the log file,
epiBootstrapper.log, stored on the user’s local machine in the
Settings\<username>\Application Data\SMA1000\LogFiles folder.
Was This Article Helpful?
Help us to improve our support portal