Related Articles
SCOM 2016 – System.Data.SqlClient. SqlException, Exception Error Code: 0x80131904 Login failed for user
Posted on Author stefanroth
Sometimes there are things you won’t understand. I tried to install a new SCOM 2016 management server in a virgin Azure VM (Windows Server 2016). The necessary SQL Server 2016 was placed on another Azure VM (Windows Server 2016). Well this is nothing special and I have installed SCOM a gazillion times, BUT now I […]
PowerShell 4.0 – Checking SCOM Required Ports
Posted on Author stefanroth
If you are going to install SCOM there are requirements which you have to be aware of. Microsoft has a great article on TechNet which describes precisely what the requirement and supported configuration is for your SCOM setup. Depending on the size of your (distributed) SCOM infrastructure, you might have to install several management servers, […]
Azure Policy – Audit and Deploy CanNotDelete Lock on Resource Group Based on Tags
Posted on Author stefanroth
If you move your workloads to production or even preproduction it is highly recommended to protect them not only against data loss but also from accidential deletion. One feature in Azure which can help are Resource Locks. Depending how you configure the lock, you cannot delete the resource, but still read and modify (CanNotDelete lock) […]