- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- vcmuser on the Onboard Administrator module
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
08-26-2011 06:00 AM
08-26-2011 06:00 AM
vcmuser on the Onboard Administrator module
Hiro had a question about the "vcmuser" role:
*********************
My customer recently bought and configured 2 c7000 enclosures with VC Flex-10.
He asks me about vcmuser.
He says vcmuser is added on the OA of one enclosure but not on the OA of another enclosure.
What is the role of vcmuser and when is the user added on the OA?
Why vcmuser exists on the OA of one enclosure but not on the OA of another enclosure?
Setup and Installation Guide says "Virtual Connect creates a local user named "vcmuser" on the OA module. Do not modify the credentials for this user. Do not change the "local users" authentication setting for the OA module."
***************
Jeroen replied:
*****************
Its made and used by Virtual Connet Support Utility (VCSU) only to check domain status etc; normally it would delete the user as well after doing the operation against the OA but if that process got terminated before VCSU officially ended then the vcmuser will still be there.
******************
Any other comments or questions?