Microsoft Exchange Server 2010 – Organizational Settings for MailTips

MailTips are informative messages displayed to users while they compose a message. Works with only Exchange server 2010 with Outlook 2007/2010.

Microsoft Exchange Server 2010 analyzes the message, including the list of recipients to which it’s addressed. If a potential problem is detected, MailTips notify users prior to sending the message. With the help of the information provided by MailTips, senders can adjust the message they are composing to avoid undesirable situations or non-delivery reports (NDRs).

You can’t use the EMC to enable or disable MailTips. You need to be assigned permissions before you can perform this procedure. To see what permissions you need, click here

EMS : Set-OrganizationConfig cmdlet to enable or disable MailTips in your organization. MailTips are enabled by default, when you install a new Exchange 2010 organization.

Examples of Mailtips, when you activate is like

  • Invalid Internal Recipient : The Invalid Internal Recipient MailTip is displayed if the sender adds a recipient that appears to be internal to the organization but doesn’t exist in Active Directory. It comes due to name resolution cache or an entry in the sender’s Contacts or if the sender types an SMTP address with a domain for which Exchange is authoritative and the address doesn’t resolve to an existing recipient. The MailTip indicates the invalid recipient and gives the sender the option to remove the recipient from the message…cool na
  • Mail Box full :  MailTip is displayed if the sender adds a recipient whose mailbox is full and your organization has implemented a Prohibit Receive restriction for mailboxes over a specified size. MailTip will be updated every two hours in his/her draft folder even if you save it and did’nt send the message.
  • External Recipients : The External Recipients MailTip is displayed if the sender adds a recipient that’s external, or adds a distribution group that contains external recipients. By default, this MailTip is turned off. You can turn it on using the Set-TransportConfig cmdlet. The External Recipients MailTip relies on group metrics data. Therefore, if you enable the External Recipients MailTip, make sure that the group metrics MailTip is also enabled. EMS : Set-OrganizationConfig -MailTipsExternalRecipientsTipsEnabled $true

To know more.. click here

Exchange server 2010 SP1 is bringing up with more featueres and i will update you this in my comming blog

Exchange Server 2010 SP1…Now Available

From my previous post Exchange Server 2010 Service Pack 1 Beta released and Exchange Server 2010 Service Pack 1 – Sneak-peak , they have released the RTM of Exchange server 2010 SP1..Read the blog 

Release Notes for Exchange Server 2010 SP1…Click here
What’s New in Exchange 2010 SP1…Click here
Exchange Server 2010 SP1 – Deployment topics … Click here
Deploy it today

Exchange Server 2010 Service Pack 1 Beta released

In my last post Exchange Server 2010 Service Pack 1 – Sneak-peak and Microsoft Exchange Team Blog Yes Virginia, there is an Exchange Server 2010 SP1, the team shared information on some of the features  and  expected fixes  that are coming with the SP1 update. Microsoft committed to providing the final version of Exchange Server 2010 SP1 before the end of 2010, and now they have release the Beta of Exchange Server 2010 SP1. Video Preview from MSEXCHANGE Team ..You can download the Microsoft Exchange Server 2010 SP1 Beta from here…This pre-release software is intended for evaluation purposes only. You must accept the license terms before you are authorized to use the software. There is no product support for this trial software.

Is The New Exchange 2010 Service Pack Enough to Stop the Migration to Google Apps?..Click here to read

Configure EWS, Autodiscover, OWA, OAB, ECP on Exchange Server 2010

As you all know that the service connectivity for a mail server is the  main concern to all of us. In Exchange server 2010, the connectivity is as same as Exchange server 2007. Once you migrate or install the new version, this should be tested with the proper credentials and certificate..or else, you will end up with your mail server IP going to the blacklist, because of the wrong pointers and configurations. First of all, do the internal test. Go to your computer start bar, right side where Date and time is showing, you will find the Outlook icon, hold Ctrl + right click on the outlook icon and click “Test Email Auto Configuration…”

Select the “Use AutoDiscover” and click Test..

Above one is a success one..If failed, do the below. The Exchange Web Service (EWS) is the web service that allows access to the Out of Office service. If either the internal or external URL for the EWS is missing or incorrect, OOF will fail and other services may not work as expected. Using Exchange Management Shell, check the URLs assigned to the web service virtual directory using the Get-WebServicesVirtualDirectory command

First goto CAS server

Type the following Power Shell command for EWS (Exchange Web Service)

Copy code Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

You will get the result like below

Identity    : ECAS1\EWS (Default Web Site)
InternalUrl : https://mailv.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mailv.domain.com/ews/exchange.asmx

Identity    : ECAS2\EWS (Default Web Site)
InternalUrl : https://mailv.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mailv.domain.com/ews/exchange.asmx

If this is not correct, you need to fix it.. This has to be done on Powershell command on the CAS server.

To do that…Copy code

[PS]C:\Windows\system32>Set-WebServicesVirtualDirectory -Identity “ECAS1\EWS (Default Web Site)” -InternalUrl https://mail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$true

[PS]C:\Windows\system32>Set-WebServicesVirtualDirectory -Identity “ECAS2\EWS (Default Web Site)” -InternalUrl https://mail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$true

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

Identity    : ECAS1\EWS (Default Web Site)
InternalUrl : https://mail.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mail.domain.com/ews/exchange.asmx

Identity    : ECAS2\EWS (Default Web Site)
InternalUrl : https://mail.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mail.domain.com/ews/exchange.asmx

Now you can see that the URL has been fixed. This is for Web Services.

Now for Autodiscovery….

[PS] C:\Windows\system32>Get-AutodiscoverVirtualDirectory

To see the settings

[PS] C:\Windows\system32>Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri

RESULT

[PS] C:\Windows\system32>Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri
Identity                       : ECAS1
AutoDiscoverServiceInternalUri : https://mailv.domain.com/Autodiscover/Autodiscover.xml

Identity                       : ECAS2
AutoDiscoverServiceInternalUri : https://mailv.domain.com/Autodiscover/Autodiscover.xml

To FIX it..

[PS] C:\Windows\system32>Set-ClientAccessServer -Identity ECAS1 -AutoDiscoverServiceInternalUri https://mail.domain.com/Autodiscover/Autodiscover.xml
[PS] C:\Windows\system32>Set-ClientAccessServer -Identity ECAS2 -AutoDiscoverServiceInternalUri https://mail.domain.com/Autodiscover/Autodiscover.xml 

 Now for the Outlook Web Apps, Exchange Control Panel, Exchange ActiveSync, Offline Address book…you have to go to Exchange Management Console (EMC)

  1. Goto one of the CAS server
  2. Open EMC
  3. Goto Server Configuration
  4. Select Client Access
  5. On the Middle top pannel, you can see the CAS server listed.
  6. Select one, on the bottom pannel, you will see like below.

Select each tab and then right click on the object and change the path as required. Once you done with the first CAS servr, do the same for the second as well.

Thats it…you are good to go for production.

Exchange Server 2010 Service Pack 1 – Sneak-peak

Exchange Team Blog that provides the first public details about Exchange Server 2010 Service Pack 1 (SP1).  SP1 will of course include fixes and enhancements in the areas customers have helped us identify (including code from all of the Exchange 2010 post RTM update rollups we’ve released to date).  But SP1 will also include some new features and functionality changes, as well….cool

  • A new search preview helps with early case assessment by providing you an estimate on the number of items in the result set-with keyword statistics-before e-mail located in the search are copied to the designated discovery mailbox.
  • And, a new search result de-duplication option, when checked, only copies one instance of a message to the discovery mailbox.

Look at the below  menu for the DAG…what a cool feature it will be

With the release of Exchange Server 2010 last November, Microsoft introduced integrated archiving capabilities aimed at helping you preserve and discover e-mail data. In SP1, this has enhanced its archiving functionality based on the great feedback you’they got since the launch. This includes adding the flexibility to provision a user’s Personal Archive to a different mailbox database from their primary mailbox. This means your organization can now more easily implement separate storage strategies (or tiered storage) for less frequently accessed e-mail. And, we didn’t just stop there! We’ve also added new server side capabilities so you can import historical e-mail data from .PST files, directly into Exchange, as well as IT pro controls to enable delegate access to a user’s Personal Archive.

To help streamline the implementation of retention policies, SP1 updates the Exchange Management Console with new tools to create Retention Policy Tags, so you can automate the deletion and archiving of e-mail and other Exchange items. New optional Retention Policy Tags give you even more flexibility in defining your organizations retention management strategy….coooool

Can’t wait to get hold of this…Announcement blog from Microsoft Exhange Team …click here Yes Virginia, there is an Exchange Server 2010 SP1

Learn more about our approach to archiving by reading the Archiving with Exchange 2010 whitepaper.

Scott Schnoll’s weblog…click here

Exchange Server 2010 Migration – Useful tools

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.

Performance Monitor..Click here or click here

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.

Exchange server 2010 – SAN certificate creation for autodiscover,EWS and OWA etc…!

Good News for installations guys out there, Exchange server 2010 SAN certificate creation very easy…click here to read my blog
ENJOY!!!!!!!!!!!!!!!!!!!!

Exchange server 2007 to 2010 Live migration!!!! Live blog!!! Live Platform…real time scenario!!!

Please find on my blog, one page dedicated to this task…you can see it on my blog top page… or click here

             TO                                          

 MIGRATION…Started on June 8, 2010 ….Today 20th of June..all the objects has been replicated to Exchange 2010..Now the decommissioning starts..Finish too

Exchange 2010 Mailbox role – installation failed

Error

Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()

This error occurs because the federated built-in e-mail account that links to the computer account no longer exists. Or, the federated built-in e-mail account in the Active Directory directory service is corrupted.

Resolution..go to Active Directory server

  1. Click Start, click Run, type adsiedit.msc, and then click OK.
  2. Locate the Default Naming Context node, and then locate to the CN=Users container.
  3. Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click Delete.
  • Rerun the Exchange Server 2010 Mailbox role setup application.
  • Create a new federated e-mail account by using the following command: (No change in the below command…just type as it is)
    New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
  • Useful link : http://support.microsoft.com/kb/978776