Transcript • Aggressive pace for this session • Impossible to cover every possible migration blocker in granular detail in a one hour session •

• 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
•
Migration Best Practices from CM07 to CM2012 – UD-B404
• Migrating from CM07 to CM2012 – UD-B316
http://support.microsoft.com/kb/2817245/en-us.
• Objective
• Service Pack 1(SP1) Notes From The Field
• Cumulative Update 1(CU1) Notes From The Field
• Migration Experiences
• Case Studies
Provide information that will help you avoid and
isolate any potential problems that can affect
downtime during the migration process and
general operations.
http://www.microsoft.com/en-us/download/details.aspx?id=34595
http://www.microsoft.com/en-us/download/details.aspx?id=30652
• Deployment Tools
• Windows Preinstallation Environment (Windows PE)
• User State Migration Tool (USMT)
KB 2734608
http://support.microsoft.com/kb/2817245/en-us
At Long Last - AddCMDistributionPoint PowerShell CMDLET included in Configuration
Manager SP1 CU1
Migration Experiences
Migration
Components
Prepare
For
Migration
Experiences
During
Migration
Experiences
After
Migration
•
•
•
•
Prepare For Migration
Agenda
Hardware
Configuration
SQL Server
Configuration
Data Gathering
Requirements
Software Update
Requirements
1. Disk I/O performance
2. Available memory
3. CPU
http://blogs.msdn.com/b/shitanshu/archive/2012/04/10/configuration-manager-2012hardware-configuration-used-in-microsoft-it.aspx
• 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.
• 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.
Equal
Equal
Agenda
Permissions
Transfer
Objects?
Yes/No
Task
Sequences
OSD Notes
Drivers
Agenda
Virtual
Applications
Branch
Branch
Distribution
Distribution
Points
Points
Server Shares
• 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.
“SCCM Provider is missing read, write, or delete privilege for the
driver package source path.”
Standalone
Co-located with
other site roles
Co-located with
secondary site server
Standard DP
Y
N
Y
DP on Server Shares
Y
N
N
*Branch DP
Y
N
N
Planning for Content Deployment During Migration to System Center 2012 Configuration Manager
http://technet.microsoft.com/en-us/library/gg712275.aspx
Server Share (+) Secondary Site = Not Eligible
1. Enable the standard DP on the secondary site server.
2. Redistribute the content to that standard DP.
3. Remove Server Share on Secondary Site.
4. Remove the duplicate site system role.
5. The DP becomes eligible for upgrade.
Experiences After Migration
Agenda
Custom
Reports
Client
Migration
Notes
Managing
CM07 &
CM2012
Clients
PXE
CacheExpire
Setting
Source
Package
Location
• CM07 reports cannot be migrated.
• Copy classic reports to SQL Reporting Services in CM07.
• Backup Reporting database.
• Export RDL files.
• Import to CM 2012.
Migration Options
Option 1: SSRS Report Downloader
http://ssrsdownloader.codeplex.com
Option 2:
Copying RDL files from one reporting server to the other
Option 3:
Report Sync
http://code.google.com/p/reportsync/downloads/list (not endorsed by Microsoft).
• CM2007 clients with App-v must have 4.6 SP1 or later to
migrate.
• Clients will resend inventory to new destination hierarchy
after migrating.
• Compliance data will be resent to new destination hierarchy.
CM07
• If both CM07/2012 sites are in the
same boundaries remove
boundaries from CM07 site.
• Configure Advertisement for
unreliable network boundary.
CM2012
• Disable Automatic Client Push Installation in CM2012
environment during migration.
• Phase in Client Migration (software deployment, SUP, etc.).
• CM 2012 clients check for site version.
• In CM2007 you could change the CacheExpire setting
per KB2019640 to prevent PXE failures within one hour
of a previous deployment.
• The CacheExpire setting does not exist by default
in CM2012.
• In CM2007 you could modify the registry key
HKLM\Software\Microsoft\SMS\PXE\CacheExpire.
• The key does not apply in CM2012 because PXE is
integrated with the Distribution Point.
Add CacheExpire Regdword to the Software\Microsoft\SMS\DP registry key.
• Change local package source paths.
• Change package source in Configuration Manager 2007
environnent.
• Change package source in Configuration Manager 2012
environnent.
• Reference Sean Mahoney’s script in note page.
Case Studies
Cases
CM2012 &
Server
Notes
CM2012 &
SQL 2012
Notes
Cannot
Read SQL
Version
SQL Setup
Not
Supported
Client
Unable To
Register
with MP
Cases
Cannot
Create/Edit
Report
CM2012 &
SQL 2012
Notes
Software
Metering
Rejected
App Not
Deployed
to some
users
MP Install
fails on
Server 2012
Cases
SUM
Deployment
Not
Downloading
http://technet.microsoft.com/enus/library/gg712697.aspx#BKMK_RecoverSite
• Windows Server 2012 allows you to leverage WSUS 4.0.
SQL 2012 SP1 version.
ConfigMgrSetup.log fails to read
ERROR: Failed to get Service Pack version for SQL Server
Failed to connect
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Instance Names\SQL registry key for reading on SQL Server
[NYC-CFG.LAB.local]. Configuration Manager Setup
Failed to connect
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Instance Names\SQL registry key for reading on SQL Server
[NYC-CFG.LAB.local]. Configuration Manager Setup
• Compared a side by side comparison of SQL 2008 R2 with the SQL
2012 SP1 and the registry keys.
• Added Registry information to SQL 2012 SP1 installation from the
ConfigMgrSetup.log:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Instance Names\SQL
SQL Server version is not supported.
ConfigMgrSetup.log produces
SP1 GDR Setup
Update that fixes known
Windows Installer issues.
403.4 SSL required The request is made over a nonsecure channel, and the
web application requires a Secure Sockets Layer (SSL) connection.
CCM_POST /ccm_system_windowsauth/request - 80 - 10.10.10.10 ccmhttp - 403 4 5 2
Why do we see port 80 and not 443 if this is configured for HTTPS Only?
CCMSETUP.EXE /UsePKICert CCMALWAYSINF=1
CCMHOSTNAME=HTTPS://NYC-CFG.Contoso.com SMSSITECODE=CFG
Problem
• After upgrading to CM 2012 SP1 cannot use edit/create report button
Troubleshooting
• Reporting Server is SQL 2008 R2 SP1 CU6.
• Uninstalled/Reinstalled Reporting Services Point.
• Modify registry ReportBuilder value from 2.0 to 3.0.
http://technet.microsoft.com/enus/library/gg712698.aspx#BKMK_ReportBuilder3
Resolution
• Modify Microsoft.ConfigurationManagement.exe.config file and
registry.
Problem
• The Reports folder is empty after enabling a Reporting Services
Point(RSP). Received following error message when click on
Create Report.
"At least one report category must exist before a report
can be created"
Troubleshooting
•
•
•
•
•
•
Verified permissions – Reporting Services CM.
Verified SMS_SRSRP folder and contents exist.
No errors in event logs.
Verified SQL Reporting Services was running.
Verified MSSQL Instance name existed – SQL CM.
Noticed “invalid class” errors and could not retrieve the
reporting services name for instance “MSSQLSERVER”
in srsrp.log.
Resolution
1.
2.
3.
4.
Stop WMI services
Backed up SQLmgmproviderxpsp2up.mof.
Verified I had a CM2012 database backup.
Compile SQL MOF file from C:\Program Files (x86)\Microsoft
SQL Server\100\Shared\ sqlmgmproviderxpsp2up.mof
Problem
• Software Metering data being rejected
swmproc.log:
“Error processing file 09W0XWFR.MUX, file contains bad start or
end time value”
Troubleshooting
• Software Metering data being rejected
• Enabled SQL Tracing
Problem
• App deployment to user collection never runs for some users.
• Never shows up as available under software center.
Troubleshooting
• App is located on DP.
• Boundary is in correct Boundary Group.
• Logged on another machine with same user with same result.
Troubleshooting
• Reviewed IIS logs on DP and noticed HTTP 400 errors.
• Reviewed HTTP 400 - Bad Request (Request Header too long)" error in Internet
Information Services (IIS).http://support.microsoft.com/kb/2020943
• Verified AD group membership of user.
Cause
• User is a member of too many AD User Groups.
Resolution
1) Decrease the number of AD groups.
OR
2) Modify MaxFieldLength and MaxRequestBytes registry settings on IIS servers. New
resolution for problems with Kerberos authentication when users belong to many
groups http://support.microsoft.com/kb/327825
Problem
• MP Install fails to get installed on Windows Server 2012
• Mpmsi.log shows following failures:
Failed to compile 'D:\Program Files\SMS_CCM\CcmExec_Global.mof' (Phase: 3, Object: 5,
Lines: 76 - 83, Error: 80041002)
MSI (s) (AC!18) [10:37:11:128]: Product: ConfigMgr Management Point -- Error 25140.
Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
Error 25140. Setup was unable to compile the file CcmExec_Global.mof
Troubleshooting
• Removed and Reinstalled MP.
• Disabled UAC on Server 2012 and Rebooted.
• Reviewed Mpmsi.log again and noticed line 76 is failure for instance
CCM_Service_HostingConfiguration with compiled 'D:\Program
Files\SMS_CCM\CcmExec.mof‘ error.
• Reviewed the root\CCM class and noticed CM7 client version.
Resolution
• Removed the CM07 client.
• Remove MP and Reinstall.
Problem
• Software Update Deployment not downloading on some clients.
Troubleshooting
• Reviewed ContentTransfer.log.
• Reviewed LocationServices.log.
ContentTransferManager.log:
CCTMJob::UpdateLocations - Received empty location update for CTM Job {D33F82F94E52-416A-8439-6909C6C13486}
CTM job {D33F82F9-4E52-416A-8439-6909C6C13486} suspended
ContentTransferManager
LocationServices.log:
Calling back with empty distribution points list LocationServices
Cause:
Site Server with the DP was not in a Boundary Group
Solution:
1) Add the DP to a boundary group that the client belongs to
OR
2) In the deployment properties, check the option “Download and
install software updates from the fallback content source location”
• I would like to thank the following individuals for their contributions to this sessions
either through sample cases, input, review or morale support. Thank You!
•
•
•
•
•
•
•
•
Buz Brodin
Neil Peterson
Christine Gerth
Eric Orman
Randy Ivey
Don Brown
Heath Lawson
Ray Rosen
•
•
•
•
•
•
•
•
•
Sean Mahoney
Rushi Faldu
Nat Bowman
Anzio Breeze
Scott Williams
Frank Rojas
Matthew Grimshaw
Santos Martinez
Oz Messner