HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- SIM running on Server 2008 - WBEM not working - fi...
Server Management - Systems Insight Manager
1833051
Members
2220
Online
110049
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
10-07-2009 07:35 AM
10-07-2009 07:35 AM
SIM running on Server 2008 - WBEM not working - fix
Excellent documentation for WBEM is here:
http://h18000.www1.hp.com/products/servers/management/wbem/documentation.html
The documentation for integrating WBEM with HP SIM is missing the firewall section for Server 2008 which is another document:
"HP Insight Management WBEM Providers for windows Server 2003 and Windows Server 2008 User Guide”
Basically, you need to check off the box for WMI access
---------------------------------------
You can establish direct remote WMI access on a computer running the Windows Server® 2008
Firewall, but the default configuration does not provide for this access. However, by using the built-in
firewall rules, you can enable remote WMI access with two commands.
Locally execute the following commands on the Windows Server® 2008 machine that is providing WMI
access (on a computer running the Insight Providers on Windows Server® 2008):
netsh advfirewall firewall set rule group="Windows Management
Instrumentation (WMI)" new enable=yes
Output: Updated 4 rule(s).
Ok.
The commands enable all firewall rules contained in the specified firewall group. If the command output
does not confirm that the rules were updated, check that the group name and each word in the command
are correct. The following is an example of a group name with spacing highlighted in bold:
"Windows
This first command is equivalent to selecting the Windows Management Instrumentation (WMI) checkbox
in the Control Panel > Windows Firewall > Settings > Exceptions tab.
An additional firewall rule is needed to enable a remote user to establish a WMI session. It can be
enabled with the following command:
netsh advfirewall firewall set rule name="Network Discovery (NB-Name-
In)" new enable=yes
This command updates a portion of a rule group (a single rule). It can also be done in the user interface,
using the following procedure:
1. Click Administrative Tools > Windows Firewall with Advanced Security > Inbound Rules.
2. Enable the Network Discovery (NB-Name-In) rules.
3. Select the rule, and then click Action > Enable Rule.
This rule and its equivalent rule appear in the Network Discovery and the File and Printer Sharing
firewall rule groups, respectively.
If the Windows® Firewall has either of these already enabled, the latter command does not affect a
change, and only first command is necessary.
Similar rules can be created that are more restrictive but that enable remote WMI access in specific
circumstances (such as restricting which users, computers, and network addresses can remotely access),
depending on your setup.
There can be additional configuration and connection requirements on the client-side depending on the
client operating system and firewall used.
For more information, see Connecting to WMI Remotely Starting
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