Solved

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

Posted on 2014-09-18
8
280 Views
Last Modified: 2014-10-01
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
Comment
Question by:FlyboyExch60
  • 4
  • 4
8 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40329877
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
 

Author Comment

by:FlyboyExch60
ID: 40330097
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
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40332909
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
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

Author Comment

by:FlyboyExch60
ID: 40335996
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
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40336363
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
 

Author Comment

by:FlyboyExch60
ID: 40343249
--------------------------------------------------------
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
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 40344592
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
 

Author Closing Comment

by:FlyboyExch60
ID: 40355615
Ultimately I used ADSIEDIT to remove the database.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question