Disk Monitor MP for SCOM

A flexible way of monitoring disk space availability for Windows Server 2008 and 2012 R2 versions.

Simply add the text file to the logical drive root for the monitor instance (Server > Drive)and choose warning and critical alert levels.  The powershell script supports cookdowns and other features to allow further refinements.

Download here


Posted in Downloads | Tagged | Leave a comment

SMTRAK Enterprise Dashboard for SCSM2012

SMTrak is the only enterprise ready reporting tool for Microsoft System Center Service Manager 2012 that provides, out of the box, a full range view of your Service Desk operation. SMTrak provides the persistent visibility every Support manager requires to ensure smooth operation.

SMTrak provides customizable filters for all components allowing users to view information, reports or charts from different perspectives to meet the most demanding requirements.

SMTrak dashboards present various ITIL key metrics and business analytics  support executives and analysts require for monitoring performance of service desk operations

SMTRAK Features:

  • Works on your desktop or mobile device
  • Configure different access for every user
  • Active Directory integrated
  • ITIL processes visualization and measurement


Posted in Downloads | Tagged | Leave a comment

Runbook to Create Computer Account in OU Create VM and Send Alerts to Operations Manager.

To configure or to create the same Runbook in your environment.

Find the below links:

Part 1 – Orchestrator System Center Integrations Part 1 – Setting up the Integration Packs


Part 2 – Orchestrator System Center Integrations Part 2 – Creating a computer account in an OU


Part 3 – Orchestrator System Center Integrations Part 3 – Creating a VM based on a Template in VMM


Part 4 – Orchestrator System Center Integrations Part 4 – Adding Alerts to Operations
Manager for a VM based on a Template in VMM


Posted in SCO | Tagged | Leave a comment

System Center Orchestrator 2016 Step by Step Installation

You can download the installation from following Link. I downloaded my copy from Microsoft volume licencing.


When you download the ISO you need to extract the files on some location and once done you can follow step by step:

Step 1: Once the files are downloaded we need to start the setup by running the Orchestrator setup.exe.


Step 2: Once you run the setup you will get the following screen click on install.


Step 3: Enter the licencing details.


Step 4: Accept the Eula.


Step 5: Click Next.


Step 6: I am installing all components on one server as this is a test environment. In production you can install different components on different servers. Once done click next.


Step 7: Once you click next it will check the pre-requisites and if something is missing you can fix just by checking the tick box as displayed. Once done click next.


Step 8: It will then install the missing components.Once pre-requisites are installed click next.



Step 9: Once done enter the credentials and click next.


Step 11: Enter the database information.


Step 12: A new database will be created. Click next.


Step 13: Verify the user group ad click next.


Step 14: The default ports are 81 and 82. If you want you can specify accordingly but the recommended ports are 81 and 82.Once checked click next.


Step 15: You can change the location as per your preference.


Step 16: If you are using SCCM to patch then you can select the 2nd option else select the first option and click next.


Step 17: Click next.


Step 18: You will get the summary of all the action performed so far. Please verify and click install.


Step 19: The installation will start and will look like the following.


Step 20: The setup is now complete.


Enjoy 🙂

Posted in SCO | Tagged | Leave a comment

System Center Service Manager 2016 step by step installation

Server Names & Roles

SQL-01: SQL Database Services, SQL Analysis Services, SQL Reporting Services.
SM-01:  Management Server
DW-01:  Data Warehouse Management Server
SMP-01: Self Service Portal

SQL 2016 Enterprise with SP2 will be the base standard for all SQL Database, Analysis, and Reporting services.

Service Accounts

In AD, create the following accounts and groups, according to your naming convention:

DOMAIN\Srv-SMSrv             Service Manager Server Service Account
DOMAIN\Srv-SMWf             Service Manager Mail Enabled Workflow Account
DOMAIN\Srv-SMRep           Service Manager Reporting and Analysis Account
DOMAIN\Srv-SQL                 SQL Service Account
DOMAIN\Service Manager Admins   SM Administrators security group

Add the three SM service accounts, and the domain users who will be Service Manager Admins to the “Service Manager Admins” Group.  Also add the “Service Manager Admins” domain group to the Local Administrators group on each server.

Obviously change the naming conventions to meet your organisational requirements.


Service Manager setup requires some prerequisites.  Before starting with Service Manger 2016 installation, make sure that these are installed. The following prerequisites are required to successfully install Service Manager 2016:


Now you start the Service Manager installation.  Click Service Manager management server under the Install section:


Enter your product registration details and product key if applicable:


Select the default installation location unless you wish to change it:


If you installed all the necessary prerequisites, you should see a similar screen to this, if not ensure you carry out the required actions install any missing items:


Next you need to specify SQL Server and Instance name where Service Manager will create the main database. Note i am installing the databases on a stand alone SQL server in this series of articles and Service Manager 2016 also supports SQL AlwaysOn installations:

Note: The Service Manager Sizing Helper Tool is provided as a downloadable utility, the Service Manager Sizing Helper tool can help to establish the number of Server Manager servers you need and assist with sizing your databases.  The tool is a graphical utility that is part of the Service Manager Job Aids documentation set. You can download the Service Manager Sizing Helper Tool from http://go.microsoft.com/fwlink/?LinkId=186291.


Note that if you are using the default collation (SQL_Latin1_General_CP1_CI_AS), you will receive the following warning. It basically warns you that support for multiple languages in Service Manager is not possible when using the default collation:image

Now define the name of the new Service Manager management group. They must be unique and not the same as the DW server or Operations Manager management groups!  Also specify the  administrators group you created earlier:


Enter the credentials of the Service Manager Service Account (In this case its Srv-SMSrv). This will be the Operational System Account and becomes the logon account for the “System Center Data Access Service” and “System Center Management Configuration service”.

This account should already be a member of the Local Admin group on the SM server as you should of added the Service Manager Admins group to the servers earlier in this article.


Now enter the credentials of the Service Manager Workflow Account (In this case Srv-SMWf). This account is used for all the workflows and is made a member of the Service Manager Workflows user role.


By default Microsoft now collects diag and usage data.  This can be turned off later but click next to continue the installation:


Click Install to start the installation:


After 15 minutes or so the installation should complete, click close and the Encryption Backup or Restore wizard should start:


You MUST backup the encryption key as it is used to encrypt sensitive information in Service Manager and is required should you ever need to perform a management server restore.  Save it somewhere safe, NOT on the Service Management Servers! Winking smile


SPN Records

One configuration step often missed is setting the SPNs (Service Principle Names) for Service Manager.  Note, the account completing the install doesn’t has permission to create the SPN as its not a Domain Admin!

If the SPNs aren’t registered you will notice an event log warning is registered. The event ID is 26371 “The System Center Data Access Service failed to register an SPN”.

To check the SPNs registered to your service account you can use the SETSPN command:

SETSPN –l DOMAIN\SMServiceAccount

Where domain is your domain and SMServiceAccount is the Service Manager Server Service Account.


You can see above there are no SPN’s registered therefore in order to register them run the following commands:

setspn –A SMServiceAccount/SMSERVERNAME DOMAIN\SMServiceAccount
setspn –A SMServiceAccount/SMSERVERNAME.fqdn.name DOMAIN\SMServiceAccount

For Example:

setspn –A Srv-SMSrv/IC-OR-SM-01 INDICIUM\Srv-SMSrv
setspn –A Srv-SMSrv/IC-OR-SM-01.indicium.cloud INDICIUM\Srv-SMSrv

Now when you run:

SETSPN –l DOMAIN\SMServiceAccount


You can see the SPN has been registered.

Posted in SCSM | Tagged | Leave a comment

System Center Operations Manager (SCOM) 2016

I will be installing System Center Operations Manager 2016 (SCOM) RTM, Build Number 7.2.11719.0.

Here is some of the background information. As this post will concentrate on the installation of SCOM 2016, I am going to omit the setup and configuration of the Domain Controller, Windows Server 2016 for both SCOM Management Server and SQL Server (Please note, I am using SQL Server 2016, both servers on Windows 2016).

If you need help setting up SQL 2016 for SCOM 2016, please visit HERE.

Environment:  Virtual; ESX 6.0 Hypervisor

SCOM Management Server:

  • Windows Server 2016
  • 4 vCPU (2.00GHz)
  • 12 GB memory
  • 100GB Diskspace
  • 1GB vNIC

SQL Server:

  • Windows Server 2016
  • SQL Server 2016
  • 4 vCPU (2.00GHz)
  • 24 GB memory
  • 300GB Diskspace
  • 1GB vNIC

Service Accounts and Local Administrator:

Domain\Account Description Local Admin on…
domain\SCOM_AA SCOM Action Account SCOM & SQL
domain\SCOM_DA SCOM Data Access/SDK Account SCOM & SQL
domain\SCOM_Admins SCOM Administrators Group SCOM
domain\SQL_SA SQL Service Account SQL
domain\SQL_SSRS SQL Service Reporting Services Account SCOM

Now, if you’re lazy like me, or are tired of doing this setup for environments, I have scripted the automation of these accounts. You can find that link here, Microsoft TechNet Gallery.

Let’s Begin:



For completeness, let’s install all the features of SCOM 2016. (I am hosting a default SQL 2016 instance on the SCOM Management Server for SSRS)



Well, that’s not new… Errors. Since this is a clean, vanilla Windows 2016 server, we will need to install all the necessary Web Console components, along with Report Viewer Controls (probably SQL CLR Types too..)

Note, oddly I was unable to install with CLR SQL 2016, Reports Viewer still complained and required CLR SQL 2014.

  • Here is the PowerShell command I ran to install the necessary IIS features/roles:
Import-Module ServerManager
Add-WindowsFeature Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext45, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Mgmt-Compat, Web-Metabase, NET-Framework-45-Features, NET-Framework-45-Core, NET-Framework-45-ASPNET, NET-WCF-Services45, NET-WCF-HTTP-Activation45, NET-WCF-TCP-PortSharing45, WAS, WAS-Process-Model, WAS-Config-APIs -restart

Once the server is back online, you will need to register ASP.Net.


You will need to apply the following using Command Prompt (as Administrator)).

  1. cd %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\
  2. aspnet_regiis.exe -r
  4. Reboot your server…

Once the server is back online, let’s try that Prerequisites check again….


Great! Now all of Prerequisites have been met!


Provide a meaningful Management Group Name (there’s no going back after this…)


SQL Server will be where your SCOM SQL instance(s) were installed. For me, I have built two instances on my SQL2016 server (SCOM_OPSMGR & SCOM_DW).









I recommend always keeping this off, and manually updating your SCOM infrastructure.


One quick review. Looks good. Hit Install, and get some fresh air!


A few minutes later….


Sweet! All good. I hope this helps. If you have any questions or issues, please drop me a line.

Please note, it is STRONGLY ADVISED to install the Update Rollup 1 once you have deployed SCOM 2016.



Posted in SCOM | Leave a comment

Configuration Manager CB 1702 step by step installation

Lets begin


Well as I did take my time to write this blog post there is already a new version the 1704 for the Technical Preview Branch of System Center Configuration Manager. The installation process is the same. For more info about the 1704 build checkout the two links below,



New features in the 1704 version are:

  • Improvements to operating system deployment
  • Reload boot images with current Windows PE version
  • Configure Android apps with app configuration policies
  • Add child task sequences to a task sequence
  • Hardware inventory collects Secure Boot information

New features in the 1702 version are:

  • Azure Active Directory Domain Services support – You can install a ConfigMgr site on an Azure Virtual Machine

    Virtual operating environment which runs inside a hypervisor such as Hyper-V and simulates with software the functionality of a physical computer.

    Virtual Machines require substantial compute resource overhead since hardware services and functions are simulated inside software running on top of a virtual machine

    that is connected to Azure Active Directory Domain Services, and use the site to manage other Azure virtual machines connected to the same domain.

  • Improvements for in-console search – Based on User Voice feedback, we have added several improvements to in-console search, including searching by Object Path, preservation of search text and preservation of your decision to search sub-nodes.
  • Windows Update for Business integration – You can now implement Windows Update for Business assessment results as part of Conditional Access compliance policy conditional rules.
  • Customize high-risk deployment warning – You can now customize the Software Center warning when running a high-risk deployment, such as a task sequence to install a new operating system. The default string regarding data may not apply in scenarios like in-place upgrade.
  • Close executable files at the deadline when they would block application installation – If executable files are listed on the Install Behavior tab for a deployment type and the application is deployed to a collection as required, then a more intrusive notification experience is provided to inform the user, and the specified executable files will be closed automatically at the deadline.

This release also includes the following improvements for customers using System Center Configuration Manager connected with Microsoft Intune to manage mobile devices:

  • Non-Compliant Apps Compliance Settings – Add iOS and Android applications to a non-compliant apps rule in a compliance policy to trigger conditional access if the devices have those applications installed.
  • PFX Certificate Creation and Distribution and S/MIME Support – Admins can create and deploy PFX certificates to users.  These certificates can then be used for S/MIME encryption and decryption by devices that the user has enrolled.
  • Android for Work Support – You can now manage Android for Work devices. This enables you to enroll devices, approve and deploy apps, and configure policies for Android for Work devices.

Update 1702 for Technical Preview Branch is available in the Configuration Manager console. For new installations please use the 1610 baseline version of Configuration Manager Technical and upgrade from this.


To get the Updates go to the Cloud

A self-service, pay-as-you-go model of providing computing resources to an organization or to the general public.

Cloud Computing evolved from existing technologies such as a fast and reliable Internet, virtual operating environments including virtual machines and virtual storage and is provided cloud

services  and check for updates. this could take a whale.



But when the Update is arrived you can update the SCCM version. I choose for the test first and do later the Update. Just to make sure I don’t wreck the SCCM server directly. and as always in SCCM there are plenty of log files.



As showing the Progress in the GUI you can check every step. So installing this is just easy and I did first the prereqs check and then when installing there is no point off doing the check again therefor there is a little checkbox.



As you can see I can select the options but If you can’t no problem you can do this later. just go to the Hierarchy Setting Properties, under General, check the box “Consent to use Pre-Release features“. Furthermore once you decide to use these features and enable it, you cannot undo the changes. So if you have decided to use these features, check the box, click Apply and OK. And every preview is only valid for 90 days so once updated you need to go with the updates every time.



I don’t have a preview collection everything is already test so start the installation.


The installation is taking some time so don’t worry it things are going that fast.


When opening the console again the console does his upgrade to the new version.

image  imageimage

After this the new Version is installed and ready for testing. But for this testing you may need to install some other updates than SCCM what about the ADK version for the new Windows 10 deployments ?


While upgrading do the Update from the ADK also Download Windows ADK for Windows 10 Version 1703

Posted in SCCM | Tagged | Leave a comment