Azure Site Recovery–Story revamped using new portal

hybrid cloud and datacenter management

In this blog post I’ll guide how to setup Azure Site Recovery (ASR) on the new portal using ARM model. If you’re not familiar with the ASR concept you can refer here. Compared to setting up ASR on old Azure portal, Microsoft ASR team carried out significant enhancement on the new portal and make it very much UI friendly.

In this blog post I’ll explain how to protect HYPER-V VM’s. You can protect VM’s hosted on single HYPER-V (Stand alone) or HYPER-V cluster (without VMM) using these steps. Few things I won’t cover in this blog post are how to create resource group, Virtual network….etc. I’ll provide relevant links for that for you to get in depth idea.

1. Wow to create a resource group in Azure – https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview

2. How to setup networking for ASR – https://azure.microsoft.com/en-us/blog/networking-infrastructure-setup-for-microsoft-azure-as-a-disaster-recovery-site/

So with the assumption you have HYPER-V server with bunch of…

View original post 553 more words

Advertisements

Azure – How to trigger Azure runbooks with Azure Monitor

Awesome

Manjunath Rao

Today we shall see how to trigger runbooks using webhooks when an alert is fired from Azure Monitor.

To illustrate this, I have taken a specific example of triggering a runbook, when an Azure virtual machine is de-allocated.

Step 1: Simulate a de-allocation event by Stopping a virtual machine.

Step 2: Check the activity logs for the de-allocation event.

1

Step 3: Click on the “+ Add activity log alert”. This will start up a pane to fill out the alert details.

2

Step 4: Before filling out the alert details, I encourage you to go ahead and create an empty Runbook. So that you can create the webhook for the Runbook, which is required while filling out the alert details.

3

Step 5: Once you click on the “Webhook”, you will get the below pane. Click on “Create new webhook” and fill out the details accordingly. Make sure you copy the URL…

View original post 118 more words

Monitoring Domain Controllers in SCOM 2016 – Event ID 1102

SCOM & Other Geeky Stuff

So  you deploy a SCOM2016 agent to a Windows 2016 Domain Controller, only problem is, after the agent push, discovery doesn’t work. Well, the agent isn’t corrupted… Ports are open… SCOM agent is being deployed using the System Local account…  etc. etc. So, now what?

Taking a look at the Windows 2016 domain controller and its event log, the domain controller OpsMgr log is getting bombarded with Event IDs 1102….

After some investigation, seems to be this has been an issue in SCOM 2012 (and 2012R2) as well. Well, here’s the fix…

Taking a look at the HSLockdown, the Local System account is being denied access..  Browse to the following folder “%windir%Program FilesMicrosoft Monitoring AgentAgent “and run the following command (elevated access…), “HSLockdown.exe /L

Now that we can see the Local System account is being denied access, let’s give it access… Running the…

View original post 30 more words

SCOM Servers not “Remotely Manageable”?

SCOM & Other Geeky Stuff

Odds are you probably will have some machines where you can’t deploy the SCOM agent via SCOM console, or PowerShell, or some automated way, and you must install and configure the agent manually. Days/weeks/years go by and now you need to decommission that troublesome, manually installed agents Primary Managed Server. You go to the console and right click, and notice you cannot change the machines primary management server.  Well that is because any manually installed agents SCOM/SQL disables this feature. Well, there is a workaround!

Launch SQL and run the following query against the OperationsManager database to get a list of all manually installed servers:

select bme.DisplayName from MT_HealthService mths
INNER JOIN BaseManagedEntity bme on bme.BaseManagedEntityId = mths.BaseManagedEntityId
where IsManuallyInstalled = 1

Now that you have determined which servers were manually installed, to re-enable the remotely manageable feature, run the following SQL query (against the OpsMgr DB).

UPDATE MT_HealthService
SET IsManuallyInstalled=0

View original post 33 more words

Enabling SCOM 2012R2 Agent Proxy

SCOM & Other Geeky Stuff

The other day, I’m asked, “what the heck are these SCOM agent proxy alerts!?” I’m sure you fellow SCOM admins have seen these alerts before:

1

You could go to the computer that SCOM is complaining about and manually enable the agent proxy via Administration > Managed Computers, and modifying its properties, see below:

2

Or…… you could make your life easier, and do this…

The fix is easy, and the explanation are both below:

To resolve the “Agent proxy not enabled” alert for all machines in your current environment, run the following PowerShell code in the SCOM PowerShell Console:

get-SCOMagent | where {$_.ProxyingEnabled -match "False"} | Enable-SCOMAgentProxy

3

To prevent this alert in the future, run the following below:

add-pssnapin "Microsoft.EnterpriseManagement.OperationsManager.Client";
new-managementGroupConnection -ConnectionString:yourSCOMserverFQDNhere;
set-location "OperationsManagerMonitoring::";
Set-DefaultSetting -Name HealthServiceProxyingEnabled -Value True

4

View original post 24 more words

Step-by-Step – SCOM 2016 Update Rollup 2 (UR2) Install Procedure

SCOM & Other Geeky Stuff

My personal notes for installing SCOM2016Update Rollup 2, Step-by-Step. UR2 (Update Rollup) has a lot improvements, please see below the many updates being provided in this UR. Two fixes I am seeing that makes me happy, is having the alerts view fixed… Previously alerts within the Alerts view would still appear even after the alert was closed. Also, the Get-SCOMGroup cmdlet consistently failed when there was a great number of groups within an environment.

It is highly recommended to upgrade your lab/Dev environments first before upgrading your Production environment(s). The step by step procedures below are the steps I took and in no way shape or form do I accept responsibility for any data loss, and/or issues within your environment. It is advised to always take a backup of your SQL databases and/or snapshots of your SCOM environment(s). Please take these notes as suggestions. Always refer to…

View original post 900 more words

Step-by-Step – SCOM 2012 R2 Update Rollup 11 (UR11) Install Procedure

SCOM & Other Geeky Stuff

My personal notes,  SCOM 2012 R2 Update Rollup 11 (UR11) has a lot of networking monitoring fixes, Linux/UNIX support and security fixes, along with more OMS integration. What is OMS, please go HERE. It is highly recommended to upgrade your lab/Dev environments first before upgrading your Production environment(s). The step by step procedures below are the steps I took and in no way shape or form do I accept responsibility for any data loss, and/or issues within your environment. It is advised to always take a backup of your SQL databases and/or snapshots of your SCOM environment(s). Please take these notes as suggestions. Always refer to Microsoft’s KB (posted above) for full documentation steps.

Here are the key updates for UR11 (source Microsoft):

Issues that are fixed in this update rollup can be found here, https://support.microsoft.com/en-us/kb/3183990

Once you are ready to begin your upgrade, it is recommend you…

View original post 325 more words

Step-by-Step – SCOM 2016 Update Rollup 1 (UR1) Install Procedure

SCOM & Other Geeky Stuff

Well, that was fast… System Center/Microsoft Operations Manager (MOM) team just released Update Rollup 1 for SCOM 2016, only weeks after the System Center 2016 suite and Windows Server 2016 were released.

The MOM team did not indicate what exactly the fixes were in this Update Rollup, so your guess is good as mine. However, I believe one of the issues that may have been resolved was the SCOM 2012R2/SCOM 2016 Console crash due to the October Cumulative Update, October 2016 Windows Server Cumulative Update(s).

Below step by step procedures below are the steps I took and in no way shape or form do I accept responsibility for any data loss, and/or issues within your environment. It is advised to always take a backup of your SQL databases and/or snapshots of your SCOM environment(s). Please take these notes as suggestions. Always refer to Microsoft’s KB (posted below) for full documentation steps.

View original post 472 more words