HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Identification/Discovery not using all configured ...
Server Management - Systems Insight Manager
1836752
Members
2683
Online
110109
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
Go to solution
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
09-13-2006 08:29 AM
09-13-2006 08:29 AM
Hi all,
I just noticed something strange happening on our SIM 5 SP4 system. I was looking at some of the DCOM 10009 errors being recorded in the server's System Log whenever a identification or discovery was run; I know that these errors will crop up with non-Windows devices. However, I was also seeing them for some Windows servers.
In the Global Protocol Settings for SIM, I have configured three user names and passwords under "Default WBEM Settings." The first is a local admin user, let's call it "Fred." The second is a domain admin user, let's call it "DOMAIN\George."
I discovered that our sysadmin set the password for "Fred" incorrectly for the servers for which the DCOM errors were being logged. However, shouldn't SIM have gone on and tried to use "DOMAIN\George" instead of logging the error? If I run an identification, it succeeds, but the DCOM 10009 error is logged.
Is this expected behavior? Is the second set of credentials ever getting used?
Thanks,
- Steve
I just noticed something strange happening on our SIM 5 SP4 system. I was looking at some of the DCOM 10009 errors being recorded in the server's System Log whenever a identification or discovery was run; I know that these errors will crop up with non-Windows devices. However, I was also seeing them for some Windows servers.
In the Global Protocol Settings for SIM, I have configured three user names and passwords under "Default WBEM Settings." The first is a local admin user, let's call it "Fred." The second is a domain admin user, let's call it "DOMAIN\George."
I discovered that our sysadmin set the password for "Fred" incorrectly for the servers for which the DCOM errors were being logged. However, shouldn't SIM have gone on and tried to use "DOMAIN\George" instead of logging the error? If I run an identification, it succeeds, but the DCOM 10009 error is logged.
Is this expected behavior? Is the second set of credentials ever getting used?
Thanks,
- Steve
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 02:16 AM
09-22-2006 02:16 AM
Solution
Hi steve,
my opinion is that probably the first attempt fails and so it is logged. But the second attempt is not logged because it does not take an error....does this make sense? :)
If you want to test if wbem works, take a look of attached file.
In class info you have to specify the CIM class (mine is vpar).
When you press Enumerate instances you have to see some information on the bottom of page (you don't have to take CIM_ERR message you see in my file)
regards
Luca
my opinion is that probably the first attempt fails and so it is logged. But the second attempt is not logged because it does not take an error....does this make sense? :)
If you want to test if wbem works, take a look of attached file.
In class info you have to specify the CIM class (mine is vpar).
When you press Enumerate instances you have to see some information on the bottom of page (you don't have to take CIM_ERR message you see in my file)
regards
Luca
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 03:12 AM
09-22-2006 03:12 AM
Re: Identification/Discovery not using all configured WBEM user names
Thanks, Luca! That's a useful tool to know about.
- Steve
- Steve
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