Is it possible to auto monitor partitions on servers where the cdm probe is pushed using the MCS?
Can you add a little more details on what exactly you are wanting?
1) what OS type and versions are you taking about
2) are the partitions in question mapped to drive or mount points?
3) can you currently do what you are asking with the CDM probe?
A little more details will help us provide you better direction.
The server OS types are Linux and Windows. Some partitions are mapped to drives, and there are mount points, but most of those will be excluded.
I found this comment in the documentation:
Configure File Systems with Monitoring Configuration Service
Use either the Default Disk(s) or the Disk(s) profile type to create a configuration profile for file systems (disks) in your CA UIM environment. If you inadvertently configure both profile types for a USM group, the configuration profiles might not be applied to target devices as you might expect.
Note: It's important that all the devices in a group have similar characteristics. Before you configure one of the Disks profile types, ensure the configuration settings are applicable to all storage locations for devices in the group.
A monitoring administrator selects the Default Disk(s) profile type to create a configuration profile for a group of UNIX servers. The administrator configures default settings, and these settings are applied to all storage locations on servers in the group. The administrator does not configure the Disk(s) profile type.
As file storage locations are added to servers in the group, the Default Disk(s) configuration profile is applied.
A monitoring administrator selects the Disk(s) profile type to create a configuration profile for a group of Windows devices. The administrator configures settings for disks C:, D:, and E:. This profile is deployed and applied to all disks C:, D:, and E: on devices that are members of the group. The administrator does not configure the Disk(s) profile type.
As new disks are added to devices in the group, the Disk(s) configuration profile is applied.
I've tried Scenario 1 and it does work, except that it is going to require intervention in order to get the existing file storage locations to be monitored with the default disk profile. The MCS deploys the cdm probe and once the cdm probe is deployed, file storage locations are identified. Next, the profile is applied, but it is only going to apply to any new file storage location. I can open the cdm probe and delete all partitions and when they are re-discovered the profile will apply, but that decreases the value of using MCS. Unless I've missed something, it looks like I have to do this for all the existing servers and any new server that is added, if I want to use MCS.
So I think the problem is coming in for your existing CDM deployment.
The Scenario 1 should work find for new systems that do not have CDM deployed and configured.
Currently I do not believe MCS has an upgrade option from normal CDM to CDM-MC that will reset the disks for so that the new template can be applied.
You may want to try resetting first with a old configuration package
Re-initialize discovery of disks on existing cdm deployments
and then apply the template.
Short of that it will be a manual process.
Here's the order that actions occur from my observation on a server with no CDM probe:
1. Copy default disk policy to server
2. MCS deploys probe
3. Probe starts and discovers file systems
4. MCS applies policy
5. Policy does not apply to existing file systems
6. Add a new filesystem
7. Policy applies to new file system