You are browsing the archive for 2015 December.

Avatar of Florent

by Florent

SCOM and OMS: Error 2200: Unable to register the Advisor Service

8:48 am in Azure, OMS, SCOM by Florent

OMS.png-320x240

Today, I tried to connect my SCOM 2012 R2 UR8 to OMS. So I follow the step-by-step on TechNet and I had this error:

Error 2200: Unable to register to Advisor Server. Please contact the system Administrator.

SNAGHTML2744cebc

After few investigation, I found that by default, the new management pack for OMS (Advisor) was not imported. So, I added it. The source of these MP updates are located in C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups. The following MP has been imported:

  • Microsoft.SystemCenter.Advisor.Internal.mpb
  • Microsoft.SystemCenter.Advisor.mpb
  • Microsoft.SystemCenter.Advisor.Resources.ENU.mpb
  • Microsoft.SystemCenter.Visualization.Library.mpb

imageimage

When it’s done, close your SCOM console and reopen it. You will see that the name is now Operations Management Suite and not Advisor:

image

You can now perform the new connection to OMS:

SNAGHTML274901df

Avatar of Florent

by Florent

How to change an Azure VM Subnet

8:22 am in Azure, Microsoft by Florent

microsoft-azure-logo

Yestarday I created a SQL VM on Azure. I completed the installation and so on, but after, I saw that the VM was not in the good subnet in my network.

I searched on Internet how to change the subnet and I found this documentation.

So, I will explain to you how to do this with PowerShell (this is the only possibility to do this). As you can see, I have the IP address 10.0.0.4:

SNAGHTML21dc9f7b

My two subnet in my network are the following:

SNAGHTML21d5b844

As you can see, the VM is actually in the FrontEnd subnet and I would like to move it in the BackEnd subnet. To do this, execute the following PowerShell command:

Get-AzureVM -Name sql-001 -ServiceName Demo | Set-AzureSubnet -SubnetNames BackEnd | Update-AzureVM

SNAGHTML21db5a77

The VM will restart after the execution of the Update-AzureVM cmdlet. When it’s done, go back to your Azure VM interface. You can see that the new IP is in my BackEnd range:

SNAGHTML21df4df1

Don’t forget to change the IP in your DNS too if you don’t allow DNS Dynamic Updates. In my VM, I have the following IP:

SNAGHTML220bb08d