Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SAM Credentials and HTTPS

Hey guys,

I have been adding all my servers in SolarWinds via SNMPv2 and just recently started adding in components / applications that seem to need WMI credentials to work properly. One such template is the Windows Print Services. When testing the template, it asks me to enter in Windows credentials. I was under the impression that SNMP would work the same as WMI in this aspect. If that is not the case, is it better to add the servers via WMI rather than SNMP?

Also, this shows up when it asks for me to enter in the credentials:

What would be better? Should I setup SolarWinds via HTTPS or just add the credentials locally on the server? How do I go about adding them locally on the server if that is the better option? I am currently looking through the SAMAdminGuide, but so far haven't found were it talks about adding them locally, just through the web console.

Thanks,

Jeryn

Find more posts tagged with

Accepted answers

mharvey

Normally these would be local or domain credentials that are admins on that server. I would recommend using a mixture of SNMP and WMI. SNMP for the NPM monitoring and WMI for monitoring services on the servers that you don't get via SNMP. SNMP can only go as far as processes and OIDs, but not the full service, that's what you need WMI for. I'd keep the nodes added as SNMP, then setup the admin account for WMI access. You don't HAVE to have your website in HTTPs, for that, but it's simple enough to add a https binding.

Regards,

Matthew Harvey

Loop1 Systems

All comments

mharvey

Regards,

Matthew Harvey

Loop1 Systems

jeryn

I went ahead and setup SSL (HTTPS), but I keep getting an un-trusted certificate warning.. I can ignore it and continue on, but what do I need to do to fix this? Can I do it server side so any computer that tries to connect wont get that warning? I imported them into the Trusted Root Certification Authorities like it states, but it doesn't seem to have made any effect.

mharvey

What certificate did you use? Did you create a self-signed certificate, or did you have one already setup from a third party for this server?

jeryn

I used the SolarWinds-Orion Cert that was already on the server.. Do I need to create a self signed cert? Sorry, I haven't messed with Certs to much and need to do some reading up on them.

jeryn

Just an update and one more quick question for clarification.

Firstly, adding in the third party cert seemed to have resolved the issue, so, big thanks for the help on that.

Secondly, where you talked about using either SNMP or WMI. If I was to add a server via SNMP and then add in the server admin credentials to allow the template / application to work. Would that be just as effective if instead I was to just go strait WMI? Or would enabling WMI and adding the node that way, get me better results?

rjnicholson

Use SNMP so you can get Interface information from the servers when managing them in NPM. Use WMI on the application template side for SAM monitors.

You don't need to set any creds at that time you are adding the node to NPM unless you are assigning an application monitor/template that needs creds to poll using WMI at that time.

If you are setting creds for polling and not assigning a template I would say you are wasting time since you will do this again once you assign a template to the node for Application monitoring. Just set the Creds up in the Credential Manager under the SAM Settings page, and then you can use them as a drop down to fill in when you assign templates.

aLTeReGo

is correct. Many customers who own NPM and SAM manage their servers via SNMP so they can monitor network interface statistics on their servers. This is something SAM is working to natively support so you can continue to monitor network interfaces on your Windows servers for WMI managed nodes.