Customer configured purge maintenance on the children separately from its configuration on the parent. The reason for this was because with AMS and CMS residing on the same parent, they can not allow records to get purged from the parent DB.
Customer reported that the purge maintenance settings on the parent replicate to the child servers, even if the settings are manually altered on the children. They need to have purge maintenance on the child enabled, and purge maintenance on the parent disabled. But, because of replication the disabled purge setting on the parent, replicates to the children each night, disabling resource purging on the child NSs.
Symantec Management Platform 7.x, 8.x
This is working as designed.
Post to SMP 7.5 SP1:
Starting with SMP 7.5 SP1 now you can change if these settings are replicated or not. On your Parent SMP go to
Console>Settings>Notification Server Settings>Purging Maintenance. Right-click on it and select 'Hierarchy>Properties'. You will see under 'Hierarchy Properties' window 'Purge Data' and 'Purge Computers' checkboxes. Selecting
'Purge Data' will allow you to edit and keep the changes on the Child SMP for the 'Purge Legacy Saved Reports' and 'Purge Outdated Agent Registration Entries' sections under the 'Purging Maintenance' tab. Selecting
'Purge Computers' checkbox allows you to edit and keep the changes on the Child SMP under 'Purge computers managed by this NS, which have not reported data for: ' section.