Currently the only workaround to correct this is as follows:
1. Record the current metrics being monitored and alarm thresholds configured for all currently deployed cdm probe profiles by reviewing these from the Monitoring tab of the UMP USM portlet.
2. Delete all cdm templates from all monitoring groups from the UMP USM portlet.
3. Migrate the older cdm MCS templates ('Setup cdm', 'CPU Monitor', 'Default Disk(s)', 'Memory Monitor') to the versions associated with the 6.30-MC cdm probe using the activate_template command from the mon_config_service probe utility.
4. Deploy the 6.34 cdm_mcs_templates package to the primary hub
5. Activate the 6.34 cdm MCS templates with the activate_probe_templates_package command from the mon_config_service probe utility.
6. Deploy the 6.42 cdm_mcs_templates package to the primary hub
5. Activate the 6.42 cdm MCS templates with the activate_probe_templates_package command from the mon_config_service probe utility.
At this point the Enhanced cdm templates should be available from the Monitoring tab of the UMP USM portlet and either legacy or enhanced cdm probe templates can be created for the required monitoring groups.