Tuesday, September 20, 2011

SCCM 2012 News




64bit
New Console with more speed, reliability and new features!
Hierarchy
Software Update improved
Security
Health
Distribution Points – Single Instance Store
User-centric management
Collection-based configuration settings
Dependency-based software distribution
Software Center and Application Catalog
Sites are no longer used to support administrator segmentation
Better FEP integration
More advanced Asset Intelligence
Better Mobile Management
Powershell


More news
Boundaries can now be automatically discovered from AD, but clients can only be assigned to boundary groups. In addition, content (e.g. DPs) can be assigned boundaries separately as well.
The reporting point and PXE point roles have gone. The Reporting point role has been superseded by SQL Reporting Services, and the PXE point has been incorporated into the DP function.
Client settings can now be assigned to collections
New pre-defined security roles
Throttling capability to DPs
DP groups, helps admin of package distribution. Packages can be deployed to a DP group and automatically get propagated to all DPs in that group!
No upgrade path from SCCM 2007 - only a migration path. No upgrade from any other version.
Advertisements are now called deployments
Deployments can be dependent upon hardware spec. specified in new dependencies section.
Software Updates - new automatic deployment of pre-configured categories i.e. critical updates.
OSD - Offline servicing of WIM files to pump in new drivers without having to recapture images.
Now 411 reports available in SCCM 2012
Server Configuration Packs (aka DCM) will be available from May 2011 based around best practice configuration for several scenarios. e.g. Win 2008 server, IIS, SQL and others.
Package Conversion Manager available to convert classic packages to make them SCCM 2012 ready.
SCCM 2012 will include native support for UNIX and LINUX !! .... but not at RTM stage.
System generated data (i.e. HINV, SINV) can be configured to go directly to the CAS (aka CSS). DDR info goes directly to the top of the hierarchy for processing and then is disseminated out to child site servers.
No more branch DPs, DPs support multicast, DPs require IIS
Content Prestaging, replaces Courier sender and some other features.
Each Primary site requires a separate instance of SQL 2008. All dB comms is encrypted.
SMS_DEF.MOF file replaced by UI. Old settings however can be imported.
High availability: No longer a requirement for NLB for MPs as clients can "roam" if unable to connect to their normal MP
Automatic remediation for unhealthy clients.
Native mode gone along with requirement for separate primary site. Now clients communicate with HTTP or HTTP/HTTPS.
Cross forest management requires a two way full trust.
Forefront Endpoint Protection will fully integrate with SCCM 2012, you only need one console to manage your clients
Desired Configuration manager now has auto remediation (as promised it would have) and is renamed "Compliance“
New for the user is the Software Catalogue portal or the Software Centre on the workplace
With the Software Catalogue portal you can easily search for new software and install or request the software on your computer
A new concept - the "Primary Device". You can define relations regarding applications, from one application like Office 2010, a user on their primary (computer) device will receive the MSI version and a user on someone else's device will receive the App-v version.
A "public" computer may use RDP to connect to a version on a remote PC. The user won’t know the difference, except for the deployment speed.
The migration path from SCCM 2007 to SCCM 2012 will be enabled with tools for the purpose - all the migrated applications will be “legacy apps”, although there will not be a direct migration capability as there is such a huge difference in infrastructure. The migration will take the form of a move rather than upgrade.
For applications created with SCCM 2012 you have “optional apps” and “required apps”
You can manage the SCCM Client agent settings centrally per collection.
You can now throttle or schedule Distribution Point replication, negating the requirement for a secondary site in a lot of instances.
SCCM 2012 can branch cache to minimize the load on the WAN
Microsoft Updates can be deployed to groups OR individual systems, and also to stored WIM images.
Inboxes have been largely done away with as SCCM 2012 moves to SQL replication to replace inboxes. Processing of inventory data is now done once at the "local" sccm site and passed up the hierarchy without further processing - making for a more efficient hierarchy.
There are also UI hooks into PXE deployments using OSD enabling users/engineers to input variables in the build process which will affect the task sequence process.
With the inclusion of WAIK, there is now the ability to update your WIM images without having to recapture them. - injecting drivers or apps etc.
Users can define their own work hours so SCCM doesn't interrupt them with software updates.

No comments:

Post a Comment