Link to home
Start Free TrialLog in
Avatar of Aaron Olsen
Aaron Olsen

asked on

Offline Address Book Created in Exchange 2013, Want to Delete It and Create it in 2010

Hi all,

I have been tasked with an issue of recreating our Exchange Offline Address Book. For whatever reason the previous admin started to spin up an Exchange 2013 Server in our environment and never finished the deployment. But he changed our Offline Address Book.

Fortunately the Virtual Machine he installed Exchange 2013 to still exists. Its just not connected to the network because it apparently causes issues with Exchange when they connect it.

So i have a half implemented Exchange 2013 system, where i have shell access.

A.) I am unsure of how to remove the address book, i know the shell command, i am just worried of deleting it and effecting the organization (I am not an exchange admin primarily so alot of this is new territory for me.

B.) If i do delete it, how do i recreate it from the Exchange 2010 shell on the correct server?

C.) How do i remove this Exchange 2013 system from our Exchange Environment safely?

Any help you can lend would be greatly appreciated!
Avatar of Henry Dunn
Henry Dunn
Flag of United States of America image

I'd say if you don't want Exchange 2013, you should remove it.  Set the DB OAB back to 2010, then remove Exchange 2013.

Assign OAB to all DBs for Exchange 2010
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "Default Offline Address Book"

Remove Exchange 2013 server by uninstalling it from the server it's on using control panel remove programs.
Avatar of Aaron Olsen
Aaron Olsen

ASKER

We eventually do want Exchange 2013 however we are not ready to move to it yet. There are some issues being caused by it being half implemented
Also,

So assume i am not a powershell guru.

What exactly, do i need to do,

a.) identify who current holds the OAB (When i try to manage it from the gui in Exchange 2010 it tells me i need to manage it from an Exchange 2013 shell
b.) remove it (delete it for all databases)
c.) regenerate a new OAB (I'd like to do this from the Exchange 2010 shell)
d.) assign all the databases to use the new OAB (Again would like to do this from the Exchange 2010 shell)
I have.  I guess i just don't feel comfortable with it given that running even those simple commands on the exchange 2013 side generates errors.
ASKER CERTIFIED SOLUTION
Avatar of hecgomrec
hecgomrec
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hecgomrec is right. I literally just did this, removed rogue 2013 servers, last week, and am now in the process of standing up their new 2013 environment for actual use. It's prob going to take someone who knows what they're looking at looking into your configuration. Maybe a few days work, you should hire a consultant.
Figured. Thanks for all the advice :)