Solved

Upgrade Exchange 2003 Standard to 2003 Enterprise

Posted on 2007-03-22
12
1,962 Views
Last Modified: 2011-09-20
Hello,
We're running Exchange 2003 Standard SP2.  The IS size is approaching 75gb, so we are planning an upgrade to Exchange 2003 Enterprise.  I have read other posts regarding the upgrade process and it seems straightforward... run setup.exe on the Enterprise disc and choose "reinstall".

I'm just wondering if any of the following configs on my Exchange server could cause a problem...
1.  We have GFI MailSecurity and MailEssentials installed on the Exchange server.  Will they be affected by the upgrade or have an effect on the upgrade process?
2.  We have a second server running GFI Faxmaker that points uses an SMTP Connector on the Exchange server.  Will this be affected by the upgrade or have an effect on the upgrade process?
3.  My predescesor installed Outlook 2003 on the Exchange server.  Will this be affected by the upgrade or have an effect on the upgrade process?
4.  I have good backups of the IS and System State of the Exchange server.  Should anything else be backed up "just in case"?

I'm planning on doing the upgrade this Saturday night, so I want to make sure I've accounted for all possibilities.

Thanks.
Scott
0
Comment
Question by:gouldandlamb
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
  • 3
  • +1
12 Comments
 
LVL 10

Accepted Solution

by:
MATTHEW_L earned 300 total points
ID: 18771936
I would have to say that this is very straight forward.  Shouldn't be any problems.  The GFI applications will work with std and ent.  Faxmaker the same thing, as long as the connector is still available should work fine.  Like you said, good backups.  I would backup the whole server.  For some instances I have actually made complete Ghost backups of a server before an upgrade just so that I could easily put everything back in case of a failure.  If you don't do that, backup your Information store, system state, any other data, etc. on the server.

Why do you have Outlook on an Exchange Server?
That is a very bad idea.  This can cause many problems .
http://support.microsoft.com/kb/266418
0
 

Author Comment

by:gouldandlamb
ID: 18772830
Thanks for the response Matthew L.  I have no idea why Outlook is on the Exchange server.  The "Last used" date in Add/Remove Programs is July 2006.  Like I said, my predescesor installed it (and he did quite a few other bone-headed things).  I've heard and seen the documentation advising against having Outlook on an Exchange server.  My concern now is uninstalling Outlook... do you think it will cause any problems?
0
 
LVL 10

Expert Comment

by:MATTHEW_L
ID: 18773587
I have heard problems with MAPI after uninstalling Outlook.  I definatly think getting it off of there is a good idea though.
0
Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

 

Author Comment

by:gouldandlamb
ID: 18773901
If uninstalling Outlook could cause MAPI problems, would the upgrade/reinstall to Enterprise resolve those problems?
0
 
LVL 10

Expert Comment

by:MATTHEW_L
ID: 18774066
I have fixed problems related to outlook on an Exchange server by removing outlook and running a re-install of Exchange.
0
 
LVL 104

Assisted Solution

by:Sembee
Sembee earned 200 total points
ID: 18775289
What I would do, is remove Outlook and reboot the server.
Then run the reinstall option to get the server up to Enterprise edition.
Finally I would re-install Exchange 2003 SP2 and download any updates from Microsoft again, to ensure that everything is up to date.

Simon.
0
 

Author Comment

by:gouldandlamb
ID: 18782347
Thanks for the input guys.  I'll follow Sembee's order of events.
Any idea how long it *SHOULD* take for the Enterprise upgrade?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 18783299
Exchange 2003 install takes about 30 minutes, so as it hasn't got to install much, it shouldn't take that long. However then you have the service pack on top - but even so, you should be able to get things done in an hour.

Simon.
0
 

Author Comment

by:gouldandlamb
ID: 18784100
Excellent.
Thanks again for your help Matthew and Simon!
0
 

Author Comment

by:gouldandlamb
ID: 18792374
Well the process went flawlessly on Saturday.  Thanks again for your assistance.

I uninstalled Outlook 2003 and then rebooted, upgraded to Exchange Enterprise and finally reinstalled SP2, all without a hitch.  I must say however, that the Enterprise upgrade is a bit missleading... I was expecting the "Reinstall" option to be available much earlier in the process...  I was a bit hesitant to choose the "Install first Exchange Server" option, knowing that I already had one.  At any rate, I finally got to the component installation, chose "Reinstall" and let it do its thing.

The last issue I have is... I'm still geting Event 9688 in the Application Log, stating that the database size is 72gb and approaching the 75gb limit.  Is this because the upgrade to Enterprise didn't change the Registry keys limitting the size of the database?  Is it now just a matter of changing (or removing) the database size entries in the Registry?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 18792435
I will confess that I haven't done a standard to enterprise upgrade on SP2 for a while. Removing the registry keys is the first thing I would do, as all that is happening is that those keys are being read to see what the entry says. Remove them and then cycle the server. If the upgrade didn't occur properly then without the keys the store will simply fail to mount. Put them back in and it will.
Does ESM report Enterprise Edition?

Simon.
0
 
LVL 4

Expert Comment

by:upandrun3
ID: 25050923
After I upgraded to Enterprise and then attempted to install Service Pack 2 I got a message. It said that a previous version of Intelligent Message Filter is already installed and needs to be removed. Here is what I did to fix that.

Manual Removal of IMF v1 or v2

   1. Stop all Exchange services, including the Information Store, System Attendant, SMTP, services, plus any Exchange antivirus applications.
   2. Rename the folder "MSCFV1" or "MSCFV2" in C:\Program Files\Exchsrvr\bin
   3. Rename the file C:\Program Files\Exchsrvr\bin\ContentFilter.dll file
   4. Open Regedit and browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange key.
   5. Export a copy of that key for backup purposes.
   6. Delete the "ControlFilterVersion" subkey from the registry.
   7. Restart the server.
   8. Install/Reinstall Exchange 2003 SP2.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article explains how to install and use the NTBackup utility that comes with Windows Server.
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question