Justin

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Justin

  • Rank
    Community Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. What I would like is to just have the list of devices found during a NetScan attached to the email that it sends out. Or the above! something...
  2. As a workaround you could place the device/alert in SDT. You can configure if those send notifications in your escalation policy I believe.
  3. It is not necessary to add in the cluster resources as devices, they are monitored instance under the cluster named device.
  4. I was referring to the fact that the core datasources do not work on server 2008.
  5. I'm not sure what you are using for SSO, but Okta does exactly this for me and my clients.
  6. I wasn't happy with the idea that this would only work on Server 2012, so I updated it to run on the collector instead of the monitored DHCP server. this also removes the need to add psconfig properties. The only catch is that all of your collectors must be running Server 2012 with DHCP management tools installed. The script will check and if necessary install the DHCP tools at first discovery. Let me know your thoughts. Solved a lot of issues for me. DHCP_Scope: 4P2WKM DHCP_Server_Stats: MT7GPT
  7. Ryan, I have a group for cluster nodes, and clusters. I add in the clusters using their DNS name so even if it fails over to another node, it still shows as up. I then apply the property ClusterNode to the nodes and WindowsCluster to the cluster name. I have modified the datasources for monitoring windows cluster resources, groups, and nodes to only apply to devices with the category of WindowsCluster. On my groups, I disable all datasources that may be duplicated between them This works perfectly for all clustering, exchange and sql, but not for Always-On clusters as services need to be running on both sides. To correct this, I manually add the sql monitoring to each of the nodes. This may sound a little confusing, but it was pretty straightforward to setup. Happy to help if this sounds like what you are looking for. It does cost an extra device per cluster though...