This is a product defect that is scheduled to be corrected in a future version of CMDB Solution.
The following workaround can resolve this:
- In the SQL Server Management Studio, run the following SQL script:
USE Symantec_CMDB
SELECT Guid, Name, CreatedDate
FROM vItem
WHERE Name = '<Custom Resource Name>' -- Change this to the name of the custom resource.
Note the CreatedDate date and time value.
- Run the following SQL script:
SELECT s.Guid, s.CreatedDate
FROM String s
JOIN vItem vi
ON vi.Guid = s.BaseGuid
WHERE String = 'New Resource Type'
Note the CreatedDate date and time value. As there may be more than one New Resource Record found, compare the CreatedDate date and time to the one found from step 1. There should be one very close, within normally one minute. This is the record that will be changed in step 3. Once this is identified, copy its GUID value for the next SQL script.
- Run the following SQL script:
WARNING: The following makes permanent changes to the String table. The user may wish to back this table up, or even the entire Symantec_CMDB database, before continuing.
UPDATE String
SET String = '<Custom Resource Name>' -- Change this to the same name as used in step 1's custom resource name.
WHERE Guid = '<GUID>' -- Change this to the GUID copied from step 2.
- On the Symantec Management Platform Server, restart IIS. WARNING: Resetting IIS will temporarily cause Altiris to be offline and may result in lost work by users if they were in the process of using Altiris. This may therefore need to be performed during a non-production time.
- In a Symantec Management Platform Console, click on Manage > Organizational Views and Groups.
- Click on Default.
- Click on the Filter button.
- The changed name of the custom resource should now appear alphabetically as the correct name, not as New Resource Type.
Related Article
Custom resources cannot be found in the Symantec Management Platform Console
http://www.symantec.com/business/support/index?page=content&id=TECH201505
Applies To
Symantec Management Platform versions 7.5 and 7.5 SP1
CMDB Solution versions 7.5 and 7.5 SP1
This also occurs in older versions of Symantec Managment Platform 7.1/CMDB Solution 7.1, but is resolved with its v9 patch.