1 / 13

Exchange 2010 TOI

Exchange 2010 TOI. Background. A lot of the background information is captured in an internal wiki: http://zed.cisco.com/confluence/display/UCBU/Exchange+2010+Investigation Note that there are “children” pages off the main Ex2010 wiki. They contain important information too.

redell
Download Presentation

Exchange 2010 TOI

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Exchange 2010 TOI

  2. Background • A lot of the background information is captured in an internal wiki:http://zed.cisco.com/confluence/display/UCBU/Exchange+2010+Investigation • Note that there are “children” pages off the main Ex2010 wiki. They contain important information too. • Please follow the installation instruction. This TOI is not going to repeat that.

  3. CAS – Client Access Server • All MAPI traffic goes through the CAS when dealing with 2010 mailboxes. • It is very important to install a CAS first before any other role. Otherwise mailbox access, even through Outlook, will fail.

  4. CAS – Client Access Server • To check if a mailbox database has CAS set correctly, run the following in Exchange Management Shell (EMS): [PS] C:\>Get-MailboxDatabase Name Server Recovery ReplicationType ---- ------ -------- --------------- Mailbox Database 1049916361 SIB-E2K10-C False None Mailbox Database 1952193598 SIB-E2K10-D False None [PS] C:\>Get-MailboxDatabase "Mailbox Database 1952193598" | fl RpcClientAccessServer RpcClientAccessServer : SIB-E2K10-C.SIB.ECSBU-LAB-SEA.CISCO.COM

  5. CAS – Client Access Server • If RpcClientAccessServer does not point to the correct CAS, issue the following command in EMS: Set-MailboxDatabase <Mailbox Database name> -RpcClientAccessServer <name of the CAS server> For example: Set-MailboxDatabase "Mailbox Database 1952193598" -RpcClientAccessServer SIB-E2K10-C.SIB.ECSBU-LAB-SEA.CISCO.COM

  6. DAG – Database Availability Group • Unity works with Exchange 2010 DAG. However there is currently one limitation. When there is a DAG switch over, Unity could take up to 15 minutes (default GC sync interval) to detect that. During this period, Unity will be in UMR mode. (CSCtg15295)

  7. Throttling Policy • Exchange 2010 enforces a throttling policy. Unity must has this throttling policy set to unlimited. To do that, follow the instruction on this wiki page. (This should be covered in the installation doc as well.) • http://zed.cisco.com/confluence/display/UCBU/Removing+the+Exchange+2010+RPC+limit+for+the+Unity+Messaging+Account

  8. Script to check Throttling Policy • We have created a PowerShell script to check if an acceptable throttling policy has been applied to the Unity messaging account (typically named “UnityMsgStoreSvc”). • This script can be downloaded from the same place where you downloaded this TOI. We are also planning to including this script into CommServer\TechTools.

  9. Running the script [PS] S:\wfu\Ex2010>.\umsg.throttle.check.ps1 Enter the name of the Cisco Unity Messaging Services Account ==>: UnityMsgSvc Account Name: Unity MsgSvc [CN=Unity MsgSvc,CN=Users,DC=SIB,DC=ECSBU-LAB-SEA,DC=CISCO,DC=COM] RecipientType: UserMailbox ExchangeVersion: 0.10 (14.0.100.0) Unity MsgSvc is assigned to ThrottlingPolicy "Unity Exchange 2010 Policy". RCAMaxConcurrency value for Unity Exchange 2010 Policy is null (unlimited). This account is acceptable for use as the Cisco Unity Messaging Services account when Unity subscriber mailboxes are hom ed on Exchange 2010. Log file has been written to C:\Users\ADMINI~1.SIB\AppData\Local\Temp\2\diag_umsgthrottlecheck_20100409_142430.txt [PS] S:\wfu\Ex2010>

  10. Permission Permission Permission • It is important to run the updated PW to grant Unity access to the Exchange 2010 mailbox database. • After the initial installation of Exchange 2010 support, when new mailbox database is added, make sure to run PW again.

  11. New mailbox database • When new mailbox database is added in Exchange, make sure to run PW. • Also reboot Unity after a new mailbox database is added. These are not new, but worth to watch out for.

  12. MAPI DLLs • When working with Exchange 2010, it is important to make sure that the correct set of MAPI DLLs are installed on the Unity box. If you follow the installation instruction, you should be OK. But to double check: • Make sure there is no emsabp32.dll and emsmdb32.dll in windows\system32 directory. • Windows\system32\mapi32.dll should be at version of 6.5.7654.9 or higher. Or still at version 1.x. Anything in between is no good.

  13. Misc • UDP-Push Notification mechanism isn’t used any more with 2010 mailboxes; async RPC (slow RPC poll) is now used.

More Related