The Microsoft Connectivity Analyzer Tool is a downloadable client program that is used to identify connectivity issues that occur between email clients and a server that is running Microsoft Exchange Server. The tool can also be used to identify connectivity issues between email clients and Office 365. The tool can be used both by email users, to identify common problems, and by IT Administrators, to troubleshoot issues that are affecting their Exchange Server deployments.
The Microsoft Connectivity Analyzer Tool simulates several client logon and mail flow scenarios. When a test fails, many of the errors message provide troubleshooting tips to help the user or IT Administrator to resolve the problem.
This tool is a companion tool to the Remote Connectivity Analyzer website. Whereas the Remote Connectivity Analyzer website enables IT Administrators to pinpoint connectivity issues by simulating connectivity from a location outside the customer environment, the Microsoft Connectivity Analyzer Tool lets both email users and IT administrators run the same tests within the user’s environment.
You must be running one of the following operating systems:
- Windows 8
- Windows 7
- Windows Server 2008
- 64-bit edition of Windows Vista
Download the client tool (Microsoft Connectivity Analyzer (Beta) here.
Connectivity check as follows
Select one of the option below to continue to next screen
Enter the credential you want to check for connectivity issues
They have done it again.. now with a lot of option
Microsoft Connectivity Analyzer (beta), a portable version of the Remote Connectivity Analyzer website, and a short 49 second video that introduces the Microsoft Connectivity Analyzer.
Read more…click here
Microsoft Connectivity Analyzer Pre-Requisites
- The tool supports the following operating systems: 64bit Windows 7, Windows 7, Windows Server 2008+
- Microsoft .NET Framework 4.5 is required.
- Browsers requirements:
The installation will work on all modern browsers. However…
Good work folks!!!
The improvements to the Remote Connectivity Analyzer CAPTCHA experience. It was very annoying to have both password fields get blanked out if you got the challenge incorrect. While we can’t remove this “feature” completely, we hope the enhancements will make a big difference.
The latest version (V1.4) of the Remote Connectivity Analyzer has the following improvements:
We are using a new CAPTCHA service provided by an internal team!!! EHLO rocks again!!!
- The challenge is NOT case sensitive, so it doesn’t matter if you type upper or lower case letters. We also note this on the web page.
- The CAPTCHA challenges will not include hard to distinguish letters/numbers. For example 2 and Z or O and 0.
- If you get the challenge wrong, the password entries will not be removed.
- Once you enter a correct response to the challenge, you will be verified for a set amount of time. This means you will not see additional CAPTCHA challenges until the timeout period expires.
- The inbound SMTP test now inserts the IP address of the user performing the test into the test email message. The IP is also inserted into an SMTP Header (X-Originating-IP).
- Fixed an issue in the Sender-ID test where certain DNS responses while evaluating the “exists” mechanism were incorrectly being treated as a TempError
- The outbound SMTP Sender-ID tests now conform to the RFC specified limit of ten DNS-based mechanisms that can be used during the evaluation of the SPF record.
To know more, click here
Microsoft Exchange Remote Connectivity analyzer is now the Microsoft Remote Connectivity Analyzer.
The future direction for this tool is to incorporate more products as we have done with Office 365.
Thus dropping “Exchange” from the name made sense.
Tabbed user-interface to support multiple products and Office 365. Office 365 Single sign-on validation. This test allows you to validate identity federated scenarios with Office 365. Specifically, this new test targets the “Basic Authentication” federated scenario where a client sends credentials to Office 365 which in turn validates them against the on-premises ADFS server.
Below is the test result of a SSO from RCA.
Un-installing/De-commissioning Exchange server 2007 Mailbox from Passive cluster node for Exchange 2010
Open the command prompt of the Passive mailbox server..make sure you logged in as domain administrator.
Go to C:\Program Files\Microsoft\Exchange SErver\Bin
Type the command setup /mode:uninstall
Now you have successfully uninstall the Exchange server mailbox role from the passive node, but the cluster environment server information still exists, and we need to remove that as well.
To do that we need to…
- Open the Cluster Management Tool
- Expand the cluster resource name
- Expand the Nodes
- Right click the passive node server
- Click on More actions -> click on “Stop cluster service”
Once you “Stop Cluster Service”, then click on More actions again and click Evict and click the Evict Node….
Once you done this, restart the server.
Once the server is up…do the following too
- Open the Server manager console
- Click on Features and then click on Remove Features
- Uncheck Failover Clustering
- Click on Yes to reconfirm and click on NEXT
- Click on Remove.
- After the Server is restarted
- Remove any remaining files and folders from the Exchange Server program files folder and subfolders.
Thats the end of Exchange Server 2007 Mailbox de-commissioning on a Passive node….Now go to the Active mailbox server of Exchange server 2007
This process is not as same like passive node. Here we can’t go with uninstall command only, because this server holds the culstered mailbox server information and it is online. In order to remove this,
Go to the command prompt..change the directory to C:\Program files\Microsoft\Exchange Server\Bin
Type command setup.com /removeCMS /CMSName:<Clustername>
This will take the mailbox now offline from the cluster…
Now type setup /mode:uninstall
Once you finish this uninstallation, Exchange server 2007 last mail box has been remove from your domain..now do the evict
Goto command prompt (If the command prompt is open, close it and open it and then type
Cluster <mailbox cluster name> node <nodename> /force
That’s the end of the “EXCHANGE SERVER 2007 DE-COMMISSIONING PROCESS”
Now you are completely depended on Exchange server 2010.
Exchange Pre-Deployment Analyzer..Click here
The ExPDA tool performs a scan of your existing Exchange and Active Directory environments and produces a report that lists all items that require attention prior to deployment.
Exchange Server Profile Analyzer..Click here
The EPA tool performs a scan of either a single database or the entire organization to create an aggregated report of mailbox statistical information.
Log Parser…Click here
Log Parser, a powerful tool for querying text-based log files such as those that are generated by IIS and Message Tracking on Exchange servers
Exchange Server Remote Connectivity Analyzer..Click here
This tool will help you analyze whether the configuration has been done properly.
The built-in Performance Monitor tool for Windows lets you collect performance data for every element of the Exchange servers and use it for capacity planning of the new Exchange 2010 servers.
Mailbox Server Requirements Calculator…Click here
The most complicated server role in an Exchange Server 2010 environment to calculate the sizing for is the Mailbox Server role, particularly when it comes to storage.