HipCheck Frequently Asked Questions
HipCheck Frequently Asked Questions |
|
To get started with licensing and using Me Inc. HipCheck, please start by visiting the HipCheck Mobility Service Documentation at:
http://hcmon.team1systems.com/hipcheck-files/doc/
For the latest issues and news please see:
http://hcmon.team1systems.com/hipcheck-files/doc/LateNews/index.html
If you need assistance with using HipCheck then we recommend that you read the Support Frequently Asked Quesitons (FAQ), Licensing and other documentation at:
http://hcmon.team1systems.com/hipcheck-files/supportfaq/
Each Me Inc. account is assigned a Community Name which identifies your account in the Me Inc. community. The Community Name is set when your account is opened an is an important piece of information for accessing your account and HipCheck Services.
Account members can use the Me Inc. Mobility Center for HipCheck, provided on the HipCheck Mobility Server hosted by SCO, hosted by a reseller, or deployed by an end user, to perform account, subscription, and HipCheck management tasks. The Me Inc. Mobility Center for HipCheck is available at https://<CommunityName>.hcmon.team1systems.com, where <CommunityName> is the Community Name for your account. The Mobility Center provides the following resources:
Subscribers can use this site to keep their personal information up-to-date and to create groups, which are collections of other account subscribers. Additionally, account managers can use this site to perform account administration, such as managing HipCheck licenses, and adding and deleting subscribers.
For managing the list of systems that are being monitored by HipCheck, as well as the HipCheck privileges and alert responsibilities assigned to subscribers. This is also the place to go to activate the HipCheck service and to download the various HipCheck components that you need to install.
Microsoft Vista development is underway.
Agents will be made available for other platforms when there is a business case to do so.
For a deployed end user HipCheck installation, licensing is site-wide and perpetual, and is governed by a number of subscribers and a number of monitored systems.
You are likely seeing cached data if:
On UNIX Systems, only lines with certain keywords (Error, Fail, Abort, Died, Crash, "Out of") with reasonable variations in capitalization are being displayed out of syslog. Also some events are logged as multiple lines, but the Error Event view only shows the first line, so the event message may get truncated. To see all the syslog events look in /var/adm/syslog on the system.
On Windows systems, only error events reported in the last 7 days are shown from all Windows event logs. To see all the event log messages not just errors, and any errors older that seven days, go to Control Panel -> Administrative Tools -> Event Viewer on the system and view each log.
On SCO Unix Systems you need to learn about the svcmon interface. Additional information can be found on the monitored system in /usr/lib/svcmon.d/how-to.txt
Some disabled services can be started and they will run until the system is rebooted, while other disabled services need to be enabled or even configured before they will start. In the future an enable service feature will be added, but for services like MSTPPP, some configuration would still be required before it could be started.
No. The alerts need to be reset via the client once they have been triggered.
Yes, processes are identified by name, not by process id.
Yes, if you have specified an Unreachable event for that monitored system. This event is set from the Alerts option off the System Info screen. You can specify a polling interval and a number of times to try reaching the system, to avoid spurious alerts due to transient network conditions.
We recommend a thorough reading of Chapter 5, "Managing HipCheck agents" in the HipCheckTM Mobility Service Installation and User Guide"