
When I run it, I got an error (below) and I wasn’t able to upload the logs to the MS. The online tool wouldn’t run on Win2k8 R2 and so, I had to use a in-built MSDT tool on these servers (instructions will be there on the mail that the MS Support Engineer sends).īasically, the Microsoft Support Engineer would provide you with a pass code, which is pre defined with a set of information to gather on the server having issues.

Recently, I opened a case with Microsoft and they requested me to run the Support Diagnostics tool on my Exchange 2010 running Windows 2008 R2 Enterprise.

Hope this helps someone wandering in the wild for an answer! :)Guys, You might want to run netsh winhttp reset proxy to revert to default settings after running this tool! 😉 There are few other codes in the KB article too, that might interest you! You can use the netsh winhttp import proxy source=ie to import the Proxy settings from IE (if the Proxy settings is not forced by GPO, then you might have to configure your Proxy settings IE before running this command – few admins wouldn’t like to have GPO applied on them). This is due to the fact that you have a proxy servers that provides internet access for your users (and servers wouldn’t have direct internet connection). The one that I feel is more often bound to happen would be 0x80072EF3. Clicking on the small link gives more details on the error.Īfter a bit of digging on the internet, I came accross the Microsoft KB article that answers the FAQs about this tool and has the error codes and the common troubleshooting steps.


When I run it, I got an error (please scroll down a bit below) and I wasn’t able to upload the logs to the MS. The online tool wouldn’t run on Win2k8 R2 and so, I had to use a in-built MSDT tool on these servers (instructions will be there on the mail that the MS Support Engineer sends).īasically, the Microsoft Support Engineer would provide you with a passcode, which is pre-defined with a set of information to gather on the server having issues. Recently, I opened a case with Microsoft and they requested me to run the Support Diagonostics tool on my Exchange 2010 running Windows 2008 R2 Enterprise. Found this after so much of search and so I thought I’ll pen it down for anyone who might be looking for something related to this.
