Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Alert Summary page shows the old server name

Alert Summary page shows the old server name

Table of contents

Updated May 10, 2017

Overview

This article explains why a new alert is working as expected but shows the old server name on the Alert Summary page.

Environment

All SAM versions

Detail

This occurs when the SwisUriSystemIdentifier setting within the WebSettings database table is set to the old server.

 

Note: SolarWinds does not recommend changing this setting to the new server name because this requires rebuilding containers, limitations, dependencies, and so on. The alert will continue to work and will not cause any issues.

 

See the following for more information:

Alert variable issue

Migrating Orion is leaving the old hostname in the SwisUriSystemIdentifier in the WebSettings table

 

Last modified

Tags

Classifications

Public