exchange 2013 migration - system/discovery/federated mailboxes corrupted

Hopefully near the end of a 2007->2013 Exchange server move.  Evidently there was some incomplete metadata tied to a long gone server from back in the Ex2003 days which needed to be deleted in order for mailbox migration to happen.  Once I deleted it, now I have errors concerning all the system/discovery/federated mailboxes.  If I run get-mailboxes -arbitration I see 2 good ones including a migration mailbox and a system mailbox with GUID ending {..928C}.  I also have several bad ones - discovery {..852} which is from 2010, federated {..042}, also 2010, system {..ed9}, 2013 and system{..638} and I have no idea what adprep made this last one.  So since I still have my Ex2007 in the picture handling mailboxes, and my Ex2013 server is handling mailflow, I'm not sure which server to go to (or both) to correct this.   Obviously once I migrate mailboxes and PF and OAB, I'm ready to take the EX07 box out of the picture.  If one of you MSEX wizards can steer me, I would much appreciate it.
dvanakenAsked:
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.

Simon Butler (Sembee)ConsultantCommented:
You could just remove them all and recreate them. They are just system mailboxes do don't hold anything that cannot be replaced.
Move all the users to the new platform, then remove them and recreate.

Simon.
0
dvanakenAuthor Commented:
Simon - thanks for your help.  So like this:

1. move mailboxes to 2013
2. delete the "bad" system mailboxes from AD
3. run adprep from the 2013 setup disk
4. run ExchShell commands to re-create them (does this work for federated)?

 *** do I need to recreate all of them - even the ones from earlier versions? The EX2013 adprep only creates the 2013 GUIDs I think.  Any need to run adprep from 2010 or 2007 disk or do it all on 2013 box?  Sorry, <- this is the part I'm confused about.

5. Move PF and AOB as final step?

Thanks, Dale
0
Simon Butler (Sembee)ConsultantCommented:
Before taking the old mailboxes out of AD, I would try doing so through Exchange first. It may not let you though - it isn't something I have had to do recently so cannot remember.
Running the prep commands should recreate most of them. There are Technet instructions for the discovery mailboxes.

I would just do it on the Exchange 2013 box. Thinking about it, I would actually remove them as part of the process for removing the old server. Do you have anything on the Exchange 2007 server? If not, remove it. Get it out of the way.

Simon.
0
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

dvanakenAuthor Commented:
Simon you are awesome.  

The old server is where I am moving from - mailboxes partly moved, still have PF and OAB.  I can move all those items and recreate the missing 2013 system mailboxes - I will try to delete the bad mailboxes through exchange first.  Please confirm the steps:

1. move rest of mailboxes and pf and oab
2. try to delete bad mailboxes with exchange (or AD if I have to)
3. recreate the system mailboxes using the 2013 setup

then what - uninstall exchange 07 from the old server?  Or should i try that before step 2 above?

I'll be moving mailboxes all night so I won't get to the rest of this until Saturday - just confirm the steps and order please!  Thanks again --Dale
0
Simon Butler (Sembee)ConsultantCommented:
Get the databases and public folders off first, before you do anything else.
Then move the OAB and anything else on the Exchange 2007 server. Get it as close to ready to remove as possible. You will be unable to remove the server using add/remove programs because of those arbitration mailboxes, so you will probably have to remove the bad mailboxes at that point. Once done, remove Exchange using add/remove programs.

Once you have done that, then re-run prep.

Simon.
0

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
dvanakenAuthor Commented:
Simon- Will give it a shot tomorrow and post back one way or the other.
0
dvanakenAuthor Commented:
Simon-  A very long weekend ensued but I finally got mailboxes all moved and re-established connectivity to the desktop users ( I got dragged kicking and screaming into Outlok Anywhere).

Now I have a problem with public folders, it won't move a folder called EFORMS and complains about a member in the folder.  I thought you might know if this is common.

Also, when going from 2007->2013 do I need to actually move the OAB or is that accomplished in the mailbox move?  If PF is all that I have left maybe I can get the 07 server decommissioned in the next day or so.  Thanks and best regards.
0
Simon Butler (Sembee)ConsultantCommented:
The only thing you need to do with the OAB is move the generation server. The distribution is handled by either public folders and/or web distribution within Exchange.

EFORMS is a system folder and can probably be ignored. What is the exact error you get when you try to work with it?

Have you tried using the move all replicas script to clear the public folders out?

Simon.
0
dvanakenAuthor Commented:
This appears to be the most relevant part...

FailureSide                      : Target
Message                          : Error: Property expression "Company Forms" isn't valid.

Valid values are: Strings  formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !,  #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.
0
Simon Butler (Sembee)ConsultantCommented:
You need to look on the properties of the folder "Company Forms" and remove the space. Wait half an hour or so for the change to replicate, then try again.

Simon.
0
dvanakenAuthor Commented:
Simon - that worked!  

A little fumbing with cmdlets and I now have the PF DB on the new server.   I turned off the Exchange services on the legacy server and we seem to be still fine, although when I run "Get-PublicFolderDatabase" on either server it still shows me the old server name which is baffling since Ex13 shows all the PFs correctly in the EAC.

Do I uninstall Ex07 in its entirety next?  EMC still shows mounted databases and I remember that I need to clear out mailboxes, etc at some point.  Maybe that's next?

-Dale
0
dvanakenAuthor Commented:
Simon-

All is well.  I successfully uninstalled Ex07 from the legacy server and no problems so far.  If I could only find a way to stop Outlook from logging synch error emails I would be done.  None of the methods in articles actually work.

Thank you once again.  --Dale
0
dvanakenAuthor Commented:
Simon - thank you again for all your expertise and guidance....
0
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
Windows Server 2012

From novice to tech pro — start learning today.