MGT 313 Microsoft System Center Configuration Manager 2012

MGT 313 Microsoft System Center Configuration Manager 2012: Plan, Deploy, and Migrate from Configuration Manager 2007 to 2012 John Vintzel Senior Program Manager Microsoft Corporation Wally Mead Senior Program Manager Microsoft Corporation

Content: Objects: Server Settings: Client Information

Majority conducted side-by-side Server Infrastructure Clients Reassigning and Upgrading Scripts or MCS tools Deployment Objects Inventory & Compliance Data Regenerate or preserve

Promise Fears How painful is it going to be to migrate?

Assist with Migration of Objects Assist with Migration of Clients Minimize WAN impact Assist with Flattening of Hierarchy Maximize Re-usability of x 64 Server Hardware

Assist with Migration of Objects How does this all work? Assist with Migration of Clients Minimize WAN impact Assist with Flattening of Hierarchy Maximize Re-usability of x 64 Server Hardware

Plan Assess current environment Test/Proof of Concept Design Requires Config. Mgr 2007 SP 2 Config. Mgr 2012 HW Reqs: Windows Server 2008 x 64* SQL Server 2008 x 64 Deploy Setup Initial Config. Mgr 2012 Site(s) Configure Software Update Point & Synchronize Updates Setup server roles Make sure the hierarchy is operating and software deployment works Migrate Configure Migration Enable Distribution Point Sharing Create Migration Jobs Migrate Objects Migrate Clients Upgrade Distribution Points Uninstall Config. Mgr 2007 sites Rinse & Repeat

Three types of Migration Jobs: 1. 2. 3. Object Collection Objects modified after migration Object Migration by type/instance Enables admin to “cherry pick” objects to migrate Also, “Objects modified after migration”, allows the remigration of previous migrated object Collection Migration Enables admin to include all related objects for a collection and all objects targeted to the members of the selected collection Objects can be excluded so they are not automatically selected for subsequent jobs

Collections Operating System Deployment: Boot Images, Driver Packages, Drivers, Images, Packages and Task Sequences Advertisements-via collection migration Settings Management: Boundaries Asset Intelligence Customizations Software Distribution Packages and Virtual Application Packages Software Metering Rules Software Update: Deployments, Deployment Packages, Templates and Software Update Lists Configuration Baselines and Configuration Items

DEMO Enable Migration and Migrate Objects

Prerequisites: Ensure Software Update Point is configured and first sync completed successfully Ensure Product Classifications and Products are the same between Config. Mgr 2007 and Config. Mgr 2012 Supported by migration: Conversion of Update Lists to Update Groups Software Update Deployments are migrated to Deployments and Groups Software Update Packages Software Update Templates Considerations: Custom Updates are not supported, must republish using SCUP 2011

Supported by migration: OS Image/Package Task Sequences Drivers & Driver Packages Special cases: 3 rd party integrated Task Sequences may not migrate, for example, MDT Boot image customizations do not migrated, only injected drivers are migrated and merged with default boot image in destination Config. Mgr 2012 site During migrating Task Sequence will automatically update to reference the Config. Mgr 2012 client installation package

Supported by migration: Configuration Items and Baselines created by customers & ISV’s Un-interpreted Configuration Items are not supported Upon re-migration of the object the changes are added as a new revision Existing 2007 Config. Packs can also be added to 2012 through Import feature Schema will be automatically converted from 2007 to 2012 schema during migration

Package source file path is migrated as-is Standardize on UNC paths for package source files For OS image and boot image the CAS must have at least read access to the Config. Mgr 2007 source path Config. Mgr 2012 clients can acquire migrated content from Config. Mgr 2007 Distribution Point. (Distribution Point Sharing)

Classic Package and Programs are migrated as is: Preserve investment in classic software distributions, this will help as you migrate and transition to Config. Mgr 2012 Two ways to migrate: 1. 2. Can migrate just the package/program via object migration Migrate the collection and the package, program, and advertisement are migrated Use UNC mappings in Config. Mgr 2007 for package source files Programs disabled by default during migration Can use Package Conversion Manager (PCM) to convert some classic package/program to new Config. Mgr 2012 App. Model

Analyzes migrated packages and programs to determine readiness to convert to App Model Converts packages & programs to App Model by building: Applications Deployment Types Analyzes collections that the package/program advertised to in order to determine: Global Settings Requirement Rules Dashboard offers customers ability to track success/failures in migration process

Reports not migrated

Collections are evaluated at each primary site No mixed collections: Ship with two read-only root collections No more sub collections Two main uses of sub-collections in Configuration Manager 2007 1. 2. Means to organize collections in a folder-like manner Config. Mgr 2012 answer = Organizational Folders Advertisement reuse and/or staggered deployments Config. Mgr 2012 answer = Composable Collections No more linked collections

All related collections are automatically migrated Empty collections become organizational folders Desktops Sites (Folder) Desktops North America Redmond B 41 Config. Mgr 2007 Desktops North America B 44 Redmond (Folder) B 41 Config. Mgr 2012 B 44

Sub or Linked Collections no longer exist Composable collection with include membership rules are created Redmond B 41 Config. Mgr 2007 B 44 Redmond (composable) Redmond (Folder) B 41 B 44

DEMO Collection Migration

Concern: Advertisements or collections created in Config. Mgr 2007 at a child site would automatically increase in scope when migrated to the CAS in Config. Mgr 2012 Mitigation: Scope increase will be avoided by providing an option to limit a collection to an existing Config. Mgr 2012 collection Config. Mgr 2007 Central Site Collection Win 7 Clients Execs North America Execs NAM 0987 CAS 0023 North-America Site Advertisement of software specific to North-America Shanghai Site Advertisement of software specific to Shanghai Collection Migrated After migration advertisement is global, need “limit to” existing collection to prevent increase in scope

Collections not supported: User and device resource types, or other custom resource types in one collection Sub/linked collection structure containing mixed types Collections with “limit to” queries to multiple collections

Direct Membership Collections migrated as is Collections which are limited to multiple collections Collections that have queries that reference advertisement ID’s Collections which contain sitecodes in the query

Collections in Config. Mgr 2012 are used for more than just deploying software updates and software distribution Targeting Scope of what collections are used for in Config. Mgr 2012 has expanded. Segmentation Client settings (inventory, remote control, power management, etc) RBA Client Settings Role Based Administration Targeting Preserve Config. Mgr 2007 investment during migration period Don’t try to fit the “■ in the O” when migrating collections from Config. Mgr 2007 Segments

Config. Mgr 2007 Distribution Point sharing Config. Mgr 2012 clients can retrieve content for migrated packages which are hosted on Config. Mgr 2007 Distribution Points Primary scenario is for Software Distribution and Software Updates Management Supported for all types of Config. Mgr 2007 Distribution Points; Branch, Servers Share and Standard Distribution Points *Excludes Boot images and App-V content

Config. Mgr 2007 Config. Mgr 2012 2. Deploy Office 2010 to Config. Mgr 2012 clients Data. Center Primary Site 1. Migrate Office 2010 packages 1 Primary Site 3. Client retrieves content from Config. Mgr 2007 DP 2 3 Distribution Point 2007 2012 Site Primary Site Branch Office Distribution Point

Shared Distribution Points: Not permanent link between old and new Fill the gap during transition when migrating Can be fragile Read Only Configured and enabled per Primary Site

“Enable an in-place upgrade path to easily migrate to a Config. Mgr 2012 Distribution Point while preserving migrated content at remote locations hosting Config. Mgr 2007 Secondary Site, Branch Distribution Points, and or Distribution Points. ” Configuration Manager 2007: Standard Distribution Point Server Share Distribution Point Branch Distribution Point Secondary Site with co-located Distribution Point Configuration Manager 2012 Distribution Point

An orchestrated end-to-end action Supports Branch, Server Share and Standard Distribution Points Content for migrated packages converted into Config. Mgr 2012 content library and single instance store Support Secondary Sites that have co-located Distribution Points Ensure no additional site system roles exist

Platform support Role can be installed on clients and servers Clients - Windows Vista SP 2 and later Servers - Windows Server 2003 SP 2 and later Readiness Administrator console provides status of eligibility for upgrade Distribution Points: No additional roles can be present, (PXE, SMP, etc), only distribution point role Secondary Sites: Nothing is blocked

DEMO Migration Distribution Point Upgrade

1. Enable Migration 2. Enable Distribution Point sharing 3. Navigate and select a Shared Distribution Point to upgrade 4. Complete Upgrade Migration job wizard 5. Migration job runs: Config. Mgr 2012 uninstalls Config. Mgr 2007 Secondary Site Upgrade job pauses until the next Data gathering job to verify Secondary Site uninstall has completed Config. Mgr 2012 Distribution Point installs Content Conversion performed Job completed

Package type Is converted Must be redistributed Boot Image No Yes OS image Yes No App-V Yes No SUM Yes No Software Distribution Yes No Some Config. Mgr 2007 content remains on server after conversion. Delete in order to save/increase available space after migration Leverage Prestage to distribute Config. Mgr 2012 Boot image to server before performing the Migration DP upgrade

Branch DP’s Configuration Manager 2007 client must be removed before performing upgrade Content Config. Mgr 2007 content is preserved after upgrade – must do manual clean-up Will copy between drives Restart functionality allows conversion to restart where it left off in case of interrupted event Monitoring Monitor Distribution Manager log for detailed status One upgrade migration job is performed and each subsequent job is queued No multi-select or bulk action to create multiple DP upgrade jobs Leverage SDK to create multiple upgrade jobs Best Practices of Distribution Point upgrade Start from bottom up Ensure standalone role Remove unwanted data before upgrading

Roaming Clients Config. Mgr 2007 client roaming into Config. Mgr 2012 boundaries Config. Mgr 2012 client roaming into Config. Mgr 2007 boundaries Client Upgrades Clients retain execution history on upgrade Avoids re-running advertisements GUID is preserved Client machine variables are migrated Inventory and state is regenerated

Client installation package Created during setup Distributed automatically to all Distribution Points Deployment ccmsetup attempts to acquire client files from distribution point first then falls back to management point SLP removed and integrated into Management Point Use SMSMP= switch as a replacement for Config. Mgr 2007 SMSSLP= Pre-requisites . NET 3. 0 or higher otherwise. NET 4. 0 will install Silverlight

(Operational changes and behaviors to implement now with Config. Mgr 2007) Get to Config. Mgr 2007 SP 2 Collections: Avoid mixing user & devices in collection definitions, these are no longer supported Don’t use collections with multiple query rules which limit to different collections Package Source Path Use UNC (\servermyapp. msi) in package source path instead of local path (d: myapp) Ensure minimum of. NET 3. 0 or else client will install. NET 4 at time of installation Migrate current XP based BDP’s to Win 7 BDP’s Use “Branch Distribution Point Maintenance Task” to migrate from Windows XP to Windows 7 without having to redistribute content Start implementing Branch. Cache™ with Configuration Manager 2007 SP 2 Consider virtualizing your Config. Mgr infrastructure

Always start from “bottom up” when performing Migration Distribution Point upgrades, this ensures no sites are accidently orphaned Choose to migrate by entire remote location site, both clients and servers Targeting Specify site codes when upgrading clients Site codes between Config. Mgr 2012 and 2007 have to be unique—package ID’s are preserved when migrated RBA During transition leverage Shared Distribution Points and content Pre. Stage functionality Clients Settings Flatten hierarchy where possible: Replace Config. Mgr 2007 Secondary Sites with Config. Mgr 2012 Distribution Points that have scheduling/throttling & PXE Understand collections-used for more than just targeting now Segment

Breakout Sessions MGT 309 | Microsoft System Center 2012 Configuration Manager Overview MGT 310 | Microsoft System Center 2012 Endpoint Protection Overview MGT 311 | Microsoft System Center 2012 Configuration Manager Deployment and Infrastructure Technical Overview MGT 312 | Deep Application Management with Microsoft System Center 2012 Configuration Manager MGT 318 | Patch and Settings Management in Microsoft System Center 2012 Configuration Manager WCL 388 | Client Management Scenarios in the Windows 8 Timeframe

Hands-on Labs: MGT 23 -HOL | Deploying Windows 7 to Bare Metal Systems with Microsoft System Center 2012 Configuration Manager MGT 24 -HOL | Implementing Endpoint Protection 2012 in Microsoft System Center 2012 Configuration Manager MGT 12 -HOL | Compliance and Settings Management in Microsoft System Center 2012 Configuration Manager MGT 25 -HOL | Deep Dive: Microsoft System Center 2012 Configuration Manager SQL Replication Labs MGT 21 -HOL | Basic Software Distribution in Microsoft System Center 2012 Configuration Manager MGT 16 -HOL | Migrating from Microsoft System Center Configuration Manager 2007 to System Center 2012 Configuration Manager MGT 14 -HOL | Implementing Role Based Administration in Microsoft System Center 2012 Configuration Manager MGT 15 -HOL | Deploying a Microsoft System Center 2012 Configuration Manager Hierarchy MGT 11 -HOL | Introduction to Microsoft System Center 2012 Configuration Manager

#TEMGT 313 Hands-On Labs Talk to our Experts at the TLC DOWNLOAD System Center 2012 Evaluation DOWNLOAD System Center 2012 SP 1 CTP microsoft. com/systemcenter

Learning Connect. Share. Discuss. Microsoft Certification & Training Resources http: //europe. msteched. com www. microsoft. com/learning Tech. Net Resources for IT Professionals Resources for Developers http: //microsoft. com/technet http: //microsoft. com/msdn

Evaluations Submit your evals online http: //europe. msteched. com/sessions