Exchange 2003 problems after upgrade from 5.5 then server removal

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Galvanon - 30 Jun 2005 15:14 GMT

Hello all --

I upgraded a NT4.0 domain and Exchange 5.5 computer to Win2k3 AD and
Exchange 2003. During the final steps of removing the Exchange 5.5 server,
I made a mistake by not rehoming the public folders to the next Exchange
2003 server and now the Exchange 5.5 server is deleted and gone from the
Organization.

Anyway, people were getting the error message:

"Unable to update public free/busy data. The contents of this public folder
are curretnly unavailable. Either the Microsoft Exchange Server computer
servicing the public folder is down or the public folder has not replicatied
to this site. See your administrator"

So, as I looked at the SCHEDULE+ FREE BUSY folder, and I noticed that it
didn't have a replication partner, so I ADDED itself to be it's replication
partner. Now, people are no longer getting that error message. However,
now what happens is if I create a meeting request, some (but not ALL) of the
people who I request a meeting with show their data as Unavailable. Any
ideas what I should do next?

Thanks,
Blake

Reply to this Message

Lloyd Carnie - Quest Software - 30 Jun 2005 21:49 GMT

Hi Galvanon,

During migration you would typically want to rehome or migrate PF system
data such as FreeBusy to the new environment. In your case it sounds as if
you have lost this data because you did not rehome it before removing the
server.

If you check the freebusy maps (right click the PF All Public Folders store
and select to view the system folders) and then click content you should see
all of the FreeBusy maps for that Admin Group. I would think in your
situation it will be mostly empty??

Your migrated users should access their calendars and manually update their
free busy (done within outlook) in order to create new FB maps I think.

Try this with a few accounts and if it works drop me a mail at Quest
Software. I can give you an unsupported tool which may help you here.

Lloyd Carnie - Quest PS

> Hello all --
>
[quoted text clipped - 20 lines]
> Thanks,
> Blake

Reply to this Message

Galvanon - 01 Jul 2005 14:52 GMT

Lloyd,

I actually started the Outlook clients with the /cleanfreebusy switch and
that fixed their problems. And yes, I didn't rehome the PF for Free/Busy
(it was a slight, but glaring oversight -- but at the end of a 25 hour
migration, I got sloppy...)

> Hi Galvanon,
>
[quoted text clipped - 49 lines]
>> Thanks,
>> Blake

Reply to this Message