Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Binding the Orion Web Console to a host name

Binding the Orion Web Console to a host name

Table of contents

Updated March 14, 2017

Overview

If you added a site binding to a host name before you upgrade, you must bind the Orion Web Console to a fully qualified domain name (FQDN).

 

If you upgrade any SolarWinds Orion product without binding to a FQDN, the top menu may disappear. In this case, bind the Orion Web Console to an FQDN and restart IIS.

 

Environment

Products running on Orion Platform 2017.1, such as:

  • NPM 12.1
  • SAM 6.4
  • NTA 4.2.2
  • NCM 7.6
  • SRM 6.4
  • Integrated VMAN 7.1
  • VNQM 4.4

Detail

If you setup IIS to use host name bindings for the Orion Web Console, you must use the fully qualified domain name.

  1. Log in to the Orion server as an administrator.
  2. Open IIS Manager.
  3. Expand Sites and select your SolarWinds website.
  4. Click 'Bindings' under Actions.
  5. Change the host name to a FQDN.
  6. Restart IIS.
 

 

Last modified

Tags

Classifications

Public