Ops Manager does not show up under Assets in vSphere Client

Ok so I just went through some very painful hours and I hope nobody else has to ever go through this. Thats the reason fro this post. So I am sort of rearranging parts of my lab which really started the whole mess. I had to redeploy Operations Manager. Sounds pretty simple right? Read on..

Everything went great as far as registering Ops Mgr to my vCenter etc but then something odd really happened. I wasn’t able to apply the license for Ops Mgr. Keep in mind, you can only apply the license for Ops Mgr using the vSphere-Client under Home –>Administration –> Licensing, when there click on the “Asset” radio button and there you would see your unlicensed Ops Mgr waiting for your license key.

Only in my case, I saw both my hosts and the vCenter but no Ops Mgr. I tried everything under the sun from un-registering, re-registering but nothing really worked. I power cycled the vApp, restarted by vCenter service in hopes for it to start seeing things. Interestingly I could see “vCenter Operations Manager” in my home screen under “Solutions and Applications” but clicking it came back with a message saying you are not licensed you idiot. Well not quite but you know what I mean.

I was inches away from re-deploying the vApp when I figured well lets try one more thing. I looked around and noticed people had more luck with launching the vSphere client from the vCenter Server and that seem to have worked for a few folks. I figured well why not. So far I was accessing all this from the vSphere client installed on my laptop. So I logged into my vCenter (Mr. Hades) and launched the vSphere client there to see if that made a difference.

I was pleasantly surprised to see that this time around I did see Ops Mgr under Assets in licensing. Why did this work and the other didn’t? I have no clue but if I have to take a guess I would say it must have something to do with the vSphere client and not really Ops Mgr, but I am not sure. Now I did deploy Ops Mgr a few months ago and don’t recall having this issue before (I do have bad memory so its possible that I just forgot). But this is really for someone else out there who happens to see the same issue as I did, try accessing your vCenter from the vSphere client installed on the vCenter server itself and see if you have any luck.

From here onwards, you should be able to license your Ops Mgr and finally log in. For the record I am running vSphere 5 U1 and I am NOT running the vCSA. Getting the license applied in Ops Mgr is really important because basically you can’t really login to the Ops Mgr portal if its not licensed. If you are having the same issue as described above, hopefully you found this blog before you ruined your entire day like I did.


vSphere Licensing Advisor

Ok, there were scripts that worked and something didn’t work, there was confusion about how many licenses do I need. And finally when the information started to sink in, the licensing got changed (for the better of course). Thankfully now there is an official tool that will help you figure out what you need to make the move to vSphere 5. The tool is pretty simple, it connects to your vCenter and sees whats in there and comes back with your options for the upgrade. It’s pretty straight forward and helps you realize your world with not end with the new licensing model. The download like for vSphere Licensing Advisor is here.


Revision in VDI licensing for vSphere 5

More good news from VMware. Apart from the vRAM entitlements that have been increased, VMware has ensured that existing VDI customer are not left out in the woods. I think the original model didn’t include existing VDI customers. But all that has changed.

We already know that for VDI in vSphere 5, you can either use the vSphere 5 licenses along with the vRAM limits or utilize the vSphere Desktop packages (based on powered on VMs) with unlimited vRAM. Todays announcement adds another good news which is if your vSphere 4.x license was purchased prior to September 30th 2011 for desktop virtualization purposes, you are entitled to unlimited vRAM.

customers with spare vSphere licenses from past purchases can use it to host a VDI environment. Customers who purchased licenses for vSphere 4.x (or previous versions) prior to September 30, 2011 to host desktop virtualization, and hold current SnS agreements, may upgrade to vSphere 5.0 while retaining access to unlimited vRAM entitlement.

So if you run a 3rd party VDI solution, you can upgrade without the vRAM caps as well.  And if the 3rd party VDI solution does not support vSphere 5 yet, you can always downgrade to vSphere 4 until your VDI solution is supported on vSphere 5. This is of course for folks who want to buy more licenses before the sept 30th deadline (3rd qtr sales :)). If you are new to VDI, then you would probably purchase vSphere 5 Desktop with unlimited vRAM.

However there a few a things to keep in mind:

  • vSphere 5 Desktop and upgrades for vSphere 4.x (with unlimited vRAM) can only be used for VDI environments only. You cannot run non-VDI servers on these hosts.

vSphere Desktop can be used only to host a desktop virtualization environment or desktop management and monitoring tools.  You can use vSphere Desktop for desktop management and monitoring tools in a VDI environment only.

  • Your VDI environment should be on a separate vCenter instance than the one running the server load.
 like VMware View Deployments on vSphere 4.x you will need a separate vCenter server for your VDI hosts.

I think for all those who have been upset due to licensing changes for the past few weeks, this change must be a nice gesture from a company that could have just kept quite.

Seriously this is my last post about licensing.

vCartoon of the Week (07/25/2011)



Licensing Party

Credit: M. Ali


Licensing Poll Result; vRAM = Cloud

So this past saturday I posted a poll in hopes for trying to understand besides the reasons I covered for VMware to switch their licensing model, what else could be the driving factor for VMware to make such a drastic change. Before I get into what I discovered, let me summarize the feedback from the polls.

As of today, I received 195 responses and if you are interested in computing the margin of error, be my guest I think its somewhere between 7%-9%. Out of the 195 responses only 24.1% said they will either pay less or the same with the new licensing model. 60.51% of the respondents will either have to pay 2, 3 or even 4 times as much. And 15.38% said the change will ruin their future plans. Somehow based on what I have seen @ VMTN in the pass few days, I am not surprised by these numbers. But I found something else that I thought was very interesting.

84.61% of the respondents owned 100 or less hosts in their environment and 54.87% owned less than 25. Also, 51.28% of the respondents represented companies with 500 or less employees. 21.03% had 500-2500 employees, 20.51% had 2500-25000 employees and only 7.18% were representing large organizations of 25000 employees or more. I think this has been the most interesting part of the poll. It’s clear from the numbers that the SMBs are the ones that are really getting impacted by this in a huge way. Specially small businesses with 100 employees or less. And I can understand why this would be the case as well. Being an IT shop in a small business, one will be required to do more with less and oversubscription of memory would have been a big thing for them. Now with vRAM, they may see a huge cost increase and as result we might even witness a mass exodus.

Here is my conspiracy theory and no its not that Paul Maritz owns a lot of shares in MS, I find that comical. What I think is happening is that VMware is pushing the SMB towards the cloud. And if you calm down and think about it for a second, its actually beneficial for you and for VMware as well. Most people who are angry at VMware are screaming and yelling about how they will switch to Xen or even HyperV. Come on, its not like your girlfriend has cheated on you and now you have to get even. It’s time to think smart!

If you are on the switching platform bandwagon and HyperV, Xen etc are among your options, please keep in mind that VMware came on this road for a reason and its only a matter of time before the others follow. Not to mention, the others have always been the followers when it comes to virtualization and what we are witnessing today is not any different. If you do switch to a different platform, you will only end up being mad at MS, Citrix or whomever else you end up with for the very same reason VMware may have upset you today. Unless you like being tortured, I would highly recommend that you look at different cloud providers as your option as well. This will be your most viable option and I am not saying this because I happen to be a major cloud provider’s employee.

Let’s face it, the cloud is here to stay and we have heard the word being thrown over and over again for sometime now. But nobody really knows what it is. If you ask 10 people to define a cloud, you will get 10 different definitions of a cloud. That’s because every cloud is different and unique in its own way. Instead of wasting your time with evaluating inferior hypervisors because you can’t afford the best in the business anymore, I recommend that you look into the world of clouds seriously. You will end up in the cloud one way or another and its about time that you seriously look into what they have to offer.

Keep in mind, if VMware has upset you today, going to competitors isn’t your best option. If you are leaving because you can’t afford VMware anymore and going to a competitor will teach ’em a lesson, I would really like to see you getting signed up for SNL. Look into the cloud today, the competitors will push you there anyways, its a matter of time. Keep in mind, they are always playing catch-up and this time around isn’t any different.

On a lighter note if you think your girlfriend has cheated on you, what does getting even really do for you? 🙂