Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > LEM Agent installation on Windows 2016, Windows 2012 R2, Windows 10, or Windows 8.1

LEM Agent installation on Windows 2016, Windows 2012 R2, Windows 10, or Windows 8.1

Table of contents


Steps for a LEM Agent Installation on Windows 2016, Windows 2012 R2, Windows 8.1, or Windows 10.


All LEM Versions.

Windows 2016 is supported on LEM 6.3.1 and higher only.


Note: Before running this install, remove your current Agent installation by uninstalling it from Programs and Features. The ContegoSPOP folder must be removed from C:\Windows\SysWOW64\ (C:\Windows\system32\ for 32-bit systems).

1. Download the local Agent installer to the local hard drive and un-zip the installer file. The Agent installer file should be the same version as the LEM version, or a previous version that can be upgraded by the LEM.


Note: Do not use an Agent version that is newer than the LEM version. If you are installing the Agent on Windows 2016, LEM 6.3.1 or higher is required. SolarWinds recommends installing Windows Agent 6.3.1 HF 5 or higher. 


2. Whether using the local installer or remote installer, the Agent install requires "Run as Administrator", which only works if the installer file is on the local hard drive.
     Note:  Be aware that if you are using roaming-profiles, the user profile (desktop) will be on a network share, which does not allow the agent to have the permissions necessary to communicate with the LEM.
3. Right-click the installation file and select run as administrator for the install, and follow the prompts to complete the install. Windows XP and 2003 did not need run as administrator, but each newer Windows version has additional security settings.


4. If the agent does not appear in the GUI-console Node List, or does not send log data, you may need to perform one of the following:
     - access the Windows server/workstation, stop the agent service, delete the "spop" subdirectory (under C:\Windows\SysWOW64\ContegoSPOP\), start the Agent service, and note whether the Agent shows in the list.


     - un-install the Agent, and right-click to set install properties for "windows 7 compatibility", in addition to "run as administrator". (This indicates a higher level of 'security' policies)

5. If you still have an issue, contact SolarWinds support.





Last modified