- 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