After importing the management pack: When you add the automated defragmentation pack, two groups are created: “Drives to AutoDefragment” and “Drives to disable fragmentation monitoring”. The two group approach provides a way that the OpsMgr administrator can approach any of the common disk defragmentation requirements that I have run into:
1) I don’t want to know if this drive is fragmented: Add the drive to the “Drives to disable fragmentation monitoring” group.
2) I want to know it’s fragmented but don’t want to autodefragment the drive. Add the drive to the exclusions section of the “Drives to AutoDefragment” group.
The “Drives to AutoDefragment” group includes all drives identified for Windows 2003, Windows 2008 or Windows 2012 systems as shown below:
Monday at noon: This pack will automatically reset the monitors for fragmentation to healthy at noon on Monday. This process also closes out any existing alerts for high fragmentation. This is done through an embedded PowerShell script.
Saturday at 3:00 am: When the monitor re-checks fragmentation status (Saturday at 3:00 am by default) and drives are found to be fragmented two actions occur.
1) An event is written to the event log on the server where the defragmentation will run using a diagnostic. This event is used to track what automated defragmentations have occurred in the environment.
2) An automated defragmentation is activated. This is done by enabling the existing recovery to defragment the drive with an override which is included in the automated defragmentation management pack.
Monday at noon: The monitors are reset and the process is ready to occur again the next week.