Having trouble phasing out an old Exchange 5.5 server. Can you help?

We used to run purely Exchange 5.5.  We had two 5.5 servers and mailboxes were split between them.  Then we put in an Exchange 2003 machine, using Active Directory Connector to connect to the older 5.5 server running on NT4 (SP6a).  I started moving mailboxes over there ... eventually all of the mailboxes were off one of the 5.5 servers (we still have some mailboxes on the other 5.5 server).  I want to remove this server from our network, but it seems that everytime I turn it off people start complaining about Outlook features (speciafically Calendar items) not working correctly.  I crank up the old 5.5 server and the problems go away.  Any ideas?

This is a long shot (I'm not an Exchange guru), but would it have anything to do with the System Attendant on the old 5.5 server?  Or, maybe the fact the 5.5 server I'm trying to take offline was the original 5.5 server.  At any rate, I want to get this thing off my network.  Plus, I'm soon to have all the mailboxes on the new 2003 server and I'll want to remove the other 5.5 server at that time.  What could be the hangup?

I'm open to suggestions ... fire away.  If you need more detail please let me know.  Thanks.
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.

It's not the System Attendant, but it is the fact that this was likley your first Exchange server, and as such, it houses many of the default system public folders, such as Free/Busy data.  You need to rehome those public folders, and then you can decommission the old server.  Check the following KB article for a description of the process.


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
griffisblessingAuthor Commented:
I think you hit it on the head with the moving of the Free/Busy folder.  As I recall, that was the specific error people were getting ... something about not being able to locate Free/Busy data.  I've moved the folders from the old 5.5 server to the new 2003 server.  Thanks for the great MS article.  Even if this isn't the exact answer you've given me a big push in the right direction.  So you get the points.  Thanks again.
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.