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
- Automatic rescan of all nodes in a domain
- 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 change time interval value of agent_checkin_delay
- 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
- No empty blocks in meta database.
- Script to get a list of nodes which have no AlertGroup
- SysOrb agent is not checking in to the Sysorb server
- SysOrb agent stops checking in from a windows server with very long system uptime
- 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
Migrating the configuration of a Windows SysOrb server from 32 to 64 bits
When installing the 64-bit SysOrb Server package on a Windows Server which previously ran a 32-bit version of the SysOrb Server, the installer does not remember the previous configuration settings such as SMTP server and reply-to address. Furthermore, if other tuning parameters have been configured (using the SysOrb configuration tool) they too will not be seen by the new 64-bit installation.
The server configuration options are stored in the Windows registry, as is normal for Windows applications. However, Windows keeps two separate registries, one for 32-bit applications and one for 64-bit applications, and presents one of these two as "the only registry" to an application depending on whether the application is 32-bit or 64-bit.
The old 32-bit SysOrb server will have stored all its configuration options in the 32-bit registry. The new 64-bit SysOrb Server will only see the 64-bit registry and will therefore not be able to see the 32-bit options.
The configuration options would normally be available under
HKEY_LOCAL_MACHINE\Software\SysOrb\SOServer
On a 64-bit server you can access the 32-bit registry under
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Software\SysOrb\SOServer
You can now manually compare the values under these two registry keys, migrating the relevant keys from the old 32-bit registry into the new 64-bit registry.
