Hello All,

You may be already experimented this issue with System Center Orchestrator 2012 RC, the statistics available in the web console are never updated and always stay at zero. The two print screens below represent the problem that I had in my lab environment :

This problem is due to a SQL Store procedure that doesn’t start and doesn’t update the statistics in the web console.

To solve that, the very first step is to ensure that the SQL Broker in enable on your SQL Server. Go to you SQL Server and run the following Query :

select is_broker_enabled from sys.databases where name= 'Orchestrator’

If it is not (you get a return value of 0) then you need to enable it by doing the following:

alter database Orchestrator set enable_broker WITH ROLLBACK IMMEDIATE

Now, we’ll check the last execution time of the procedure that is taking care of the statistic update. Execute the follow query :

SELECT
      [m].[Name],
      [m].[IsEnabled],
      [m].[IntervalInSeconds],
      [m].[LastExecutionTime]
FROM [Orchestrator].[Microsoft.SystemCenter.Orchestrator.Maintenance].[MaintenanceTasks] [m]

This will return the following table :

We could see that the LastExcutionTime of the Statistics store procedure is MARCH 15, or this normally procedure has to run every 10 minutes (600 seconds). It’s clear that something is going wrong there.

To start manually this procedure, we have to run the follow query :

EXEC [Microsoft.SystemCenter.Orchestrator.Maintenance].[EnqueueRecurrentTask] @taskName = 'Statistics'

After a few seconds, we must find some data in the following table :

SELECT *
FROM [Orchestrator].[Microsoft.SystemCenter.Orchestrator.Statistics.Internal].[Statistics] 

Running manually the procedure must solve the issue in the majority of the case, but if you still have any statistic  data after running all the SQL queries above, it’s certainly due to your SQL Server that is not working properly.

In fact, it was my case, still no updated statistics. if like me, you are running  your lab SQL server in  a VM on your laptop, VM that you never shutdown /reboot, but always use the PAUSE feature. This could cause some problem with the SQL Store procedures.

How to solve that ? Simply reboot your SQL Server. After the reboot, my statistic updated automatically.

I hope this help you

Thanks to Travis Wright and Chris Sanders for their help on this topic.

Christopher KEYAERT

database · FROM · MaintenanceTasks · Orchestrator · Store

Hi Everyone,

Kurt Vanhoucke and myself will present two sessions about System Center Orchestrator 2012.

Event Details

Come and join us for our first event after the hot summer months. During this event we will discuss the new System Center Orchestrator, what has changed, new integration packs and also how to migrate from Opalis 6.3 to SCORCH.

Agenda

Thursday, September 29, 2011 from 6:00 PM - 9:00 PM (GMT+0100)

TimeSlot	Speaker	Title
18.00 – 18:30		Welcome and Pizza
18.30 – 19:30	Kurt Vanhoucke	System Center Orchestrator 2012 : Overview
19:30 – 20:30	Christopher Keyaert	System Center Orchestrator 2012 : Migration Plan

Location

Microsoft Belgium
Leonardo Da Vincilaan 3
Zaventem
Belgium

or Online via LiveMeeting (Lync)

Registration

Go to the registration website.

Cheers
Christopher KEYAERT
http://twitter.com/keyaertc

Migration · Orchestrator · pizza · Thursday · Vincilaan

Get a sneak peak preview of System Center Orchestrator and see what Opalis can do in your environment today.

By combining the power of the system center suite, we will demonstrate an entire workflow automated through Opalis. This will provide the attendees a view of the Opalis solution and how to implement runbook solutions with or without other System Center Products.

Watch the video : http://technet.microsoft.com/en-us/edge/introduction-to-opalis-and-a-sneak-peek-at-system-center-orchestrator

Microsoft System Center Orchestrator 2012 Resources :
Microsoft System Center Orchestrator 2012 beta is available as public beta at the Microsoft Download Center : http://www.microsoft.com/download/en/details.aspx?id=26503

Microsoft System Center Orchestrator 2012 Team Blog : http://blogs.technet.com/b/scorch/

TechNet Forums for System Center Cross Platform and Interoperability :http://social.technet.microsoft.com/Forums/en-US/category/scinterop

Cheers
Christopher KEYAERT
http://twitter.com/keyaertc

blog · opalis · Orchestrator · platform · technet microsoft

Adam Hall, Senior Technical Product Manager for Orchestrator, just posted new Orchestrator Integration Packs for the System Center 2007/2008/2010 releases and the Quick Integration Kit (QIK).

Quick Integration Kit (QIK):
http://download.microsoft.com/download/9/B/2/9B262883-BDF9-465D-99A8-9836539F4323/Opalis_Quick_Integration_Kit.EXE

1. System Center 2007/2008/2010 IPs direct download: http://download.microsoft.com/download/C/F/3/CF375506-F342-4974-B7B5-F06EFDEC159C/Opalis_SystemCenter_IntegrationPacks.EXE

2. Extract the files:

3. Start the System Center Orchestrator Deployment Manager, right click on Integration Packs and select Register IP with the Orchestrator Management Server.

4. Pass the welcome screen by clicking Next:

5. Click on add and select the IPs that you extracted:

6. Once all the Integration Packs added, click on Next:

7. Validate the information and click on Finish:

8. you will be prompt for license agreement, accept all of them:

9. Confirm in the log of the console than all the IPs has been well imported:

10. Go to Integration Packs view:

11. Select all of them, right click and select Deploy IP to Runbook Server or Runbook Designer:

12. Pass the Welcome screen:

13. Select all the IPs that you want to deploy on your Runbook server/Runbook designer:

14. Enter the name of your Runbook server/Runbook designer:

15. If you want to deploy immediately, left the options unchanged:

16. Review the information and click Finish:

17. Deployment in progress:

18. Confirm that the IPs has been well deployed on the Runbook Server/Designer:

19. Start the System Center Orchestrator Runbook Designer and take a look to the new IPs:

20. System Center Configuration Manager activities:

21. System Center Operations Manager 2007 activities:

22. System Center Service Manager activities:

23. System Center Data Protection Manager activities:

24. System Center Virtual Machine Manager activities:

That’s all for this first overview

Christopher KEYAERT

Kit · look · Orchestrator · Packs · virtual machine manager

• System Center Advisor announced: Azure service previously code-named “Project Atlanta” uses the OpsMgr Agent to return configuration and make recommendations for changes to the configuration. This application was demonstrated during the keynote showing how a hotfix would be relevant for the servers and what has changed in the environment. Licensing – if you have software assurance on Windows Server you are licensed to use this on the server (or Exchange software assurance for Exchange servers). Beta currently available.
• The next version of Opalis Integration Server is officially named System Center Orchestrator 2012.
• SCVMM 2012 beta announced.
• System Center 2012 officially announcement: Every product in the (System Center) portfolio will have new revisions in the next year.

Credits : http://opsmgrunleashed.wordpress.com/2011/03/22/mms-2011-keynote-322-summary-for-geeks/

code-named · Licensing · Orchestrator · software assurance · year