4/12/2017 2:31 AM MGT313 Microsoft System Center Configuration Manager 2012: Plan, Deploy, and Migrate from Configuration Manager 2007 to 2012 Bryan Keller Senior Program Manager Lead Microsoft Corporation Wally Mead Senior Program Manager Microsoft Corporation © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Outline Background on Migration and why we decided to implement functionality within ConfigMgr 2012? Overview of migration process Configuring Migration Object migration Shared Distribution Points Migration Distribution Point upgrade Best Practices and operational changes and behaviors to implement now

Terminology Content: Objects: Server Settings: Client Information Package binaries / files Objects: Packages, Configuration Items (DCM), Software Update Deployments, OS Images, etc. Server Settings: Site Role Settings and Site Properties, etc. Client Information Client GUID, Inventory, State, etc.

How Did Customers Migrate To Configmgr 2007? Majority conducted side-by-side Scripts or MCS tools Server Infrastructure Deployment Objects Clients Inventory & Compliance Data Reassigning and Upgrading Regenerate or preserve

Operational Reality Of Migrating To Configmgr 2012 TechReady12 4/12/2017 Operational Reality Of Migrating To Configmgr 2012 Promise Fears How painful is it going to be to migrate? © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Configuration Manager 2012 Migration Goals Assist with Migration of Objects Assist with Migration of Clients Minimize WAN impact Assist with Flattening of Hierarchy Maximize Re-usability of x64 Server Hardware

Migration Functionality Within Configuration Manager 2012

Migration Functionality Within Configuration Manager 2012 TechReady12 4/12/2017 Migration Functionality Within Configuration Manager 2012 Object Migration Migration of collections, software distribution packages, boundaries, metering rules etc. Distribution Point Sharing Allows ConfigMgr 2012 client to acquire migrated content from ConfigMgr 2007 Distribution Point Content Prestaging Similar to PkgPreLoadOnSite tool but more robust Distribution Point Upgrade In-place upgrade of ConfigMgr 2007 Distribution Point to a ConfigMgr 2012 Distribution Point Migrated content converts which reduces need to redistribute content Import of ConfigMgr 2007 inventory MOF files Clients retain advertisement execution history Assist with Migration of Objects Assist with Migration of Clients How does this all work? Minimize WAN impact Assist with Flattening of Hierarchy Maximize Re-usability of x64 Server Hardware © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

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

Migration Jobs Three types of Migration Jobs: 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

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

Enable Migration and Migrate Objects DEMO Enable Migration and Migrate Objects

Software Update Management Prerequisites: Ensure Software Update Point is configured and first sync completed successfully Ensure Product Classifications and Products are the same between ConfigMgr 2007 and ConfigMgr 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

Operating System Deployment Supported by migration: OS Image/Package Task Sequences Drivers & Driver Packages Special cases: 3rd 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 ConfigMgr 2012 site During migrating Task Sequence will automatically update to reference the ConfigMgr 2012 client installation package

Settings Management (DCM) 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 ConfigPacks can also be added to 2012 through Import feature Schema will be automatically converted from 2007 to 2012 schema during migration

Content 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 ConfigMgr 2007 source path ConfigMgr 2012 clients can acquire migrated content from ConfigMgr 2007 Distribution Point. (Distribution Point Sharing)

Software Distribution Classic Package and Programs are migrated as is: Preserve investment in classic software distributions, this will help as you migrate and transition to ConfigMgr 2012 Two ways to migrate: Can migrate just the package/program via object migration Migrate the collection and the package, program, and advertisement are migrated Use UNC mappings in ConfigMgr 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 ConfigMgr 2012 AppModel

Package Conversion Manager (PCM) What is it? 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

Other Objects Additional objects: Reports not migrated Asset Intelligence customizations Software Metering Rules Search and Administrative Folders Boundaries Application Virtualization (App-V) App-V packages are converted to applications, after migration a deployment needs to be created Ensure clients have the App-V 4.6 SP1 client installed before upgrading the ConfigMgr client For App-V Distribution Point Sharing not available Reports not migrated

Collections 101 in Configuration Manager 2012 Collections are evaluated at each primary site No mixed collections: Ship with two read-only root collections All Systems (Device) All Users and User Groups (Users) No more sub collections Two main uses of sub-collections in Configuration Manager 2007 Means to organize collections in a folder-like manner ConfigMgr 2012 answer = Organizational Folders Advertisement reuse and/or staggered deployments ConfigMgr 2012 answer = Composable Collections No more linked collections Added two new membership rules, Include and Exclude

Collection Migration Primary goals for collection migration: Preserve the customer investment in collections and advertisements Assist with the migration of objects targeted to the collection Prevent unintentional increase in collection scope

Preserve Collection Investment: (Folders) All related collections are automatically migrated Empty collections become organizational folders Desktops Sites ConfigMgr 2012 Desktops North America Redmond (Folder) Sites (Folder) Desktops (Folder) B44 B41 Desktops North America Redmond B41 B44 ConfigMgr 2007

Preserve Collection Investment: (Sub-collections) Sub or Linked Collections no longer exist Composable collection with include membership rules are created Redmond Redmond (composable) Redmond (Folder) B41 B44 B41 B44 ConfigMgr 2007

DEMO Collection Migration

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

Mixed Collections 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

Other Collection Scenarios 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 site- codes in the query

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

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

Shared Distribution Point Example ConfigMgr 2007 ConfigMgr 2012 Migrate Office 2010 packages Deploy Office 2010 to ConfigMgr 2012 clients Client retrieves content from ConfigMgr 2007 DP DataCenter Primary Site 1 Primary Site 2 3 Distribution Point 2007 2012 Site Primary Site Distribution Point Branch Office

Considerations For Shared 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

Customer Goal Configuration Manager 2007: “Enable an in-place upgrade path to easily migrate to a ConfigMgr 2012 Distribution Point while preserving migrated content at remote locations hosting ConfigMgr 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

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

Migration Distribution Point Upgrade Platform support Role can be installed on clients and servers Clients - Windows Vista SP2 and later Servers - Windows Server 2003 SP2 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

Migration Distribution Point Upgrade DEMO Migration Distribution Point Upgrade

Migration Distribution Point Upgrade: Secondary Site With Co-located Distribution Point Enable Migration Enable Distribution Point sharing Navigate and select a Shared Distribution Point to upgrade Complete Upgrade Migration job wizard Migration job runs: ConfigMgr 2012 uninstalls ConfigMgr 2007 Secondary Site Upgrade job pauses until the next Data gathering job to verify Secondary Site uninstall has completed ConfigMgr 2012 Distribution Point installs Content Conversion performed Job completed

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

Considerations For Migration Distribution Point Upgrade Branch DP’s Configuration Manager 2007 client must be removed before performing upgrade Content ConfigMgr 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

Secondary Sites There is no direct upgrade path from a ConfigMgr 2007 Secondary Site to a ConfigMgr 2012 Secondary Site You probably don’t need Secondary Sites in ConfigMgr 2012 Distribution Points have PXE along with scheduling and throttling capabilities Upward flow of network traffic is only compelling reason to implement a Secondary Site in ConfigMgr 2012 Scenarios for migrating to ConfigMgr 2012 Secondary Site P2V migration toolkit Upgrade and attach as remote Distribution Point Create PreStage from upgraded Distribution Point

Clients Roaming Clients Client Upgrades ConfigMgr 2007 client roaming into ConfigMgr 2012 boundaries ConfigMgr 2012 client roaming into ConfigMgr 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 Deployment Client installation package Deployment 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 ConfigMgr 2007 SMSSLP= Pre-requisites .NET 3.0 or higher otherwise .NET 4.0 will install Silverlight

Prepare For Configuration Manager 2012 (Operational changes and behaviors to implement now with ConfigMgr 2007) Get to ConfigMgr 2007 SP2 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 (\\server\myapp\myapp.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 Win7 BDP’s Use “Branch Distribution Point Maintenance Task” to migrate from Windows XP to Windows 7 without having to redistribute content Start implementing BranchCache™ with Configuration Manager 2007 SP2 Consider virtualizing your ConfigMgr infrastructure

Recap Of Best Practices 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 Specify site codes when upgrading clients Site codes between ConfigMgr 2012 and 2007 have to be unique—package ID’s are preserved when migrated During transition leverage Shared Distribution Points and content PreStage functionality Flatten hierarchy where possible: Replace ConfigMgr 2007 Secondary Sites with ConfigMgr 2012 Distribution Points that have scheduling/throttling & PXE Understand collections-used for more than just targeting now Start fresh, build new collections beginning with segmentation Migrate ConfigMgr 2007 collects in order to preserve investment during transition Targeting RBA Clients Settings Segment

Related Content Breakout Sessions MGT309 | Microsoft System Center 2012 Configuration Manager Overview MGT310 | Microsoft System Center 2012 Endpoint Protection Overview MGT311 | Microsoft System Center 2012 Configuration Manager Deployment and Infrastructure Technical Overview MGT312 | Deep Application Management with Microsoft System Center 2012 Configuration Manager MGT318 | Patch and Settings Management in Microsoft System Center 2012 Configuration Manager WCL388 | Client Management Scenarios in the Windows 8 Timeframe

Related Content Hands-on Labs: MGT23-HOL | Deploying Windows 7 to Bare Metal Systems with Microsoft System Center 2012 Configuration Manager MGT24-HOL | Implementing Endpoint Protection 2012 in Microsoft System Center 2012 Configuration Manager MGT12-HOL | Compliance and Settings Management in Microsoft System Center 2012 Configuration Manager MGT25-HOL | Deep Dive: Microsoft System Center 2012 Configuration Manager SQL Replication Labs MGT21-HOL | Basic Software Distribution in Microsoft System Center 2012 Configuration Manager MGT16-HOL | Migrating from Microsoft System Center Configuration Manager 2007 to System Center 2012 Configuration Manager MGT14-HOL | Implementing Role Based Administration in Microsoft System Center 2012 Configuration Manager MGT15-HOL | Deploying a Microsoft System Center 2012 Configuration Manager Hierarchy MGT11-HOL | Introduction to Microsoft System Center 2012 Configuration Manager

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

Complete an evaluation on CommNet and enter to win!

Please Complete an Evaluation Your feedback is important! Be eligible to win great daily prizes and the grand prize of a $5,000 Travel Voucher! Multiple ways to Evaluate Sessions Scan the Tag to evaluate this session now on myTechEd Mobile

4/12/2017 2:31 AM © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

4/12/2017 2:31 AM © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.