HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: VMM 2.0 will not recognise license
Server Management - Systems Insight Manager
1830801
Members
3189
Online
110016
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
09-28-2005 07:58 AM
09-28-2005 07:58 AM
VMM 2.0 will not recognise license
Hi All,
We have a single licensed VMware ESX host in our VMM.
Downloaded and updated VMM from 1.11 to 2.0.
Updated the VMware Agent, reran Identification.
When I try and drill down to the Virtual Machines it tells me the VM Host has not been licensed.
If I look in the Manage Keys section of HPSIM, the key is there and laoded against that Server.
I removed 2.0, manually removed the agent and reinstalled 1.11. Everything back as they should be.
Re-tried the 2.0 upgrade, this time electing to upgrade the agents as part of the process. No change.
I've also manually restarted the agents (you cannot from HPSIM because it thinks they're unlicensed!) restarted HPSIM and VMM Services. Unregistered and re-registerd the agents.
Any help appreciated, at this point I'll need to revert to 1.11 as 2.0 will just not work for us.
I've also notified the local HP folk about this but not heard back yet.
We have a single licensed VMware ESX host in our VMM.
Downloaded and updated VMM from 1.11 to 2.0.
Updated the VMware Agent, reran Identification.
When I try and drill down to the Virtual Machines it tells me the VM Host has not been licensed.
If I look in the Manage Keys section of HPSIM, the key is there and laoded against that Server.
I removed 2.0, manually removed the agent and reinstalled 1.11. Everything back as they should be.
Re-tried the 2.0 upgrade, this time electing to upgrade the agents as part of the process. No change.
I've also manually restarted the agents (you cannot from HPSIM because it thinks they're unlicensed!) restarted HPSIM and VMM Services. Unregistered and re-registerd the agents.
Any help appreciated, at this point I'll need to revert to 1.11 as 2.0 will just not work for us.
I've also notified the local HP folk about this but not heard back yet.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2005 01:38 PM
09-28-2005 01:38 PM
Re: VMM 2.0 will not recognise license
It was SNMP.
The Host Server had its System Properties set to not use the Global Properties. And the System properties contained the default public and private community names which we do not use.
As soon as I changed it and reran the Identifcation it worked.
Odd that this didn't affect VMM 1.11.
The Host Server had its System Properties set to not use the Global Properties. And the System properties contained the default public and private community names which we do not use.
As soon as I changed it and reran the Identifcation it worked.
Odd that this didn't affect VMM 1.11.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP