It’s been over seven months since the release of Exchange 2000 SP2 and in that time Exchange Admins have clamored for fixes to fix the fixes in SP2. It’s no secret that SP2 was not a favorite install of many Exchange Admins, while many others installed it and have had no problems. Fortunately, I am among the group that has had no problems with SP2, but then again each situation is different depending on which of the many ways you have deployed and configured Exchange 2000 Server. Let’s take a quick look at what’s going in SP3. In a later article I will take a more detailed look into specifics, but for right now I am just going to cover the highlights and basic information. Oh yeah, before I get any further, you can get Exchange 2000 SP3 here.
SP3 Upgrade Concerns
As you might expect, there are some concerns associated with upgrading Exchange 2000 Servers to SP3. The most pertinent concerns are:
· Windows 2000 SP2 or SP3 (not yet released as of this writing) must be installed on the server that you are installing Exchange 2000 SP3.
· You can run Exchange 2000 SP3 on Windows 2000 SP3 servers in Windows .NET Server domains with Windows .NET Server domain controllers.
· You cannot run Exchange 2000 SP3 on servers running Windows .NET Server. This will require the next version of Exchange Server, code-named Titanium.
· In order to deploy Exchange 2000 SP3, you will require Exchange Full Administrator permissions at the Organization level or the Administrative Group level.
· In order to deploy Exchange 2000 SP3 on a clustered solution, you will require Exchange Full Administrator permissions at the Organization level.
· In order to deploy Exchange 2000 SP3 on a server acting as an Exchange Key Management server, you will require Enterprise Administrator and Exchange Full Administrator permissions at the Organization level.
· In order to deploy Exchange 2000 SP3 on a computer that has only the Exchange System Manager installed, you will require only Local Machine Administrator permissions.
Post SP2 Hot Fixes
From the Microsoft Web site, you can see that the list of Post SP2 Hot Fixes for Exchange 2000 Server is quite extensive. It’s no where near as long as the list of fixes for something like Windows 2000 or Windows XP, but it’s still pretty long in its own right. This list is as
You should be aware of the following issues that are specific to installing Exchange 2000 SP3:
· If you have an Outlook Web Access implementation setup using a Front-End / Back-End solution, you must upgrade all Front-End servers before upgrading any of the Back-End servers. OWA clients download scripts from the Front-End servers that they connect to; these scripts are not compatible with any Back-End servers that running an older Service Pack, such as in the case where you mistakenly upgraded your Back-End servers to SP3 while leaving your Front-End servers at SP2. If you are running multiple Front-End servers, you do not have to upgrade all of them at once but you must upgrade all of them before upgrading any of the Back-End servers.
· Installation of Exchange 2000 SP3 does not automatically update the help files for OWA clients. You will need to update the files manually or install them by running an .MSI file or language pack for each language that is used by your OWA clients. You must remove any existing SP1 or SP2 OWA help files from the Add/Remove Programs applet before installing the SP3 help files. To update your OWA help files, click Outlook Web Access Help Files from the Microsoft Exchange SP3 main setup screen. Complete the installation process for each language required by your OWA clients. Alternatively, you can access the help files in the x:\setup\i386\exchange\exchweb directory, where x is the location of your SP3 files.
· After an upgrade from Exchange 2000 or Exchange 2000 SP1 to Exchange 2000 SP3, the Exchange MTA Stacks service and Exchange Information Store (IS) service will not start if you do not meet the following requirements. Pay attention to this as this is one of those gotchas you can prevent with careful pre-planning!
o At least one available global catalog server resides in a domain where you ran the DomainPrep utility. This utility creates the groups and permissions necessary for servers running Exchange to read and modify user attributes.
o A Recipient Update Service exists in that same domain.
If you are using a global catalog server in a different domain, then you must run DomainPrep in that domain, create a new Recipient Update Service for that domain and then restart the newly upgrade Exchange 2000 SP3 server. Only by doing this will you get Directory Access to run properly.
That’s All for Now
Well, that’s all I have to share for now about Exchange 2000 SP3. As promised, I will revisit this issue once I have had adequate time to work with SP3. Have you deployed SP3 and have something to share? Please do not hesitate to email me with your comments or concerns. Until next time…