System Center Virtual Machine Manager Self-Service Portal 2.0 SP1 released

Are your datacenter costs rising? Does your current infrastructure make it difficult to scale up or down quickly to respond to the changing needs of your organization? To meet these challenges, you need a more cost-effective, agile way to provide IT services—quickly, efficiently, and on demand.

System Center Virtual Machine Manager Self-Service Portal 2.0 SP1 is a free, partner-extensible solution that allows you to dynamically pool, allocate, and manage datacenter resources. Using the Self-Service Portal, you can reduce IT costs, while increasing agility for your organization. The Self-Service Portal works with products and technologies you know and trust, like Windows Server and the System Center product suite. This solution delivers:

  • Automated web portals and a workload provisioning engine that integrates with System Center.
  • Tested guidance and best practices to help configure and deploy private cloud infrastructures.
  • Guidance to help partners easily extend functionality.
  • Localization in three languages: Japanese, Traditional Chinese, and Simplified Chinese.

Self-Service Portal Technology Partners

The Self-Service Portal includes powerful extensibility features for Microsoft technology partners. Independent software and hardware vendors can customize different virtual machine actions (create, delete, stop, start, shut down, connect, pause, and so on) to take advantage of the unique characteristics of their infrastructure.

Citrix

Citrix Integration Pack for Self-Service Portal

The integration pack integrates Essentials for Hyper-V with System Center by automatically provisioning the storage whenever a virtual machine is commissioned though the Self-Service Portal.
Learn more >

Compellent

Compellent Solution Pack for Self-Service Portal

Utilizing Windows PowerShell® with the Compellent Storage Center SAN, Compellent’s Solution Pack enables the integration and support for self-service provisioning of data storage resources with Virtual Machine Manager and Windows Server Hyper-V™ through the Self-Service Portal.
Learn more >

f5

F5 Solution for Self-Service Portal

The F5 solution for Virtual Machine Manager Self-Service Portal adds the option for traffic management by the BIG-IP application delivery controller (ADC) within the service role section of a user request. Executing this option automatically configures the BIG-IP for the request of VMs as they come online.
Learn more >

HP

HP Services Using the Self-Service Portal

Accelerate your journey to the private cloud with HP’s Converged Infrastructure and HP Technology Consulting services. Begin with a short assessment, then continue to implementation based on HP’s deep experience in the datacenter. HP uses pre-developed scripts, portals, and cmdlets to integrate into your environment and build a self-service infrastructure.
Learn more >

Intel

Intel Cloud Builder Guide: Cloud Design and Deployment on Intel Platforms

The Intel reference architecture will assist organizations that require their cloud data and assets to reside on premises and those that need to support a new business domain with a separate IT infrastructure that is scalable and flexible.
Learn more >

NetApp

NetApp ApplianceWatch PRO 2.1.1

Accelerate virtual machine provisioning, and increase storage efficiencies in private cloud implementations managed by the Self-Service Portal with the integration scripts and PowerShell cmdlets included in ApplianceWatch PRO 2.1.1 that enable rapid provisioning of space-efficient VMs using NetApp FlexClone technology.
Learn more >

VKernel

VKernel Chargeback with Hyper-V

VKernel Chargeback with Hyper-V enables private clouds to automatically map virtualization costs to applications and customers by reporting on allocated costs and by measuring and expensing the actual consumption of server and storage resources by cloud customers.
Learn more >

Moving the SCOM Database to another Database server

There may be certain situations where you need to move the Operations Manager database (OperationsManager) from one SQL Server 2005-based computer to another, including the following:

· The current server is experiencing hardware issues and is not considered reliable.

· The OperationsManager database is collocated on the same server as the Root Management Server and you have decided to dedicate a SQL Server 2005 for the database to improve scalability and performance.

· You need to move the database and log file to a different volume because of space or performance reasons.

· The current server is leased and is due to expire soon.

· New hardware standards have been developed and approved, and you must upgrade your SQL Server-based computer to the new hardware specification.

SQL Server 2005 supports the ability to change the location of the data files and of the log files between SQL Server-based computers, between instances on the same SQL Server-based computer, and different volumes on the same SQL Server-based computer.  For more information about using this function in SQL Server, see the SQL Server 2005 documentation at http://go.microsoft.com/fwlink/?LinkId=93787.  The following section describes the procedures to move the Operations Manager database from one SQL Server-based computer to another.

Before You Start

Go through this checklist before moving the OperationsManager database.

· Make a current backup of all databases, especially the master database, from their current location.

· Verify you have system administrator permissions on both SQL Server-based computers.

· Verify you have installed and configured the new SQL Server-based computer as the existing one.

· Verify you know the name and current location of the Operations Manager database.

· Stop the OpsMgr services (OpsMgr Config Service, OpsMgr SDK Service, and OpsMgr Health Service for Root Management Servers and OpsMgr Health Service for Management Servers) on the Management Servers in the Management Group before proceeding.

· Backup the secure encryption key on the Root Management Server using the SecureStorageBackup.exe utility.

· Stop SQL Service if you want to copy the .mdf and .idf files to a different location.

Note: If the SDK account is “LocalSystem” on the original system, you need to add that account to the new system. Specify OperationsManager as the default database for that account.

Detaching the Database

Perform the following steps on the SQL Server-based computer currently hosting the OperationsManager database:

1.   Open SQL Server Management Studio.

2.   In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, and in the Authentication list, and then click Connect.

3.   Right-click the OperationsManager database, point to Tasks, and then click Detach.

Note: This menu is visible only if you are a member of the sysadmin fixed server role and the server to which you are connected is SQL Server 2005-based.

4.   In the Detach Database dialog box, check the status of the database.  To successfully detach a database, the Status should be The database is ready to be detached.  Optionally, you can select to update statistics prior to the detach operation.

5.   To terminate any existing connections from the database, click Clear.

6.   Click OK. The database node for the detached database is removed from the Database folder.

7.   Once the database has been detached, you can copy the OperationsManager.mdf and OperationsManager.ldf files to a destination directory on the new SQL Server-based computer.

Note: The default location of the OperationsManager.mdf is Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Dataand the default location of the OperationsManager.ldf is Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG.

Attaching the Database

Perform the following steps on the SQL Server-based computer that will be hosting the OperationsManager database:

1.   Open SQL Server Management Studio.

2.   In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, in the Authentication list, and then click Connect.

3.   Right-click the Databases folder, and then click Attach.

Note: This menu is visible only if you are a member of the sysadmin fixed server role and the server to which you are connected is SQL Server 2005-based.

4.   In the Attach Database dialog box, click Add to specify the database to be attached.

5.   In the Local Database Files dialog box, select the disk drive were the database resides and expand the directory tree to find and select the OperationsManager.mdf file.

6.   Click OK, and the database node for the attached database will appear when you refresh Object Explorer by clicking Refresh on the View menu.

Update the Database Server Name on the Management Servers

After you have successfully moved the OperationsManager database, update the Registry on each Management Server in that Management Group to reference the new SQL Server-based computer.

1.   Log onto the Management Server with administrator permissions.

2.   Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor.

Note: Before editing the Registry, follow your site’s backup policies with regard to the registry.

3.   Under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup, double-click the value DatabaseServerName, and then change the value to the hostname of the SQL Server-based computer now hosting the OperationsManager database.

4.   Click OK.

5.   Close the Registry Editor.

6.   After you have completed this step on all Management Servers in the Management Group, restart the OpsMgr Config Service, OpsMgr SDK Service and OpsMgr Health Service on the Root Management Server and restart only the OpsMgr Health Service on the remaining Management Servers.

Important: Do not start the OpsMgr Config Service and OpsMgr SDK Service on the Management Servers, as these services should only be running on the Root Management Server. .

Update the dbo.MT_ManagementGroup table

1.     On the Windows desktop, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2.     In the Connect to Server dialog box, in the Server Type list, select Database Engine; in the Server Name list, select the server and instance for your new Operations Manager database (for example, computer\INSTANCE1); in the Authentication list, select Windows Authentication; and then click Connect.

3.    In the Object Explorer pane, expand Databases, expand OperationsManager, and then expand Tables.

4.    Right-click dbo.MT_ManagementGroup, and then click Open Table.

5.     In the results pane, scroll to the right to the column titled SQLServerName_<guid>.

6.     In the first row, update the value to reflect the name of the new database server name, replacing the name of the old server.

7.     Click File, and then click Exit.

Setting ENABLE_BROKER

Before you can run tasks and use the Discovery Wizard to install agents, you need to set the ENABLE_BROKER value:

1.   Open SQL Server Management Studio.

2.   In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, in the Authentication list, and then click Connect.

3.   Click New Query.

4.   In the query window, enter the following query:

ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE

5.   Click Execute.

6.   Enter the following query:

ALTER DATABASE OperationsManager SET ENABLE_BROKER

7.   Click Execute.

8.   Close SQL Server Management Studio.

Note: Closing SQL Server Management Studio closes the connection to the database in single user mode. Depending on your configuration, you may have to manually kill any process that is connected to the database before completing the ALTER query below.

9.   Open SQL Server Management Studio.

10. In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, in the Authentication list, and then click Connect.

11. Click New Query.

12. In the query window, enter the following query:

ALTER DATABASE OperationsManager SET MULTI_USER

13. Click Execute.

You can verify the setting for ENABLE_BROKER is set to 1 by using this SQL query: SELECT is_broker_enabled FROM sys.databases WHERE name=’OperationsManager’.

Note: Before you can use discovery, you must restart the following services: OpsMgr SDK Service, OpsMgr Config Service, and OpsMgr Health Service. You may have to restart the following services: SQL Server and SQL Server Agent.

Backup Custom Management Packs

Perform the following steps to backup your custom Management Packs.

1.   Log on to a Management Server with an account that is a member of the Operations Manager Administrators role for the Operation Manager 2007 Management Group.

2.   In the Operations Console, click Administration.

3.   In the Administration pane, click Management Packs.

4.   In the Management Packs pane, right-click the Management Pack you want to export, and then click Export Management Pack.

5.   In the Save As dialog box, type the path and file name for the Management Pack file, or click Browse to save the file to a different directory, and then click Save.

Service Level Dashboard 2.0 Beta for System Center Operations Manager 2007 R2 RC1 Now Available!

This free Solution Accelerator collects and monitors operational measurements for your line of business (LOB) applications. Its graphical dashboard makes it easy to keep tabs on service availability and performance, letting you:

  • Spot trends in service availability and performance
  • Head off problems before they occur
  • Reduce costs by streamlining IT operations

This new version of the Service Level Dashboard uses System Center Operations Manager as the engine, and Windows SharePoint Services 3.0 as its presentation platform to track and report service levels on a near real-time basis. The Dashboard now tracks additional metrics for service level compliance, including mean time to repair (MTTR), mean time between failures (MTBF), and application service level trends.  Its SharePoint-based authentication lets you create individual Dashboards by department, so you can easily track service levels for different groups in the organization.

Try it Now!

  1. Click the link to join the Service Level Dashboard 2.0 Beta on Microsoft Connect as part of the System Center Operations Manager Beta Program. You will see the sign-in page for Connect.
  2. Sign in to Connect with your Windows Live ID (or follow the directions to get a free  Live ID if you don’t have one).
  3. In the next screen that appears, click the link “Apply for Participation in this Program.”
  4. Fill out the nomination survey to join the System Center Operations Manager public beta.
  5. You will then see the Operations Manager beta connections page, which provides a link to the Service Level Dashboard 2.0 beta.

Already using SCOM 2007 R2 Release Candidate 1? Click here to start .

SCOM Dell Management Pack Version 3.1.1

An updated on the Dell MP was released this past Friday,

Version A00 changes:
– Dell Server and Printer Management Pack (Dell.Connections.001.mp) code was modified with fixes for discovery of Storage Controllers with Server Administrator version 5.5, and a known defect with health of Virtual Disks, where in some scenarios health of Virtual Disks were not shown correctly.
– The executable ‘DellBMCLog.exe’ was modified to include improved error handling.
– The Storage Array Management Pack (Dell.Connections.StorageArray.mp) and the executable ‘dellabb.exe’ was modified to add support for MD Storage Arrays (MD3000/MD3000i), both generation 1 with firmware version 06.xx.xx.xx as well as generation 2 with firmware version 07.xx.xx.xx.

Download Here : Dell OpsMgr 2007 Management Pack Version 3.1.1

Operations Manager 2007 R2 Beta Now Available!

The System Center Operations Manager team is excited to announce the availability of the Operations Manager 2007 R2 Beta , which is ready for you to download through Microsoft Connect today!

As announced and demonstrated by Brad Anderson at TechEd EMEA 2008 earlier this month, Operations Manager 2007 R2 will deliver key new capabilities including cross-platform monitoring, service-level tracking, new and updated monitor templates (including process, OLE DB, NT Service, and Unix/Linux log file), and much more!

Downloading the Operations Manager 2007 R2 Beta

About Operations Manager 2007 R2

Operations Manager 2007 R2 introduces key new and enhanced functionality, including:

  • Enhanced application performance and availability across heterogeneous platforms Integrated discovery and management of Windows, Unix, Linux and networking devices
    • Delivers monitoring across Windows, Linux and Unix servers–all through a single console.
    • Extends end to end monitoring of distributed applications to any workload running on Windows, Unix and Linux platforms.
    • Maximize availability of virtual workloads with integration with System Center Virtual Machine Manager 2008.
  • Improved management of applications in the data centerService Level Monitoring
    • Delivers on the scale requirements of URL monitoring of your business.
    • Meet agreed service levels with enhanced reporting showing application performance and availability.
    • More efficient problem identification and action to resolve issues.
  • Increased speed of access to information and functionality to drive management
    • Faster console load times for views and results.Integrated Management Pack selection and download
    • Simplified identification and download of new and updated Management Packs through an integrated wizard.
    • Faster identification of where Management Pack settings have been tuned using the new overrides summary view.
    • Simplified notification setup and management.
    • Improved and simplified management pack authoring experience.

The Operations Manager 2007 R2 beta integrates the functionality delivered with the Cross Platform Extensions Beta, which was originally made available at MMS 2008 in April.  Work also continues on the Interoperability Connectors (which enable the sharing of information between Operations Manager and other management systems), and new betas of these will become available in December through the Operations Manager R2 Connect program (we will announce through this blog and to those signed up to the R2 Beta accordingly).

More details can be found in this What’s New & Improved in Operations Manager R2 Overview , or in the documentation found within the R2 Beta Connect program.  Additionally, the Operations Manager 2007 R2 page on TechNet will be updated later today with additional information and links to the download.

Support for the Operations Manager 2007 R2 Beta can be found through the following:

We look forward to your evaluating this exciting new beta release, and hearing your feedback on the Operations Manager 2007 R2 beta.

OpsMgr by Example: Server 2008 POC – Part 5 (Reporting Server)

This is the final of a five part series discussing lessons learned through installing System Center Operations Manager onto a fully Windows 2008 environment (DC, RMS, SQL, and Reporting servers). You can see previous posts in this series at:

At this time, we have successfully completed all of the required pieces of the environment other than the reporting components. This post discusses installing the Reporting Server on Windows Server 2008. The Reporting Server installation is definitely the most error-prone part of the entire OpsMgr installation, be it on Windows 2003 or Windows 2008.

Hotfixes for OpsMgr 20007 – Windows 2008 Servers with Agents

Each of the servers in this configuration needed to have three hotfixes applied to them:

After applying these hotfixes, you will need to reboot the system.

OpsMgr Prerequisites

The .NET Framework 3.0 components are not installed by default. You can install these in the Server Manager by adding the Application Server role.

Prior to installing the reporting components for Operations Manager, follow the steps identified in KB article 938245 (http://support.microsoft.com/kb/938245/ ) to configure reporting services on Windows Server 2008.

Do not attempt to install the reporting components on a system until you can successfully browse to both http://localhost/reports and http://localhost/reportserver on the reporting server . Configuration is required within the Reporting Services Configuration. Browsing of either of the above URL’s will not work until the Reporting Services Configuration is working, we display a functional example below. During our configurations we needed to create a new Report Server Virtual Directory, configure the Database Setup section, and perform an IISReset of the website to get it to a green state for the first six items, as shown in this screenshot:

Reporting Services Configuration Manager

A successful browse of http://localhost/reports and http://localhost/reportserver will look like this:

Success01

Success02

Do not pass go, do not collect $200 /We spent several hours trying to resolve issues that were actually related to configurations necessary for SQL 2005 Reporting Services to work on Windows Server 2008. Installing the reporting components on a system that does not already have functional reporting services will just make the situation worse.

The prerequisites for the Reporting Server component include SQL Server 2005 with Reporting Services (which in turn requires the Web role, etc) with SQL 2005 Service Pack 2 applied.

OpsMgr Reporting Server installation

The installation of Operations Manager’s Reporting Server worked just the same as on a Windows 2003 platform (once the prerequisites had been configured correctly).

What’s Next?

  • Validate reporting functionality both from the existence of the reports and the ability to get valid data from the reports (the Management Pack ODR report is a simple one to validate this with).
  • Deploy Operations Manager agents into the environment.
  • Integrate additional management packs.
  • Wait on official support for Windows Server 2008 as a platform for all of the Operations Manager components.

Lessons Learned

OpsMgr by Example: Server 2008 POC – Part 4 (Data Warehouse Server)

This is the fourth of a five part series discussing lessons learned through installing System Center Operations Manager onto a fully Windows 2008 environment (DC, RMS, SQL, and Reporting servers). You can see previous posts in this series at:

We previously installed and configured the Operations Manager database and the Root Management Server (see parts 2-3 of this series). The next step is installing the Data Warehouse server, followed in Part 5 by the series, which discusses the most difficult of the steps – the reporting server installation.

Hotfixes for OpsMgr 20007 – Windows 2008 Servers with Agents

Each of the servers in this configuration needed to have three hotfixes applied to them:

After applying these hotfixes, you will need to reboot the system.

OpsMgr Prerequisites

The prerequisites were checked for the Data Warehouse in part 2 of this article (http://ops-mgr.spaces.live.com/blog/cns!3D3B8489FCAA9B51!710.entry ), since the same server is hosting both the Operations database and the Data Warehouse components in this environment.

OpsMgr Data Warehouse installation

The installation of Operations Manager’s Data Warehouse worked the same as on a Windows 2003 platform.

Firewall change

The SQL firewall change discussed in part 2 of this series (http://ops-mgr.spaces.live.com/blog/cns!3D3B8489FCAA9B51!710.entry ) provides the documentation for the firewall rule change required to allow connectivity to the SQL Server.

Lessons Learned

There were no surprises when installing the Data Warehouse server on Windows Server 2008.

OpsMgr by Example: Server 2008 POC – Part 3 (Root Management Server)

This is the third of a five part series discussing lessons learned through installing System Center Operations Manager onto a fully Windows 2008 environment (DC, RMS, SQL, and Reporting servers). In this post, we will install and configure the Operations Manager Root Management Server (RMS), as we now have a functional Windows 2008 SQL Server (see Part 2 of this series at http://weblog.bassq.nl/?p=236 ).

Hotfixes for OpsMgr 20007 – Windows 2008 Servers with Agents

Each of the servers in this configuration needed to have three hotfixes applied to them:

After applying these hotfixes, you will need to reboot the system.

Additional hotfixes are required that are specific to the servers with installed OpsMgr components. These include:

OpsMgr Prerequisites

There are several prerequisites for installation of the Root Management Server (plus the console and the web console).

  • With Windows 2008, we need to add the Web Server role (including ASP.net, windows authentication, IIS 6.0 management compatibility and ASP). For background on this, we worked from the article on how to install and configure reporting services on Windows Server 2008 available at http://msdn.microsoft.com/en-us/library/bb839480.aspx .
  • Using the Application Server role adds the .Net framework components.
  • We ended up installing the Windows PowerShell via a command line (ServerManagerCmd –i Powershell ).

OpsMgr RMS, Web Console, Console Install

Installing the Operations Manager’s RMS, Operations Console and Web Console components worked just the same as on a Windows 2003 platform. The only item to note is if the RMS cannot contact the OpsMgr database server, it will display this error:

Setup cannot locate the SC database

Check out the video showing the installation steps:

Firewall change

The RMS installation made the required changes for the Windows 2008 firewall. These included the following ports:

  • Health Service (5723)
  • SDK (5724)
  • Web Console (51908)Application Error Monitoring (51906)
  • Connector Framework (51905)
  • Customer Experience Improvement Program (51907)

Server Manager on RMS

Lessons Learned

  • Windows Server 2008 now installs as roles several of the prerequisite components required for OpsMgr.
  • The Windows 2008 firewall creates the appropriate firewall rules to allow OpsMgr to function on the system.