|
|
 Microsoft
Exchange 2000 Service Pack 3 by
Michele Deo
There are some new caveats that you need to understand
before approaching MS Exchange 2000 Service Pack 3. Some are quite
serious, where are others I'm providing some hints on what to watch for and
understand.
-
Be aware that when
installing MS Exchange 2000 Service Pack 3, you will not be able to
uninstall it easily if something goes wrong. The only way to get rid
of the Service Pack is to totally rebuild the MS Exchange system back up to
MS Exchange 2000 Service Pack 2. I haven't gotten a true answer as to
why Microsoft did it this way, but I believe it has something to do with
make MS Exchange 2000 now .Net compatible. Microsoft has posted an
Exchange 2000 SP3 Deployment Guide that I recommend you download and
review to understand the issues with installing this Service Pack entail.
Key areas of concern and what to watch
for in upgrading to Service Pack 3 for Exchange 2000 -
-
Upgrade path should follow what
you used for Service Pack 2. If you are in an "mixed" mode
configuration (Exchange 5.5 exists with Exchange 2000), you need to do the
ADC (Active Director Connector) Servers first, then the SRS (Site
Replication Servers) and then the rest of the servers.
-
A new local.map and remote.map are
provided with this Service Pack. When upgrading the ADC, the new map
files will overwrite the existing files, which is not an issue if you
haven't customized them for your particular configuration. If you
have, or don't know, it's advisable that you export the
msExchServer1SchemaMap and msExchServer2SchemaMap using the LDP tool.
-
If you are utilizing one-way
connection agreements and want to switch them to 2-way connection
agreements, don't do it until after you have upgraded all of your ADC
servers to Service Pack 3. There is a significant fix in this service
pack that if you were to move your CA's to two way prior to SP3, that you
could potentially lock your Exchange 5.5 users out of their mailboxes.
Q317861 on the Microsoft website goes into more detail on this topic.
-
Upgrading the ADC server will
require that the Connection Agreements be re-created. This means that
during the upgrade, replication activity between the two infrastructures
(Exchange 5.5 and Exchange 2000) will be disrupted. Make sure that
your Default ADC policy doesn't get duplicated, doesn't get disconnected
from the ConfigCA's , that the RUS (Recipient Update Service) is not
running, and that no Add, change, and deletions are going on during the
upgrade.
-
RUS (Recipient Update Service)
best practice is to install one at the Enterprise level and one at the
Domain level. The only time that additional Domain level Recipient
Update services are needed is when the potential of slow network bandwidth
between domains exist.
|
