Failed to create Exchange OAB Folder

Hello,
I am stuck in my migration from Windows 2008 SBS to Windows Essentials 2012 with an on premise Exchange 2013 server.  I have installed my new Essentials server and my new Exchange 2013 server (both or created in VMware on separate hardware from the SBS 2008 server).  My problem now is OWA and removing the Exchange 2007 server.

I see through posts and comments that the ARRconfig command that I need to run as a part of the rerouting of mail.domain.com for OWA access won't complete successfully until the Exchange server is integrated with the Essentials server which won't complete successfully until the Exchange 2007 server is uninstalled.

I have migrated the mailboxes to 2013 and the public folders to 2013 but now when I try and uninstall Exchange 2008 it hangs on moving the OAB.  The error I get is

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00


Default Offline Address Book
Failed

Error:
Failed to create the 'ExchangeOAB' folder on the target server 'PPM-EXCHANGE'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform this operation. Error message : 'Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))'.

Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))

Exchange Management Shell command attempted:
move-OfflineAddressBook -Identity '\Default Offline Address Book' -Server 'PPM-EXCHANGE'

Elapsed Time: 00:00:00

I have restarted the Microsoft Exchange Message Assistant service but still no joy.  Can someone help me move past this point so I can try to complete the rest?

Thanks soo much!
blkfootAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gareth GudgerCommented:
Lots of possible answers on this forum thread.
http://forums.msexchange.org/m_1800468241/tm.htm
0
blkfootAuthor Commented:
Thanks.  I did come across that in all of my research but none of that helped.  The customer I am working with only has 20 employees so I deleted the OAB and created a new one on the new server.  After that I was able to remove Exchange.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
blkfootAuthor Commented:
I was able to resolve this myself by deleting the OAB.  This was a time sensitive issue for the client.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.