https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMTMyIiwiaGFzaCI6IjM1ZmE0MGEwLWM1NTUtNDdkNy1iN2NmLWNkMGFlYjhkYTdlNiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Changing collector heartbeat polling by EMS

Challenge

The collector will be treated as dead for only 12-24 minutes from the moment of its inavailability; however, this may lead to the problem of having innacurate monitoring.

Cause

By default, the polling timeout interval for collector is 12 minutes.

Solution

Below are the steps to decrease the polling timeout for EMS:

  1. In the EMS installation path (by default, it's  "C:\Program Files\nworks\Enterprise Manager"), find the file named nworksMCS.exe.config.
  2. Make a backup of the file.
  3. Stop nworks Enterprise Manager service and open the file with Notepad.

Locate the following lines:

 

<setting name="PollingTimeout" serializeAs="String">
        <value>720000</value>

 

The value is specified in milliseconds. You can edit it as you find appropriate. When the edit is complete you may save the file and start the nworks Enterprise Manager service.

KB ID:
1132
Product:
Veeam Management Pack for Microsoft System Center
Version:
5.x
Published:
2011-08-02
Last Modified:
2020-08-28
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later