A first look at the SCOM 2016 Technical Preview 2

As I mentioned in my last post which you can find here, SCOM 2016 has quite a lot of nice new features such as the scheduled maintenance mode. What I will show you briefly here is how to install the technical preview 2 of SCOM 2016 and what it takes to do so. You will also get a glimpse of the new scheduled maintenance mode feature 🙂 Download the Technical Preview of System Center 2016 here.


If you´ve ever installed SCOM 2012 or 2012 R2, the only difference is that you must be running SQL Server 2014 to be able to install the product. I did try to install it using a SQL Server 2012 instance as well but then I couldn´t find the instance from within the setup process. Other than the SQL part, the prerequisites are the same. Take a look at this post on how you can automate the installation of all the prereqs.

The installation process

The installation process is similar to the one you see for 2012 R2 and even the first screen you see after launching the setup says System Center 2012 R2.

Choose your features to install on the server and  move on. I will install the Reporting server later on my SQL server.

At this point, I´ve run the script you will find in my prereqs post linked above and I´m good to go.

I choose a new Management Group name, very easy to find out which version it´s running 🙂

Point out your SQL Server 2014 server and move on. It might also be a good idea to set the DB size a bit higher but since this is a really small demo environment I did just set it to 5 GB´s instead.

Put in your accounts. In this case I already had all the accounts created in my AD since I´m running another switched off 2012 R2 Management Group.

Just as expected, the setup shows an error and it´s perfectly normal. It just tells you to install a license key which can be done using the Operations Manager shell or a regular PowerShell session later on.

Now, the first time you see any difference from 2012 R2 is when you check “About Operations Manager”. The version numer of 2012 R2 is 7.1.10226.0, this is the base version number and then there´s always the UR´s with it´s version numbers as well. As you´ll see in the picture below, SCOM 2016 has a version number of 7.2.11097.0.

A first look at the the maintenance scheduler

When you´ve opened the Operations Console and have clicked the Administration pane, you will see something much appreciated and something that me and a lot of you out there have been waiting for a long time. I´m talking about the “Maintenance Schedules” button! As I mentioned in my last post, this will show up in SCOM 2016 but hopefully in an Update Rollup for 2012 R2 as well. After clicking the button, you will see an overview of your scheduled maintenance modes. To set up a new schedule, click “Create Maintenance Schedule” to the right.

Choose which server(s) should be affected by the schedule. Here you can pick single objects or groups of objects.

Pick your objects and move on.

This is where the fun part begins. Set your schedule to a “Once” in a lifetime happening or a recurring event. Set your start time and end time and move on. If you´ve tried the Scheduled Tasks feature of Windows, this might seem familiar.

Give your schedule a name, categorize it and type a comment on why the schedule is needed.

As seen below, you can also set recurring dates as to the day after patch tuesday every month for example.

An overview of the schedules will show up in the console right after you´ve created it and you´ll see who created it, when it was last run and when it will run the next time.

But where is the information stored? I dug into the OperationsManager DB and found a table named “dbo-MaintenanceModeSchedule” which contains all the information you just saw above. To find the information shown in the below picture, execute the query found below.


SELECT TOP 10 [ScheduleName] ,[ScheduleID] ,[Recursive] ,[IsEnabled] ,[Status] ,[IsRecurrence] ,[TimeZoneInfo] ,[StartTime] ,[IsEndTimeSpecified] ,[Duration] ,[ScheduledEndTime] ,[ActiveStartDate] ,[ReasonCode] ,[Comments] ,[LastModified] FROM [OperationsManager].[dbo].[MaintenanceModeSchedule]


What I´ve shown here is just a small bit of the news I mentioned in my last post. I will keep digging into this new release and report about my findings on my blog as well. So haven´t you tried the new Technical Preview yet? Do it, It won´t let you down (i think) 🙂 Now I´m just waiting for the preview MP´s for Server 2016 to show up so I can monitor my new servers as well.

As always, if you have a question or just want to get in contact leave a comment below.

10 thoughts on “A first look at the SCOM 2016 Technical Preview 2 Add Yours?

  • Nice post Daniel. Quick question , how will we migrate existing OM 2012 R2 to 2016 when the product is released next year. I know for the application Microsoft said it will be in place upgrade and not from scratch, however you have mentioned that the requirement for 2016 is SQL 2014 , does that mean we will have to migrate the existing SCOM DBs from SQL 2012 R2 to SQL 2014 before upgrading. Please throw some light on this.

    • Hi Jatin,
      Just as you mentioned, upgrading seems to be the way to go according to Microsoft. However, the SCOM 2016 requires SQL 2014 right now but I think we will see support for both SQL 2012 and SQL 2016 when they release the product. Just look at System Center 2012 R2, you have support for SQL Server 2008 R2 SP1 up to SQL Server 2014 so I think the list of supported SQL Server environments will look different when released next year.

      • Cool!!. Thanks for replying Daniel.We will be in touch next year when the upgrade happen, I am interested to migrate my DB as well to SQL 2014 but not sure how detachment of DB and re-attachment will work properly.

        • Sure thing, thanks for asking 🙂
          Get back to me when that time comes if you need help and we´ll make sure it happens!

  • Nice post! Unfortunately the second Wednesday of the month is not always the day following the patch Tuesday :/
    In any casa, a long requested feature! 🙂

  • Thank you Daniel for the nice post. I was wondering as the scheduled MM is available in the Administration Pane, which makes it unavailable for the operators and Admin access need to be granted to use this.
    Probably it would be nicer if its available in the Monitoring pane.

    Just a thought!


    • We’ll see how it turns out in the future with the release of SCOM during 2016. I haven’t played around with it too much so far but on the other hand, i don’t think regular operators should be given too much possibilities to configure MM for example as this is often a one-time configuration that then lasts for a longer time. Have you tried it out or have you just watched reviews of SCOM 2016?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: