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://hipcheck.me-inc.com/hipcheck-files/doc/
For the latest issues and news please see:
http://hipcheck.me-inc.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://hipcheck.me-inc.com/hipcheck-files/supportfaq/
If you cannot resolve the issue you have using these resources then you can raise a Support Request by either:
https://<community>.hipcheck.me-inc.com/meinc/app
where <community> is the name of the community you created when you setup your HipCheck Account and click on the "Service Request" link on the left hand side of the screen, or
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, to perform account, subscription, and HipCheck management tasks. The Me Inc. Mobility Center for HipCheck is available at https://<CommunityName>.hipcheck.me-inc.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.
To purchase a license for the HipCheck mobility service, contact a SCO authorized reseller. To find one near you, visit http://partners.sco.com/partner/locator/region.jsp
No. Just visit http://hipcheck.me-inc.com and follow the trial account link. This will open a trial account enabled for 2 users, 3 servers, and valid for 30 days.
To fully activate a trial account, purchase a new account license from a SCO authorized reseller, and enter it using the license administration pages.
Not at this time. HipCheck licenses are available exclusively through SCO's value added resellers, who are equipped to help set up and manage your account if you so desire. SCO does not sell HipCheck licenses directly to end users.
Some SCO Resellers may have such a program but it is not currently part of the standard HipCheck licensing scheme provided by SCO. Talk to your Reseller.
A server month equals HipCheck monitoring service on a single server for one month. HipCheck licenses are sold as server month units in order to make it easy and convenient to manage the expiration date in accounts of all sizes, and to provide maximum flexibility to account administrators.
Suppose you purchase a new account license for 10 servers for a year, which is valid for 120 server months. When you enter this license, the administration pages will permit you to reduce the server count to 8, and the expiration date will be extended accordingly: 120/8 = 15 months from the date of entry of the license. Alternatively you could start with a five server license and then work with an expiration of 60/8 = 7.5 months from the date of entry.
In the above scenario, suppose you need to add five more servers after using your account for 10 months. To do this, you purchase a license for 60 server months (equivalent of 5 servers for a year). When you add your new license to the system, the license administration pages will note that you still have 5 months left in your existing license for 8 servers (5 x 8 = 40 server months). With the new license your total is now 100 server months. Since you now have 13 servers, your expiration date will be adjusted by the license administration pages to 100/13 = 7.7 months from the date of entry of the new license.
No. A trial account is limited strictly to 30 days, with access for 2 users to monitor 3 servers.
No. The minimum length of time added by a HipCheck License is 30 days.
You must purchase an Extension License in order to add more server capacity to your account.
To add more authorized users to an existing account, you may purchase a license for one or more additional users. User licenses are permanent and do not expire.
The administration pages in your account display the expiration date for you to see whenever you need to refresh your memory. In addition when the expiration date approaches you will receive an email reminding you to purchase an extension license to maintain continuous service.
To add two users, you would purchase two single-user upgrade licenses. To add 5 servers and extend the license, we would recommend a 60 server month license. When this is added, the license administration page would show seven authorized servers and 62 server months remaining, corresponding to an expiration date 62/7 = 8.9 months from now. To get to a full year, we would recommend adding two more 24 server month licenses. Then the expiration date would be calculated at 86/7 = 12.3 months from now.
Yes. Any entry in the HipCheck list of monitored servers counts as one server regardless of the size of the machine.
Contact product support.
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"