How do I run a repair on Alert Manager for Helpdesk?

Article:HOWTO7154  |  Created: 2007-04-12  |  Updated: 2007-05-10  |  Article URL http://www.symantec.com/docs/HOWTO7154
Article Type
How To


Question
How do I run a repair on Alert Manager since it is not in Add or Remove Programs?

Answer

Warnings:
 (1) Repairing Alert Manager replaces all default files under the AeXHD folder with the files that shipped with the currently installed version. It is for this reason that you need to verify whether or not you have implemented customizations the correct way as documented in the Helpdesk Product Guide (KB 40604, starting on page 195). Since properly implemented customizations are done to files in a custom folder that are referenced by a custom.config file, they are not affected by the repair of Alert Manager. If you're made changes to the default files in their default location, they will be overwritten during the repair. This is why we ask you to back up your AeXHD directory before repairing.

(2) If there are other issues with Alert Manager or the Notification Server, repairing Alert Manager may cause the Notification Server to stop responding. To correct this, run an NSSetup of the Notification Server, and then repair the hotfix for it in Windows Add or Remove Programs. Afterwards, open an Altiris Console and re-enable Server Processing.

(3) Helpdesk and/or Altiris services will be offline during the repair install. Ensure that this can be run off production hours, or inform users that services may be disrupted during the procedures.

To run a repair on Alert Manager for Helpdesk, do the following:

  1. Back up your AeXHD directory if you are not using a custom.config file for your customizations. If you are not sure, look at article 32822 to determine if you are using the custom.config files.
  2. Browse to \Program Files\Altiris\Setup Files\Altiris Helpdesk\
  3. Right-click on AlertManager.msi
  4. In the right-click menu, select Repair

If the repair was expected to fix the issue but did not give the expected results, please follow these additional steps:

  1. Stop IIS
  2. Repeat steps 1-4 above
  3. Start IIS


Legacy ID



34275


Article URL http://www.symantec.com/docs/HOWTO7154


Terms of use for this information are found in Legal Notices