Hello,
I am facing issue where 2 different AMS assets details are merged and combined into one resource.
Here is the scenario. Our Service Delivery team migrates the physical server into virtual server (P2V).
The steps are:
- Disable Agent service on the physical server.
- Move the physical server to virtual server. Virtual host is completely isolated.
- Shut down the physical box
- Delete 'Server' entry on the child NS server.
- Perform the command “AeXAgentUtil.exe /resetGuid” in the virtual server (as admin).
- Enable network communication. The new virtual server gets a new Guid and sends basic inventory.
- Verify the new guid is created.
- Change asset status of physical box to 'disposed' on parent NS in AMS and rename its name to _OLD.
Until now everything works.
There is a disposed old asset in AMS on parent NS.
There is a new virtual resource on child NS.
The new VM server has new guid, new serial number and the same name.
The desired behaviour is the new VM server is replicated up to parent NS, so in the end I have 2 AMS assets:
- Server_OLD with old guid, old SN and old inventory AMS details for references
- New VM server with new guid , new SN and the same domain name
In fact , the actual behaviour is very unwanted.
Once virtual server is replicated within hierarchy, the _OLD resource is deleted and merged with new resource.
In the end I have one mixed-up asset, new guid and basic inventory but old serial number , old physical box details in AMS.
Following http://www.symantec.com/business/support/index?pag... kb article I found the resource was merged by the Merge Duplicate Resources task.
I have run the following report. Notification Server Management > Server > Resource Reports > Merged Resources
Resource Guid | Name | Type Name | Merge Key Name | Deleted Resource Guid | Deleted Resource Name | Merge Date and Time |
c76fe9a8-3d87-431c-8e79-373041c7552e | SITSSA04 | Virtual Machine | name.domain | 7e6c12f8-9c7c-46e1-9ef9-c1ad3fc399a1 | SITSSA04_OLD | 5/30/2014 1:50 |
c76fe9a8-3d87-431c-8e79-373041c7552e | SITSSA04 | Virtual Machine | fqdn | 7e6c12f8-9c7c-46e1-9ef9-c1ad3fc399a1 | SITSSA04_OLD | 5/30/2014 1:50 |
So the question is :
What exactly does the Merge Duplicate Resources task do ? How do I control it ?
How do I attack the problem ? How to prevent from merging automatically resources having different serial number, different guids but the same name ? How to keep old asset details ?
Many thanks.
Thanks,
Tomasz