After enabling the “Windows – Up Time” alarm (disabled by default) and applying the configuration across all Windows servers, it is observed that the alarm works correctly only on systems with an uptime of 99 days or less.
On servers with 100+ days of continuous uptime, the alarm is not raised even when configured thresholds should apply. This suggests a possible bug or limitation in the alarm logic once uptime reaches triple-digit values.
WORKAROUND:
Make a backup copy and then replace the file windows-WinUpTime.xml
with the attached windows-WinUpTime.xml
located in:C:\Program Files\Quest Software\Diagnostic Server\Agent\conf\Rule
Restart the Diagnostic Server (DS).
Once the DS service is running, launch Spotlight.
Go to Configure | Collection | Alarms.
Click on Alarms Drilldown.
Select the appropriate Windows connection from the dropdown.
Locate the Windows Uptime alarm.
Double-click the alarm to edit it.
Uncheck "Factory setting" and "Disable alarm".
Re-check "Factory setting".
Click OK to save.
Expected Result:
The Windows Uptime alarm should now trigger correctly on the affected Windows connection.
Note:
Apply steps 4–11 only on Windows connections where the alarm is not being raised, especially those with an uptime over 100 days.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center