Software deployment may involve changes to end-user privileges, which is obviously a security topic. Comprehensive monitoring depends on an up-to-date inventory.
And security concerns may drive patching -- especially emergency patching done outside normal maintenance schedules.
One of the many features supported by Microsoft System Center 2012 Configuration Manager (SCCM 2012) is software updates.
An important part of the planning process for SCCM 2012 is developing criteria that you can use to determine when you have reached an acceptable compliance level for updates.
Without that information, it'll be difficult for you to know when you have to spend additional time tracking noncompliant devices.
Table 1 shows sample compliance criteria for workstations.
It is important to note that different tools may focus on different processes.
Additionally, some might emphasize enterprise-scale support, while others focus on ease of use.
As you evaluate desktop management options, be prepared to accept some feature trade-offs.
45 Comments