Exchange 2010 IS/AD Interactions Warning

Hello, we have a single Exchange 2010 SP3 server with all roles installed, we are having an issue with the SystemMailboxes where we get the following event:

Event 7043 MSExchangeIS

The mailbox GUID of an external system mailbox ('Mailbox - SystemMailbox{03daeb05-03fd-48ee-b028-14f760f457c7}') does not match the information in the Active Directory for the mailbox. The existing GUID ('7598b1d8-b2ed-4f12-a193-9b2802f7c8fd: /o=Taco John's/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=SystemMailbox{03daeb05-03fd-48ee-b028-14f760f457c7}') has been replaced with the expected GUID ('dd6c102b-8b19-40eb-9656-d7182904b894: /o=Taco John's/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=SystemMailbox{03daeb05-03fd-48ee-b028-14f760f457c7}').

We also have several different AD Objects in the Microsoft Exchange System Objects Container:
AD Exchange System Objects Container
While we see these other objects in the AD Users Container:
AD Users Exchange System Mailboxes
How do we go about fixing these conflicts/errors?  I've tried recreating the schema with setup /prepareAD which doesn't seem to fix the problem, however, it did allow me to mount a newly created database that wouldn't mount before running that command.

I am hesitant to delete any of the accounts as I attempted to fix this in the past and it ended up making one of our databases un-mountable which is definitely not ideal.

Thank you in advance and please let me know if you need further information/details.
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.

AmitIT ArchitectCommented:
did you migrated from earlier version of exchange server or it was a fresh install.
TacoJohns-ITAuthor Commented:
The initial install was done on Exchange 2003 I believe, however, that was long before my time.  I migrated the system from Exchange 2007 to a new Exchange 2010 server last summer.
AmitIT ArchitectCommented:
Something similar discuss here

Which says to delete them, as they no more required.
TacoJohns-ITAuthor Commented:
I've tried that before and ended up making one of the databases there a safe way to tell which ones are not needed, I've looked at the output from "Get-Mailbox -arbitration" would I be safe to delete ones not referenced in there or are there other places to check which system mailboxes are in use?
AmitIT ArchitectCommented:
You just ignore it. It won't cause any issue. In large Exchange environment this is very common issue.

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
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

From novice to tech pro — start learning today.