[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 380
  • Last Modified:

How to delete OAB on Exchange 2007 from with in Exchange 2013

I just completed an upgrade to exchange 2013 from 2007, and I am now decommissioning the 2007 deployment. I need to remove the Public Folder database but  the default OAB cannot be moved cause it was created by version 15.0.0.0. See below.
[PS] C:\Documents and Settings\administrator>Remove-OfflineAddressBook -Iden
tity "Default Offline Address Book (Ex2013)"
Remove-OfflineAddressBook : \Default Offline Address Book (Ex2013) was created
by a newer console version. Console version 15.0.0.0 or later is necessary to m
anage this object.
At line:1 char:26
+ Remove-OfflineAddressBook <<<<  -Identity "Default Offline Address Book (Ex20
13)"
    + CategoryInfo          : InvalidArgument: (:) [Remove-OfflineAddressBook]
   , TaskException
    + FullyQualifiedErrorId : FB8CAE7F,Microsoft.Exchange.Management.SystemCon
   figurationTasks.RemoveOfflineAddressBook
The above was generated from the 2007 exchange server.
How can I manage/ remove this by using the 2013 management shell?
0
FlyboyExch60
Asked:
FlyboyExch60
  • 4
  • 4
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
That is the Exchange 2013 OAB. You shouldn't need to touch that to complete your migration. It shouldn't be using the public folders or anything like that.
Most of the time you will see two OABs, one for the legacy version of Exchange and one for Exchange 2013.

Just remove the legacy OAB and then you should be able to remove the public folder database.

Simon.
0
 
FlyboyExch60Author Commented:
Sembee,
I have completed the upgrade and now decommissioning the 2007 exchange server.
You said that it is the 2013 OAB, so if I delete that on my 2013 exchange server, that should remove it from the 2007 exchange server and I can then remove the Public Folder database?
Basically I need to remove this entry from exchange 2007 so that I can continue with decommissioning.
0
 
Simon Butler (Sembee)ConsultantCommented:
Why do you think that is the cause of the problems with the Exchange 2007 server? It is an Exchange 2013 OAB therefore it shouldn't even be on the Exchange 2007 server.

What is the exact error you get when you attempt to drop the Exchange 2007 public folder database?

Simon.
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
FlyboyExch60Author Commented:
The error I am getting is at the beginning of the question.
Interesting enough, I deleted the default OAB in Exchange 2013, and it removed the entry in 2007.
0
 
Simon Butler (Sembee)ConsultantCommented:
The error you posted was about being unable to remove the OAB.

What I was asking was what error you were getting when you tried to remove the public folder database, which lead you to believe that you needed to remove the OAB from Exchange 2013.

You should not have needed to remove the OAB on Exchange 2013 at all.

You have asked for a solution to what you think is the problem without actually stating what the original error was (being unable to remove the public folder database). It is a common problem on forums.

Simon.
0
 
FlyboyExch60Author Commented:
--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
The storage group 'Second Storage Group' cannot be removed.

Second Storage Group
Failed
Error:
The storage group "server2007\Second Storage Group" cannot be removed when at least one database exists under it.




--------------------------------------------------------
OK
--------------------------------------------------------
0
 
Simon Butler (Sembee)ConsultantCommented:
That has nothing to do with the OAB. That means there is a database on the server. You need to drop the database, then drop the storage group.

Simon.
0
 
FlyboyExch60Author Commented:
Ultimately I used ADSIEDIT to remove the database.
0

Featured Post

Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now