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
In previous versions of Exchange, you would need to access the user’s mailbox to be able to do this. Without access to the mailbox, you can’t modify data in it.
Two ways for an exchange/domain administrator to access an user mailbox:
- Grant yourself full Access mailbox permission to the user’s mailbox.
- Change the user’s password and log in as the user.
The first option grants the administrator access to all of the data in the user’s mailbox.
The second option grants the administrator access to all of the data that the user account can access within your company and locks the user out of his own user account.
Configure auto-reply options using the ECP
In Exchange 2010 SP1, you can configure auto-reply options for your users without using either of the above options.
Login to ECP through owa as Administrator or member of that group. Click options (right side top) and select “See all options”, From this screen, where “Manage Myself”, click “Another User” -> select the user you want and double click on the user. This will open his mail option ECP, and click “Tell people you’re on vacation” -> and select Automatic Replies and fillout the information and click Save.
Configure auto-reply options using the Shell Command
This command schedules internal and external auto-replies
Example, if a user is going on leave from 11/11/2011 to 12/10/2011: (MM/DD/YYYY format)
Set-MailboxAutoReplyConfiguration email@example.com –AutoReplyState Scheduled –StartTime “11/11/2011” –EndTime “12/110/2011” –ExternalMessage “External OOF message here” –InternalMessage “Internal OOF message here”
For detailed syntax and parameter descriptions, see Set-MailboxAutoReplyConfiguration (Applies to Exchange Server 2010 SP1).
This command retrieves auto-reply settings for a mailbox.
This command disables auto-reply configured for a mailbox:
Set-MailboxAutoReplyConfiguration firstname.lastname@example.org –AutoReplyState Disabled –ExternalMessage $null –InternalMessage $null
Most of you guys must have experience the scenario when “Outlook connection lost….” even if you have Exchange server 2010 (with Edge, 2 clustered H&C and 2 DAG configured MB) and Outlook 2010 in place. The reason is that, when you are doing a maintenance on one of the H&C, and if the client is connected to that H&C, communication to the MB is lost. The reason for this is that the cluster load balancing on the H&C cluster handler is not in place, even if the cluster name is published in the DNS server.
In Exchange 2007, 5 server roles that performed distinct functions within the Exchange organization. One role in particular – the Client Access server role – introduced a variety of new Web services, including the Availability service, the Auto discover service and Calendar Concierge services.
In Exchange 2010, same 5 server roles exists. However, there are some significant architectural changes and some shift in responsibilities. The most significant change in Exchange 2010, two new services on CAS called the RPC Client Access and Address Book services establish the RPC (Repote Procedure Call) endpoint for MAPI(Messaging Application Programming Interface), NSPI(Name Service Provider Interface) and RFR (Request for Response) client access. This new functionality replaces the RPC endpoints in the Information Store. The RPC endpoint in the Information Store has not been removed in Exchange 2010, but it has been modified to only accept requests from CAS servers. The RPC endpoint for public folder database access remains on the Mailbox server, however, Outlook clients now communicate directly with the RPC Client Access service on the Mailbox Server for public folder database access, and not with the Information Store.
When CAS starts communicating with the Mailbox server, it makes sense to view it as the Client Access server communicating with the Mailbox database via the Mailbox server that hosts the database. This is especially evident in a load-balanced array of Client Access servers and/or where your environment is configured to use Database Availability Groups that are associated with a Client Access server or Client Access server array.
- In a non-load balanced environment, the mailbox database is associated with only a single Client Access server.
- In a load-balanced environment, the Mailbox database is associated with the load balanced array of multiple Client Access servers.
By default, before a Client Access array is configured,
- all databases are associated with a Client Access server in the environment
- the Outlook clients communicate directly with the Client Access server until the association with the database is updated to be the Client Access array.
In order for the clients to utilize a CAS array
- Create a Client Access array with an FQDN (Fully Qualified Domain Name).
- Load balance your CAS servers in a CAS array by whatever method you choose – Both Hardware LB or Windows Network LB are supported load balancers
- Add the Client Access servers within the AD site to a load balanced array and in DNS associate the unique FQDN to the Virtual IP of the load-balanced array.
- Configure your load balancing array to load balance the MAPI RPC ports – TCP 135, UDP/TCP 6005-65535; or set static ports
- Configure the databases to utilize the CAS array… Use the new-clientaccessarray cmdlet to create the CAS array object. Eg: New-ClientAccessArray –Name “Tromso CAS Array” –Fqdn tromso.site.com” –Site “SITEA”
How to Setup!!!..
Goto one of the CAS server where the NLB is ( to read more about New-ClientAccessArray cmdlet, click here )
 Check is there are any pre-created CAS Arrays. PS Command : Get-ClientAccessArray
 Create new Client Access Array. Run the Cmdlet in EMS New-ClientAccessArray -Fqdn server.contoso.com -Site “Redmond” -Name “server.contoso.com”
 Associate databases with this CAS Array –
Use this CMDLet to add mailbox database to CAS array. Add all mailbox databases at once – Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “CASNLB.contoso.com”
Now the best part –
Configuring Outlook 2010 using Auto Discover
If you already configured Outlook client, Close the outlook, then goto Control Panel->Mail and change the Server name to the new CAS NLB name
If you are going to use a new outlook configuration, Auto discover will return the new CAS NLB name.
Thats all folks!!! Enjoy!!!
In the previous edition of OWA and Exchange server 2007, there was a problem for users to change their password…because the loss of the IISADMPWD virtual directory as a supported feature in Windows Server 2008/IIS 7.0. This prevented OWA users with expired passwords from being able to change their password and log on. This was a problem for many OWA users ; especially remote/mobile users with non-domain-joined computers..From Exchange Server 2010 Service Pack 1 and Exchange Server 2007 Service Pack 3 (running on Windows Server 2008 or Windows Server 2008 R2) onwards, they have a new feature that will allow users with expired passwords to change their password. This also works for users who have their accounts configured to change password on next logon.
Use this procedure to enable it on Exchange 2007 SP3 and Exchange 2010 SP1 Client Access servers. If you are using a CAS Array, you must perform these steps on each CAS in the array.
- On the Client Access Server (CAS), click Start > Run and type regedit.exe and click OK.
- Navigate to HKLM\SYSTEM\CurrentControlSet\Services\MSExchange OWA.
- Right click the MSExchange OWA key and click New > DWord (32-bit).
- The DWORD value name is ChangeExpiredPasswordEnabled and set the value to 1.
Note: The values accepted are 1 (or any non-zero value) for “Enabled” or 0 or blank / not present for “Disabled”
- After you configure this DWORD value, you must reset IIS. The recommended method to reset IIS is to use IISReset /noforce from a command prompt.
NOTE : User can’t use a User Principal Name (UPN) (eg: email@example.com) in the Domain\user name field in the Change Password window like below. It should be domain\myname
Once you done with it, click submit…make sure that your new password should match with the domain password policy.
Even if you delete item from the deleted items from your outlook 2010, you can go to the tab under folder on the main page of the outlook 2010 and click “Recover Deleted Item” and view the items on the list
Recently we have noticed that some of the users after upgrading from Microsoft Outlook 2007 to 2010, Meeting request gets auto accept and user won’t notice it.
How to resolve it in Outlook 2010…!
Goto->File->Options->Calender->Resource scheduling and uncheck it
Thats it…uncheck and click ok..problem solved.
Evernote 4 is a major departure from Evernote 3.5 in every way. While 3.5 added tons of great new features. So theydecided to start over from scratch, with fast, native C++ that we knew we could rely on. As you’ll see, the results are amazing. This new version will set a foundation for rapid improvement. It is designed to give you a great experience on any computer that you use, whether you’re on a netbook, a five year old Windows XP machine or a super fast top-of-the-line Windows 7 computer.
Here are a few of our favorite user interface improvements:
- Space saving layout: The toolbar and menu bar are merged to take up less screen space. You can always switch to the old school layout in the Option menu.
- More responsive interface: Switching between notes, displaying searches, bringing Evernote into the foreground, and virtually all other interactions are much faster.
- Easier new note creation: We’ve added a New Note split button, which lets you pick the type of note you wish to create (text, ink or webcam). It will remember your selection for next time.
- Relocated Search Bar: Note search and the search description now reside directly over the note list—a more intuitive location. You can click the small arrow to open and close the search description. Closing the description gives you more room to view your notes list, opening it makes it easy to modify your search.
- Clearer note info: The note information panel is more crisp and clear with the title, notebook and source links right up top. Just like the search panel, you can open the note information panel to access the details. Navigating through the note info panel and tagging notes using your keyboard is fast and efficient.
When you have a mail enabled public folder in your exchange server 2007/2010 environment, you might face issues with email forwarding from the public folder from your user account, where you will get an error “Operation failed”.
- Logon to outlook with administrator(Domain) credemtial
- Goto the Public folder
- Select the folder where you are facing the issue
- Right click
- Select Properties
- Goto Permission TAB
- Add users
- Check mark the appropriate rights on the “Write” permission area..normally “Edit all” will do the work
- Click apply and click ok.