HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Initial PSP Install issues
Server Management - Systems Insight Manager
1833777
Members
2120
Online
110063
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
06-11-2004 05:16 PM
06-11-2004 05:16 PM
Initial PSP Install issues
There's been a considerable amount of traffic already on this subject, but I'm running into a couple of things that I haven't seen in other posts.
Like others, I was running into a bad SSH user config but I cannot use an "Administrator" account due to local policies. I've adjusted the execution user in the proliant-msa-tools.xml file for the appropriate tools and 'mxtool -m'd the file to set the new values in the database. The problem I'm having is that the new settings have not persisted across a clean reboot, causing the authentication exception again.
Secondly, due to driver testing and hardware needs, I need to deploy a custom package using the tool and would prefer using the custom baseline creator rather than editing existing XML files. I've tried using setupc.exe for remote deployment outside of the SIM graphical interface, but have not had success with custom baseline XML files. Does anyone know a workaround?
Thanks for any info!
Like others, I was running into a bad SSH user config but I cannot use an "Administrator" account due to local policies. I've adjusted the execution user in the proliant-msa-tools.xml file for the appropriate tools and 'mxtool -m'd the file to set the new values in the database. The problem I'm having is that the new settings have not persisted across a clean reboot, causing the authentication exception again.
Secondly, due to driver testing and hardware needs, I need to deploy a custom package using the tool and would prefer using the custom baseline creator rather than editing existing XML files. I've tried using setupc.exe for remote deployment outside of the SIM graphical interface, but have not had success with custom baseline XML files. Does anyone know a workaround?
Thanks for any info!
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