Cumulative Update 6 for System Center Operations Manager 2007 R2 is available. Cumulative Update 6 for Operations Manager 2007 R2 resolves the following issues:
For all the details and a download link, see the following Knowledge Base article:
KB2626076 - Cumulative Update 6 for System Center Operations Manager 2007 R2 is available
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Managing and Operating a Microsoft Private Cloud—How to Apply the Microsoft Operations Framework (MOF)
The Microsoft Operations Framework team is working on a new guide: Managing and Operating a Microsoft Private Cloud—How to Apply the Microsoft Operations Framework.
Get the beta here.
This guide leads you through the process of how to manage and operate a Microsoft private cloud using the service management processes of the Microsoft Operations Framework (MOF). The guide applies MOF’s IT service management principles to that conceptual architecture and technology stack. It describes how to maximize the potential of MOF’s people, process, and technical capabilities to manage and operate a Microsoft private cloud.
Follow this guidance for a private cloud that is better aligned to meet your business needs. Employ MOF’s service management functions (SMFs) to help align IT and business goals, which can enable you to perform private cloud activities effectively and cost-efficiently.
This guide focuses on the SMFs in the Operate Phase and the Manage Layer of MOF to give IT pros and managers what they need to know about managing and operating a private cloud. Management reviews—internal controls that ensure goals are met to achieve business value—are also included.
Tell us what you think! Download and review the beta guide, then send your feedback to mofpm@microsoft.com by June 11, 2012. We would especially appreciate feedback in the following areas:
· Usefulness – Is the technical depth of this guide sufficient for the topics covered? Will this guide be useful to you on a day-to-day basis? What portions of the guide are the most useful to your organization?
· Usability – Is the structure or flow of this guide effective? Is the information presented in a clear and logical manner? Can you easily find key content?
· Impact – Do you anticipate that this guide will save you time and accelerate deployment of Microsoft products in your organization? Has this guide had a positive influence on your opinion of the Microsoft technologies it addresses?
Benefits for participation:
· You get an early look at the guide.
· You will be listed on the acknowledgments page for providing usable feedback.
Subscribe to the MOF beta program and we will notify you when new beta guides become available for your review and feedback. These are open beta downloads. If you are not already a member of the MOF Beta Program and would like to join, follow these steps:
1. Go here to join the MOF beta program:
https://connect.microsoft.com/site14/InvitationUse.aspx?ProgramID=1880&InvitationID=MOFN-M6H9-PV3X
If the link does not work for you, copy and paste it into the web browser address bar.
2. Sign in using a valid Windows Live® ID.
3. Enter your registration information.
4. Continue to the MOF program beta page, scroll down to Microsoft Operations Framework, and click the link to join the MOF beta program.
Please send your comments and feedback to mofpm@microsoft.com.
Want to learn more about other MOF guides?
Visit our MOF page for information on the full series of Microsoft Operations Framework guides.
Check out our other Solution Accelerators:
You can see our full catalog of Solution Accelerators here.
Questions & Feedback:
For Microsoft-internal questions and feedback on the guide, please contact us.
Here’s a new Knowledge Base article we published this morning. This one describes an event you may see when deleting a Favorite in AVIcode or System Center 2012 Operations Manager.
=====
After deleting a Favorite Report from AVIcode Advisor in AVIcode 5.7 or Application Advisor from System Center 2012 Operations Manager, you may see an event logged with the message below. The event is logged as an Informational Event with ID 0 in the Intercept Log in AVIcode 5.7 and as an Error Event with ID 34852 in the Operations Manager log in System Center 2012 Operations Manager.
Subscription for Favorite cannot be deleted Message: System.Web.Services.Protocols.SoapException: The value for parameter 'SubscriptionID' is not specified. It is either missing from the function call, or it is set to null. ---> Microsoft.ReportingServices.Diagnostics.Utilities.MissingParameterException: The value for parameter 'SubscriptionID' is not specified. It is either missing from the function call, or it is set to null. at Microsoft.ReportingServices.Library.DeleteSubscriptionActionParameters.Validate() at Microsoft.ReportingServices.Library.RSSoapAction`1.Execute() at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.DeleteSubscription(String SubscriptionID) --- End of inner exception stack trace --- at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.DeleteSubscription(String SubscriptionID) at Microsoft.ReportingServices.WebServer.ReportingService2005.DeleteSubscription(String SubscriptionID) Source: System.Web.Services Target Site: System.Object[] ReadResponse(System.Web.Services.Protocols.SoapClientMessage, System.Net.WebResponse, System.IO.Stream, Boolean) Stack Trace: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Avicode.Intercept.SEManager.Core.Services.ReportingServices.ReportingService.DeleteSubscription(String SubscriptionID) at Avicode.Intercept.SEManager.WebViewer.Modules.FavoritesSelector.DeleteFavorite()
This event occurs when the Favorite report being deleted has a NULL value for the SubscriptionID column in the dbo.FAVORITE table in the SEViewer database for AVIcode 5.7, or in the apm.FAVORITE table in the OperationsManager database for System Center 2012 Operations Manager. This event can safely be ignored as the report is successfully removed from the users Favorites.
For the most current version of this article please see the following:
2704138 - Deleting a Favorite in Advisor produces an error in the Event Log
An update to Update Rollup 1 for System Center 2012 has been released. In addition to the previous fixes for Virtual Machine Manager (VMM) and App Controller (AC), the update rollup now includes fixes for Operations Manager (OM).
A few things to note:
1) What we used to call ‘Cumulative Updates’ (CU) are now called ‘Update Rollups’ (UR).
2) We will release Update Rollups for the entire suite not individual components as we have in the past. Not every component will have something to release in each Update Rollup.
3) The UR 1 was originally released a couple of weeks ago. This is an update to the UR that now includes some fixes for SCOM.
You can find out more about what is in Update Rollup 1 and get details on how to download and install it here:
http://support.microsoft.com/kb/2686249
The VMM and App Controller updates are available via Microsoft Update.
Below is a snapshot of the VMM and App Controller updates on Microsoft Update.
This came out a little while ago but better late than never to promote it!
This management pack synchronizes System Center 2012 - Operations Manager Application Performance Monitoring (APM) alerts and Team Foundation Server (TFS) work items. After importing this management pack, operators can manually assign APM alerts to the engineering team. Assigning an APM alert to engineering creates a new work item in Team Foundation Server. The management pack workflow tracks and synchronizes changes made to TFS work items and changes made to associated Operations Manager APM alerts. Important: Only APM alerts that are directly linked to events in Application Diagnostics can be linked to TFS work items. If you assign any other type of alerts to engineering, they will not synchronize with TFS work items. Feature Summary After importing this management pack, operators can:
Download here:
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=29422
With Microsoft System Center 2012 Operations Manager connections to other Enterprise Management (EM) tools or Service Desks are now provided via System Center 2012 Orchestrator. Customers have been asking how to build a suite of Orchestrator Runbooks which enable a robust flow of data from Operations Manager 2012 to these other EM tools and Service Desks.
Kelverion have developed and recently released a series of ‘free of charge’ Runbooks that use best practices to connect Operations Manager 2012 to a number of EM tools and Service Desks as follows:
Service Desks
Enterprise Management Tools
These Runbook Connectors deliver a number of inter-connection functions such as;
For customers looking for event enrichment and more in-depth processing of events from Operations Manager, this can be achieved by adding further Runbooks to the base solution.
The package includes the Runbooks, User Guide, evaluation copy of the Integration Pack for Databases and Runbook Surveyor documentation of the Runbook configurations. The package is available to download from here.
The product description is available on the Kelverion website here.
If you have any questions regarding these Connectors or require assistance please contact info@kelverion.com
Here’s a new Knowledge Base article we published this morning. This one discusses a database related issue you may run into when installing System Center 2012 Operations Manager.
While installing System Center 2012 Operations Manager, the installation fails and you receive the error "Setup Cannot be Completed".
This may occur if the OperationsManager.mdf and OperationsManager.ldf files already exist in the directory where you chose to install the new OperationsManager database. If this occurs you will see an error similar to the following in the OpsMgrSetupWizard.log file: [05:44:19]: Error: :Exception running sql string CREATE DATABASE [OperationsManager] ON PRIMARY(NAME=MOM_DATA,FILENAME='C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\OperationsManager.mdf',SIZE=1000MB,MAXSIZE=1000MB,FILEGROWTH=0MB) LOG ON(NAME=MOM_LOG, FILENAME='C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\OperationsManager.ldf',SIZE=500MB,MAXSIZE=500MB,FILEGROWTH=0MB) COLLATE SQL_Latin1_General_CP1_CI_AS: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\OperationsManager.mdf' because it already exists. Change the file path or the file name, and retry the operation. CREATE DATABASE failed. Some file names listed could not be created. Check related errors. [05:44:19]: Error: :StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlStrings(String[] sqlCommands) [05:44:19]: Always: :Failed to create and configure the DB with exception.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\OperationsManager.mdf' because it already exists. Change the file path or the file name, and retry the operation. CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
NOTE The OpsMgrSetupWizard.log file is located in C:\Users\<InstallationAccount>\AppData\Local\SCOM\Logs
To resolve this issue, you must either delete the old OperationsManager mdf and ldf files, or move them to a separate location and run the install again.
2705760 - You may receive the error "Setup Cannot be Completed" when installing System Center 2012 Operations Manager
Update Rollup 1 for System Center 2012 contains a number of fixes for System Center 2012 Operations Manager, App Controller and Virtual Machine Manager, including cross platform fixes and support for Oracle Solaris 11.
I won’t go into all the details here but you can see what’s included as well as get a download link in the following KB article:
KB2686249 - Description of Update Rollup 1 for System Center 2012 (http://support.microsoft.com/kb/2686249)
Here’s a new Knowledge Base article we published today. This one talks about an issue where the Orchestrator Runbook Service starts and then stops after 30-60 seconds and logs a 7023 event.
The Orchestrator Runbook Service (orunbook) on a System Center Orchestrator Runbook Server starts successfully but then terminates after 30-60 seconds. In the System Event Log of the System Center Orchestrator Runbook Server, the following sequence of events will be seen:
Log Name: System Source: Service Control Manager Date: Event ID: 7036 Task Category: None Level: Information Keywords: Classic User: N/A Computer: <Computer> Description: The Orchestrator Runbook Service service entered the running state.
Log Name: System Source: Service Control Manager Date: Event ID: 7036 Task Category: None Level: Information Keywords: Classic User: N/A Computer: <Computer> Description: The Orchestrator Runbook Service service entered the stopped state.
Log Name: System Source: Service Control Manager Date: Event ID: 7023 Task Category: None Level: Error Keywords: Classic User: N/A Computer: <Computer> Description: The Orchestrator Runbook Service service terminated with the following error: %%-2147467259
Additionally the following may be observed.
When querying the status of the Orchestrator Runbook Service using SC.exe, the following output shows the last exit code when the service is in a stopped state:
C:\Windows\system32>sc query orunbook
SERVICE_NAME: orunbook TYPE : 10 WIN32_OWN_PROCESS STATE : 1 STOPPED WIN32_EXIT_CODE : -2147467259 (0x80004005) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0
One or more exceptions may be captured in the Orchestrator Runbook Service logging folder on the Orchestrator Runbook Server computer. The default path for these logs is "C:\ProgramData\Microsoft System Center 2012\Orchestrator\RunbookService.exe\Logs".
The Orchestrator Runbook Service was not able to connect to the Orchestrator database. This could be due to any of the following reasons:
Correct the problem that is preventing the Orchestrator Runbook Service from connecting to the Orchestrator database.
The Orchestrator Runbook Service will only terminate due to failed connectivity to the Orchestrator database during the service start. Once the service has successfully started with full database connectivity, any future database issues will be captured and logged without the service terminating. This issue occurs most frequently when the System Center Orchestrator environment is restarted and the Orchestrator Runbook Service starts before the Orchestrator database is fully online. In this case, configuring the Orchestrator Runbook Service Recovery Properties can often automatically remediate the problem by having the service wait a period of time and then attempt to start again.
2702157 - The Orchestrator Runbook Service starts and then stops after 30-60 seconds
Here’s a new Knowledge Base article we published this morning. This one discusses a database issue you may run into when installing System Center 2012 Operations Manager.
When configuring the database during the System Center 2012 Operations Manager installation, next to the database name field, you may receive a Red Circle with an X inside and no tooltip provided with further information about the error if you hover over it.
This issue occurs when the database name provided is greater than 128 characters. To resolve the issue, shorten the database name to less than 128 characters.
2704143 - Configuring Database fails and presents a Red X when installing System Center 2012 Operations Manager