If you are denied access to a remote client computer, perform the following steps:
![]() |
CAUTION: Back
up your computer data files before making changes to the registry.
Incorrectly editing the registry may render your operating system
unusable. |
If you are unable to complete installation of the Intel® ASF Alerting Agent, check the following:
If you are unable to receive any alerts or heartbeats, confirm that ASF is enabled (Enable = True) and the correct remote management station IP address (DestinationAddress) is set, by checking the Settings tab of the Intel ASF Agent WMI Console or by using a WMI browser. To confirm that heartbeats are enabled (EnablePresenceHeartbeats = True), check the console Timers Settings tab or use the WMI browser. Verify that your remote management console supports ASF alerting.
If you are unable to receive chassis intrusion alerts, verify that chassis intrusion alerting is turned on in the client's system setup program.
If you are unable to receive system password alerts, verify that the system password (not only the BIOS password) is set up in the client computer's system setup program. Note that an alert is sent only after the third unsuccessful password entry attempt.
If the ASF management console intermittently fails to receive all packets, increase the retransmission count (RetryCount). User Datagram Protocol (UDP) packets are not guaranteed delivery, and heavy network traffic may be causing the Platform Event Trap (PET) packets to drop.
If you are seeing too many heartbeats at the remote management console, adjust the heartbeat timer (PresenceHeartbeatInterval). Reducing the retransmission count (RetryCount) could prevent alerts from being seen at the management station if heavy network traffic causes the PET packets to drop.
Copyright © 2002 Intel Corporation.
Legal Information
Last modified on 11/05/02 1:32p Revision 1