• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 498
  • Last Modified:

Uninstall and Reinstall of Exchange Server 2007 to Fix Problems Left Over From SharePoint 3.0

I've got an Exchange Server 2007 installation that originally had SharePoint Service 3.0 (64-bit) on it, which ended up breaking OWA.  I removed SharePoint, uninstalled and reinstalled CAS, which now works.  However, while I still have my IIS virtual folders for OWA and Exchange ActiveSync, I'm missing the Public folder items, as well as others in IIS that used to be there before the uninstall.  I don't have confidence in the installation at this point and would like to uninstall Exchange Server 2007 and reinstall it so that I have all of the folders that I should have.  What is the best way to accomplish this and what might happen as a result?  Are the negative repercussions to the uninstall and reinstalls?
0
rgmckenz
Asked:
rgmckenz
  • 3
  • 3
1 Solution
 
czcdctCommented:
It's the best option. SOmeone should have told you that you can't put SPS on an Exchange box. Only WSS is supported and then only after quite a few steps within SharePoint.
Carry out the uninstall in the normal way. If there is content in the PF stores you will need to convince the server that you've moved the replicas away to another server but at the end of the day you should be able to uninstall without too much trouble.
Do the re-install using the same name in order to keep AD neat and in order.
0
 
rgmckenzAuthor Commented:
Thanks for the reply, czcdct.  Actually, it was WSS 3.0 64-bit, and both it and OWA were working right up until I extended the site in IIS.  Big mistake.  I've uninstalled WSS and uninstalled and reinstalled Exchange CAS, but still have the problem of the missing folders (public, etc.) is IIS.  The CAS reinstall only seems to take care of OWA and ActiveSync.

Are there any critical questions that the uninstall will ask me, such as "removal of the last Exchange server in the forest" stuff?  I want to keep things as neat and clean as possible.  Thanks ahead for your reply.

-RGM
0
 
czcdctCommented:
Gotcha.
Since you're going to re-install the box you won't have too much of a worry. You might have a little bit of a problem uninstalling Exchange if you're leaving any PF content lying around but since you're on WSS I might assume that you're not intending on using PFs in 2007 (perhaps?)
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
rgmckenzAuthor Commented:
OK, that begs another question...can you use the legacy Public Folders in a brand new Exchange Server install, or is it just around to support migration from Exchange 2003/2000/5.5?  Right now, there's no PF stores at all, so it shouldn't be a problem.  I was intending on using WSS 3.0 in place of the public folders, but now I have to find another server to put it on.  The only one really available is a DC (the others are a backup server, an app-specific server and a Citrix server), and I don't want to put it on there.  If I can use legacy public folders with the new install, then I might do that and move to WSS when I have resources to put another server in place.  Any other thoughts?  I will try the uninstall and reinstall later today.
0
 
czcdctCommented:
Best to move forward without PFs. You'll save yourself a migration headache-ette further down the line.
0
 
rgmckenzAuthor Commented:
Thanks, czcdct!  That's what I'll do.  No more headaches needed here!

I'll let you know how everything works out.  Quite different, this Exchange 2007.  I've been around Exchange since the 4.5 and 5.0 days, but things haven't changed that much since 2000 was released.  2007 is a whole new ballgame, but I can see some of the advantages right away.  I just wish they would allow you to run WSS 3.0 on the same server as OWA / Exchange without complications, especially if it is the replacement for public folders.  We service a lot of small to medium-sized customers that don't have the resources to dedicate a server to every single task.  But anyway, I digress.  Thanks again and enjoy the day!

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

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now