• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 24 subscribers
  • Views 214 views
  • Users 0 members are here
Options
Related
This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Monitor Exchange in differnt domain

jwashburn

I am trying to get Exchange Monitoring setup.  I have no problems reading the drive space, services, etc but that is using SNMP.  With Exhange it needs to use WMI.

No matter what credential I try and setup I keep getting service context does not have the necessary privileges to impersonate.

I have tried domain\username with the domain being the domain the exchange server is in.  I have tried setting up a local accout on the exchange box and using usernam and .\username.  No luck on either.


Any ideas?

  • 0

    Did you try using the wbemtest utility and/or WMI Explorer locally on the exchange server and then remotely from the Solarwinds server?

    If the credentials do not work locally then there is no chance it could work remotely.

    Here is a WMI troubleshooting guide that might help you as well. It shows the steps to use the wbemtest utility.

    http://www.solarwinds.com/support/apm/docs/APMWMITroubleshooting.pdf

    Let us know how it goes.

    Yann

  • 0 in reply to Yann

    Thanks for the links to the tools.  I didnt know that existed.

     

    I am able to connect using wbemtest.exe from both the Exchange server AND the IPMonitor server.  However IPMonitor still gets the error.

  • 0 in reply to jwashburn

    Not sure if this will work for you, but the solution to a similar problem in our network was to create a local account on the ipMonitor server *and* a local account on the remote server, both with the same name and password.  For instance:

    ipMonitor Server Account:  IPMON\ipMonExchange
    Exchange Server Account:  EXCHANGE\ipMonExchange

    Assign the proper permissions to the EXCHANGE\ipMonExchange account and it should work.  Our ipMonitor server is in one domain and most all the servers we monitor services on are in another domain and this seems to work for us.  It's a kludge-y workaround, but it works.

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.