There is a problem that has been documented concerning OAL generation on the shared storage of an SCCCluster on Server 2008. The default setting is to create the ExchangeOAB share and files on the shared storage w/ the mailbox databases. However the OAL Generator consistantly fails and the error is ambiguous even w/ maximum logging. Apparently it cannot write to the shared storage. However it goes as far as creating the UID folder, then fails. The workaround is to edit the registry to generate the OALand ExchangeOABshare on a local drive, which defeats the purpose of SCC, nor is it available by using the cluster name in theUNC path. Rather you have to look at the node that generated the OAL. I amforced to usethis work around in a production system after moving from 2003 to 2007. Is there a fix for this or a better workaround, so this will function normally? Is this a verifiable bug, or isolated to some configurations? Thanks, Tommy

Hi Tommy, I would like to explain that it is a product issue to generate the OAB on the SCC cluster on Windows Server 2008. Our product team is investigating on the issue. To work around the issue, please use the following method: WORKAROUND 1. Change the following Registry value "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\CLUSTERNAME\OALDropFolderLocation" to a local path, for example "C:\Program Files\Microsoft\Exchange Server\Mailbox\OAB" on all Nodes. 2. Remove the old Shared Folder for ExchangeOAB. 3. Create with command "mklink" a new linked Directory on the Shared Drive like the example below: mklink /d "D:\Microsoft Exchange\Mailbox\ExchangeOAB" "C:\Program Files\Microsoft\Exchange Server\Mailbox\OAB\ExchangeOAB" 4. Add the Shared Folder for ExchangeOAB in the Failover Cluster Management. 5. Failover the Exchange Resource from the active to the passive Node and update the Offline Address Book then check if the OAB-Files are available on the shared Drive. Mike

I don't suppose there's any update on this issue?

Exchange 2007 SP1 Hotfix Rollup 4 is out, but I don't see anything in it indicating that this has been repaired. Kind of a pain cause when the cluster is moved over the data is stale for several hours, until it regenerates on the new box, and then publishes up to the CAS servers. Seems very odd that the system can create the sub-OAB folder, but can't write the files into the folder.