System Center 2012 Configuration Manager SP1 Case Studies and Migration Experiences - PowerPoint PPT Presentation

slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
System Center 2012 Configuration Manager SP1 Case Studies and Migration Experiences PowerPoint Presentation
Download Presentation
System Center 2012 Configuration Manager SP1 Case Studies and Migration Experiences

play fullscreen
1 / 102
System Center 2012 Configuration Manager SP1 Case Studies and Migration Experiences
166 Views
Download Presentation
lesley-love
Download Presentation

System Center 2012 Configuration Manager SP1 Case Studies and Migration Experiences

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. System Center 2012 Configuration Manager SP1 Case Studies and Migration Experiences Rodney Jackson Sr. Premier Field Engineer Microsoft UD-B340

  2. OPENING POINTS • Aggressive pace for this session • Impossible to cover every possible migration blocker in granular detail in a one hour session • Opportunity for further discussion • Speaker Q&A Session – Tuesday, April 9th, 5:30-6:30pm –Location- Social Central • Evaluation following session VERY important

  3. ASSUMPTIONS • You are new to ConfigMgr 2012 and have not deployed it yet. • You have attended or/and will review the breakout sessions related to Migration. • Migration Best Practices from CM07 to CM2012 – UD-B404 • Migrating from CM07 to CM2012 – UD-B316

  4. SETTING EXPECTATIONS • This is not a session on troubleshooting migration or every single case covered. • This session is intended for those who recently or are planning to deploy Configuration Manager 2012into production. • This is a review of issues that have been reported, discussed, and documented through troubleshooting and/or proactive solutionsfrom engineers in the field and in the premier support line.

  5. Assumptions You are familiar with the migration process & tool. You are at least running CM 2012 SP1, Windows 2008 R2, SP1 and SQL 2008 R2(with latest Cumulative Update) in your lab. You review all the SP1 requirements (AIK, WSUS hotfixes, etc.) Apply Cumulative Update 1 for System Center 2012 Configuration Manager SP1  http://support.microsoft.com/kb/2817245/en-us.

  6. Agenda • Objective • Service Pack 1(SP1) Notes From The Field • Cumulative Update 1(CU1) Notes From The Field • Migration Experiences • Case Studies

  7. Session Objectives Provide information that will help you avoid and isolate any potential problems that can affect downtime during the migration process and general operations.

  8. Service Pack 1 Notes From The Field Review SP1 Links slides- Hidden Slide following this section. Install WMF 3.0 if you are not running Windows Server 2012http://www.microsoft.com/en-us/download/details.aspx?id=34595. SP1 requires PowerShell 3.0. Uninstall the WAIK. Install ADK (http://www.microsoft.com/en-us/download/details.aspx?id=30652) When you run the Windows ADK setup, select the following features: • Deployment Tools • Windows Preinstallation Environment (Windows PE) • User State Migration Tool (USMT)

  9. Service Pack 1 Notes From The Field Install WSUS Patch KB 2734608(Ensure that the CAS, Primary and Remote SUP site systems are patched). SUP/WSUS Ports may be changed to default port if you have custom ports during upgrade. Remove Anti-virus software for Boot Images prior to upgrading.

  10. Service Pack 1 Notes From The Field Prerequisite checker may give warnings if your primary server has remote site (MP, DP, and SUP) in a different domain without trust(like DMZ). Warnings will be related to BITS, IIS and Server service. These warnings are because the account which runs prerequisite checker doesn’t have proper access on Remote Site Systems.

  11. Cumulative Update 1 (CU1) Notes Review http://support.microsoft.com/kb/2817245/en-us The CU1 installation will prompt to create several additional packages, one of these is a console package. To add the new Powershell CMDLET - Add-CMDistributionPoint you have to install the console package. Take a quick look at Neil Peterson’s blog At Long Last - Add-CMDistributionPoint PowerShell CMDLET included in Configuration Manager SP1 CU1

  12. CU1 Package Has To Be Applied To Console

  13. Three Types Of Packages Are Created

  14. Migration Experiences Migration Components Prepare For Migration Experiences During Migration Experiences After Migration

  15. Migration Components • SMS_Migration_Manager Component • MIGMCTRL.LOG • Mmctrl.box • Database Tables and Views

  16. Migration Tables

  17. Migration Views

  18. Prepare For Migration

  19. Agenda Hardware Configuration Software Update Requirements Data Gathering Requirements SQL Server Configuration

  20. Hardware Requirements The key factors that limit performance of the overall system include the following, in order: Disk I/O performance Available memory CPU System Center 2012 Configuration Manager Hardware used for site roles in Microsoft IT http://blogs.msdn.com/b/shitanshu/archive/2012/04/10/configuration-manager-2012-hardware-configuration-used-in-microsoft-it.aspx

  21. SQL Server Memory Configuration When you use a database server that is co-located with the site server, limit the memory for SQL Server to 50 to 80 percent of the available addressable system memory. When you use a dedicated SQL Server, limit the memory for SQL Server to 80 to 90 percent of the available addressable system memory. Each environment is different, so adjust that percentage until you find the right balance.

  22. CM Requires SQL to reserve 8 GB min

  23. Data Gathering -Permissions • SMS Provider Account: • This account is used to access the SMS Provider of the source site and requires Read permission to all source site objects. • Site SQL Server Account: • This account is used to access the SQL Server database of the source site and requires Read and Execute permissions to the source site database.

  24. Port Requirements For Data Gathering • When CM2012 gathers data, the following network protocols and ports are used: • NetBIOS/SMB – 445 (TCP) • RPC (WMI) - 135 (TCP) • SQL Server - 1433 (TCP) • Note: You can use a custom port for SQL Server as long as you open the port when connecting.

  25. SUP CM07 Catalog Products/Language Must Match CM2012 Prior To Migration

  26. Experiences During Migration

  27. Agenda Agenda Permissions OSD Notes Task Sequences Transfer Objects? Yes/No Drivers

  28. Agenda Virtual Applications Server Shares Branch Distribution Points Branch Distribution Points

  29. Permission Failure For Data Gathering

  30. Console Permissions

  31. SysAdmin Permission

  32. What Objects Should You Transfer?

  33. OSD CM 2012 SP1 Notes From The Field CM2012 SP1 does not support deploying Win PE 3.0 boot images. SP1 requires ADK which is based on Win PE 4.0(Windows 8 and higher). Win PE 4.0 does not support non-ACPI computers. CM2012 RTM used Windows AIK and was based on Win PE 3.0.

  34. OSD CM 2012 SP1 Notes From The Field So, how do you continue deploying images to legacy machines? Option 1 Use MDT (with WAIK) for machines that are not ACPI compliant computers (example VMWare 4.1 and earlier). Option 2 Remain at CM 2012 RTM until you have upgraded your legacy hardware.

  35. OSDPreserveDriveLetter – Set Value

  36. OSDPreserveDriveLetter -Set Drive Letter Variable

  37. OSDPreserveDriveLetter Variable

  38. Task Sequence Notes From Field All objects within a task sequence must migrate during the migration or it will fail. Trick from the field - duplicate all task sequence you plan to migrate. Verify all package and objects within a task can be migrated.

  39. Task Sequence Notes From Field Remove any objects from task sequence that cannot migrate and add them in CM2012. Task that contain steps from MDT 2010/2012 cannot be migrated using the wizard tool.

  40. Drivers Do Not Migrate -Permissions Verify you have full permissions to the driver source folder. Check Migctrl.log for similar error: “SCCM Provider is missing read, write, or delete privilege for the driver package source path.”

  41. Drivers Do Not Migrate -Permissions All Drivers MUST be imported to migrate. If the trick of pointing a driver package to the source files in a share versus importing the drivers in CM07 was used the drivers will not migrate in CM2012. Import drivers in CM2012.

  42. Virtual Application Migration Notes Ensure 64-bit clients have AppV4.6 and higher before upgrading to CM 2012 client. CM 2012 SP1 supports 5.0. You can migrate a virtual application package by using object migration.

  43. Virtual Application Migration Notes You cannot migrate virtual applications by using Previously Migrated Object Migration type. If you need to migrate the same Virtual App from your CM07 source side again. Delete the migrated virtual application package from CM 2012> And then create a new migration job to migrate the virtual application.

  44. Upgrading Branch DP Notes Make sure the site server machine account is in the local Admin Group of the BDP. Uninstall CM2007 client prior to upgrading BDP to CM 2012 DP. If site server machine account is not in local Administrators group of BDP and you do not uninstall the CM2007 client prior to upgrading to a CM2012 DP all content will be lost.

  45. Shared DP Eligibility Upgrade Guide Planning for Content Deployment During Migration to System Center 2012 Configuration Manager http://technet.microsoft.com/en-us/library/gg712275.aspx

  46. Migrating Content On Server Shares Server Share (+) Secondary Site = Not Eligible

  47. Redistribute Server Share Content • Enable the standard DP on the secondary site server. • Redistribute the content to that standard DP. • Remove Server Share on Secondary Site. • Remove the duplicate site system role. • The DP becomes eligible for upgrade. Step-by-Step

  48. Experiences After Migration