This is the first stage in a two-stage process. Following a successful SP1 upgrade the next step will be to upgrade to Configuration Manager 2012 R2

Transcription

1 Project Page 1 Project Synopsis 10 January :47 To upgrade our Current Configuration Manager to SP1 This is the first stage in a twostage process. Following a successful SP1 upgrade the next step will be to upgrade to Configuration Manager 2012 R2 Proposed date of upgrade: February 17th 2014

2 Project Page 2 Current Configuration 10 January :48 Single Server containing Configuration Manager with all Site System roles and SQL Database Network Configuration: o IP: xx.xx.xx.xx o Gateway: xx.xx.xx.xx o DNS: xx.xx.xx.xx, xx.xx.xx.xx Server Name: X Site Code: XXX Configuration Manager Install Directory: C:\Program Files\Microsoft Configuration Manager Configuration Manager Build Number: 7711 Site System Roles: o Application Catalog web service point o Application Catalog website point o Asset Intelligence synchronization point o Component server o Distribution point o Endpoint Protection point o Management point o Reporting Services point o Site Database server o Site Server o Site System o Software Update point o State migration point Current installed version of SQL is: SQL Server 2008 R2 Std SP1 + CU6 (Source: Helpstar:22619)

3 Project Page 3 Current MSInfo for Config Mgr Server: XXX xxx IPConfig /all: xxx Site Details: xxx

4 Project Page 4 Current Site Maintenance Tasks 15 January :46 Current Site Maintenance Tasks These three Site Maintenance tasks will need to be temporarily disabled while the upgrade to SP1 takes place.

5 <picture removed> Project Page 5

6 Project Page 6 Current BackUps 13 January :23 XXX has a full 7 day daily backup via Backup Exec which includes all drives and content. A Config Manager Site Maintenance Task scheduled to run every day between 03:00 and 05:00 backups up the site database and site configuration files to F:\XXBackup on the configmgrserver. This back up is also part of the nightly tape backup as mentioned above using Backup Exec.

7 Project Page 7 PreReq Checks 13 January :17 Check that we meet all prerequisites according to the documentation Check requirements against this document. SQL Requirement Our Current Installation: Pass / Fail SQL Server version PASS Database Collation PASS SQL Server Features PASS Windows Authentication PASS SQL Server Instance PASS SQL Server Memory PASS Operating System Deployment Requirement Windows Assessment and Deployment Kit 8.0 (ADK) Our Current Installation: Pass / Fail FAIL We currently have AIK installed. We will need to remove AIK and install ADK prior to SP1 Windows Management Framework 3.0 As per step 4 of this document, WMF 3.0 is required. Requirement Our Current Installation: Pass / Fail Windows Management Framework 3.0 FAIL This will need to be installed prior to SP1

8 Project Page 8 Proposed Install Order 15 January :19 Proposed Order for installation o Run a test upgrade on a copy of the live site database in a Virtual Machine o Review Site Status and Component Status (In Configuration Manager Console: Monitoring > System Status) o Remove AIK o Install ADK 8.0 Selecting only the following features: Deployment tools Windows Preinstallation Environment (Windows PE) User State Migration Tool (USMT) o Install Windows Management Framework 3.0 (WMF 3.0) o Copy off the Site Database backup o Disable Maintenance tasks: Back up site server Delete aged client operations Delete aged discovery data o Run the prerequisite Checker (D:\SMSSETUP\BIN\X64\prereqchk.exe) o Restart the server o Install SP1 o Upgrade standalone configuration manager consoles (eg on CSU computers) o Reenable maintenance tasks o Turn on auto client upgrade

9 Project Page 9 License 14 January :42 Setup key: <Removed>

10 Project Page 10 Links 13 January :19 Initial Reading and Research I started off by reading the following documents in order to get an overall view of the complete process: How to upgrade System Center 2012 Configuration Manager to SP1 Planning to upgrade System Center 2012 Configuration Manager Supported Configurations for Configuration Manager Technical Reference for the Prerequisite Checker in Configuration Manager Upgrade Configuration Manager to a New Service Pack Backup and Recovery in Configuration Manager Test the Site Database for an upgrade I also took a look at this video: Upgrading System Center 2012 Configuration Manager to Service Pack 1

11 How To's Page 11 How to Create a Site Maintenance Task to Create a Site Backup 15 January :29 Here is the document that I used for ensuring that our Site Maintenance Backup was correctly configured: It is worth noting that the backup will be overwritten the next time the Site Maintenance task runs. Luckily, after the backup has run it will look for and run the AfterBackup.bat file if you have created one. This can contain any post backup commands that you wish to take place such as copying the backup to another server for example. For our scenario we will not be running any postbackup commands as the backup created by the Site Maintenance task is backed up every night as part of our main BackupExec tape backup.

12 How To's Page 12 How to perform a test upgrade on the site database 15 January :48 It is highly recommended to perform a test upgrade on the most recent copy of the site database. This is the documentation I followed: Here are the steps I followed in order to do this: Please note that you do not need an installation of Configuration Manager 2012 in order to do this only SQL server In a virtual machine ( I was using HyperV) I installed the same Server OS and SQL server version including all service packs and Cumulative Updates as our live system. Copy the Site Back up to the virtual server To attach the backed up database, open SQL Server Management Studio in your virtual machine, RightClick Databases and select 'Attach' then browse to the CM_XX.mdf file in your copied site back up. (As per step 2 above) Run the following command in order to perform a test upgrade on your imported database: (Where D: is you CD drive that has the SP1 installation media, MSSQLSERVER is the name of your SQL instance and CM_XX is the name of the database. D:\SMSSETUP\BIN\X64\Setup.exe /TESTDBUPGRADE MSSQLSERVER\CM_XX If you do not know the instance name then in your virtual server, open Sql Server Configuration Manager and look under the node: SQL Server Network Configuration. In the screenshot below the instance name is: MSSQLSERVER 6. When I ran this, the Installation prerequisite checker gave me an error about SQL Server Native Client not being installed.

13 It turns out that this is installed as part of the actual upgrade when you come to do it so is only needed separately in our test environment. To remedy this error you need to download and install the 2012 feature pack from here: Scroll to about halfway down the page and you'll see sqlncli.msi Download and install this and then rerun the upgrade test as per step 4 above: How To's Page 13

14 7. This time we have success. Click on the 'Begin TestDBUpgrade' button to begin: How To's Page 14

15 How To's Page Three log files are created in the root directory (in my case c:): ConfigMgrPrereq.log, ConfigMgrSetup.log and ConfigMgrSetupWizard.log. Take a look at all of these logs however, we are looking for the following line at the end of the ConfigMgrSetup.log to indicate a successful upgrade: INFO: Configuration Manager Setup has successfully upgraded the database.

16 Tasks Page 16 Prereq Tasks 10 January :44 Research SP1 upgrade procedure Check Existing prereqs met Ensure site maintenance backups successful Initial test upgrade of site database in VM (Result: Successful) Download all media (SCCM SP1, WMF 3.0, ADK 8.0) Configuration Manager 2012 with SP1 and Endpoint Protection Windows Management Framework 3.0 Windows Assessment and Deployment Toolkit (ADK) v8.0

17 Tasks Page 17 Install SP1 16 January :36 Run a test upgrade on a copy of the live site database in a Virtual Machine Review Site Status and Component Status (In Configuration Manager Console: Monitoring > System Status) Remove AIK Install ADK 8.0 Selecting only the following features: Deployment tools Windows Preinstallation Environment (Windows PE) User State Migration Tool (USMT) Install Windows Management Framework 3.0 (WMF 3.0) Restart server Copy off the Site Database backup Disable Maintenance tasks: Back up site server Delete aged client operations Delete aged discovery data Run the prerequisite Checker and resolve any issues. (D:\SMSSETUP\BIN\X64\prereqchk.exe) (Initially failed see PreReq Failure page) Restart the server Install SP1 Restart the server

18 Tasks Page 18 PreReq Failure 17 February :44 Failed Prereq check: Solution: Our Version is Downloaded and installed KB x64 Downloaded and installed KB x64 KB required a server restart.

19 Tasks Page 19 Post SP1 16 January :36 Check c:\configmgrsetup.log Check Config Manager Health (site and Component status) Reenable previously disabled maintenance tasks Upgrade standalone configuration manager consoles (eg on CSU computers) Turn on auto client upgrade Check Config Manager functionality: Imaging Software Deployment AntiVirus updates Remote Control Reporting Check and Adjust task sequences eg change Config Manager Client version

20 Tasks Page 20 ConfigMgrSetup.log 17 February :27 <log removed>

21 Configuration Manager Console installation failed 17 February :40 Error: Resolution: Resolved by installing the Configuration Manager on the server Manually via the splash.hta: Tasks Page 21

22 Tasks Page 22 FearTheMonkey 19 February :41 See for resolution to the following issues encountered: Configuration Manager Console not upgraded on server. Boot Images not upgraded to correct version PXE not functioning Error E53 (This despite the boot image issue being resolved) User State Migration not working in the task sequence.

23 Impact Page 23 Impact 16 January :01 Estimated server downtime: 1hr 50mins Uninstall AIK: 20 Minutes ADK 8.0 Installation: 20 Minutes WMF minutes Install SP1 1hour Services Affected: While the Configuration Manager Server is being upgraded the following services will be unavailable: Affecting Computer Services: Imaging Software Deployment Reporting Windows Updates AntiVirus updates Remote Control Affecting End Users: SelfImaging XP to Win 7 Software Deployment from the Software Catalogue \ Software Center

24 Impact Page 24 Disaster Recovery 16 January :58 Disaster Recovery: Reference Document: In the event of catastrophic failure the rollback of SP1 is not supported. To rollback we will need to uninstall all site system roles and then the Configuration Manager Site itself. After the site is uninstalled we can then reinstall the site with the version of Configuration Manager that we require (ie nonsp1) and restore the original site database from back up. Installation Media (non SP1) Location required for Rollback: S:\BusinessSupport\CSU\CSUArchives\Software (Microsoft)\System Center\Configuration Manager 2012 Estimated Time to recover basic services (Remote Control and Antivirus protection) following a disaster: 2 days

25 Impact Page 25 External Support 16 January :01 We have a technical support contract with XXX Standard support hours are 8am to 5pm xxx