HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: IM Auto Deployement
Server Management - Systems Insight Manager
1833543
Members
2829
Online
110061
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-20-2006 06:13 PM
04-20-2006 06:13 PM
IM Auto Deployement
Hi
When we deploy our servers with an OS, the IM is being installed through scripting (actually the cmd that installs all the software from the smartStart CD 7.(1)4). Also smtp settings are pushed and working.
Installation is fine but the server is showing up as unmanaged.
If we install the software via IM itself, it works but we like to have it there when servers get a new RIS image.....
Are there some things we should mind?
Any help would be greatly appreciated.
Jan Gezels
When we deploy our servers with an OS, the IM is being installed through scripting (actually the cmd that installs all the software from the smartStart CD 7.(1)4). Also smtp settings are pushed and working.
Installation is fine but the server is showing up as unmanaged.
If we install the software via IM itself, it works but we like to have it there when servers get a new RIS image.....
Are there some things we should mind?
Any help would be greatly appreciated.
Jan Gezels
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2006 09:44 PM
04-23-2006 09:44 PM
Re: IM Auto Deployement
You might download the correct Support Pack, and extract all files into one directory.
Then start SETUP.EXE.
Preconfigure all options you can preconfigure, most notably "Systems Management Homepage", Version Control Agent" and "Insight Agents".
Do not install the Support Pack, but quit the application.
You might notice that three "cpXXXXX.exe"-files have been changed.
Make sure the extracted Support Pack files are available when installing the server, and start installation of the Support Pack using "SETUPEX.EXE" (no, it's not a typo). This is the silent install mode of the Support pack.
Using this method, you can already include the name of the VCRM-server, as well as the HPSIM server Certificate.
In order to identify "Managed Systems", verify:
-SNMP settings
-name resolution for the HPSIM/VCRM-machine
-login info for VCRM
-whether any ports are blocked (specificly 161, 162, 280, 2301 and 2381).
-network routing (subnets, default gateway).
-HP Management Agents are enabled (see Control Panel)
Then start SETUP.EXE.
Preconfigure all options you can preconfigure, most notably "Systems Management Homepage", Version Control Agent" and "Insight Agents".
Do not install the Support Pack, but quit the application.
You might notice that three "cpXXXXX.exe"-files have been changed.
Make sure the extracted Support Pack files are available when installing the server, and start installation of the Support Pack using "SETUPEX.EXE" (no, it's not a typo). This is the silent install mode of the Support pack.
Using this method, you can already include the name of the VCRM-server, as well as the HPSIM server Certificate.
In order to identify "Managed Systems", verify:
-SNMP settings
-name resolution for the HPSIM/VCRM-machine
-login info for VCRM
-whether any ports are blocked (specificly 161, 162, 280, 2301 and 2381).
-network routing (subnets, default gateway).
-HP Management Agents are enabled (see Control Panel)
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