- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- VMM Licensing
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2006 02:15 AM
тАО02-09-2006 02:15 AM
VMM Licensing
Anyway, since then I have rebuild the CMS and started with a brand new database. I have since deployed VMM licenses to the ESX hosts, and it now appears as licensed. However, other licenses I have added also appear as being used, since they were deployed to an ESX host in the past.
I have had an open case for several months now, with the hope that the newest releases of SIM and VMM would resolve the issue. Initially I was told that a "Collect License" function would free up the license for deployment elsewhere. Then I was told that was incorrect, and that all the license information is stored in the registry on the CMS. That is not true, as I can still see past licenses I have deployed to the same host AFTER rebuilding my CMS and the database. So there must be some licensing information stored on the ESX host.
What I want to find out is how to clear the VMM license information on an ESX host. How can I clear up my past license deployments?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2006 02:32 AM
тАО02-09-2006 02:32 AM
Re: VMM Licensing
In my case that cleaned up the ESX Server based License Informations.
Try it, may be that helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2006 03:36 AM
тАО02-09-2006 03:36 AM
Re: VMM Licensing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2006 07:33 AM
тАО02-09-2006 07:33 AM
Re: VMM Licensing
If you've misused licenses you may need to get some replacement licenses from HP. I'm not sure trying to fudge the registry is a good way to go.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2006 07:39 AM
тАО02-09-2006 07:39 AM
Re: VMM Licensing
I can state this definitively. The reason why is because I completely rebuild my CMS - formatted the drive, and started for the first time with a SQL database on an external SQL server. Yet when I added the ESX host and registered them, I have hosts which are consuming multiple licenses - even when I haven't deployed any since the rebuild!
There must be some place licensing information is stored on the ESX host.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2006 08:32 AM
тАО02-09-2006 08:32 AM
Re: VMM Licensing
There may be other elements in the database, I don't know if your SIM database is on the CMS or not. And there may be a final tie up to entries on the ESX Server.
I was suggesting that it may be an easier process to get your local HP to generate a new VMM key rather than try and flush out all of the corresponding entries.
Also, it may be the new HPSIM discovers the ESX Server and the license entries that it repopulates the registry.
It's guesses, I do not know how the whole mechanism works. It is designed so that the one-off licenses cannot be easily re-used.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2006 08:40 AM
тАО02-09-2006 08:40 AM
Re: VMM Licensing
You may be right about contacting HP - in fact, they had given me a new license once as a temporary workaround for not having an a quick answer. But after three months now, I am getting the distinct impression that the functionality of VMM licensing is a closely-held secret even within HP, as no one seems to know how it *really* works.
But the description of your theory is right on target. I think that is exactly what happened. It seems that it should be a simple matter of somehow deleting the licensing information from the ESX host. Apparently that is not an easy thing to do.