System Centre Virtual Machine Manager 2012 R2 The object was not found on the server

October 30, 2013 1 comment

Issue:

When setting or amending a configuration setting in SCVMM 2012 R2 against a Hyper-V Clustered VM I got a error which looked something like

 

Error (2915)

The Windows Remote Management (WS-Management) service cannot process the request. The object was not found on the server (SERVER NAME)

Unknown Error (0x80338000)

image

This put the VM in the console into a failed state, the natural first action is to try and repair the VM, this generates another error which looks like:

Error (12711)

VMM cannot complete the WMI operation on the server (HOST Server Name) because of an error (MSCluster…….) The cluster resource could not be found.

the cluster resource could not be found (0x138F)

 

image

 

1.Logon to one of the host servers and from a Powershell session run:

2.Import-Module FailoverClusters

Get-ClusterResource -c CLUSTERNAME | where {$_.resourcetype.name -eq ‘virtual machine configuration’} | Update-ClusterVirtualMachineConfiguration

3.From VMM console refresh cluster

4.From VMM console repair VM

How to Extend a Windows 2012 R2 CSV volume

October 29, 2013 Leave a comment

Just had to extend a CSV volume in our Windows Server 2012 R2 cluster due to low available disk space that was alerted by SCOM.

The good news it was the same process as Windows Server 2008

1) Increase size of LUN on you storage.
2) RDP to current CSV owner
3) run diskpart from Command Prompt
3.1) rescan
3.2) list volume
3.3) select volume 4
3.4) extend
3.5) list volume

Error Uninstalling VMM 2012 SP1

October 18, 2013 2 comments

With the release of System Centre 2012 R2 it was time to upgrade our production deployment of VMM.

This is installed on a single Windows 2012 Standard Edition server.

The plan was to uninstall VMM and the console and upgrade the OS to Windows 2012 R2.

I immediately hit a issue where VMM would not uninstall using add and remove programs.

I was presented with a pop up error message saying:

“you cannot upgrade from the currently installed version of VMM to system center 2012 SP1 virtual machine manager. You must first uninstall VMM,  and then install SCVMM 2012 SP1. If you are running system center suite, when you uninstall VMM, you can retain the database. When you install System center 2012 SP1, use the retained database”

Solution:

Using the Following TechNet Article as a reference use the command line to uninstall the VMM Server and Console:

http://technet.microsoft.com/en-us/library/hh852761.aspx

The VMServerUninstall.ini file was modified as below:

NOTE: The below Deleted the VMM Database, make sure you take a backup!

[OPTIONS]
# RemoteDatabaseImpersonation=1
# RetainSqlDatabase=1
# ForceHAVMMUninstall=1

 

The command I ran from and administrative command prompt was:

setup.exe /server /x /f c:\temp\VMServerUninstall.ini /SqlDBAdminDomain "DOMAIN" /SqlDBAdminName "USERNAME" /SqlDBAdminPassword "PASSWORD"

 

setup.exe /client /x

 

SNAGHTML5162d6

The result, VMM 2012 SP1 uninstalled, I am now moving on to upgrading the OS to Windows 2012 R2 and re-installing VMM Server

Categories: SCVMM Tags:

System Centre Virtual Machine Manager 2012 SP1 Error (2912)

 

Failing to create virtual machine from within Virtual machine manager getting Error (2912)

Error (2912)

An Internal error has occurred trying to contact the <SERVER NAME>: NO_PARAM: NO_PARAM

 

SNAGHTML2311d5a

Oh great, no matter what I do I cannot seem to create a virtual machine.

What’s happened? Virtual Machine Manager has been working pretty well for a while now.

I noticed that whenever this fails the virtual machine is being created on the same host server, this host server had some issues last week and I rebuilt the server.

What’s happened, the certificate on the VMM server has not been updated.

To  fix this, remove the host from VMM completely, delete the certificate from the VMM server.

The certificate can be found in the Trusted People store on the local computer

Add back in the host server and that’s it, you should be up and running again.

 

image

Categories: Hyper-V, SCVMM

SCOM 2012–Create Agent Maintenance Account to support SSH Key

December 31, 2012 1 comment

So I guess my last post for 2012, I am working on setting up monitoring of some Linux servers using SCOM 2012 SP1. One of the requirements is to setup a account for Agent Maintenance. I am going to explain how I setup the Ubuntu server to accept a user account and support a SSH as authentication. And hopefully at the end we will have a account that will work with SCOM 2012.

I am using Ubuntu version 12.04 LTE, I have deployed a standard server that is ready for me to logon with my default account I created on install.

Operations Manager contains three predefined profiles to use in monitoring UNIX and Linux computers and performing agent maintenance:

image_thumb43

The Linux Action Account is used for basic health and performance monitoring, the Linux Privileged account is used for monitoring protected resources and actions that require higher privileges and the Linux agent account is used for agent maintenance operations.

I am using Ubuntu version 12.04.1 LTS, I have deployed a standard server that is ready for me to logon with my default account I created on install.

Logon to the Server using your favourite method, I am using Virtual Machine manager 2012 console.

SNAGHTML95778c_thumb1

Create a user:

sudo adduser <username">

Follow the instructions to create a standard user account.

SNAGHTML88b07e

Next we need to configure sudo elevation for the user account we just created.

Use the vusudo program to edit the sudo configuration.

sudo visudo

Find the section root ALL=(ALL:ALL) ALL

Insert under it the same but replace root with the username you just created and add “NO PASSWRD: ALL

eg

<Username> ALL=ALL:ALL) NOPASSWD: ALL

SNAGHTMLca4c73

This is allow the user account to sudo without supplying a password which is a requirement of SCOM monitoring.

Next we need to create some authentication keys.

1.Download yourself a copy of Putty Generator and open it.

2.Select Generate and move the mouse around the blank area at the top until it has generated you a set of keys.

The text displayed at the top is the public key.

3.Copy and past that into notepad (we will need this later) but exclude the last part (rsa-key-20121229)

4.Type in a passphrase in the two available boxes

5.Select “Save Private Key” and save it to a safe place.

 

image

 

You have now generated a set of keys made up of a public and private key, the private key is protected with a Passphrase, the next step is to configure the server with this.

1.Logon to the server with the user account we created above using Putty.

2. Create a folder and file

mkdir /home/scom-agentacct/.ssh

nano /home/scom-agentacct/.ssh/authorized_keys

3. Paste in the public key you created using Putty Generator and save the file.

Next we need to set the permissions on the new folder and the file.

1. Specify exclusive owner access to the directory

cd /home/<username>

chmod 700 .ssh

2. navigate to .ssh directory

3 Give the user read and write permissions to the authorized keys file:

chmod 600 authorized_keys

 

Ones this has been completed, go back to the SCOM Console and update the Run AS accounts and the Profile and test… Smile

Categories: SCOM, System Center, Ubuntu Tags: ,

SCOM 2012–Create Linux Privileged User Account.

December 31, 2012 Leave a comment

So I guess one of my last posts for 2012, I am working on setting up monitoring of some Linux servers using SCOM 2012 SP1. One of the requirements is to setup a account monitoring that will be allowed to elevate it’s permissions. I am going to explain how I setup the Ubuntu server for this monitoring account

Operations Manager contains three predefined profiles to use in monitoring UNIX and Linux computers and performing agent maintenance:

image_thumb43

The Linux Action Account is used for basic health and performance monitoring, the Linux Privileged account is used for monitoring protected resources and actions that require higher privileges and the Linux agent account is used for agent maintenance operations.

 

I am using Ubuntu version 12.04.1 LTS, I have deployed a standard server that is ready for me to logon with my default account I created on install.

Logon to the Server using your favourite method, I am using Virtual Machine manager 2012 console.

SNAGHTML95778c_thumb1

Create a user:

sudo adduser <username">

Follow the instructions to create a standard user account.

SNAGHTML88b07e

 

Next we need to configure sudo elevation for the user account we just created.

Use the vusudo program to edit the sudo configuration.

sudo visudo

Find the section root ALL=(ALL:ALL) ALL

Insert under it the same but replace root with the username you just created and add “NO PASSWRD: ALL

eg

<Username> ALL=ALL:ALL) NOPASSWD: ALL

 

SNAGHTMLca4c73

This is allow the user account to sudo without supplying a password which is a requirement of SCOM monitoring.

 

Once that is complete, pop back into the SCOM Console, create a Run As account for this monitoring account as per the previous article, and update the profile, ensure on the Run As wizard you select “Elevate this account using sudo for privileged access” and you correctly set the distribution.

 

SNAGHTMLcdba61

 

image

 

Useful Articles:

http://technet.microsoft.com/en-us/library/hh230690.aspx

http://technet.microsoft.com/en-us/library/hh212926.aspx

http://blogs.technet.com/b/kevinholman/archive/2012/03/18/deploying-unix-linux-agents-using-opsmgr-2012.aspx

In the next article, I will be creating an account to be used for agent maintenance and enabling public, private key logon.

Categories: SCOM, System Center, Ubuntu Tags: ,

SCOM 2012–Create Linux Unprivileged User Account.

December 31, 2012 Leave a comment

So I guess one of my last posts for 2012, I am working on setting up monitoring of some Linux servers using SCOM 2012 SP1. One of the requirements is to setup a account monitoring. I am going to explain how I setup the Ubuntu server for this monitoring account

Operations Manager contains three predefined profiles to use in monitoring UNIX and Linux computers and performing agent maintenance:

image

The Linux Action Account is used for basic health and performance monitoring, the Linux Privileged account is used for monitoring protected resources and actions that require higher privileges and the Linux agent account is used for agent maintenance operations.

 

I am using Ubuntu version 12.04.1 LTS, I have deployed a standard server that is ready for me to logon with my default account I created on install.

Logon to the Server using your favourite method, I am using Virtual Machine manager 2012 console.

SNAGHTML95778c

Create a user:

sudo adduser <username">

Follow the instructions to create a standard user account.

SNAGHTML88b07e

 

Once the user account has been created on the Ubuntu server you can the goto the SCOM Console and start the “Create Run As Account” wizard found under the Administration tab under Run As Configuration\Unix/Linux Accounts.

Follow the wizard ensuring you select Do not use elevation with this account, you have distributed these RunAs accounts to all the management servers that will be monitoring your servers and then save it.

 

SNAGHTML8c627a

 

SNAGHTML8ce48a

Once the Run As profile has been setup you then need to update the Unix/Linux Action Account profile, found on the Administration tab under Run As Configuration\Profiles with the newly created account.

 

image

 

image

And that’s it for this bit, once you have an agent deployed this is all you will need for basic monitoring.

The next blog post will cover setting up the privileged monitoring account and a third blog post will cover the setting up of the agent maintenance account so we can actually discover these machines Smile

 

Links of use during my journey of discovery:

http://blogs.technet.com/b/kevinholman/archive/2012/03/18/deploying-unix-linux-agents-using-opsmgr-2012.aspx

http://technet.microsoft.com/en-us/library/hh476947.aspx

Categories: SCOM, System Center, Ubuntu Tags: ,