Microsoft has released Update Rollup 2 for Microsoft Exchange Server 2007 Service Pack 2 (SP2). You may feel UR1 just came out. but UR2 come out with many bug fixes. See below shown links.
In November Microsoft Exchange Team have been released the initial version of Exchange Deployment Assistant. That initial version included instructions to upgrade from Exchange Server 2003. Microsoft Exchange Team announced today they have been added new upgrade scenarios to that Deployment Assisitant. See fallowing scenarios.
- Upgrading from Exchange Server 2007
- Upgrading from a mixed Exchange Server 2003/2007
- New Exchange Server 2010 installation
Click here to enter to Exchange Deployment Assistant.
MailTips is a one of the new features of Exchange Server 2010. When a Sender composing a message, MailTips gives the some status information of the recipient and that helps to reduces unnecessary and undeliverable e-mails, as well as reduce some embarrassing things done by senders. MailTips are hosted as an Exchange Web Services on the Client Access Server.
MailTips are work with the Scenarios given below.
- If one of the recipients is out of office.
- When the recipient’s mailbox is full
- Message size exceeds sender’s send limit.
- If The Message quota exceeds of the recipient.
- When Sending email to a large number of recipients.
- When trying to send email to restricted recipients.
- When a booking a room with exceeded invitees.
- When sending to External and invalid domains.
- When trying to send to moderated recipients.
- Attaching more attachments than allowed.
Gather Organization wide configuration MailTips settings.
Run below CMDlets on Exchange Management Shell to gather ORG settings. See figure 1.
Get-OrganizationConfig | fl *mailtips*
Enable or Disable MailTips.
You must use “Set-OrganizationConfig” CmdLet to enable or disable mailTips. Mailtips are enabled by default. See figure 2.
Set-OrganizationConfig -MailTipsAllTipsEnabled $true
Configure the large audience size for MailTips.
You must use “Set-OrganizationConfig” Cmdlet to configure large audience size. With a fresh Exchange Server 2010 installation it would be 25 by default. If we decrease it to 15, then Mailtip would be display to sender if sender add more than 15 recipients. See figure 3.
Set-OrganizationConfig -MailTipsLargeAudienceThreshold 15
Large Audience Threshold MailTip will display after adding more than 15 recipients . See figure 4.
Enable or disable the External Recipients MailTips
We have some embarrassing experiences of sending some internal information to external parties. However company doesn’t want to restrict sending emails to outside domains. With MailTips at least we can give a alert to the sender before click send button. See figure 5.
Set-OrganizationConfig –MailTipsExternalRecipientsTipsEnabled $True
External Recipients MailTips displays when trying to send to an external domains. See figure 6.
Enable or disable MailTips that rely on mailbox data
Mailbox based MailTips are rely on the mailbox data. There are two Mailbox based Mailtips, The Recipient Out of Office and Mailbox Full MailTips, rely on the mailbox data. See figure 7,8 and 9 .
Set-OrganizationConfig -MailTipsMailboxSourcedTipsEnabled $true
The Recipient Out of Office. You can get to know if whether the recipient is out of the office before you send the email. See figure 8.
Mailbox Full. If recipient’s Mailbox is full, you can know that before sending the email. See figure 9.
Configure Group Metrics
MailTIps relies on Group Metrics data to provide information on the the size of distribution groups and dynamic distribution groups. Exchange server normally query a lot of LDAP requests to the Active Directory to get group membership information for each message.This could affect the the performance experienced by the users. To eliminate these issues Exchange server uses the Group Metric data. Group Metric data can be scheduled to run during office hours. You should use Set-MailboxServer CmdLet to configure Group metric Data. See figure 10.
Set-MailboxServer EX10-MB01 -GroupMetricsGenerationEnabled $true
Exchange 2010 RTM has been released a few weeks back. Exchange 2010 came with some cool new features compared to previous versions and also some major differences in the field of High Availability. All High availability scenarios which came with previous Exchange server versions have been removed in this version.
Exchange server 2010 doesn’t have LCR, CCR or SCR high availability options, instead it has DAG (Database Availability Group) . You can achieve your high availability goal with DAG adding minimum 2 database copies and up to 16 database copies. DAG uses Continues replication technology that was first introduced with Exchange 2007 and DAG is essentially a combination of CCR and SCR that was available in Exchange 2007. You can find more information of DAG here.
Best practices of Database Availability Group
- Need to run two network adaptors on DAG nodes to support Windows Clustering.
- Be aware of choosing server hardware for DAG nodes. Because exchange DAG node should have the ability to manage load of replica of other master copies.
- Should be plan proper IP address schema for current and future requirements.
- Running NLB and DAG on same node isn’t support by Microsoft.
- Must disable Power Management setting on both BIOS and windows configurations.
- Test failover and failback before migrating users to DAG databases.
- Need to monitor DAG health periodically.
- Make Sure Database names are unique.
- Periodically move the master database among other DAG nodes to verify DAG is working properly.
In this article I’ll show you how to configure DAG using Exchange management Shell. Here I’ll use two DAG member servers, one Hub transport, client access server and one domain controller.
Step 1 – Creating new DAG
Create new database availability group using Exchange management shell. Run CMDlet given below in the exchange management shell. This Cmdlet contains file share witness server name, DAG IP address for MAPI network and DAG name. (See figure 1)
New-DatabaseAvailabilityGroup -Name E14-DAG -WitnessServer EX10-CAHT -WitnessDirectory “c:\FSW” -DatabaseAvailabilityGroupIPAddresses 18.104.22.168 –Verbose
Figure 1 – Creating new DAG
Step 2 – Add first node to the DAG
At this point DAG has been created, but DAG has no DAG members yet. So we should run cmdlet given below to add EX10-MB01 server to DAG. (See figure 2).
Add-DatabaseAvailabilityGroupServer -Identity E14-DAG -MailboxServer EX10-MB01 -Verbose
Figure 2 – Adding first node to the DAG.
Step 3 – Add second node to the DAG.
Add-DatabaseAvailabilityGroupServer -Identity E14-DAG -MailboxServer EX10-MB02 -Verbose
Figure 3 – Adding second node to the DAG.
Step 4 – Verify DAG through the Exchange Management Shell
Now we have finished creating DAG and adding members to that . Now we can see some new information via EMS made by the DAG.
Use Get-DatabaseAvailabilityGroup Cmdlet to verify DAG installation. Run this CMDlet in EMS. (See figure 4).
Get-DatabaseAvailabilityGroup -Identity E14-DAG –Status
Figure 4: Display operational Servers
We can see E14-DAG has been added to the Exchange and EX10-MB01 and EX10-MB01 have been added to the DAG as members.
Run Get-DatabaseAvailabilityGroupNetwork Cmdlet to see available Network settings for the DAG. Run the CMdlet given below in EMS. (See figure 5).
Get-DatabaseAvailabilityGroupNetwork -Identity E14-DAG
Figure 5: Display available Network Settings for the DAG.
At this point we have created the DAG. Now we should add the Database copies to the DAG. Run CMDlet given below to replicate MB01 with EX10-MB02 and replicate MB02 with EX10-MB01 servers. See figure 6.
Add-MailboxDatabaseCopy -Identity MB01 -MailboxServer EX10-MB02
Figure 6: Adding MB01 database to EX10-MB02
Add-MailboxDatabaseCopy -Identity MB02 -MailboxServer EX10-MB01
Figure 7 : Adding MB02 database to EX10-MB01
At this point we have configured the DAG successfully. Now we should verify if whether the DAG is configured or not .
Run Get-MailboxDatabaseCopyStatus to monitor the overall health check of database copies. (See figure 8).
Figure 8: Check overall health status of the DAG
We can see information of database copies by running the below CMDLets. Run below CMDlet to see MB01’s Database copy information. See highlighted area. (See figure 9).
Figure 9: See MB01 database copy information.
Run Test-ReplicationHealth CMDlet to check replication status of DAG. (See figure 10).
Figure 10 : Test replication health of DAG.
In this article I have guided you in deploying Database Availability Group, Which is the coolest feature out of many in the new Exchange 2010. I’ll show you how to test failover scenarios in a future article.
Today at the Microsoft TechED 2009 conference in Germany , Microsoft Business Division President Stephen Elop announced that Microsoft Exchange Server 2010 is now available worldwide to help businesses reduce costs, protect communications and delight e-mail users.
According to a commissioned study of technology early adopters conducted by Forrester Consulting on behalf of Microsoft Corp., a customer can see a payback period of less than six months when upgrading to either Exchange Server 2010* or Windows Server 2008 R2. Here Microsoft PressPass story.
Here is some of the new top features
- Reduced deployment cost
- Simplified high availability and disaster recovery
- Greater mobility and flexible access
- Easier administration and decreased dependence on the help desk
- Decreased inbox overload and increased productivity
- Transformed voice mail
- Safeguards for sensitive information
- Simplified compliance
- Reduced risk of malware and spam
Download from here: Microsoft Exchange Server 2010
Microsoft has updated new version of Remote connectivity analyzer. Exchange administrators can simulate several clients logon and mail flow scenarios using Remote connectivity analyzer. They added few new features and updates with this update. Here are some.
- New user interface
- New CAPTCHA add-on
- Beta label has removed
- Exchange Web Services test added
- Outbound SMTP test added
- Outlook anywhere test compatible with Exchange 2010
- added the TechNet forum link
- Added Password confirmation text box
See below Screenshots
Figure 1 – New added things on interface
Figure 2- password confirmation text box.
To see full story, Click here.
Using Moderated Transport feature in Exchange 2010 administrator have capability to push emails for moderated approval process if the destination moderated user. You would be able to configure email moderation for any type of recipient type.
Components of Moderated Transport
- Categorizer – Categorizer is responsible to initiate approval process.
- Store Driver – The store driver process the email messages that categorizer marks for approval process.
- Information Assistant – The information Assistant monitors the Arbitration mailbox and its resubmit if any messages approved or delete any rejected messages.
- Arbitration Mailbox – The Arbitration Mailbox store all email messages for approval process.
Configure a Moderated Recipient
Using Exchange Management Console
Required permission to configuration Moderated Recipient.
Administrator wants to enable Moderation for “Company Users” distribution group and nominate Mike and Vonod as Moderators, then notify only internal senders if users messages were rejected, not for the external recipients.
1. In the EMC console tree, click Recipient Configuration then click distribution group. See figure 1
2. Click the Company Users distribution group in the result pane and select properties .Then select Mail Flow Settings tab. See figure 2
3. Select Message Moderation and click properties. See figure 3
4. Select the Messages sent to this group have to be approved by a moderator check box.then click add to add Moderated Recipients and select Mike and Vinod.then click ok. See figure 4
5.Click the Notify senders in your organization only when their message is not approved option.Then click OK twice. See figure 5.
Test E-mail moderation.
OK E-mail moderation configuration part is done. Now we want to test email Moderation is working or not.
Send email to Company Users distribution group. Immediately appeared mail tip and it was mentioned Company Users distribution group is Moderated and it might reject or delayed. See figure 6.
Check Mikes mailbox to see whether email has come for approval. See figure 7
If moderator rejected the email, Users will receive delivery failure notification as shown below. See figure 8
Microsoft Exchange team will do the six developer web casts to give what exchange 2010 mean for them. They have released channel9 video to give you an introduction regarding Exchange 2010 web services.
Microsoft has been made change the information store manageability from server to Organization level of Exchange 2010. In exchange 2010 Database no longer connected to Server object and its now belong to Organization configuration node in the Exchange management console. Also you can see the Database information location has been changed under CN=Databases in the ADSI (Active directory Services interface). See below Screenshots.
See figure 1.Please see under the InformationStore and notice there is listed databases of Exchange 2007.
Configuration\CN=Configuration,DC=msglab,DC=local\CN=Services \CN=Microsoft Exchange\CN=First Organization\CN=Administrative Groups\CN=Exchange Administrative Group\CN=Servers\CN=Ex2007\CN=Information Store\CN=First Storage Group
Figure1 Exchange 2007 Database information appears under server object.
See figure 2, please see under the information store object and note there is no Exchange 2010 database information in the detail pane.
Configuration\CN=Configuration,DC= msglab,DC=local\CN=Services\CN=Microsoft Exchange\CN=FirstOrganization\CN=AdministrativeGroups\CN=ExchangeAdministrative Group\CN=Servers\CN=Ex2010\CN=Information Store
See figure 3.Please see under the databases object and notice there is listed Database information of exchange 2010.
Configuration\CN=Configuration,DC=msglab,DC=local\Services\CN=Microsoft Exchange\CN=First Organization\CN=Administrative Groups\CN=Exchange Administrative Group\CN=Databases
Also look at below Exchange management Console and note the Database configuration listed under the organization configuration.
- This moment writing this post Exchange 2007 can install only on Windows 2003 SP2 and Windows 2008 SP1.
- Exchange Management Console or Management Shell can’t install on windows 7 unless on Windows XP mode in windows 7.
- Exchange administration via Exchange management console and Exchange management shell can install only on Windows XP SP2 and Windows Vista SP2.
- Even Exchange 2007 SP, cannot install on Windows 2008 R2.
- Windows 2008 R2 allow you to use as Domain controller roller.
- Exchange server 2010 doesn’t support on Windows 2003.
- Exchange 2010 Can install on Windows 2008 with minimum SP2 and Windows server 2008 R2.
- Exchange management shell and management console can be install on Windows vista SP2, Windows 7, Windows server 2008 R2, Windows server 2008 SP2
Exchange Server 2007
|Windows XP SP2||
Yes(Exchange management tools)
|Windows Vista||Yes||Management tool can install with only SP2|
|Windows 7||No but can install on windows XP mode||Yes|
|Windows 2003 SP2||Yes||No|
|Windows 2008 Sp1||No||Yes|
|Windows 2008 Sp2||Yes||Yes|
|Windows 2008 R2||No||Yes|