HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: New SIM server replacing old - Certificate que...
Server Management - Systems Insight Manager
1833304
Members
3157
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
04-24-2008 03:42 AM
04-24-2008 03:42 AM
New SIM server replacing old - Certificate question
Hi,
We've replaced our ageing 5.2 SIM server with new hardware/OS/DBase and only kept the IP and name the same. All servers in now but obviously there's a new certificate. Normally Id copy it out to the C:\hp\hpsmh\certs folder and restart the MHPage but it doesn't do the trick this time.
Can anyone suggest a better method of distributing the new certifiate to the 600+ servers currently reporting in?
Many thanks if so,
Rosco
We've replaced our ageing 5.2 SIM server with new hardware/OS/DBase and only kept the IP and name the same. All servers in now but obviously there's a new certificate. Normally Id copy it out to the C:\hp\hpsmh\certs folder and restart the MHPage but it doesn't do the trick this time.
Can anyone suggest a better method of distributing the new certifiate to the 600+ servers currently reporting in?
Many thanks if so,
Rosco
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2008 05:51 AM
04-24-2008 05:51 AM
Re: New SIM server replacing old - Certificate question
Hi,
Just under menu configure, Configure or Repair Agents.
You must group servers by OS (linux, Windows), enter credential and check Trust relationship Set to "Trust by Certificate".
The new certificate would be copied.
That works fine for me for approx 150 servers.
Regards
Francois
Just under menu configure, Configure or Repair Agents.
You must group servers by OS (linux, Windows), enter credential and check Trust relationship Set to "Trust by Certificate".
The new certificate would be copied.
That works fine for me for approx 150 servers.
Regards
Francois
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2008 05:21 PM
04-25-2008 05:21 PM
Re: New SIM server replacing old - Certificate question
A method I've used is to update the SMH in the VCRM with the new certificate.
From the VCRM configure a new Baseline Pack with just the SMH which now contains the new certificate.
Use the deploy mechanism to redeploy just the SMH. It uses login credentials rather than the trust, which you don't have at this point.
The SMH doesn't need a reboot either when its redeployed.
You just need to select the force update switch if the SMH is the same version as whats already deployed.
From the VCRM configure a new Baseline Pack with just the SMH which now contains the new certificate.
Use the deploy mechanism to redeploy just the SMH. It uses login credentials rather than the trust, which you don't have at this point.
The SMH doesn't need a reboot either when its redeployed.
You just need to select the force update switch if the SMH is the same version as whats already deployed.
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