HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: WBEM - Windows Server
Server Management - Systems Insight Manager
1834593
Members
3264
Online
110069
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
11-24-2010 04:57 AM
11-24-2010 04:57 AM
WBEM - Windows Server
Hi,
I need set WBEM comunication between HP SIM 6.2 and non-HP Windows Server node. My problem is with security. I need set rights fon non-admin account on target system. Where can I set rights on the target Windows Server system?
Thank you
Martin
I need set WBEM comunication between HP SIM 6.2 and non-HP Windows Server node. My problem is with security. I need set rights fon non-admin account on target system. Where can I set rights on the target Windows Server system?
Thank you
Martin
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2010 10:47 PM
12-01-2010 10:47 PM
Re: WBEM - Windows Server
The following steps should be followed to make a non-root/Administrator user get WBEM data from a Windows box,(These steps would usually work :-))
1. Create a new user account under the "Standard Users" group or "Users" group. Make sure this user account is "password protected"
2. Give DCOM permissions to this new user, the steps for this are as follows
a) Start->Run->dcomcnfg , an MMC opens called "Component Services" under "Console Root" expand "Component Services" to show "Computers" expand "Computers" to get "My Computer", right click "My Computer"-> Properties, "My Computer Properties" opens up, click on the tab "COM Security" .
b) Under "Access Permissions" click on "Edit Limits" give the newly created user Local and Remote access
c) Under "Launch and Activation Permissions" click on "Edit Limits" give the newly created user "Local Launch", "Remote Launch", "Local Activation" and "Remote Activation" permissions.
3. Give the user access to namespaces , so that he can access namespaces locally/remotely
a) Start->Run->Compmgmt.msc . An MMC opens up called "Computer Management" , expand "Services and Applications" , right click "WMI Control" -> properties, "WMI Control Properties" opens up, click on the tab "Security"
b) Select the namespace that you want the user to be able to access, if its all namespaces then select "root" and click on the "Security" button, here give your user the permissions you want him/her to have, now click on "Advanced" button and give the specifier that you want these permissions for this namespaceto be inherited to all other namespaces . (since "root" is the main parent namespace, doing these steps on "root" gives permissions to all other namespaces below it also)
1. Create a new user account under the "Standard Users" group or "Users" group. Make sure this user account is "password protected"
2. Give DCOM permissions to this new user, the steps for this are as follows
a) Start->Run->dcomcnfg , an MMC opens called "Component Services" under "Console Root" expand "Component Services" to show "Computers" expand "Computers" to get "My Computer", right click "My Computer"-> Properties, "My Computer Properties" opens up, click on the tab "COM Security" .
b) Under "Access Permissions" click on "Edit Limits" give the newly created user Local and Remote access
c) Under "Launch and Activation Permissions" click on "Edit Limits" give the newly created user "Local Launch", "Remote Launch", "Local Activation" and "Remote Activation" permissions.
3. Give the user access to namespaces , so that he can access namespaces locally/remotely
a) Start->Run->Compmgmt.msc . An MMC opens up called "Computer Management" , expand "Services and Applications" , right click "WMI Control" -> properties, "WMI Control Properties" opens up, click on the tab "Security"
b) Select the namespace that you want the user to be able to access, if its all namespaces then select "root" and click on the "Security" button, here give your user the permissions you want him/her to have, now click on "Advanced" button and give the specifier that you want these permissions for this namespaceto be inherited to all other namespaces . (since "root" is the main parent namespace, doing these steps on "root" gives permissions to all other namespaces below it also)
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