Exchange Server 2013 Cumulative Update 5

Exchange Server 2013 Cumulative Update 5 has been released kb2936880 has list of improvements and fixes CU5 contains. Don’t forget to test the latest CU and RU updates before applying them to production servers.

List of Issues CU5 has fixed and improved are,

This update resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2963590 Message routing latency if IPv6 is enabled in Exchange Server 2013

• 2963566 Outlook Web App accessibility improvement for UI appearance in Exchange Server 2013

• 2962439 You cannot sync contacts or tasks in Microsoft CRM client for Outlook in an Exchange Server 2013 environment

• 2962435 CRM synchronization fails if the time zone name of a meeting is not set in an Exchange Server 2013 environment

• 2962434 Slow performance in Outlook Web App when Lync is integrated with Exchange Server 2013

• 2958430 "Some or all Identity references could not be translated" error when you manage DAG in Exchange Server 2013 SP1 in a disjoint namespace domain

• 2957592 IME is disabled in Outlook Web App when you press Tab to move the focus in an email message in Exchange Server 2013

• 2942609 Exchange ActiveSync proxy does not work from Exchange Server 2013 to Exchange Server 2007

• 2941221 EWS integration for Lync works incorrectly in an Exchange Server 2013 and 2007 coexistence environment

• 2926742 Plain-text message body is cleared when writing in Outlook Web App by using Internet Explorer 8 in Exchange Server 2013

• 2926308 Sender's email address is broken after importing a PST file into an Exchange Server 2013 mailbox

• 2925559 Users always get the FBA page when they access OWA or ECP in Exchange Server 2013

• 2924519 "SyncHealth\Hub" folder is created unexpectedly after installing Cumulative Update 2 for Exchange Server 2013

• 2916113 Cannot open .tif files from email messages by using Windows-based applications in an Exchange Server 2013 environment

• 2592398 Email messages in the Sent Items folder have the same PR_INTERNET_MESSAGE_ID property in an Exchange Server 2010 environment

Exchange Server and Update Rollups Build Numbers

http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-build-numbers.aspx

 

Best regards,
Oz Casey , Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Http://smtp25.blogspot.com (Blog)
Http://telnet25.wordpress.com (Blog)

Mailbox move failed at 95% with Exception Unable to modify Table (Exchange 2003 to Exchange 2010)

 

If  you are in the middle of migration and you have started to run into issues moving mailboxes, you might have seen MB move fails when it gets to 95 percent with above error. First thing to look at is the move logs to determine the root cause of the problem. From my experience the issues related to a corrupted item within the user mailbox. ( see details of the MB move report)

The top ones to look

• Corrupted or empty outlook rules
• Corrupted Calendar Items
• Corrupted item in the deleted item folders

Easy way to deal with all these issues before you start messing with MFCMAPI is

• Backup User mailbox to PST File
• Assign yourself Full mailbox permissions
• Delete everything ( send items , deleted items, all rules, all contacts etc.
• Perform MB move
• Import PST
• Remove full MB permissions

Working with MFCMAPI

You need to assign Full mailbox permissions to yourself for mailbox the problem mailbox

Setup an Outlook profile with the mailbox that has the problem, logon with your credentials.

1. Open MFCMAPI,
2. click Session
3. Logon
4. Pick the outlook profile you like to load into MFCMAPI

In our case this the problem user is "Aki.Armstrong" we will log into her mailbox

1. Right click on Problem  mailbox
2. Choose Open store
3. Expand the tree, and find the problem folder listed in the MB Move log file
4. Locate the folder listed in the logs.

Example: Folder: '/Top of Information Store/Inbox/USers's Emails/Inbox', entryId [len=46, data=000000001026823AF4CCDA45936168C4A4275CE001008 )

1. Right click on the folder and choose Other tables... and then Rules table...
   Delete the corrupted Item ( rule etc.)
2. Right click on the folder and choose Other tables... and then Rules table...
3. Delete the corrupted rule.
4. Go back to the Exchange Management Console and resume the move-request.

 

Best regards,
Oz Casey , Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Http://smtp25.blogspot.com (Blog)
Http://telnet25.wordpress.com (Blog)

Exchange Server Back Pressure

Back pressure is a resource monitoring feature with Exchange servers which build into Transport service. ( Mailbox Servers ) The idea is to have Exchange Server detect the issues and take necessary action so the messaging servers wont be completely un available.

There are 4 event ID associated with correlating events and actions messaging server would perform.

Figuring out such event can be very usefully when back pressure becomes the issue.

# Explain event descriptions
Write-Host "--------------------------                              ------------------------------"
Write-Host "Event ID 15004 = Resource pressure increased" -Fore Cyan
Write-Host "Event ID 15005 = Resource pressure decreased" -Fore Cyan
Write-Host "Event ID 15006 = Low available disk space" -Fore Yellow
Write-Host "Event ID 15007 = Low available memory" -Fore Yellow
Write-Host "---------------------------                                  ------------------------"

To automate the process we have developed PS script. You can download from TechNet scripting library.

Special thanks to Benjamin Bohn for taking his time and turning my simple script into great resource script.

Stay tuned until next time.

Best regards,
Oz Casey , Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Http://smtp25.blogspot.com (Blog)
Http://telnet25.wordpress.com (Blog)

Migrate DHCP Service from Windows 2003 onto Windows 2008 R2

We will migrate DHCP Service from windows 2003 DC onto Windows 2008 R2 DC. Just follow the simple steps to get the work done

Environment :

• Source Server  windows 2003 ( DC,GC) DHCP Installed here server name is = Server
• Destination Server Windows 2008 R2 ( DC,GC) = We will migrate DHCP Service and all related configurations here
• Log into Source Server where DHCP is installed
• Click Start Open Cmd.exe

Netsh dhcp server export c:\temp\dhcp.txt

Make sure temp directory exist if not create one on the C drive….

Now log into Target Server

• Click start
• In the search type
• ServerManager.msc
• Hit enter
• Click Add Roles

• Now you need the file we have created earlier to import into this server
• I am going to connect the first server and get the file we have created which does have all existing settings for the DHCP server

I am going to copy the dhcp.txt file onto server1 onto temp directory

Click Start

Type Cmd.exe and hit enter

type following and hit enter

Netsh dhcp server import c:\temp\dhcp.txt

 

Now open back to DHCP management

If you refresh all your existed settings are now in this new DHCP Scope

Last thing we need to do is to go back and un-install DHCP services from source server, running DHCP from two servers will same scope will be ugly (-:

Log back onto first server

Well done you have completed DHCP migration

Stay tuned until next time.

Best regards,
Oz Casey , Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Http://smtp25.blogspot.com (Blog)
Http://telnet25.wordpress.com (Blog)