Exchange Management Console Troubleshooter

The EMTshooter runs on the local (target) Exchange server and attempts to identify potential problems with management tools connection to it.The troubleshooter runs in 2 stages. First, it will look at the IIS Default Web Site, the PowerShell vdir, and other critical areas, to ide
4.6 Star
117,675 times
Add to favorites
E-mail Twitter Digg Facebook
  • Problem with console and shell
    1 Posts | Last post October 03, 2018
    • Hi,
      I am running a SBS2011 computer. I have problems to open the Exchange Management console and Exchange Powershell. Running the EMTShooter.ps1 gives me the following result: Failed to connect to any Exchange serverin the current site.
      Problem found:
      Looking for error.
      but it does not resolve anything.
      Can anyone help me?
  • 报错了
    2 Posts | Last post September 26, 2017
    • 1.刚开始报get-user <username>这里的“<”运算符是为将来使用而保留的。我把username改成域用户名然后报下面的错:
      $transcript = $path+"\transcript.txt"后面缺少结束符,我加了一个”这个报错也没有了,然后又报错什么findone()方法返回错误之类的,调试不下去了,你们都没出问题?
    • 不知道你解決這個錯誤了嗎? line 136 最後面少了一個quote("), 補上去就可以了.
      I downloaded the scripts and found the EMTshooter.ps1 lack of a quote(") at the end of line 136.
      After adding it, the script runs well.
  • Exchange Mnagment Tools
    1 Posts | Last post September 02, 2015
    • Hi,
      I have Exchange server 2010. I give rights to my college remotely Create, Edit & Delete Recipients. I add his user ID in "Recipient Management" security group in AD.
      I install Exchange Management Tools on his Win7 64 Bit Machine. when i open exchange management tools following error accord.
      [] Connecting to remote server failed with the following error message : Access is denied. For more info
      rmation, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true'. 
  • Version for Exchange Server 2013?
    2 Posts | Last post November 21, 2014
  • Why not include a Topology Sites Coverage Check?
    1 Posts | Last post April 29, 2014
    • You should enable a test IF the Subnets the Exchange Server are in are LISTED correct under Actice Directory Sites & Services. I know this is a must but in complex setups with Load Balancers and many VLANS and Transport Nets sometimes this gets forgotten. The check would be very easy. And also MS could include that check while the Topology Service snoops around direct in the GUI > You IP Subnet or single subnets are not listed correct in sites and service please add X.X.X.X to the coresponding site.
      Would be so easy sometimes. I must say that Microsoft is including more and more checks in every rollup they release and often it solves problems we had days just with a click for the next release. So a good thing.
  • The tool does not verifes IPV6 is enabled
    1 Posts | Last post August 26, 2013
    • Make sure IPV6 is ENABLED on your Exchange Server, specifically if it is also a DC.
  • Excellent
    1 Posts | Last post August 24, 2013
  • unknown error
    3 Posts | Last post December 06, 2012
    • I’m running a SBS2011 and since the last reboot yesterday I have some problems connecting to my exchange server – but emailing works. After surfing through the web I found your blog with EMTshooter. I ran the script but got an unknown error.
      the transcript.txt entry:
      Start der Windows PowerShell-Aufzeichnung
      Startzeit:    20120919120651
      Benutzername: NTEC\igor 
      Computer:	 NTECSBS (Microsoft Windows NT 6.1.7601 Service Pack 1) 
      AUSFÜHRLICH: Connecting to NTECSBS.ntec.local
      [ntecsbs.ntec.local] Beim Verbinden mit dem Remoteserver ist folgender Fehler aufgetreten: Der Client kann keine Verbindung mit dem in der Anforderung angegebenen Ziel herstellen. Stellen Sie sicher, dass der Dienst auf dem Ziel ausgeführt wird und die Anforderungen akzeptiert. Lesen Sie die Protokolle und die Dokumentation für den WS-Verwaltungsdienst, der auf dem Ziel ausgeführt wird. Hierbei handelt es sich meistens um IIS oder WinRM. Wenn das Ziel der WinRM-Dienst ist, führen Sie den folgenden Befehl auf dem Ziel aus, um den WinRM-Dienst zu analysieren und zu konfigurieren: "winrm quickconfig". Weitere Informationen finden Sie im Hilfethema "about_Remote_Troubleshooting".
          + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
          + FullyQualifiedErrorId : PSSessionOpenFailed
      The Exchange Management Troubleshooter successfully completed connecting to:
      Ende der Windows PowerShell-Aufzeichnung
      Endzeit: 20120919120656
      Do you have any idea what to do?
    • interesting, thanks
    • Hi Martin,
      Could you please post your error output in English?
      Thank you!
  • This tool has some 'issues'
    1 Posts | Last post June 22, 2011
    • Welcome to the Exchange Management Troubleshooter!
      We recommend that you run the troubleshooter after making changes to
      IIS to ensure that connectivity to Exchange Powershell is unaffected.
      Checking IIS Service...
      Checking the Exchange Install Path variable...
      Checking the Powershell Virtual Directory...
      Checking the Powershell vdir SSL setting...
      Checking the Powershell vdir path setting...
      Checking HTTP Port 80...
      Checking HTTP Port 80 Host Name...
      Testing for errors...
      VERBOSE: Connecting to
      [] Connecting to remote server failed with the following error message : Access is denied. For
          + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
          + FullyQualifiedErrorId : PSSessionOpenFailed
      The Exchange Management Troubleshooter successfully completed connecting to:
      Failed to connect to any Exchange Server in the current site.
      Problem found:
      Looking for error...
      After each error is resolved, close this window and re-run the tool to check for additional problems.