v6.0.2

Fixed several small bugs, full Release Notes

• Added WSDL endpoint based N-Central Server verification for environments where Echo/ICMP is blocked, or where additional verification that the server N-Central is up and accessible. Enabled by setting the attribute to True
• Added forced removal/cleanup when bad MSI uninstall information or MSI unable to remove old/rogue agent when needed using the AgentCleanup4.exe. Enabled by setting the attribute to True

5.0.1 - Hotfix 1

2019-08-26

Fixes and Bug Control

• Fixed an issue with the Agent Version comparator, partly due to the bizarre Windows Version numbering method for the Agent Installer - e.g. Version 12.1.2008.0 (12.1 HF1) is "greater than" Version 12.1.10241.0 (12.1 SP1 HF1)
• Fixed an issue during Diagnosis phase where incorrect Service Startup Behavior was ALWAYS detected, even after Repairs complete successfully
• The following issues were identified, explored and reported by Harvey via SolarWinds MSP Slack (thank you!):
  • Removed references to the PowerShell 3.0 function Get-CIMInstance (from a previous optimization) to maintain PowerShell 2.0 Compatibility
  • Fixed a premature stop error in the Launcher when a Device has .NET 2.0 SP1 installed, but needs to install PowerShell 2.0

New Features

• Added Script Instance Awareness:
  • The Agent Setup Script will first check to see if another Instance is already in progress, and if so, terminate the Script with an Event Log entry indicating so, in order to preserve Registry results of the pre-existing Instance
  • If the pre-existing Instance has been active for more than 30 minutes, the Script will proceed anyway, thus overwriting results

Housekeeping and Nuance

• Added Detection Support for .NET Framework 4.8
• Updated some Messages written to the Event Log for clarity

Tweaks and Optimizations

• None this time!

5.0.0 - Initial Release

2018-11-08

Tweaks and Optimizations

• Converted InstallAgent.vbs to PowerShell 2.0 Compatible Script (InstallAgent.ps1) - SEE NOTES SECTION BELOW
• Converted InstallAgent.ini to XML file (PartnerConfig.xml) for direct parsing and variable-typing in PowerShell 2.0

New Features

• Improved Windows Event Log Reporting:
  • Detailed Script Results are packaged in a single Event
  • Missing/Invalid Items required by the Script are identified along with provided resolutions
  • Problems discovered with the Agent are listed in addition to Repair actions taken and their results
  • Details regarding Installers used and Install Methods attempted
• Real-time Windows Registry Reporting:
  • Prerequisite Launcher now stores Execution values in the same root key as the Setup Script
  • Action and Sequence Updates are made to the Registry in real time as the Script progresses
• Added Local Agent Activation Info retention (Location specified in Partner Configuration)
• Added Activation Key Builder (based on Appliance Info)
• Script prioritizes Activation Info as follows:
  • Discovered Activation Key (currently installed Agent)
  • Discovered Customer/Site ID (currently installed Agent)
  • Historical Activation Key (Local History File)
  • Historical Customer/Site ID (Local History File)
  • Default Customer ID for New Devices (GPO/Command-Line Parameter)
  • Historical Default Customer ID (Local History File, if no GPO/Command-Line Parameter is Present/Valid)
• Added Repair for Invalid Appliance ID in ApplianceConfig.xml, typically -1, which causes the N-Central Server to be unable to map the Agent to a Device (results in an Agent that either never Imports or spontaneously dies)
• Added Legacy Agent parameters to Partner Configuration to support installation/repair of an older Agent on Windows XP/Server 2003 (provided Agent copy is 11.0.0.1114 aka 11.0 HF3)
• Added Takeover Action for Rogue/Competitor-Controlled Agents (if the configured Server for the current installation does not match the N-Central Server Address in the Partner Configuration, the Agent will be removed and installed using the Script Customer ID - this also fixes an Agent configured with "localhost" N-Central Server Address)

Housekeeping and Nuance

• Moved Script Execution Registry Key to HKLM:\SOFTWARE\Solarwinds MSP Community
• Added a Legacy Version Cleanup method to the Agent Setup Script, which will automatically remove values/files created by older versions of the Script (Huge thanks to Tim and Jon for their tireless contributions!)

Fixes and Bug Control

• None this update! (Initial Release)

Notes on PowerShell 2.0 Conversion

The intent of the conversion is to:

1. Maintain currency of the Scripting Platform and key features
2. Remove the need to pass Configuration variables between Scripts
3. Remove lesser-used/deprecated features of the original VBScript
4. Categorize Script actions by Sequence for better reporting clarity
5. Simplify and organize Script body by making use of PowerShell Modules