Tuesday, January 29, 2013

SCOM 2012 - NetApp Data ONTAP 3.1 MP Discovery Issues

I was working on a customer site today and came across this annoying discovery issue with the NetApp SAN Data ONTAP 3.1 Management Pack. This will most likely occur in every SCOM 2012 SP1 environment until you either apply the workaround below or until NetApp release Data ONTAP v3.2

After you install the NetApp Data ONTAP 3.1 management pack (check out Stefan's post here for some easy to follow instructions), you will probably find that shortly after adding in the NetApp controllers that they show up with a Critical health state.

If you have read the guide that comes with the NetApp ONTAP 3.1 MP, you can be forgiven for thinking that discovery of your controllers will happen automatically - as stated in the guide. As it turns out, Automatic Discovery of controllers in SCOM 2012 does not work and you will have to manually run the discovery task instead. The following NetApp kb article confirms this (you'll need to register first to read this):

https://kb.netapp.com/support/index?page=content&id=2017408&actp=LIST_RECENT&viewlocale=en_US&searchid=1359463483322

This is where the fun starts!

Taking heed of the NetApp kb article above, when you go and manually run the controller discovery using the task from inside the SCOM 2012 Operations Console, after a few minutes, the Windows Event viewer OnCommand Application Event Log reports the following message: 'Operations Manager could not log into controller'


Log Name: OnCommand
Source: Data ONTAP MP
Date: 12/19/2012 12:51:40 PM
Event ID: 1022
Task Category: (1)
Level: Error
Keywords: Classic
User: N/A
Computer: PHCHBS-S5194.XY.DOMAIN.net
Description:
Operations Manager could not log into controller XX.XX.XX.XX. Using the Data ONTAP credentials manager for System Center Operations Manager, check that valid credentials have been entered for this
controller, and if "Require HTTPS" is selected, verify that the controller is configured to accept HTTPS connections.
Address: XX.XX.XX.XX


These messages are logged every 15 minutes for each and every storage controller that is added into SCOM. When you've tired yourself out trying all different types of combinations to get the above error to go away (with https, without https, different user accounts etc.), then you'll be glad to know that NetApp have kindly provided a workaround to the problem along with a slight admission that this is a known issue with Data ONTAP 3.1 and that they will have it resolved in version 3.2!

This NetApp kb article has the information you need to get up and running (again, you will need to register first to view it):

https://kb.netapp.com/support/index?page=content&id=1014162&actp=search&viewlocale=en_US&searchid=1359463483322

I've copied the text from the kb article here for your convenience:

In the Run Discovery task GUI, use the option to run the task under a different domain admin user.
  1. Create a new Run As action account. Go to Administration > Run As configuration > Accounts > Create Run As account.
  2. Under Run As Account Type, select Action Account.
  3. Make the new account the default action account. Go to Administration > Run As Configuration > Profiles > Default Action Account
  4. Select the Default Action Account, select Properties, and change the Run As Account for the Management Server to the new account created under Create Run As Account.
After the above modification to the new default action account, the discovery will work as expected.
 
Note: In OnCommand Plug-in 3.2, running the Manage Controller Credentials within the context of the default Run As Account  and  issues such as this will be detected immediately when entering the credentials.
 
When you go to run the Discovery task manually again, make sure that you also specify an account in the Task Credentials section as below
 
 
Once the task is complete, you should see the following dialog box
 
 
That's all you should have to do now to ensure that your NetApp SAN and Storage infrastructure get discovered and managed in SCOM 2012 and after waiting for 10 or 15 minutes, you should see all of the LUN's, Volumes, vFilers etc. coming through inside the console.

Wednesday, January 23, 2013

Free SQL Server guide for System Center 2012

A good friend of mine and fellow Irish System Center MVP Paul Keely has taken the time to write up an excellent guide on SQL 2008 R2 and System Center that will help you make design decisions for your deployments.

From the description:

This is a guide to help you make design decisions and maintenance plans for SQL Server 2008 R2 to support System Center 2012.  In the guide you will learn to make server and instance specific changes to support SQL server for the different workloads that System Center requires. We will look at the install requirements per product, what we need to move the data bases and how we should back them up.

Paul has made this guide available on the Microsoft TechNet site and it can be downloaded from here:

http://gallery.technet.microsoft.com/SQL-Server-guide-for-8584c403

He will be refreshing this guide to take into account SQL Server 2012 with System Center in the near future but until then, I'd highly recommend that you take advantage of yet another excellent FREE resource that the System Center community has made available to you and download this today!

Wednesday, January 16, 2013

SCOM 2012 SP1 Prerequisites - The PoSh Way

If like me, you're a System Center consultant and find yourself deploying SCOM/OpsMgr 2012 quite frequently (like once or twice a week), then you will know that acquiring and installing the software prerequisites can be a monotonous task. It's not that they are difficult, just a pain when you have to do it regularly as there are some files to be downloaded from the Microsoft download centre and then a number of Windows Server roles and features to be added too.

The order in which you deploy these prerequisites can also determine the number of additional tasks that you have to carry out to get IIS and .NET framework to work together properly. For these reasons, I wanted to share my quick and easy way of getting these prerequisites installed onto your servers.

This post will serve two purposes. Primarily, it's going to be my own central reference point for when I'm out doing deployments and secondly, it might just serve a useful purpose for others too.


In a Windows environment, if you want to get stuff done quickly and efficiently, then there's no better way in my opinion than to use PowerShell. People that know me, will also probably know that my PowerShell Kung Fu isn't great but that I've promised myself this year to ramp up on it. This post is the start of my New Years resolution and I've included some PowerShell scripts here that will download the relevant prerequisite software and install the roles and features for both Windows Server 2008 and Windows Server 2012 - depending on which O/S you are installing SCOM 2012 SP1 onto.

The Real Credits

Before I go any further, it needs to be noted that the scripts in this blog post are an amalgamated and modified version of the excellent scripts originally posted by Tim McFadden here and Steve Beaumont here. I take no credit for the original code and all I have done is to join the two of them together and add one or two very small changes to suit my own SCOM 2012 SP1 deployments. If you haven't already, then I'd encourage you to take the time to read through Tim and Steve's blog's as they contain loads of valuable information to help you along your way when working with System Center.

SCOM 2012 SP1 Prerequisites

If you are installing SCOM 2012 SP1, then here are the software prerequisites listed on TechNet based on server role:

System Requirements: System Center 2012 SP1 - Operations Manager

As you can see from the link above, some of the server roles only have one or two but with the Web Console role, there are quite a few prerequisites that need to be taken into account. If you were using the GUI to configure and deploy these prerequisites, you can be sure that at some point you'll miss something and have to go back to it once or twice before you get it right.

The Windows Server 2012 Scripts

These scripts are also scoped to each individual SCOM 2012 SP1 role that is deployed onto the Windows Server 2012 Operating System. The main differences though to the Windows Server 2008 prerequisites is that .NET Framework 4.0 can be installed directly using PowerShell in Windows Server 2012 and as such we don't need to download the .NET 4.0 redistributable. This makes integration with IIS easier and therefore less scripting is needed to quickly deploy the prereqs onto Windows Server 2012.

Windows Server 2012 - Management Server Role Only PreReq Script


#This section installs the .NET Prereq for Windows Server 2012#
Import-Module ServerManager
Add-WindowsFeature NET-Framework-Core

Click here to download this PowerShell script as a .PS1 file

Windows Server 2012 - Operations Console Role Only PreReq Script


#This section installs the .NET Prereq for Windows Server 2012#
Import-Module ServerManager
Add-WindowsFeature NET-Framework-Core

#This section will download the Report Viewer Distributable Prereq for Windows Server 2008 or Windows Server 2012 to a folder called C:\SCOM2012SP1Prereqs and will then install it automatically#
$dwnld = "C:\SCOM2012SP1Prereqs"
if (!(Test-Path -path $dwnld))
 {
 New-Item $dwnld -type directory
 }
$object = New-Object Net.WebClient
$RPTurl = 'http://download.microsoft.com/download/E/A/1/EA1BF9E8-D164-4354-8959-F96843DD8F46/ReportViewer.exe'
$object.DownloadFile($RPTurl, "$dwnld\ReportViewer.exe")
Start-Process -FilePath "$dwnld\ReportViewer.exe" -ArgumentList /q -Wait

Click here to download this PowerShell script as a .PS1 file


Windows Server 2012 - Web Console Role Only PreReq Script


#This section installs the .NET and IIS Prereqs for Windows Server 2012#
Import-Module ServerManager
Add-WindowsFeature NET-Framework-Core,AS-HTTP-Activation,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,AS-Web-Support,Web-Metabase,Web-Asp-Net,Web-Windows-Auth –restart


 
Windows Server 2012 - Combined Management Server, Operations Console and Web Console Roles PreReq Script


#This section installs the .NET and IIS Prereqs for Windows Server 2012#
Import-Module ServerManager
Add-WindowsFeature NET-Framework-Core,AS-HTTP-Activation,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,AS-Web-Support,Web-Metabase,Web-Asp-Net,Web-Windows-Auth –restart

#This section will download the Report Viewer Distributable Prereq for Windows Server 2008 or Windows Server 2012 to a folder called C:\SCOM2012SP1Prereqs. Once the file has been downloaded it will automatically install#
$dwnld = "C:\SCOM2012SP1Prereqs"
if (!(Test-Path -path $dwnld))
 {
 New-Item $dwnld -type directory
 }
$object = New-Object Net.WebClient
$RPTurl = 'http://download.microsoft.com/download/E/A/1/EA1BF9E8-D164-4354-8959-F96843DD8F46/ReportViewer.exe'
$object.DownloadFile($RPTurl, "$dwnld\ReportViewer.exe")
Start-Process -FilePath "$dwnld\ReportViewer.exe" -ArgumentList /q -Wait



The Windows Server 2008 Scripts

Although most people will be using the Combined Management Server, Operations Console and Web Console Prereq Script, I'll scope the rest of the scripts here to suit each individual SCOM 2012 SP1 role that's deployed onto Windows Server 2008. The reason for doing this is that the prereq's for each role can vary and obviously we don't want to be installing any more roles or features than we actually have to for a server. 

Windows Server 2008 - Management Server Role Only PreReq Script


#This section will download the .NET Framework 4.0 Redistributable Prereq for the SCOM 2012 SP1 Management Server role on Windows Server 2008 to a folder on the C:\ drive called SCOM2012SP1Prereqs and will then install it automatically #

$dwnld = "C:\SCOM2012SP1Prereqs"
if (!(Test-Path -path $dwnld))
 {
 New-Item $dwnld -type directory
 }
$object = New-Object Net.WebClient
$RPTurl = 'http://download.microsoft.com/download/9/5/A/95A9616B-7A37-4AF6-BC36-D6EA96C8DAAE/dotNetFx40_Full_x86_x64.exe'
$object.DownloadFile($RPTurl, "$dwnld\dotNetFx40_Full_x86_x64.exe")
Start-Process -FilePath "$dwnld\dotNetFx40_Full_x86_x64.exe" -ArgumentList /q -Wait

Click here to download this PowerShell script as a .PS1 file



Windows Server 2008 - Operations Console Role Only PreReq Script


#This section will download the .NET Framework 4.0 Redistributable Prereq for the SCOM 2012 SP1 Management Server role on Windows Server 2008 to a folder on the C:\ drive called SCOM2012SP1Prereqs and will then install it automatically #

$dwnld = "C:\SCOM2012SP1Prereqs"
if (!(Test-Path -path $dwnld))
 {
 New-Item $dwnld -type directory
 }
$object = New-Object Net.WebClient
$RPTurl = 'http://download.microsoft.com/download/9/5/A/95A9616B-7A37-4AF6-BC36-D6EA96C8DAAE/dotNetFx40_Full_x86_x64.exe'
$object.DownloadFile($RPTurl, "$dwnld\dotNetFx40_Full_x86_x64.exe")
Start-Process -FilePath "$dwnld\dotNetFx40_Full_x86_x64.exe" -ArgumentList /q -Wait

#This section will download the Report Viewer Distributable Prereq for the SCOM 2012 SP1 Operations Console role on Windows Server 2008 to a folder on the C:\ drive called SCOM2012SP1Prereqs and will then install it automatically #

$dwnld = "C:\SCOM2012SP1Prereqs"
if (!(Test-Path -path $dwnld))
 {
 New-Item $dwnld -type directory
 }
$object = New-Object Net.WebClient
$RPTurl = 'http://download.microsoft.com/download/E/A/1/EA1BF9E8-D164-4354-8959-F96843DD8F46/ReportViewer.exe'
$object.DownloadFile($RPTurl, "$dwnld\ReportViewer.exe")
Start-Process -FilePath "$dwnld\ReportViewer.exe" -ArgumentList /q -Wait


Windows Server 2008 - Web Console Role Only PreReq Script


#This section will install all the Windows Server 2008 Roles and Feature Prereqs for the Web Console Role#
import-module servermanager
Add-WindowsFeature NET-Framework-Core,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,AS-Web-Support,Web-Metabase,Web-Asp-Net,Web-Windows-Auth,AS-HTTP-Activation –restart

#This section will download the .NET Framework 4.0 Redistributable Prereq for Windows Server 2008 to a  folder on the C:\ drive called SCOM2012SP1Prereqs and will then install it automatically#

$dwnld = "C:\SCOM2012SP1Prereqs"
if (!(Test-Path -path $dwnld))
 {
 New-Item $dwnld -type directory
 }
$object = New-Object Net.WebClient
$RPTurl = 'http://download.microsoft.com/download/9/5/A/95A9616B-7A37-4AF6-BC36-D6EA96C8DAAE/dotNetFx40_Full_x86_x64.exe'
$object.DownloadFile($RPTurl, "$dwnld\dotNetFx40_Full_x86_x64.exe")
Start-Process -FilePath "$dwnld\dotNetFx40_Full_x86_x64.exe" -ArgumentList /q -Wait

#This section will enable the ISAPI and CGI extensions for IIS and .NET 4.0 once the .NET 4.0 redistributable has been installed#
c:\windows\system32\inetsrv\appcmd set config /section:isapiCgiRestriction /[path=`'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll`'].allowed:True


Click here to download this PowerShell script as a .PS1 file


Windows Server 2008 - Combined Management Server, Operations Console and Web Console Roles PreReq Script


#This section will install all the Windows Server 2008 Roles and Feature Prereqs for the Web Console Role#
import-module servermanager
Add-WindowsFeature NET-Framework-Core,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,AS-Web-Support,Web-Metabase,Web-Asp-Net,Web-Windows-Auth,AS-HTTP-Activation –restart

#This section will download the Report Viewer Distributable Prereq for the SCOM 2012 SP1 Operations Console role on Windows Server 2008 to a folder on the C:\ drive called SCOM2012SP1Prereqs and will then install it automatically #

$dwnld = "C:\SCOM2012SP1Prereqs"
if (!(Test-Path -path $dwnld))
 {
 New-Item $dwnld -type directory
 }
$object = New-Object Net.WebClient
$RPTurl = 'http://download.microsoft.com/download/E/A/1/EA1BF9E8-D164-4354-8959-F96843DD8F46/ReportViewer.exe'
$object.DownloadFile($RPTurl, "$dwnld\ReportViewer.exe")
Start-Process -FilePath "$dwnld\ReportViewer.exe" -ArgumentList /q -Wait

#This section will download the .NET Framework 4.0 Redistributable Prereq for Windows Server 2008 to a  folder on the C:\ drive called SCOM2012SP1Prereqs and will then install it automatically#

$dwnld = "C:\SCOM2012SP1Prereqs"
if (!(Test-Path -path $dwnld))
 {
 New-Item $dwnld -type directory
 }
$object = New-Object Net.WebClient
$RPTurl = 'http://download.microsoft.com/download/9/5/A/95A9616B-7A37-4AF6-BC36-D6EA96C8DAAE/dotNetFx40_Full_x86_x64.exe'
$object.DownloadFile($RPTurl, "$dwnld\dotNetFx40_Full_x86_x64.exe")
Start-Process -FilePath "$dwnld\dotNetFx40_Full_x86_x64.exe" -ArgumentList /q -Wait

#This section will enable the ISAPI and CGI extensions for IIS and .NET 4.0 once the .NET 4.0 redistributable has been installed#
c:\windows\system32\inetsrv\appcmd set config /section:isapiCgiRestriction /[path=`'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll`'].allowed:True


Click here to download this PowerShell script as a .PS1 file



Conclusion

Using the scripts above, you should be able to now deploy the prerequisites for SCOM 2012 SP1 in no time and maybe even utilise them as part of an automated service deployment in conjunction with SCVMM and Orchestrator - enjoy!

Tuesday, January 15, 2013

It's Official - System Center 2012 Service Pack 1 is now Generally Available!

Today Microsoft's Travis Wright announced on the System Center Team blog that System Center 2012 Service Pack 1 (SP1) is generally available. The RTM build bits for SP1 have been available to Technet and MSDN subscribers since before Christmas and two weeks ago you could grab it on the Volume License Center, but nothing was official until General Availability (GA) was announced.




Prior to this anticipated announcement, we've seen the release of a whole load of new SP1 specific downloads for System Center 2012 - I posted on some of them earlier this week here. We can expect to see a lot more of these updates and downloads in the coming weeks as the various product teams release updates to management packs, integration packs, solution accelerators and other tools that will take advantage of all of the new features that SP1 brings with it.

Check out the official announcement here:

Official System Center 2012 SP1 Release Announcement

So what are you waiting for?

If you can't wait to get started with SP1 and want to upgrade your existing System Center 2012 deployments then check out these posts I've written up recently to get you started:


Monday, January 14, 2013

DPM 2012 - Installing Service Pack 1 RTM (Part 2)

In Part 1 of this short series on DPM 2012 - Installing Service Pack 1 RTM, I detailed the pre-upgrade tasks that need to be carried out to prepare your DPM 2012 environment for upgrading to Service Pack 1 (SP1) along with the steps required to get your primary DPM 2012 management server upgraded. This post will go through the final steps of the upgrade deployment process to ensure that your agents, secondary DPM servers and backed up data are all running smoothly after the upgrade.

Upgrading the Agents

Once the upgrade of SP1 is complete on your primary DPM 2012 server, you will then need to update any DPM agents that you have deployed in your environment. To do this, open the DPM 2012 SP1 console and click on the Management tab from the wunderbar and then click on the Agents link to display a list of all your agents awaiting upgrade as shown below.


When you click on the Update Available link beside an agent, you will be presented with the following window asking you to confirm if you want to proceed with upgrading the agent to SP1. Click Yes to begin the agent upgrade process.



Once the agent update process completes, you should then be able to verify the SP1 upgrade by confirming that the version of the Protection Agent is set to 4.1.3313.0 as shown below


You might also notice from the Agents list that one or two servers have a status of Restart Pending beside them. These will need to be restarted before you can backup data from them and any downtime due to this will need to be planned for as part of your maintenance schedule.

Run a Manual Consistency Check on Protected Data

Once the primary server and the agents have all been upgraded, you will now need to run a manual consistency check on all of your protection groups. This for me forms the longest part of DPM upgrades when in production environments as the more data you have being backed up, the longer these manual consistency checks will take.

To run the consistency checks, open up the DPM 2012 SP1 console and navigate to the Protection tab in the wunderbar. Once here, you will see that all of your protection groups are in an inconsistent state. Simply right-mouse click on a protection group and then choose the Perform a Consistency Check option from the resulting menu as shown below to kick off a consistency check of replica's contained in that protection group.


Repeat this task on all protection groups until they are all returned to a healthy state.

Upgrade Stand-Alone Consoles

If you have deployed the DPM 2012 console onto any other servers in your environment (such as to support integration with System Center 2012 Orchestrator for example), you will need to first uninstall the Microsoft System Center 2012 - DPM Remote Administration application from the computer before deploying the upgraded SP1 version.

To uninstall the stand-alone console, logon to the server with an administrative account, click Start and type appwiz.cpl as below. 



Now hit Enter to open the Programs and Features applet, find the Microsoft System Center 2012 - DPM Remote Administration program from the list, right-mouse click on it and then choose the Uninstall option to remove it as below


Once you have uninstalled the previous version, browse to the location that you have extracted/mounted the DPM 2012 SP1 media to and then with an administrative account, right-mouse click on the Setup executable and choose the Run As Administrator option to begin the installation


From the Installation splash screen, choose the DPM Remote Administration link as shown below


Accept the licence agreement and click OK


Click Next from the Welcome screen


When all the prerequisites have passed, click Next to move on


Choose your installation location, then click Next to continue


Select your Microsoft Update option and then hit the Install button to begin the SP1 installation of the Remote Administration feature


When the installer is finished, you should see the screen below telling you that it has been successful and you can then hit the Close button to finish


Finally, open up the newly installed stand-alone console, choose the DPM server that you wish to connect with and then ensure that the title bar of the console references Service Pack 1 as below.


Upgrade the Secondary DPM Servers

If you have deployed any additional DPM 2012 servers as a secondary or disaster recovery solution (a DPM server that is backing up another DPM server), then you will also need to run the SP1 upgrade on these. The process is identical to the steps you would have already followed up to this point but for reference, here are the steps again:

On the Secondary Server:
  • Close Administrator Console and Management Shell
  • Carry out the tasks in the Upgrade Primary DPM Server section in Part 1 of this series
  • Upgrade any protection agents on the secondary server by following the Upgrading the Agents section earlier in this post
  • Run a consistency check on all protected data by following the steps in the Run a Manual Consistency Check on Protected Data section earlier in this post

Post Upgrade Tasks

So we're just about finished the SP1 upgrade of DPM 2012 and all that's left to do is to carry out a few quick tasks/checks - some of which may not be applicable to every environment.

  • If you have previously configured tape library sharing and had to remove it as part of the initial pre-upgrade tasks for SP1, you can now go ahead and reconfigure it again using the How to Setup Tape Library Sharing link on TechNet for information.
  • If you had SCVMM Hyper-V Live Migration configured before doing the upgrade, you must run Set-DpmGlobalProperty -KnownVmmServers <VmmServerName> to continue protection
  • If you were protecting system state and you have customized the location of the backup that is staged, this customization will be lost in the PSdataSourceConfig.xml file during the upgrade. The staging location will be set to the drive with the largest available disk space. This will need to be reconfigured again.

Conclusion

That should be all you need to do now to upgrade DPM 2012 to Service Pack 1. Ensure that you refer back to the 'Upgrade Sequencing for System Center 2012 SP1'. guide to ensure that you upgrade any other System Center 2012 products in the correct order.



Sunday, January 13, 2013

DPM 2012 - Installing Service Pack 1 RTM (Part 1)

At long last the final Release To Manufacturing (RTM) version bits of Service Pack 1 (SP1) for System Center 2012 are generally available (GA). 

This Service Pack has been highly anticipated as it not only delivers the customary bug fixes that are to be expected with any such release , but it also brings a large number of new exciting feature additions and enhancements.

This post is one of a number of posts that I've been working on to help people get upgraded to System Center 2012 Service Pack 1. You can check out my other posts here:


Update February 2013 - If you want to be in with a chance of winning a copy of our Mastering System Center 2012 Operations Manager book, then check out the link below to see what you need to do:

Win a Copy of Mastering SCOM 2012 by Evaluating System Center


Be aware that System Center 2012 Service Pack 1 contains updates for the whole suite of products and not just Data Protection Manager (DPM) and it's advised that you follow a particular upgrade sequence of each product as per this warning:

If you are planning to upgrade two or more System Center components, it is imperative that you first consult the guide 'Upgrade Sequencing for System Center 2012 SP1'. The order in which you perform component upgrades is important. Failure to follow the correct upgrade sequence might result in component failure for which no recovery options exist

If you are happy enough with your product upgrade sequence and are now ready to start the DPM 2012 RTM upgrade to Service Pack 1, then this blog post will detail the pre and post SP1 upgrade tasks that you need to consider along with walking you through the deployment of SP1 to your DPM server infrastructure.
Some of the information contained in this post will be taken directly from the accompanying 'DPM2012_UpgradeSP1' guide from Microsoft.

DPM 2012 Service Pack 1 Enhancements

The following list contains some of the enhancements that SP1 brings to System Center 2012 Data Protection Manager (DPM 2012):

  • Improved backup performance of Windows Server 2012 Hyper-V over CSV 2.0 deployments
  • Cluster Shared Volumes (CSVs) provide a distributed file access solution so that multiple nodes in the cluster can simultaneously access the same NTFS file system
In System Center 2012 Service Pack 1 (SP1) DPM, CSV 2.0 support allows the following benefits:
  • 900% improvement in expressful backups
  • Parallel backups
  • No performance difference between backups from owner and non-owner nodes
  • Support for SMB shares
  • Protect Hyper-V over remote SMB share

In System Center 2012 Service Pack 1 (SP1) DPM, SMB shares support allows the following benefits:
  • More efficient expressful backups
  • Continued protection even after Live Migration
  • Support for SMB shares in standalone and scaled-out deployments

DPM now allows you to exclude virtual machine pagefiles from incremental backups to improve usage of storage and improve backup performance
  • Scale out support for Hyper-V virtual machines
  • Protect Windows 8 deduplicated volumes
  • Support for Live Migration
  • Integration with Windows Azure Online Backup
  • Support for protecting file server data
  • Support for protecting virtual machines
  • Support for protecting SQL Server 2012 databases that use the AlwaysOn feature
  • You can use a stand-alone instance of SQL Server 2012 to host the DPM database
  • Support for protecting file server using Resilient File System (ReFS)
  • Support for protecting SharePoint 2013
  • Support for protecting Exchange Server 2013

Upgrading From DPM 2010

Also, before we kick off, it's worth pointing out that although you can perform an in-place upgrade of Service Pack 1 from an existing DPM 2012 RTM installation, you CANNOT upgrade directly from DPM 2010 to DPM 2012 SP1. Instead you must first upgrade DPM 2010 to DPM 2012 and then perform an in-place upgrade.

If you are running DPM 2010 and want to deploy DPM 2012 Service Pack 1, you can check out these old posts of mine to get you started:


High-Level Overview

Here's a high-level overview of what's involved to get your DPM 2012 environment upgraded to SP1:
  1. Accomplish Pre-Upgrade Tasks
  2. Upgrade Primary DPM Servers
  3. Push Install Upgrade to Agents/ Upgrade Manually Installed Agents
  4. Run a Manual Consistency Check on Protected Data
  5. Upgrade any Stand-Alone Remote Administration Consoles
  6. Upgrade Secondary DPM Servers
  7. Accomplish Post-Upgrade Tasks
  8. Return to the Upgrade Sequencing Guide

Pre-Upgrade Tasks
  • Install the latest DPM hotfixes on the DPM server and protected computers (Cumulative Update 3 KB 2751230 is the most recent). For the latest updates and hotfixes for DPM, see Downloads for System Center Data Protection Manager.
  • Ensure that the hard disk on which DPM is installed has at least 4.5 gigabytes (GB) of free disk space
  • You must back up the DPM database and save the backup file in a secure location. For obvious reasons, don't use DPM to backup it's own database prior to upgrading!
  • If you have library sharing enabled, you must first disable library sharing and then backup your DPM dataset. You can enable tape library sharing after installing DPM successfully. For more information, see Removing Library Sharing on TechNet.
  • If you are upgrading your instance of SQL Server to SQL Server 2012, it's recommended to install a new instance of SQL Server 2012 before proceeding with the upgrade. For step-by-step instructions for installing a remote instance of SQL Server, see Installing a Remote Instance of SQL Server 2008
  • Then migrate your database using the steps outlined in Remote SQL Server instance to Remote SQL Server instance
  • If you are also upgrading your operating system to Windows Server 2012, you must enable the Deduplication role.

Upgrade Primary DPM Server

Note 1
If you want to use a remote SQL instance, run the DPM Setup.exe installer on the remote SQL Server and select the DPM Remote SQL Prep tool option from the Setup page. For more information on upgrading DPM database, see the Upgrading the DPM Database article on Technet.

To begin the SP1 upgrade, logon to your DPM 2012 Management Server with an administrative account and then browse to the location that you have mounted or extracted your DPM 2012 SP1 RTM media to. Now right-mouse click on 'Setup' and choose the 'Run As Administrator' option as shown below


From the splash screen, choose the Data Protection Manager link to begin


Click to accept the license terms and conditions, then hit OK


If you haven't installed Cumulative Update/Update Rollup 3 for System Center 2012 to DPM, then you will be presented with the error message below. To upgrade first to CU3, see Downloads for System Center Data Protection Manager.


If you have deployed CU3, then you will see the Welcome screen of the DPM 2012 Setup wizard. Click Next to continue


If you are performing an upgrade of the locally installed SQL instance that runs DPM, then from the Prerequisites Check window, choose the top option as shown below. If you are installing onto a remote SQL server, then you will select the bottom option. Once you have made your selection, click the Check and Install button to move on


When the check has completed, you will be given a final warning to ensure that you have your DPM SQL databases backed up. Click Next to continue


From the Product Registration screen, input your System Center 2012 product key and then click Next


Either choose where you want to install the database files or leave as the default settings, then click Next


At the Security Settings window, enter a password that you are going to use for the DPM SQL Server service account, then click Next


Select whether or not you want to Opt In to use Microsoft Update and then click Next to continue


Choose a setting for the CEIP and then click the Upgrade button to begin the upgrade


Note 2
I had a problem when deploying this upgrade initially to my production DPM 2012 server and halfway through the installation, I was presented with Error ID 820 as the screen below shows. If you come across this issue, take a look at this link for assistance in resolving the problem. For my environment, as I had performed numerous in-place upgrades of DPM over the last couple of years, the installation was strangely failing because the SQL Agent Service for DPM2010 wasn't running. When I started this service and re-ran the upgrade, everything worked as expected!


Once the upgrade finishes successfully, you will be presented with the screen below. Click Close to exit the wizard.


Conclusion

This completes the upgrade to SP1 of your primary DPM 2012 server. In Part 2, I'll walk through the final steps required to completely upgrade your Service Pack 1 deployment.


Friday, January 11, 2013

System Center 2012 Service Pack 1 - What's New?

This is a cross post of one that Rod Trent recently published on the MyITForum.com site with a central link to all of the TechNet 'What's New' articles on System Center 2012 Service Pack 1 (SP1).

Use these links as a quick reference guide to all of the new functionality and enhancements that you get for each of the individual System Center 2012 products when you upgrade to SP1. You can check out Rod's post here and I've posted the TechNet links below for convenience:

New and Recent System Center Downloads

This is just a quick reference post to highlight some of the newest System Center downloads that Microsoft has made available through the Download Center recently.

Some of the downloads are just updated releases of existing management or integration packs and others are new additions to the catalog.

Management Packs (Operations Manager)

Active Directory Domain Services Management Pack for System Center

System Center 2012 Management Pack for Windows Server Hyper-V 2012

System Center Monitoring Pack for Duet Enterprise 2.0

System Center Global Service Monitor Management Packs

System Center 2012 Monitoring Pack for Windows Server Backup

Microsoft Dynamics NAV 2013 Management Pack for System Center


System Center 2012 Service Pack 1 Integration Pack for HP Operations Manager

System Center 2012 Service Pack 1 Integration Pack for HP iLO and OA

System Center 2012 Service Pack 1 Integration Pack for IBM Tivoli Netcool/OMNIbus

System Center 2012 Service Pack 1 Integration Pack for VMware vSphere

System Center 2012 Service Pack 1 Configuration Manager - Clients for Additional Operating Systems

Windows Phone 8 Company Portal App

Thursday, January 10, 2013

SCVMM 2012 SP1 Virtual Networking Explained

This is a cross-post that I wanted to bring peoples attention to about something that a good friend of mine and fellow Irish System Center MVP Damian Flynn (aka Private Cloud Superhero) is involved in.

Update Feb 2013: I've added Damian's second post to the series below. Check them out!

System Center 2012 Service Pack 1 brings an amazing amount of new and enhanced functionality to the whole System Center suite of products. It's understandable that people want to go out and deploy this Service Pack as soon as possible and get working with all these new features but some of them need to be explained in a lot more detail than the information contained in the official technical documentation.


The Virtual Networking functionality in System Center 2012 Virtual Machine Manager (SCVMM) SP1 is one such example of this and Damian is one of the primary authors along with Microsoft's Nigel Cain (Senior Program Manager, Windows Server and System Center) of a new series of blog posts on the official SCVMM blog that aim to unwrap the complexities and teach you how to define, configure and manage Virtual Networks in SCVMM 2012 SP1.

The first blog post in this series has gone live since 8th January and they will be authoring a total of 8 posts over the next 6 months. If you are working with System Center 2012 or plan to deploy virtualisation anytime soon, then I absolutely recommend that you check out these posts to ramp up your knowledge and get the most out of your virtual environment.

You can check out the first two posts in the series here:

Virtual Networking in VMM 2012 SP1

Networking in VMM 2012 SP1 – Logical Networks (Part I)

I'll try to keep my own blog post here updated as Damian and Nigel release new ones.

Monday, January 7, 2013

System Center 2012 Orchestrator (SCORCH 2012) - Installing Service Pack 1 RTM

At long last the final Release To Manufacturing (RTM) version bits of Service Pack 1 (SP1) for System Center 2012 are generally available (GA). 

This Service Pack has been highly anticipated as it not only delivers the customary bug fixes that are to be expected with any such release , but it also brings a large number of new exciting feature additions and enhancements.

This post is one of a number of posts that I've been working on to help people get upgraded to System Center 2012 Service Pack 1. You can check out my other posts here:



The following list contains some of the enhancements that SP1 brings to System Center 2012 Orchestrator (SCORCH/SCO 2012)
  • Support for Windows Server 2012
  • Support for SQL Server 2012
  • New Exchange Administrator Integration Pack for Orchestrator in System Center 2012 SP1
  • New Exchange Users Integration Pack for Orchestrator in System Center 2012 SP1
  • New Representational State Transfer (REST) Integration Pack Guide for Orchestrator in System Center 2012 SP1
  • Updated Active Directory Integration Pack for System Center 2012 - Orchestrator
  • Updated HP Service Manager Integration Pack for System Center 2012 - Orchestrator
  • Updated System Center Integration Pack for System Center 2012 Operations Manager
  • Updated System Center Integration Pack for System Center 2012 Virtual Machine Manager
  • Updated VMware vSphere Integration Pack for System Center 2012 - Orchestrator
Be aware that System Center 2012 Service Pack 1 contains updates for the whole suite of products (not just Orchestrator) and it's advised that you follow a particular upgrade sequence of each product as per this warning:

If you are planning to upgrade two or more System Center components, it is imperative that you first consult the guide 'Upgrade Sequencing for System Center 2012 SP1'. The order in which you perform component upgrades is important. Failure to follow the correct upgrade sequence might result in component failure for which no recovery options exist

If you are happy enough with your product upgrade sequence and are now ready to start the Orchestrator 2012 RTM upgrade to Service Pack 1, then this blog post will detail the pre and post SP1 upgrade tasks that you need to consider along with the deployment of SP1 to your Orchestrator server infrastructure.
Some of the information contained in this post will be taken directly from the accompanying 'Orch12_UpgradeSP1' guide from Microsoft.

Orchestrator 2012 SP1 Pre-Upgrade Tasks

1. Complete all runbooks running in your current Orchestrator installation and ensure they are in a stopped state. For information about stopping runbooks, see the Running Runbooks topic in the Orchestrator library on TechNet.

2. Close any open programs and ensure that there are no pending restarts on the computer. If possible and as a precaution, just restart the Orchestrator server(s) to alleviate this issue.

3. Perform a full backup of the Orchestrator database. For information about backing up the Orchestrator database, see the How to Back up Orchestrator topic in the Orchestrator library on TechNet. You can also use tools provided by SQL Server to back up the Orchestrator database. For more information, see Backing Up and Restoring Databases in SQL Server.

4. Upgrade your hardware, operating system, and other software if necessary to meet the requirements of Orchestrator in System Center 2012 SP1. You can review the SP1 requirements for Orchestrator here.

Before we continue with the upgrade, it's worth mentioning a note in the upgrade guide about System Center 2012 components and their associated integration packs:

Note
To allow you the leeway to upgrade other System Center components as needed, after you have upgraded the Orchestrator servers to System Center 2012 SP1, you can run:
  • A System Center 2012 integration pack against a System Center 2012 component.
  • A System Center 2012 SP1 integration pack against a System Center 2012 SP1 component.
  • No other configurations are supported.

High-Level Overview

Here's a high-level overview of what's involved to get your Orchestrator 2012 environment upgraded to SP1:
  1. If using SCOM 2012 to monitor your Orchestrator environment, put all of the Orchestrator servers in to maintenance mode.
  2. Uninstall any other System Center 2012 product stand-alone consoles (e.g. SCOM or SCVMM consoles)
  3. Uninstall the Orchestrator management server, any runbook servers, the Web Service, and the Runbook Designer.
  4. Install the Orchestrator management server in System Center 2012 SP1, as described in the Deployment Guide
  5. Install any Orchestrator runbook servers in System Center 2012 SP1.
  6. Install the Orchestrator Runbook Designer in System Center 2012 SP1.
  7. If needed, install the Orchestrator Web Service in System Center 2012 SP1.
  8. Take the Orchestrator servers out of maintenance mode.
  9. Update System Center 2012 Orchestrator Integration packs to SP1
  10. Return to the Upgrade Sequencing Guide.
Place Servers into Maintenance Mode in SCOM

If you are monitoring your Orchestrator 2012 servers with SCOM 2012, then it's a good idea to place these servers into Maintenance Mode in SCOM before you start upgrading them to SP1. Doing this will stop any alert storms notifying you that Orchestrator isn't functional and will ensure that your SLA's are maintained.

To place your Orchestrator 2012 servers into Maintenance Mode follow these steps:

Open the SCOM 2012 Operations console, click on the Monitoring tab from the wunderbar and then expand the System Center Orchestrator folder and click on the Management Servers state view as shown below


Now you can right-mouse click on your Orchestrator 2012 servers and choose the Maintenance Mode\Start Maintenance Mode options from the flash out menu to be presented with the Maintenance Mode Settings dialog box. As below, select the Planned radio box, choose a category and specify a duration value for how long you will have the server in Maintenance Mode, then click OK


You should then have an icon with a picture of a wrench located beside your Orchestrator 2012 server(s) as well as a status of Not Monitored indicating that you have placed it into Maintenance Mode.

Uninstall Other System Center 2012 Product Consoles

If you have integrated Orchestrator with any of the other System Center 2012 products, then you will have the relevant stand-alone console for the integrated product installed on your Orchestrator server(s). These consoles will first need to be uninstalled before you upgrade to SP1. As a matter of fact, if you follow the Upgrade Sequencing for System Center 2012 SP1 guide, you will see that some of these consoles will need to be uninstalled anyway as part of the products own SP1 upgrade.

To uninstall the stand-alone consoles, logon to the Orchestrator server, click Start, type appwiz.cpl as below


This will open up the Programs and Features window and from here, you can right-mouse click on the stand-alone console that you want to remove and simply click on the Uninstall/Change button similar to what I've done in the example below for the SCOM 2012 console


Now just follow the onscreen wizard for the relevant System Center application to remove the stand-alone console (SCOM/SCVMM/DPM etc.)

Uninstall the Orchestrator Server Components

The next step in the upgrade process is to uninstall the Orchestrator management server, any runbook servers, the Runbook Designer and the Web service. These components will be reinstalled later as part of the SP1 upgrade.

Similar to the uninstall process above, with an account with administrative permissions, logon to the Orchestrator server, click Start, type appwiz.cpl and then hit Enter to open up the Programs and Features window.

From here, you can right-mouse click on the Orchestrator Server component that you want to remove and simply click on the Uninstall/Change button as below.


Repeat this step until you have removed all of the Orchestrator server components (management server, any runbook servers, the Runbook Designer and the Web service) from your Orchestrator server(s).

Once you have uninstalled all of the Orhcestrator server components, I'd recommend a restart of the  server(s) just to ensure that there are no open files or stale registry keys before we proceed with our upgrade to SP1.

Install the SP1 Orchestrator Server Components

To install the SP1 Orchestrator server components, logon with an account that has administrative permissions and then browse to the location on your server that you have mounted or extracted the System Center 2012 Orchestrator Service Pack 1 media to.

Now locate the SetupOrchestrator executable, right-mouse click on it and choose the Run as Administrator option as below


From the System Center 2012 Orchestrator Setup splash screen, click on the Install option below the Orchestrator heading to continue


At the Product Registration screen, enter your company info and product key, then click Next to continue


Read the license terms from the next page, accept them, then click Next to continue


From the Select Features to Install window, choose the relevant Orchestrator server components that you wish to install and then click Next (in my example below, all of the components are on the same server so I can just leave them all selected.)


At the Configure the Service Account window, enter the service account credentials that you would have used when you initially installed Orchestrator 2012, click the Test button to confirm they are entered correctly and then press Next to move on


From the Configure the Database Server window, enter the SQL server and instance along with the relevant authentication and port information and then click Test Database Connection. If the database connection test succeeds, click Next to continue.


Now from the Configure the Database screen, select the Existing Database option and choose the original database that you had deployed Orchestrator 2012 RTM to. Click Next to move on.


Choose the Orchestrator users group and select the option to grant remote access to the Runbook Designer -or just leave the default settings as they are here, then click Next


Choose your ports for the Web services or just leave them at their default settings, then click Next


From the next screen, select the installation location or again leave at the default setting, then click Next


Configure the Customer Experience Improvement Program (CEIP) settings in the next screen and then click Next


Finally, at the Installation Summary screen, verify all of your configuration settings, then click the Install button to begin the upgrade to SP1


All going well, you should see the screen below confirming that you have completed Setup successfully


Now, when you open up the Orchestrator Runbook Designer, you can see that all of your previous runbooks are still present along with their associated integration packs too


To verify that you have indeed now upgraded your Orchestrator deployment to System Center 2012 Service Pack 1, click on the Help menu and then choose the About option and you will see that SP1 has been applied as shown below



Take Servers out of Maintenance Mode in SCOM

Once the upgrade process is complete, if you haven't placed a time limit on your Maintenance Mode configuration of the SCOM agents on your Orchestrator servers, ensure that you take them out of Maintenance Mode now. Follow the process further up in this post to turn off Maintenance Mode.

Update System Center 2012 Integration Packs to SP1



Once you have upgraded your Orchestrator environment to Service Pack 1, you will need to then upgrade any of your relevant integration packs to their available SP1 versions.  A couple of points to be aware of here though:

Note 1
Be aware that if you install an integration pack that is specifically for SP1, then any earlier version integration packs will need to be first uninstalled from all runbook servers and designers before you can deploy the new SP1 ones. You can then register and deploy the upgrade of the integration pack. If you do not uninstall the previous version of the integration pack prior to registering and deploying the upgrade version, the upgrade version will fail.

Note 2
To allow you the leeway to upgrade other System Center components as needed, after you have upgraded the Orchestrator servers to System Center 2012 SP1, you can run: 
  • A System Center 2012 integration pack against a System Center 2012 component.
  • A System Center 2012 SP1 integration pack against a System Center 2012 SP1 component.
  • No other configurations are supported.

On the 3rd January 2013, Microsoft released the 'System Center 2012 Service Pack 1 - Orchestrator Component Add-ons and Extensions'. It is highly recommended that once you have upgraded your other System Center 2012 products, that you then download these add-ons and extensions and deploy any integration packs that are relevant into your environment to ensure you get the most out of your Service Pack 1 experience.

Conclusion

That should be all you need to do now to upgrade Orchestrator 2012 to Service Pack 1. Ensure that you refer back to the 'Upgrade Sequencing for System Center 2012 SP1'. guide to ensure that you upgrade any other System Center 2012 products in the correct order.