Exchange 2010 PF corruption

Recently finished migrating from Exchange 2003 to 2010 and doing some cleanup. The current problem is I've got corruption within some PFs. More like spaces in the aliases. When I use "get-mailpublicfolder" I'm receiving (abrieviated) Warning: The object hoodview.fcu/Microsoft Exchange System Objects/Schedule+ Free Busy INformation - -First Adminstrative Group has been corrupted, and it's in an inconsistent state. The following validation errors happened:

Then it goes on to say that only certain characters are valid.

I believe it's spaces within the alias but am having difficulty in resolving. I've use the following code to try and remove but without success.
Get-Mailbox | Where {$_.Alias -like "* *"} | ForEach-Object {Set-Mailbox $_.Name -Alias:($_.Alias -Replace " ","")}

I had some on regular PFs and was able to remove the spaces but these are on the system PF's. It also is happenning on all of the OAB's (OAB Version 2, Version 3a and Offline address book).

I've tried to fix using the Shell and the EMC.

Thanks.
RichardPWolfAsked:
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.

RichardPWolfAuthor Commented:
Thanks,
First script looks like it only deals with mail-enabled PF's. The ones I'm having problems with are system PFs.

Tried the second one already but it didn't help.
0
Simon Butler (Sembee)ConsultantCommented:
You shouldn't be getting the errors on the system folders, unless there was something wrong with the name of the original server.
The errors can also be caused by spaces at the END of the folder names.
How many folders are you talking about? It can be just as quick to go through them manually.

Simon.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

RichardPWolfAuthor Commented:
OAB Version 2
OAB Version 3a
OFFline Address Book - \/o=Texas Partners FCU\/c,,,, <- All that's displayed
OFFline Address Book - First Administrative Group
Schedule+ Free Busy Information - First Adminst.... <- All that's displayed

Most if not all are related to E2k3 I believe so mayby it would be possible to delete these.

I'm trying to get everything cleaned up because I will be doinig another upgrade to E2k13 by end of year and I believe the fewer problems left over from E2k3 the better.
0
Simon Butler (Sembee)ConsultantCommented:
Do you have any Outlook 2003 clients?
If not then you could remove htem. Although my preference would be to reset the system folders instead.

Simon.
0
RichardPWolfAuthor Commented:
No internal 2k3 clients but may have some external. Resetting sounds good as that would leave still able to support them for now. How do you go about resetting them?
0
Simon Butler (Sembee)ConsultantCommented:
These are the instructions for Exchange 2007 - it is the same process for 2010.
http://technet.microsoft.com/en-us/library/bb331972(v=exchg.80).aspx
Simon.
0
RichardPWolfAuthor Commented:
Thanks, Looks like I need to do this after hours/weekend. In your experience how "safe" is this proceedure? In other words how often have you had this proceedure go wrong? And is it worth it?

My goal is to have a clean installation before upgrading to 2013.
0
Simon Butler (Sembee)ConsultantCommented:
It is easier on Exchange 2003. It is a safe procedure to do because it is system data. Nothing that is removed is unique, it is all published by the clients. I have done it a few times recently and it just seems to work.

The other option would be to eliminate public folders completely.

Simon.
0
RichardPWolfAuthor Commented:
Thanks. I'll see what I can do in the next couple of days. I wish it was possible to eliminate PFs but we rely to much on them right now. Would this adversely hamper my upgrading to E2k13?
0
Simon Butler (Sembee)ConsultantCommented:
Public Folders changes significantly in Exchange 2013, as they are stored in a mailbox. I would strongly suggest a lot of reading before you go anywhere near installing Exchange 2013.

Simon.
0
RichardPWolfAuthor Commented:
Thanks, I've done some prelimiary reading. The boss says he wants it installed by EOY. Oh fun oh joy.
0
RichardPWolfAuthor Commented:
Sorry for the delay. Was going to do the reset this morning but after reading the documentation a couple of times I had a question. Does this proceedure reset "all" system folders or specific ones?
0
RichardPWolfAuthor Commented:
Another question, Was reading another post where they were having similar problems. For part of the solution it was mentioned to delete the object in question from ADUC. My question since OAB version 2 and version 3a refer to older Outlook clients "could I delete these objects in ADUC safely?"

Thanks.
0
Simon Butler (Sembee)ConsultantCommented:
It resets the ones that you delete. You don't have to do them all, unless you seeing problems with other parts.
I haven't deleted the object from ADUC myself, so cannot comment on whether it will work or not.

Simon.
0
RichardPWolfAuthor Commented:
Thanks for the reply. Sorry it took so long as I didn't get my usual email saying that a reply had been posted. I should be able to do it after work today (Saturday) if no one stays around the office.
0
RichardPWolfAuthor Commented:
OK, fixed the free/busy folder. Went an looked at the OAB's in question and I don't see a "site" guid. I see "object" guid. Also to I I apply this to the address list container or to the default list or what?

Thanks.
0
RichardPWolfAuthor Commented:
OK, fixed my OAB corruption errors by mail disabling those folders. Is there anything else I should look at before we start our upgrade to 2013? i.e. removing legacy public folders?

Thanks.
0
Simon Butler (Sembee)ConsultantCommented:
The only ones that you really need to worry about are schema-root and owascratchpad. The others Exchange deals with.

Do have a good look through the process though:
http://technet.microsoft.com/en-us/library/jj150486.aspx

Simon
0
RichardPWolfAuthor Commented:
Thanks, going through the documentation now. What I've read elsewhere is those two folders aren't needed and can be removed. I'll get back with you after I read the docs you sent me.
0
RichardPWolfAuthor Commented:
Wow, what a great document. Thanks. Now do I go ahead and remove the two PF's?

 I know I've digressed on the original topic so after this answer I'll close this question until I get farther along in the migration.
0
RichardPWolfAuthor Commented:
-bump- Haven't heard anything since your last post on Wednesday. I still need an answer on my last question that you made me aware of.

Thanks.
Richard.
0
Simon Butler (Sembee)ConsultantCommented:
I didn't realise there was a further question in there.
You can remove those two folders if you wish, or replicate them off. It doesn't really matter. They should be left behind when you move to the modern public folders on Exchange 2013.

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
RichardPWolfAuthor Commented:
Thanks, Sorry for the confusion.
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
Exchange

From novice to tech pro — start learning today.