- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Entitling VMWare CMS
Insight Remote Support
1753818
Members
8366
Online
108805
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО01-11-2011 02:41 AM
тАО01-11-2011 02:41 AM
hi,
Im have trouble entitling my VMWare CMS (WIN 2008 R2) in Remote Support Configration and Services. I have installed HPSI 6.2 and using RSA 5.5. I have changed the folowing on the VMWare CMS in system properties:
System subtype 1: HP Proliant
Product Model: Proliant
as specified in config & usage guide http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02474031/c02474031.pdf
I have managed to entitle other Proliant servers succesfully but haveing trouble entitling the CMS which is a VMVare guest
any ideas?
Im have trouble entitling my VMWare CMS (WIN 2008 R2) in Remote Support Configration and Services. I have installed HPSI 6.2 and using RSA 5.5. I have changed the folowing on the VMWare CMS in system properties:
System subtype 1: HP Proliant
Product Model: Proliant
as specified in config & usage guide http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02474031/c02474031.pdf
I have managed to entitle other Proliant servers succesfully but haveing trouble entitling the CMS which is a VMVare guest
any ideas?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2011 06:54 PM
тАО01-11-2011 06:54 PM
Solution
The virtual CMS will not entitle because by default it has no serial number or product ID. You could enter the information for the hosting ESX server in the Contract and Warranty area for entitlement under the Tools and Links tab. You would also need to modify an attribute "subtype" to something like HP Prliant so the CMS will pass the business logic rule and let the CMS be passed on to the entitlement tab under options>remote support and configuration This would let the CMS entitle but since there are no diagnostics on the guest you would never see a hardware event.
Last of all make sure you have a system defined in the default group in WEBES. Normally this is the CMS but since it was not intially identified as a system to be monitored there may be no systems defined in the default group in WEBES. There needs to be at least one systems defined in this area.
brad
Last of all make sure you have a system defined in the default group in WEBES. Normally this is the CMS but since it was not intially identified as a system to be monitored there may be no systems defined in the default group in WEBES. There needs to be at least one systems defined in this area.
brad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2011 03:06 AM
тАО01-12-2011 03:06 AM
Re: Entitling VMWare CMS
Thanks Brad. That seems to have worked.
Did a test on pulling out the Power Supply and it seems to have raised a Service Event but noticed it was a Severity critical type 4 event. In the preivous version these were being raiased as Major events, has there been a change or am i missing something?
In the Event details the service Event Source now also says its "WEBES" and not "Remote Support" as before
Did a test on pulling out the Power Supply and it seems to have raised a Service Event but noticed it was a Severity critical type 4 event. In the preivous version these were being raiased as Major events, has there been a change or am i missing something?
In the Event details the service Event Source now also says its "WEBES" and not "Remote Support" as before
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP