- Key concepts
- Baseline – group of CI’s
- CI’s – definition of the settings and rules
- User and Device targeting of baselines
- if the baseline is deployed to a ‘User’ there is an option to evaluate the baseline on every device the user logs on OR the user’s primary device
- Automatic remediation!!!
- only for the following
- Registry – create the key or modify value
- WMI and script based settings
- If the above comes back non-compliant an administrator can define a ‘fix’ script
- mobile settings
- * have to select the remediation in the CI and the baseline *
- Can easily create CI’s by browsing to a “Gold System” and generating them
- can only browse file and registry system types from local or remote machine
- CI’s can be created for Windows system or Mobile Systems
MMS 2011–Software Update Management
- can now control how long before an update is expired after it has been superseded.
- example: Do not expire a superseded update until after ‘X’ many months
- Security scopes and rules are now definable!
MMS 2011– Converting Existing Software Packages into the ConfigMgr 2012 Application Model
- 2012 App Model
- Virtual containers that contain end user metadata and administrator properties
- Deployment Types
- App-V
- Scripts
- MSI
- Mobile Cab
- Requirement rules
- platform
- hardware requirements
- Utilizes DCM to determine applicability
- Dependencies
- What other applications are required in order to install
- detection method
- How to identify if the application is present
- can be product code, file version, registry location
- Content
- source files
- installation options
- Application Feature Mapping from SCCM 2007 to SCCM 2012
- Package and Programs = Application and Deployment Type
- Advertisement = Deployment
- Collection Rules = Requirement Rules and Global Conditions
- Run Advertised Programs = Software Center
- New feature – User Device Affinity (UDA)
- New feature – Software Catalog
- Best Practices BEFORE migration
- In SCCM 2007
- start using platform requirements
- User UNC patch for Source Location
- Use only MSI’s with one unique PID
- Migration Options
- Do nothing – keep packages and programs
- Manually Convert
- Convert using Package Conversion Manager