Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Reboot pending for servers with deployed agents when upgrading

Reboot pending for servers with deployed agents when upgrading

Created by Lori Krell_ret, last modified by MindTouch on Jun 23, 2016

Views: 1,323 Votes: 0 Revisions: 4

Overview

In rare situations during an upgrade, the servers with deployed agents may be flagged  as 'reboot pending'.  These servers are flagged after the currently deployed agents complete upgrading.

 

You may receive the message: "Agents are deployed in your environment and they will be upgraded. In rare circumstances, the server where the agent is installed may be flagged as 'reboot pending’."

Environment

  • NPM 12.0
  • SAM 6.2.4

Detail

When you upgrade, the currently deployed agents in your environment are also upgraded. In very rare circumstances, those servers may be flagged as 'reboot pending' after the agent completes upgrading.

 

In some cases, you may encounter polling interruptions until the server is rebooted.

Resolution

We recommend rebooting any server flagged as 'reboot pending' to ensure polling is not interrupted.

 

 

 

Last modified

Tags

This page has no custom tags.

Classifications

Public