1. Data Storage in Unified Messaging
Unified messaging stores data in a variety of
locations and formats. The different types of data include custom audio
prompts, incoming calls, configuration, and setup.
It is important to understand where the data is
stored, the relative importance of backing it up, and the method of
restoring the data. Tables 1, 2, 3, and 4 list the relevant data storage information for each type of data.
Table 1. Custom Audio Prompt Data
| Data Type | Custom audio files (.wav) for UM dial plans and UM auto attendants
Custom audio files (.wav) for telephone user interface (TUI) and Outlook Voice Access |
| Storage | File system in \UnifiedMessaging\Prompts |
| Backup | File-level backup is only needed on the prompt publishing server |
| Restore | File-level restore is only needed on the prompt publishing server |
| Data Type | Custom audio files (.wav) for UM dial plans and UM auto attendants
Custom audio files (.wav) for telephone user interface (TUI) and Outlook Voice Access |
| Storage | File system in \UnifiedMessaging\Prompts |
Table 2. Incoming Call Data
| Critical Data | Incoming calls: .eml and .wma files for each voicemail |
| Storage | File system \UnifiedMessaging\temp |
| Backup | None |
| Restore | None |
Table 3. Server Configuration Data
| Critical Data | Server configuration data, including all objects and settings |
| Storage | Active Directory configuration container |
| Backup | Backup method is domain controller replication or Active Directory backup |
| Restore | This data is reapplied to the server during a setup /m:recoverserver restore |
Table 4. Setup Data
| Critical Data | Limited information is stored in the Registry by Setup that is not essential to server restore |
| Storage | HKLM\SOFTWARE\Microsoft\Exchange
HKLM\SYSTEM\currentcontrolset\Services |
| Backup | Backup method is System State backup or Registry export |
| Restore | Restore method is System State restore or Registry import |
2. Exchange 2010 Outlook Web Application
Lync Server 2010 empowers the Exchange 2010 Outlook
Web Application (OWA) with presence and IM chat. Although Outlook users
are familiar with presence, this integration enables Outlook Web App
users the same functionality. Of course, users must be both mailbox
enabled on Exchange 2010 and Lync enabled for Lync Server 2010 to use
this cool new feature.
Here is how to enable the Lync Server functionality in Exchange 2010 OWA:
1. | First download the following files from Microsoft.com:
CWAOWA Web Service Provider (previously known as the OCS 2007 R2 Web Service Provider), CWAOWASSPMAIN.msi Hotfix for Lync Web Service provider found in KB 981256 Unified Communications Managed API (UCMA) hotfix found in KB 2282949 Unified Communications Managed API (UCMA) update found in KB 968802. The filename is UCMARedist.msp.
|
2. | On the Exchange 2010 CAS server, install the following packages in the order listed:
vcredist_x64.exe dotnetfx35setup.exe ucmaredist.msp ucmaredistHottfix2282949.msp ucmaredistHotfix968802.mssp CWAWebserviceProvider.msi CWAWebServProviderHotfix981256.msi
|
3. | Open the Exchange Management Shell and enter the Get-ExchangeCertificate |fl Services,Thumbprint.
|
4. | Record the thumbprint of the certificate assigned to IIS.
|
5. | Run the following command to configure the CAS server as a Lync presence endpoint:
Get-OWAVirtualDirectory | Set-OWAVirtualDirectory –InstantMessagingType OCS
–InstantMessagingEnabled:$true –InstantMessagingCertificateThumbprint <IIS
Certificate thumbprint> -InstantMessagingServerName <FQDN of Lync Pool/Server>
|
6. | Run IISReset to complete the process on the Exchange side.
|
7. | Open a console or remote desktop session to your Lync Front End Server.
|
8. | Open the Topology Builder tool and download the current topology.
|
9. | Expand the pool and find the Trusted Application Servers item.
|
10. | Click Create a new trusted application pool.
|
11. | Enter the FQDN of your Exchange CAS server, or the FQDN of the CAS array if applicable, and select Single Computer Pool.
|
12. | Select the current pool and site as the Next Hop Pool. Note that if you only have one pool, only one option will be present here.
|
13. | Click Finish and then publish the topology again.
|
14. | Create a new trusted application and associate it with trusted application pool you just created.
|
15. | Decide on a TCP port that is currently unused using netstat –a. We recommend 5059 because it is in close proximity to the standard Lync Server ports, but not in use by default.
|
16. | Use the New-CsTrustedApplication cmdlet. The following is an example:
New-CsTrustedApplication –ApplicationID ExchangeOWA –TrustedApplicationFQDN
<FQDN of CAS server or CAS Array> -port <choose an unused port on the Lync
Server such as 5059>
|
17. | Run the Enable-CsTopology to apply the configuration changes. Check the log files to ensure the process is successful.
|
With the configuration complete, log in to the Outlook Web Application to ensure the presence functionality is working.
