In this blog post I am going to show you a bug I found and how to create the override to silence the alerts. The bug has been reported to Microsoft.
In version 3.1.6011.0 of the System Center 2012 Virtual Machine Manager Monitoring MP there is a bug when monitoring a VMware environment. If you have added a Vcenter server to your VMM environment you will see alerts like the image below. “VGS not Installed”
In this blog post I am going to cover the install of the HP Proliant Virtual Machine Manager integration Kit, I will follow up with a second post that will cover how to update you WinPE images.
You can find the download here http://h18013.www1.hp.com/products/servers/management/integration-msc.html the current version is 7.2 it was released in March 2013.
Run the hpscvvm2012kit-2013.02.07.exe on the VMM Server, make sure that you have closed the VMM console other wise the install will generate an error during the verify step.
When installing the Cloud Services Process Pack SP1 version, I ran into a few issues that are worth noting. On the Orchestrator Server
- If you don’t have an OrchestratorUsersGroup on the local machine because you selected a domain account during the install. You will need to create one this was covered by a blog post you can find here.
- Add your service account for Orchestrator and the account running setup if they are different to the OrchestratorUsersGroup.
SQL Version Requirement, I didn’t find any documented requirements searching the web and the admin guide quickly. On the configuration screen below I was getting an error “SQL Server 2008 was not found” My SQL Server was running SQL 2008 R2 SP2. After upgrading to SQL 2008 R2 SP2 CU5 I was able to proceed past the error.
I am now stuck at the step of importing the runbooks
One thing to check is that your powershell scripts are unblocked you can find details on that here, but that didn’t allow me to proceed any further in the setup.
Update: I was able to finish the install
The last change I made that allowed the setup wizard to finish was to open the runbook designer on the server, create a new runbook check it out, then delete it.
Few other items to note that I had recently done in troubleshooting was added the logged on user to the OrchestartorSystemGroup on the local machine and added the service account to the OrchestratorUserGroup on the local machine.
Here is the Technet forum post that provided the solution to the strange problem.
In this blog post I am going to provide a step by step how to add a HP EVA as an array in VMM 2012.
Start by opening Fabric then add resources -> Storage Devices
Select Add a storage device that is managed by an SMI-S provider
Following last week’s release of SP1 to the MVLS they release Update Rollup 1 for DPM, SCOM, SPF and VMM yesterday. See the link below for a full list of the bugs fixed in this update.
In case you have not seen on other blogs the long awaited System Center SP1 bits are downloadable via MVLS now
more blog post to come as I update my lab and any thing I new I setup in Production.
Make sure to follow the upgrade Sequence – http://technet.microsoft.com/en-us/library/jj628203.aspx
Incase anyone runs into the issue there is a bug in VMM SP 1 Beta that doesn’t support Hyper V Virtual Switches to be bound to teamed NICs in Server 2012.
symptoms I experienced were: Logical networks did not populate in VMM correctly, Virtual switches didn’t show up in VMM, when you could get the virtual switches to show up in VMM and removed them to rebuild them they destroy the NIC team in addition to the virtual switches.
The solution to this is to bind the virtual switches to a single NIC then everything works.