Exchange 2010 sp3 upgrade error - AD references to old 2003 server

I've just tried running the SP3 upgrade for a clients Exchange 2010 server, so I can start a hybrid deployment with 365. The SP installer has come up with an error referring to the old 2003 exchange server and its public folder database. The client doesn't use their public folders much, so if they break its not a big deal but will there be other repercussions? Infact I'm not 100% sure what I need to be deleting in ADSI Edit as I can't find a "Property Name: PublicFolderDatabase".

The following error was generated when "$error.Clear();
initialize-AdminGroupPermissions -DomainController $RoleDomainController" was run: "Object First Administrative Group': the linked object of property 'PublicFolderDatabase' is '<domain>.local/Configuration/LostAndFoundConfig/EXCHANGE1/InformationStore/First Storage Group/Public Folder Store (EXCHANGE1)', which doesn't exist in First Organization '<domain>'. This might be because the object is corrupt in Active Directory. Please set a valid value for this property. Property Name: PublicFolderDatabase".

LVL 1

epicitAsked: 2017-11-22

Who is Participating?

Experts Exchange Solution brought to you by

Enjoy your complimentary solution view.

Get every solution instantly with premium. Start your 7-day free trial.

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.

LVL 9

RoninCommented: 2017-11-22

Have you seen this?

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

LVL 18

Jose Gabriel Ortega CEE Solution Guide - CEO Faru Bonon ITCommented: 2017-11-22

I'd ask, what happened to that exch 2003, is it still there or it was removed from the infrastructure without telling it to Active Directory servers

IF so, just clean up the metadata of the server,
https://www.petri.com/forums/forum/messaging-software/exchange-2000-2003/38979-remove-exchange-server-that-was-not-decommissioned
#if it was a dc also you need to clear the DC metadata
if it was a DC: https://www.petri.com/delete_failed_dcs_from_ad

if none of above works.
https://technet.microsoft.com/en-us/library/bb288905(v=exchg.80).aspx

LVL 1

epicitAuthor Commented: 2017-11-23

The old exchange is long gone, the backups may have even been deleted. The server has been deleted from AD and is actually sitting in lost and found in adsi edit. so those steps in the first petri link had already been done (I was not involved in decommissioning the old server)

The error is only referring to the old 2003 administrative group, Not the current 2010 group. any idea what would happen if I just deleted the whole first administrative group in ADSI edit... (probably nothing good I imagine)

screenshots show administrative groups and the old server sitting in lost and found

LVL 9

RoninCommented: 2017-11-23

As explained in the linked article, one of the objects references delete entry for Public Folders, it needs to be removed some you can continue with the setup.