0 valutazioniIl 0% ha trovato utile questo documento (0 voti)
46 visualizzazioni52 pagine
This document outlines the steps to migrate from System Center Configuration Manager (SCCM) 2007 to SCCM 2012. It involves upgrading SCCM 2007 to the latest service pack, selecting objects to migrate, designing the new hierarchy, migrating clients in small pilot groups, installing SCCM 2012 with the latest SQL and OS, and testing the new environment. It also provides considerations for migrating security boundaries, settings, distribution points, and managing remote computers between the two versions of SCCM.
This document outlines the steps to migrate from System Center Configuration Manager (SCCM) 2007 to SCCM 2012. It involves upgrading SCCM 2007 to the latest service pack, selecting objects to migrate, designing the new hierarchy, migrating clients in small pilot groups, installing SCCM 2012 with the latest SQL and OS, and testing the new environment. It also provides considerations for migrating security boundaries, settings, distribution points, and managing remote computers between the two versions of SCCM.
This document outlines the steps to migrate from System Center Configuration Manager (SCCM) 2007 to SCCM 2012. It involves upgrading SCCM 2007 to the latest service pack, selecting objects to migrate, designing the new hierarchy, migrating clients in small pilot groups, installing SCCM 2012 with the latest SQL and OS, and testing the new environment. It also provides considerations for migrating security boundaries, settings, distribution points, and managing remote computers between the two versions of SCCM.
Increase the level of Service Pack to the supported level IMPACT
Migrate the required objects
Check the functionality of the migrated objects Migrate clients in pilot Perform bulk migration of clients Decommission the old SCCM Install SCCM 2012 (ensure the required HW resources) Use the latest recommended OS and SQL level (2012) Perform the smoke and performance test on the new environment
Discover existing environment Level up SCCM 2007 SP2 Select objects to be migrated Design the new hierarchy Consideration SCCM 2007 SCCM 2012 Security boundaries - delegation New site Role Based Access Control Site-wide settings New site Client settings PXE with DP Secondary site Distribution point Manage computers in other AD forests New site Client Push installation In most cases only one SCCM 2012 site server is enough IMPACT BUT add the new SCCM 2012 server object with FULL admin right to the System Management OU in ALL concerning Active Directory domains Computer Configuration/Administrative Templates/Configuration Manager 2007/Configuration Manager 2007 Client/Configure Configuration Manager 2007 Client Deployment Settings
Computer Configuration/Administrative Templates/Configuration Manager 2007/Configuration Manager 2007 Client/Configure Configuration Manager 2007 Site Assignment Computer Configuration/Administrative Templates/Windows Components/Windows Update/Specify intranet Microsoft update service location Set the intranet update service for detecting updates: <FQDN of new WSUS server> Set the intranet statistics server: <FQDN of new WSUS server> Configure Configuration Manager 2007 Site Assignment HKLM\Software\Microsoft\SMS\MobileClient\GPRequestedSiteAssignmentCode HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryInterval(Min) HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryDuration(Hour) *...only when you have managed the SCCM agent assignments with group policy If you do not delete the keys referenced above, the newly installed SCCM 2012 clients will not be able to locate the new SCCM 2012 Management Point IMPACT $ErrorActionPreference = "SilentlyContinue" $file = Get-Content $PSScriptRoot\machines.txt foreach ($computername in $file) { $PingStatus = Gwmi Win32_PingStatus -Filter "Address = '$computername'" | Select-Object StatusCode If ($PingStatus.StatusCode -eq 0) { $reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $computername ) $regKey= $reg.OpenSubKey("SOFTWARE\\Microsoft\\SMS\\Mobile Client",$true) $regKey.DeleteValue("GPRequestedSiteAssignmentCode") $regKey.DeleteValue("GPSiteAssignmentRetryInterval(Min)") $regKey.DeleteValue("GPSiteAssignmentRetryDuration(Hour)") Write-Host "Registry keys has been deleted from $computername" } else { Write-Host "$computername unreachable" } } In a fancy newsletter with the expected changes in their life Software Center Software Catalog *requires Silverlight Tier 2 Tier 1 Top level PS1 PS2-1 BS2-1 BS2-2 PS2-2 PS3-1 PS1 SCCM 2007 SCCM 2012 Migration jobs Boundaries Asset Intelligence customizations Operating System Deployment: Boot images Driver packages Drivers Images Packages Task sequences Desired Configuration Management: Configuration baselines Configuration items SITE Collection Linked Collection 1 Linked Collection 2 SITE (Folder) Collection (Folder) Linked Collection 1 Linked Collection 2 EMPTY! C1 LC1 LC2 C1 (Folder) C1 LC1 LC2 C1 includes members of LC1 and LC2 Use Powershell instead of MDT in the future IMPACT Symptom Inject drivers to the operating system image Workaround Use /Get-WimInfo /Mount-Wim /Unmount-Wim /WimFile switches in case of Windows 7 and Windows Server 2008 R2 Note Silverlight is installed by default BUT can be skipped Ccmsetup.exe /mp:<FQDN of management point /skipprereq:silverlight.exe Installation parameters The following properties will be migrated on clients: Installed from package Pre-requisites Push install Clean up the migration data on SCCM 2012 servers
Delete SCCM 2007 secondary sites first
Disconnect the SCCM 2007 parent sites from each other started by the bottom of the hierarchy
Delete all objects from System\System Management container in the Active Directory started by Redesign the hierarchy, remove unnecessary sites and site components Avoid to migrate the unused\not needed objects and packages Use the new features instead of existing solutions (servicing, applications) Remove the obstacles from agent installation Communicate the changes in user experience to end-users Perform the migration is small batches Clean up the Active Directory and all related objects after decommission of SCCM 2007