HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Version Control Configuration v7.80
Server Management - Systems Insight Manager
1830939
Members
2655
Online
110017
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
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
07-25-2007 08:54 AM
07-25-2007 08:54 AM
I am installing/upgrading several hundred servers with the v7.80 VCA and am running into an issue with the configuration of the VCA. We have preconfigured (with the HP configuration utility) the VCA package to include the main console name and the ID to communicate with the main console. But the problem I have is that I have to go into each system to set the support pack version to compare the local system to. My question is: Is there any way to preconfigure this in the VCA install package?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2007 02:04 PM
07-25-2007 02:04 PM
Re: Version Control Configuration v7.80
Not as part of the package, but you can run a job to update the reference pack later.
Look under Configure->Replicate Agent Settings.
You'll need to have configured at least one server, then you can select the target group of servers (say all W2K3 servers) and deploy the change to them.
Look under Configure->Replicate Agent Settings.
You'll need to have configured at least one server, then you can select the target group of servers (say all W2K3 servers) and deploy the change to them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2007 06:48 AM
07-26-2007 06:48 AM
Re: Version Control Configuration v7.80
Thanks for the response.
Is there any way to automate this setting for imaging purposes so I do not have to go back and manually replicate agents settings?
Is there any way to automate this setting for imaging purposes so I do not have to go back and manually replicate agents settings?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2007 08:30 AM
07-26-2007 08:30 AM
Solution
If there is I don't know how to do it.
I don't know where the Configure stores its changes. The reference Pak file is shown when you use the replicate settings option.
So there must be a file somewhere that then points to that file. Presumably you could copy that file as part of the build.
I've had a quick look in the vcagent directory (I used the services to see where the image was) but couldn't see anything obvious.
You could try updating the reference pak and see what changes.
We're established now so it's a matter of updating the reference pak when an update is released and the replicate settings does that in a couple of passes. Just a job of each of the OSes we have.
I guess it's difficult as you cannot tell it what reference pak to use until the the VCA has contacted the VCRM to see what Paks are available.
The info could possibly be stored in the VCRM, but I doubt it.
I don't know where the Configure stores its changes. The reference Pak file is shown when you use the replicate settings option.
So there must be a file somewhere that then points to that file. Presumably you could copy that file as part of the build.
I've had a quick look in the vcagent directory (I used the services to see where the image was) but couldn't see anything obvious.
You could try updating the reference pak and see what changes.
We're established now so it's a matter of updating the reference pak when an update is released and the replicate settings does that in a couple of passes. Just a job of each of the OSes we have.
I guess it's difficult as you cannot tell it what reference pak to use until the the VCA has contacted the VCRM to see what Paks are available.
The info could possibly be stored in the VCRM, but I doubt it.
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