HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: VCRM error after upgrade to 4.2
Server Management - Systems Insight Manager
1833329
Members
3625
Online
110051
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
02-22-2005 10:29 PM
02-22-2005 10:29 PM
VCRM error after upgrade to 4.2
Just upgraded from 4.1 to 4.2 sim.
seems to have worked but can't access repos manager from managed servers.
Also the VCRM link has vanished from my Insightmanager console server.
when I try to change agent setting I use the settings I have used before, it tells me could not be accessed.
seems to have worked but can't access repos manager from managed servers.
Also the VCRM link has vanished from my Insightmanager console server.
when I try to change agent setting I use the settings I have used before, it tells me could not be accessed.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2005 12:30 AM
02-23-2005 12:30 AM
Re: VCRM error after upgrade to 4.2
if you made the upgrade to SIM 4.2, you have a new component. the system management homeoage on the SIM server. there is a new security and you have to change something.
see HP System Insight Manager 4.2 iGuide, chapter 13 Migrating Version Control to the System Management Homepage:
Previous versions of the System Management Homepage, known as Management HTTP Server,
provided three levels of account access, including administrator, operator and user. These accounts had passwords that were defined locally at the System Management Homepage and were assigned a privilege level that corresponded to the account name. When the System Management Homepage is installed, the Management HTTP Server credentials are used if any Web Agents are installed on a system. The concept of an administrator or operator level still exists and is accomplished by associating an operating system user group with that privilege level in the System Management Homepage security settings, and finally by adding the user accounts to the groups that provide the level or privilege desired.
The Version Control Agent communicates with a Version Control Repository Manager acting as
an HTTP client, just as an interactive user communicates. Therefore, Version Control Agent settings require the name of a system where the Version Control Repository Manager is installed, and the login account and password required to access the System Management Homepage on that system.
The security changes that resulted from the upgrade of the Management HTTP Server to the System Management Homepage, cause the account and password that are configured at the Version Control Agent to be migrated to System Management Homepage. Migrating the Management HTTP Server credentials allows the Version Control Agent to communicate with the Version Control Repository Manager to calculate software status and allow software downloads.
i did it and it´s working fine.
christia
see HP System Insight Manager 4.2 iGuide, chapter 13 Migrating Version Control to the System Management Homepage:
Previous versions of the System Management Homepage, known as Management HTTP Server,
provided three levels of account access, including administrator, operator and user. These accounts had passwords that were defined locally at the System Management Homepage and were assigned a privilege level that corresponded to the account name. When the System Management Homepage is installed, the Management HTTP Server credentials are used if any Web Agents are installed on a system. The concept of an administrator or operator level still exists and is accomplished by associating an operating system user group with that privilege level in the System Management Homepage security settings, and finally by adding the user accounts to the groups that provide the level or privilege desired.
The Version Control Agent communicates with a Version Control Repository Manager acting as
an HTTP client, just as an interactive user communicates. Therefore, Version Control Agent settings require the name of a system where the Version Control Repository Manager is installed, and the login account and password required to access the System Management Homepage on that system.
The security changes that resulted from the upgrade of the Management HTTP Server to the System Management Homepage, cause the account and password that are configured at the Version Control Agent to be migrated to System Management Homepage. Migrating the Management HTTP Server credentials allows the Version Control Agent to communicate with the Version Control Repository Manager to calculate software status and allow software downloads.
i did it and it´s working fine.
christia
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