Make The Move: Migrate from SCCM 2007 to SCCM 2012 SESSION CODE: SEC305 James Bannan @jamesbannan www.jamesbannanit.com Make The Move: Migrate from SCCM 2007 to SCCM 2012 (c) 2011 Microsoft. All rights reserved.

Agenda and Goals Examine in-built migration feature in SCCM 2012 4/22/2017 Agenda and Goals Examine in-built migration feature in SCCM 2012 Caveats and considerations What can I do today to prepare? © 2008 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.

SCCM 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 Hardware

Configuring SCCM 2012 Migration 4/22/2017 8:12 AM Configuring SCCM 2012 Migration demo © 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.

Migration Process to SCCM 2012 Plan Deploy Migrate

Migration Process to SCCM 2012 Assess current environment Test/Proof of Concept/Design Requires SCCM 2007 SP2 SCCM 2012 Hardware Requirements: Windows Server 2008 x64 SQL Server 2008 x64 (SP1 & CU10) Plan Deploy Migrate

Migration Process to SCCM 2012 Setup Initial 2012 Primary Site(s) Configure SUP & Synchronize Updates Setup server roles Test hierarchy and software deployment Plan Deploy Migrate

Migration Process to SCCM 2012 Configure Migration Feature Enable Distribution Point Sharing Migrate Objects Migrate Clients Upgrade Distribution points Uninstall Configuration Manager 2007 sites Plan Deploy Migrate

Inventory & Compliance Data Server Infrastructure Migration Planning Clients Deployment Objects Inventory & Compliance Data Server Infrastructure

Objects supported for Migration Collections Advertisements Boundaries Software Distribution Packages and App-V Packages Software Update: Deployments and Deployment Packages Templates and Software Update Lists

Objects supported for Migration Operating System Deployment Boot and OS Images Drivers and Driver Packages Task Sequences DCM Configuration Baselines and Configuration Items Asset Intelligence Customizations Software Metering Rules

Sites Only primary sites can be migrated TechReady12 4/22/2017 Sites Only primary sites can be migrated Manual uninstallation/reinstallation of: Secondary sites (DP/PXE replacement) All other site system roles Site codes must be unique © 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.

Distribution Points – DP Sharing Used for migrated Packages hosted on SCCM 2007 DPs Excludes Boot Images and App-V content

Reports Reports are not migrated: In SCCM 2007 start using SQL Reporting Services Export/Import custom reports (RDL file) Review the report/queries of the reports Set up SQL Reporting Services (TechNet) http://technet.microsoft.com/en-us/library/cc431393.aspx

Software Updates Management Configure: Software Update Point in SCCM 2012 Update Repository using same metadata as SCCM 2007 SUP Wsusutil.exe export/import Using wsusutil.exe (TechNet) http://technet.microsoft.com/en-us/library/cc720466(WS.10).aspx

Software Updates Management Supported by migration: Conversion of Update Lists to Update Groups Software Update Deployments are migrated to Deployments and Update Groups Software Update Packages Software Update Templates

Software Distribution Classic Package and Programs are migrated as-is: Use UNC in SCCM 2007 for package source file location! App-V App-V packages are converted to Applications Create deployment after migration Clients need App-V 4.6 SP1 installed before upgrading the SCCM client For App-V applications DP Sharing not available

Settings Management (DCM) Supported by migration: Custom Configuration Items and Baselines Un-interpreted Configuration Items are not supported Migrated object is added as a new revision Import 2007 Config Packs into SCCM 2012 SCCM 2007 schema automatically upgraded to SCCM 2012 schema

Upgrade Distribution Points Automated DP Upgrade: Content of migrated packages converted to SCCM 2012 Ensure no additional roles exist Ensure enough disk-space is available Branch DPs cannot be upgraded Manual upgrade: Uninstall from SCCM 2007 environment Deploy the DP from 2012 and use Prestage Content feature

Client Migration Clients retain execution history on upgrade Use your preferred deployment method to upgrade client Client Push Installation Software Distribution Group Policy Windows Software Update Services (WSUS) Manual Installation Operating System Deployment (OSD)

Client Migration Minimum Supported Client Versions Windows XP SP2 (64-bit) & SP3 (32-bit) Vista SP2 Windows 7 RTM and SP1 Server 2003 SP2 Server 2008 SP2 Server 2008 R2 RTM and SP1 (64-bit)

Reports 5 new reports for migration: Object Migration Jobs Objects included in Migration Job Objects Failed to Migrate Dependency on a Configuration Manager 2007 Collection Client which are excluded from upgrading to SCCM 2012

Mixed Collections Collections not supported: TechReady12 4/22/2017 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 © 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.

Boundaries Grouped by SCCM 2007 site when migrated: Migrated boundary groups only enabled for content lookup Avoids boundary overlap in Active Directory Prevents new SCCM 2007 clients from accidently getting assigned to the SCCM 2012 environment When the Shared Distribution Point option is enabled: Boundaries associated with the DP in SCCM 2007 are automatically migrated Boundary group created for each shared DP

demo Collection Migration 4/22/2017 8:12 AM © 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.

Preserve Collection Investment (Sub-Collections) Sub/Linked Collections no longer exist Adds inclusion rules for the new collections East Coast includes Sydney and Brisbane “Collection Node” East Coast Sydney Brisbane SCCM 2012 East Coast Sydney Brisbane SCCM 2007

Preserve Collection Investment (Folders) All related collections are automatically migrated Desktops Desktop Australia Sites East Coast Sydney Brisbane SCCM 2007 Desktops (Folder) Desktop Australia Sites (Folder) East Coast (Folder) Sydney SCCM 2012 Limit to

SCCM P2V Migration Toolkit Why another P2V tool? Need an offline P2V solution that works at ConfigMgr site server branch locations ConfigMgr 2012 Migration Scenario: P2V existing Configuration Manager 2007 site server Re-utilize same hardware where parallel servers are not possible

SCCM P2V Migration Toolkit Configuration Manager P2V Migration Toolkit: Captures a VHD clone of the physical server Installs & configures Server 2008 R2 with Hyper-V Utilizes VHD to re-enable SCCM 2007 Site Server services CTP available now through Microsoft Connect

Prepare for SCCM 2012 Get to SCCM 2007 SP2 at a minimum Flatten site hierarchy where possible Plan for Windows Server 2008, SQL 2008, and 64-bit Start implementing BranchCache with SCCM 2007 SP2 Consider virtualizing your SCCM infrastructure

Prepare for SCCM 2012 Avoid mixing user & devices in collections Use UNC (\\server\myapp\myapp.msi) in package source Site codes between SCCM 2012 and SCCM 2007 have to be unique Move from web reporting to SQL Reporting Services

Enrol in Microsoft Virtual Academy Today Why Enroll, other than it being free? The MVA helps improve your IT skill set and advance your career with a free, easy to access training portal that allows you to learn at your own pace, focusing on Microsoft technologies. What Do I get for enrolment? Free training to make you become the Cloud-Hero in my Organization Help mastering your Training Path and get the recognition Connect with other IT Pros and discuss The Cloud Where do I Enrol? www.microsoftvirtualacademy.com Then tell us what you think. TellTheDean@microsoft.com

(c) 2011 Microsoft. All rights reserved. Resources www.msteched.com/Australia Sessions On-Demand & Community www.microsoft.com/australia/learning Microsoft Certification & Training Resources http:// technet.microsoft.com/en-au Resources for IT Professionals http://msdn.microsoft.com/en-au Resources for Developers (c) 2011 Microsoft. All rights reserved.

(c) 2011 Microsoft. All rights reserved. 4/22/2017 8:12 AM © 2010 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. (c) 2011 Microsoft. All rights reserved. © 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.