UD-B404 Microsoft TechED

8/11/2019 UD-B404 Microsoft TechED

1/52


2/52


3/52


4/52


5/52


6/52


7/52


8/52

Increase the level of Service Pack to the supported levelIMPACT


9/52


10/52

Migrate the requ

Check the functiomigrated objects

Migrate clients in

Perform bulk mig

Decommission th

Install SCCM 2012 (ensure therequired HW resources)

Use the latest recommended OSand SQL level (2012)

Perform the smoke andperformance test on the new

environment

Discover existing environment

Level up SCCM 2007 SP2

Select objects to be migrated

Design the new hierarchy


11/52

Consideration SCCM 2007 SCCM 2012

Security boundaries - delegation New site Role Based A

Site-wide settings New site Client setting

PXE with DP Secondary site Distribution

Manage computers in other AD forests New site Client Push i

In most cases only one SCCM 2012 site server is enoughIMPACT


12/52


13/52


14/52


15/52


16/52


17/52

Computer Configuration/Administrative Templates/Configuration Manager 2007/Configurat2007 Client/Configure Configuration Manager 2007 Client Deployment Settings

Computer Configuration/Administrative Templates/Configuration Manager 2007/Configurat2007 Client/Configure Configuration Manager 2007 Site Assignment

Computer Configuration/Administrative Templates/Windows Components/Windows UpdateMicrosoft update service location

Set the intranet update service for detecting updates:


18/52

Configure ConfiguratManager 2007 Site Assignment

HKLM\Software\Microsoft\SMS\MobileClient\GPRequestedSiteAssignm

HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryIn

HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryD

*...only when you have managed the SCCM agent assignments with group p

If you do not delete the keys referenced above, the newly installedSCCM 2012 clients will not be able to locate the new SCCM 2012

Management PointIMPACT


19/52

$ErrorActionPreference = "SilentlyContinue"

$file = Get-Content $PSScriptRoot\machines.txt

foreach ($computername in $file)

{$PingStatus = Gwmi Win32_PingStatus -Filter "Address = '$computername'" | Select

If ($PingStatus.StatusCode -eq 0)

{

$reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $com

$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"

}

}


20/52

In a fancy newsletter with

the expected changes in their life


21/52

Software Center


22/52

Software Catalog

*requires Silverlight


23/52


24/52


25/52

Tier 2

Tier 1

Top level PS1

PS2-1

BS2-1 BS2-2

PS2-2

PS3-1

PS1

SCCM 2007 SCCM 2012

Migrati


26/52

Boundaries

Asset Intelligencecustomizations

Operating SystemDeployment:

Boot images

Driver packages

Drivers

Images

Packages

Task sequences

Desired ConfigurationManagement:

Configuration baselines

Configuration items


27/52


28/52

SITE

Collection

Linked

Collection 1

LinkedCollection 2

SITE (Folder)

Collection(Folder)

EMPTY!


29/52

C1

LC1

LC2

C1 (Folder)

C1

LC1

LC2

C1 includes members of LC


30/52


31/52


32/52


33/52


34/52


35/52


36/52


37/52

Use Powershell instead of MDT in the futureIMPACT


38/52


39/52


40/52


41/52

Use /Get-WimInfo /Mount-Wim /Unmount-Wim /WimFile switchin case of Windows 7 and Windows Server 2008 R2

Note


42/52

Silverlight is installed by default BUT can be skipped

Ccmsetup.exe /mp:


43/52

The following properties will be migrated on clients:


44/52

Installed from package

Pre-requisites

Push install


45/52


46/52


47/52

Clean up the migration data on SCCM 2012 servers

Delete SCCM 2007 secondary sites first

Disconnect the SCCM 2007 parent sites from eachother started by the bottom of the hierarchy

Delete all objects from System\System Managementcontainer in the Active Directory started by


48/52

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, application

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 SC


49/52


50/52


51/52


52/52

UD-B404 Microsoft TechED

Documents

Transcript of UD-B404 Microsoft TechED