Performing Ongoing Maintenance
After the HEAT–DSM environment is configured, perform ongoing maintenance to address the following scenarios.
Activate a New Computer
A new computer must be activated in DSM before being provisioned from HEAT.
Activate a Computer Manually
| 1. | In DSM, choose the Computers & Users tab. |
| 2. | Right-click the computer and select Activate Computer. |
To configure DSM so new computers are automatically activated when added to DSM, refer to the documentation provided with DSM.
Add a New Software Package to DSM and Make it Installable from HEAT
| 1. | The DSM administrator must create the software package on the DSM system. |
The package must have a property of ITSM Only or DSM and ITSM in the DSM Console. See Properties.
| 2. | Follow the procedure described in A New Software Package is Created in DSM and You Want to Make it Installable from HEAT. |
A New Software Package is Created in DSM and You Want to Make it Installable from HEAT
| 1. | Synchronize the software package. See Synchronizing Software Packages and Sets. |
| 2. | Optional. Change package parameters. See View and Edit Default Installation Parameters. |
| 3. | Specify approval requirement and/or Self Service availability, and then activate the software package. See Specify Approval for Software Packages. |
| 4. | Optional. Add the package to an FRS software record so that the package is grouped together with other similar packages and displays in a filtered list when the FRS software record is selected. See Link Software Packages to FRS Software Records. |
Add a New Computer to DSM
If the new computer does not yet have a fully qualified domain name or a running DSM client agent, map a CI to the new computer. See Map CIs to DSM-Managed Computers.
Add an Existing Computer to DSM
If the existing computer has a fully qualified domain name and a running DSM client agent, and has already been linked to a user, map a CI to the new computer. See Map CIs to DSM-Managed Computers.
Change the Recurring Schedule for Software Synchronization
Software packages can be synchronized on a daily or weekly schedule. See Scheduled Synchronization.
Change the Recurring Schedule for Mapping CIs to Computers
Configuration items can be mapped to computers by running Identify Computers on a daily or weekly basis. (We recommend that you run it daily.) See Scheduled Synchronization.