Knowledge Base
Knowlegebase articles
Welcome to SysOrb knowledge base. Her you will find detailed explanation on questions regarding SysOrb. The list is under continues development and new articles will be added. You can follow the links below or enter a "key word" to search all of the articles.
- Agent crashes
- Bandwidth consumption estimate
- Basic database tuning
- Can I customize the reports in SysOrb?
- Disabling specific checks
- Does SysOrb support SNMP traps?
- Explanation of the score keeper strategy.
- How does HTTP Netcheck work in SysOrb?
- How to automatically update alert group on all nodes to “As domain”
- How to backup SysOrb database
- How to move the SysOrb server to a new server
- How to quickly set downtime on an agent
- I cannot get all of the "performance counters/cache" entries to appear in SysOrb what should I do?
- Migrating MIB information from one SysOrb installation to another
- Migrating the configuration of a Windows SysOrb server from 32 to 64 bits
- SysOrb agent is not checking in to the Sysorb server
- SysOrb server shuts down unexpectedly
- System uptime no longer updates on windows
- Unable to monitor hardware (fans, disks, temperatures etc.) on Windows
- Upgrading SysOrb on Windows
- Uploading a SysOrb database to Evalesco
- What does KiB and MiB mean?
- What is IPMI ?
- Windows agent late for check-in every hour
System uptime no longer updates on windows
System uptime no longer updates on windows.
Some third party programs can corrupt the registry settings for performance counters.
The issue has been seen with "Symantec Embedded Database" which adds a sem5 entry in "Performance Counter" section of the agent configuration.
http://www.symantec.com/connect/forums/sepm-corrupts-windows-performance...
Run the lodctr program from Microsoft. They describe it like this
Registers new Performance counter names and Explain text for a
service or device driver, and saves and restores counter settings
and Explain text.
"lodctr /r " will restore as mush as possible.
Before you can see a change in the SysOrb web interface the agent must be rescanned.