Ever since Azure was a new thing and before it “went live”, we´ve been fed with how easy it is to get started using different services. One of my first experiences were when I deployed my blog on to the Azure platform somewhere back in 2012, and I was up and running in literally less than fifteen minutes, and this was the first time I did it which is why it took that long a time. It was just as simple as picking a WordPress instance from the gallery and deploying it. A similar experience was when I deployed my first virtual machine. A few clicks and a short time for the deployment and I had my new virtual machine ready to connect to.Continue reading
A few weeks ago, we (Approved) held our annual event called SCOM Day in Gothenburg with about 80 attendees. This year we focused on hybrid monitoring using SCOM 2019/1901 and Azure. It was a full day of sessions where we had Thomas Maurer talking about Azure Stack, Martin Ehrnst who was talking about API integrations in SCOM. And lastly, we had Marcel Zehner who showed us how he monitors and interacts with his Tesla using Azure.
I also held a session along with my colleague Jonas Lenntun about the news in SCOM 2019 and 1901 where we focused on the parts that we think makes most sense and will most likely come to use for most users. The news was announced during Microsoft Ignite that took place in Orlando in September. But to those of you who didn’t attend any of these events, the news is still important to know about.
Yesterday Microsoft Ignite started with a big bang and during the keynote several cool things were shown, some for the first time and some that we´ve seen before. Sadly, I´m not at Ignite this year but I was able to stream the keynote from home instead.
One thing that got a lot of attention was the (OMS) Log Analytics where the VMware solution was shown among others (to be continued…) and the strength of the product was shown to the 22 000 attendees along with all of us that were watching remote.
This post is covering Windows Server 2016 and SCOM 2016 TP4. A new post covering Windows Server 2016 and SCOM 2016 TP5 can be found here.
So its time for some blogging again. With all that we have in front of us with a new generation of System Center but also Windows Server 2016, there´s plenty of fun stuff to write about. In my last post I showed how to get started with the Nano server which is a part of Windows Server 2016. If you havent already, find it below.
The topic for this post is to show you how to monitor your Nano server that you created in the previous blog post using System Center 2016 Operations Manager TP4. For this post I have created a brand new Nano server according to the steps of the previous post meaning I will set up a new IIS server once again. I did run into some trouble while preparing this post so thanks to the Nano server product team for helping me out with some issues.
When Windows Server 2016 is launched later this year, we will be able to choose from three versions to deploy, the full version including the complete user interface, the core edition which we´ve seen before and the new Nano edition which we haven´t seen before.
Nano server? What´s that?
Nano server is the version that´s been on an extreme diet which you will manage remotely and also install remotely. A few advantages that Microsoft has mentioned in marketing Nano server is:
- 93 percent lower VHD size
- 92 percent fewer critical bulletins
- 80 percent fewer reboots
Getting started with Nano server isn´t as easy as we´re used to, just mounting the media and installing it onto our virtual machine so that´s why I´ve written this guide on getting started with Nano Server. You can read more about Nano server here.
Creating the Nano server VHDX file
Copy “NanoServerImageGenerator.psm1” and “Convert-WindowsImage.ps1” from the \NanoServer folder in the Windows Server Technical Preview ISO to a folder on your hard drive. In this case I´m using E:\Media\NanoIIS as the path. The next thing is to define what we want our Nano server image to be like and what the server should be named. If your planning to run your Nano server on a physical machine, you should add this line into the script as well: “-OEMDrivers”. This will include storage and network drivers in the image.
During the keynote at Microsoft Ignite on May 4th in Chicago, Satya Nadella announced the availability of Microsoft Operations Management Suite. To those of you who are familiar to Operational Insights, this will be even more familiar. Azure Operational Insights has now moved into the Operations Management Suite (OMS) where you will find all of what you´ve seen in Operational Insights but this will also be the place where you manage Azure Site Recovery, Azure Backup and Azure Automation (and more to come).
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.
So as i mentioned in my last post, I was one of the lucky 23.000 persons who got to attend Microsoft Ignite in Chicago where IT professionals, exhibitors and Microsoft came together in a large conference to share all the news and to meet new people. Since I´m a SCOM fanatic and have been for a long time, I want to share some of the news that came up during the week on what we can expect from System Center 2016 Operations Manager.
Below is just a summary of what´s to come, I will evaluate the news in upcoming posts to give you a hint on what to expect.
This monday during the keynote of Microsoft Ignite in Chicago, Satya Nadella announced the new “Operations Management Suite” which is the new name for Azure Operational Insights. What´s new with this cloud solution other than the name is the fact that this no longer just contains log analytics and the things we´ve seen before. It is now also the place where you will manage your Azure backup jobs, Azure Site Recovery and Automation. When it comes to onboarding, it´s the exact same process as there was to onboard Azure Operational Insights (and System Center Advisor before that) and there are still two ways to connect the servers to the solution.
It is now only 30 days until I fly out from Copenhagen to New York and then Chicago to attend Microsoft Ignite. Ignite is a new event which merges several different conferences like TechEd , Office 365 Summit and the Sharepoint conference(s) as well. The event takes place between May 4th and May 8th at McCormick Place in Chicago and there´s now 615 available sessions to attend (think you can attend them all?).
Yesterday, the opportunity to build your schedule was released and you can now browse all these sessions and add them to your schedule. Below I have listed the sessions to attend at Ignite that I´ve found so far concerning Operations Manager and Azure Operational Insights. You can check the schedule out at MyIgnite where you need to login with the account you used when you registered for Ignite.