PSS ID Number: Q272082
Article last modified on 11-30-2000
:
======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Exchange 2000 Server
-------------------------------------------------------------------------------
IMPORTANT: Before you upgrade Microsoft Exchange 2000 Server Release Candidate 2 (RC2) to the Release to Manufacturing (RTM) version, Microsoft strongly recommends that you consider the advantages and disadvantages of doing so. Support is provided for customers who previewed Exchange 2000 Server RC2 and who want to upgrade to the RTM version (build 4417.5). However, Microsoft cannot guarantee that issues that result from an incorrect upgrade from the RC2 Beta version to the released version of the product can be resolved. Microsoft recommends that you install the RTM version of Exchange 2000 Server on a clean computer to minimize possible issues that are associated with upgrading a Beta version.
Upgrading versions of Exchange 2000 Server earlier than RC2 is unsupported. Only installations that started with RC2 can be reliably upgraded to the RTM version of the product. Additionally, you can upgrade from the evaluation edition of Exchange 2000 Enterprise Edition Server to the fully purchased Enterprise Edition. However, because of Exchange 2000 Enterprise Edition support for databases larger than 16 gigabytes (GB), you can only upgrade from the Exchange 2000 Enterprise Server Evaluation Edition to Exchange 2000 Enterprise Server. Upgrading from Enterprise Server Evaluation Edition to the fully-purchased, standard Exchange 2000 Server is not supported by Exchange 2000 Setup.
SUMMARY
=======
This article outlines the procedures for upgrading from Exchange 2000 Release
Candidate 2 (RC2) to Exchange 2000 Release to Manufacturing (RTM) including
issues concerning a character restriction imposed on the Organization,
Administrative Group, and Site display names after RC2 was released. This
article covers the upgrade procedures for non-clustered servers, clustered
servers, and conference servers, and is intended for experienced Microsoft
Exchange Server system administrators.
This article assumes practical experience with:
- The Microsoft Exchange Server Administrator program
- Core Exchange Server functionality, connectivity, and terminology
- Microsoft Windows NT® networking and security functionality
- Microsoft Active Directory concepts and tools
The Release Notes on the Exchange 2000 RTM CD-ROM contain information that might
be important for your installation. For example, Exchange 2000 requires
Microsoft Windows 2000 with Service Pack 1 (SP1), which you can download from
the following Microsoft Web site:
http://www.microsoft.com/windows2000/downloads/recommended/sp1/default.asp
For additional information about how to remove Exchange 2000 Server from a
computer so that you can perform a new installation of the RTM version, instead
of upgrading to the RTM version, click the article number below to view the
article in the Microsoft Knowledge Base:
Q260378 XADM: How to Manually Remove an Exchange 2000 Installation
MORE INFORMATION
================
Upgrade Procedure for Exchange 2000 (Non-Clustered Server)
----------------------------------------------------------
1. If you currently use the ADC, upgrade your ADC servers by closing down all
management consoles and Microsoft Management Console (MMC) snap-ins. Then run
the ADC Setup program, and click the Reinstall option. For example:
<drive>:\adc\i386\setup
where <drive> is the letter of your CD-ROM drive.
2. Use the root Administrator account (which is a part of the Enterprise
Administrators and Schema Administrators groups). Log on to the domain where
your schema Flexible Single Master Operation (FSMO) role exists (normally the
root domain), and then run the Exchange 2000 Setup program with the
/forestprep switch. For example:
<drive>:\setup\i386\setup /forestprep
It is preferable, but not required, to run ForestPrep on the Schema FSMO role
owner.
For additional information about locating the schema master, click the article
number below to view the article in the Microsoft Knowledge Base:
Q234790 How to Find FSMO Role Holders (Servers)
3. Wait for the new schema changes to be replicated throughout your forest. This
can take an extended period of time depending on the complexity of your
Active Directory deployment. Because of the schema updates made during
ForestPrep, your global catalogs can also be rebuilt at this time.
4. In each Active Directory domain, log on as a Domain Administrator, and then
run the Exchange 2000 Setup program with the /domainprep switch. For example:
<drive>:\setup\i386\setup /domainprep
5. Wait for the DomainPrep changes to be replicated throughout your domain.
6. On the Exchange 2000 server to be upgraded, quit all management consoles and
MMC snap-ins. If you do not do this, it creates file contention during the
upgrade. Additionally, stop all Exchange services before you run Setup to
prevent timing issues during the upgrade.
7. Run the Exchange 2000 Setup program. Click the Reinstall option when you are
presented with the component page, and allow the upgrade to finish.
If you receive a file contention warning during the upgrade process, click the
Continue button. This replaces the file with the updated version. Setup
prompts you to restart the server at the end of the upgrade process, which
allows the Exchange installation access to the updated files.
8. After the first server has been upgraded to the released product, continue to
upgrade all the other RC2 servers one at a time.
9. After all servers have been upgraded to the released product, on the Start
menu, point to Programs, point to Microsoft Exchange, and then click Exchange
System Manager.
10. Double-click Recipients, and then click Recipient Update Services.
11. In the right pane is a list of all Recipient Update Services. Right-click
each one, and then click to select the Rebuild check box. Depending upon the
number of objects in your Active Directory, this process may take an
extended period of time to finish. Until the rebuild is complete, clients
cannot access their mailboxes, and they may receive an error message when
they attempt to log on.
Upgrade Procedure for Exchange 2000 Clusters
--------------------------------------------
1. Complete Steps 1 through 5 from the "Upgrade Procedure for Exchange 2000
Servers (non-clustered server)" section.
2. Individually move all Exchange virtual servers to node 2.
3. Quit all Microsoft Management Consoles (MMC) and snap-ins on node 1.
4. Upgrade node 1 by running the Exchange 2000 Setup program, click Reinstall,
and then allow the upgrade to finish.
5. Individually move all Exchange virtual servers to node 1.
6. Quit all MMC consoles and snap-ins on node 2.
7. Upgrade node 2 by running the Exchange 2000 Setup program, click Reinstall,
and then allow the upgrade to finish.
8. Move the Exchange virtual servers to their preferred nodes.
9. Continue steps 8 through 9 from the "Upgrade Procedure for Exchange 2000
Servers (non-clustered server)" section.
Upgrade Procedure for Exchange Conferencing Server
--------------------------------------------------
1. Insert the Exchange Conferencing Server CD-ROM in the CD-ROM drive, and share
it using Windows Explorer. Map a drive to this share.
2. At a command-prompt, change directory to the mapped drive, and then change
directory to the Conferencing\Setup\I386 folder.
3. Type "msiexec.exe /fvemus" (without the quotation marks), and wait for the
upgrade to finish.
4. You may be asked to restart the server at the end of the upgrade; it is not
necessary to do so.
5. Disconnect the mapped drive, and stop sharing the contents of the CD-ROM.
NOTE: You must not attempt to upgrade Exchange Conferencing Server directly from
the CD-ROM because the upgrade may not complete properly. Additionally, you must
not attempt to upgrade by using the Setup program supplied on the Exchange
Conferencing Server CD-ROM.
If you encounter issues after Setup, use Explorer or Filever.exe (available on
the Exchange 2000 CD-ROM) to ensure that the contents of your Program
Files\Microsoft Exchange Conferencing Server folder contains version 4417.x
binaries.
Procedure for Removing Invalid Characters
-----------------------------------------
You only need to follow this procedure if you have installed Exchange 2000 RC2
using characters other than those listed below for the Organization,
Administrative Group, or Site display names.
Valid characters for Organization and Administrative Group names in Exchange
2000:
- A - Z
- a - z
- 0 - 9
- Space
- Hyphen/Dash
Additionally, if you have joined a Microsoft Exchange Server 5.5 Organization
that has characters other than those listed in its Organization or Site names,
you must also remove these invalid characters from the display names of these
objects before you begin the upgrade.
This procedure relies on the use of the Active Directory Services Interface
(ADSI) Edit tool. This is included with the Microsoft Windows 2000 Resource Kit.
After you have installed the Resource Kit, register the tool. To register the
tool:
1. On the Start menu, click Run.
2. In the Open box, type "regsvr32 adsiedit.dll" (without the quotation marks),
and then click OK.
WARNING: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP
version 3 client and incorrectly modify the attributes of Active Directory
objects, you can cause serious problems that may require you to reinstall
Microsoft Windows 2000 Server and/or Microsoft Exchange 2000 Server. Microsoft
cannot guarantee that problems resulting from the incorrect modification of
Active Directory object attributes can be solved. Modify these attributes at
your own risk.
To use the ADSI Edit tool:
1. On the Start menu, click Run.
2. In the Open box, type "mmc" (without the quotation marks), and then click OK.
3. On the Console menu, click Add/Remove Snap-in.
4. Click Add.
5. In the Add Standalone Snap-in box, click to select ADSI Edit Tool, and then
click Add.
6. Click Close, and then click OK.
7. Right-click ADSI Edit, and then click "Connect to".
8. When the Connection dialog box appears, change the Naming Context to
"Configuration container" (without the quotation marks).
For more information on ADSI Edit, refer to the Windows 2000 Resource Kit
documentation.
Steps to Follow If You Have Invalid Characters in Your Organization Name:
If you have Exchange Server 5.5 computers in your Organization:
1. Start the Exchange Server 5.5 Administrator program, log on to an Exchange
Server 5.5 computer in each Exchange site in the Organization, and then
change the display name of the Organization object so that it only includes
valid characters. There is no requirement to change the directory name of the
object.
2. Follow the next procedure, "If you have Exchange 2000 servers in your
Organization".
If you have Exchange 2000 servers in your Organization:
1. Shut down all Exchange and Microsoft Internet Information Service (IIS)
services on all Exchange 2000 servers in the Organization.
2. Start ADSI Edit, and connect to the configuration naming context of your
Active Directory.
3. Click Configuration, click Services, and then click Microsoft Exchange.
4. Right-click your Exchange Organization name, and then click Rename. Change
the name so that it only includes valid characters.
5. Right-click your Exchange Organization name, and then click Properties.
6. In the "Select which properties to view" box, click Both.
7. Edit the adminDisplayName attribute so that it matches the adjusted name from
step 4. Click Set, and then click OK.
8. ADSI Edit by closing the MMC console program.
9. Wait for Active Directory replication to replicate this new value throughout
the forest.
10. Restart all Exchange 2000 servers, and verify that all Exchange services
start correctly.
11. Verify mail flow between all of your Exchange 2000 servers.
Steps to Follow If You Have Invalid Characters in Your Administrative Group Names:
If you have "pure" Exchange Server 5.5 Sites in your Organization that contain
invalid characters in the Site display name, these sites may show up as
"ghosted" objects in Exchange System Manager. Ghosted objects refers to the
black and white icons in Exchange System Manager that represent Exchange Server
5.5 sites that do not have any Exchange 2000 servers.
1. Start the Exchange Server 5.5 Administrator program, and log on to a server
in the site that contains the invalid characters.
2. Change the display name of the site so that it only includes valid
characters. There is no requirement to change the directory name of the
object.
3. Wait for Exchange Server 5.5 directory replication to replicate this new
value throughout the Organization.
4. Start ADSI Edit, and connect to the configuration naming context of your
Active Directory.
5. Click Configuration, click Services, click Microsoft Exchange, click
<org>, and then click Administrative Groups. The Exchange 2000
administrative groups as well as the objects representing the Exchange Server
5.5 sites are displayed in the right pane.
6. Right-click the names of the sites that you changed at the beginning of this
procedure, and then click Delete.
7. Quit ADSI Edit by closing the MMC console program.
8. Wait for Active Directory replication to replicate the deletion of these
objects throughout the forest.
9. Use the Active Directory Connector management snap-in to locate all Config
CA_* Connection Agreements. Right-click each Configuration Connection
Agreement, and then click Properties. Click the Schedule tab, and then click
to select the "Replicate the entire directory the next time the agreement is
run" check box. Click OK.
10. Right-click each Config CA_* Connection Agreement, and then click Replicate
Now.
11. Wait for the ADC to replicate the new Exchange Server 5.5 Site names into
Active Directory. This creates new "ghosted" Administrative Group objects.
12. Wait for Active Directory replication to replicate the new objects around
the forest.
Please note that Exchange 2000 clients may receive non-delivery report (NDR)
messages if they attempt to send messages to Exchange Server 5.5 mailboxes
before this process is finished.
If you have mixed Exchange Server 5.5 and Exchange 2000 Administrative Groups in
your Organization that contain invalid characters in the display name:
1. Start the Exchange Server 5.5 Administrator program, and log on to a server
in the sites that contain the invalid characters
2. Change the display name of the sites so that it only includes valid
characters. There is no requirement to change the directory name of the
object.
3. Wait for Exchange Server 5.5 directory replication to replicate this new
value throughout the Organization.
4. Shut down all Exchange and IIS services on all Exchange 2000 servers in the
Organization.
5. Start ADSI Edit, and connect to the configuration naming context of your
Active Directory.
6. Click Configuration, click Services, click Microsoft Exchange, click
<org>, and then click Administrative Groups. The Exchange 2000
administrative groups as well as the objects representing any Exchange Server
5.5 sites displayed in the right pane.
7. Right-click the mixed Exchange Server 5.5 and Exchange 2000 Administrative
Group name, and then click Rename. Set this to the new display name used in
step 2.
8. Right-click on the mixed Exchange Server 5.5 and Exchange 2000 Administrative
Group name, and then click Properties.
9. In the "Select which properties to view" box, click Both.
10. Change the displayName attribute to correlate with the new name chosen in
step 2 of this procedure. Remember to click Set after you change the Edit
box, and before you click OK.
11. Quit ADSI Edit by closing the MMC console program.
12. Wait for Active Directory replication to replicate these new values
throughout the forest.
13. Restart all Exchange 2000 servers, and then verify that all Exchange
services start correctly.
14. Verify mail flow between all of your Exchange 2000 servers.
If you have "pure" Exchange 2000 Administrative Groups in your Organization that
contain invalid characters in the display name:
1. Shut down all Exchange and IIS services on all Exchange 2000 servers in the
Organization.
2. Start ADSI Edit, and connect to the configuration naming context of your
Active Directory.
3. Click Configuration, click Services, click Microsoft Exchange, click
<org>, and then click Administrative Groups. The Exchange 2000
administrative groups as well as the objects representing any Exchange Server
5.5 sites displayed in the right pane.
4. Right-click the Exchange 2000 Administrative Group name, and then click
Rename. Set this to the new name.
5. Right-click the Exchange 2000 Administrative Group name, and then click
Properties.
6. In the "Select which properties to view" box, click Both.
7. Change the displayName attribute to correlate with the new name. Remember to
click Set after you change the Edit box, and before you click OK.
8. Wait for Active Directory replication to replicate these new values
throughout the forest.
9. Restart all Exchange 2000 servers, and verify that all Exchange services
start correctly.
10. Verify mail flow between all of your Exchange 2000 servers.
Steps to Follow if Exchange 2000 has Expired.:
1. Decide to do one of the following actions:
- Restore from backup.
-or-
- Leave databases in place.
-or-
- Rename the database directories.
NOTE: If you leave the databases in place, they may not get over written.
2. Use the RTM version of Exchange 2000 to run the setup.exe/disasterrecovery
switch
3. Disaster Recovery may be listed for each component that is currently
installed on the server. If Disaster Recovery is not listed, click on the
first component and write down the error message. Be ready to send your Setup
logs to PSS if you need further assistance.
4. A prompt appears:
Please use the Exchange Administration Snap-In to ensure you have a valid
Exchange Server Object for this server for which you are running setup in
recovery mode.
After you check for the object, click OK.
5. Disaster Recovery begins to copy the files for each component.
6. A prompt appears:
After Setup has completed, please restore your databases from backup and then
restart your computer.
Click OK, and then Post Installation starts
7. When Post Installation is done, click Finish.
8. You may Rename the directories or restore from backup.
9. Restart the server
10. Go into the Exchange System Manager, as the databases may be dismounted.
Right-click the Databases and choose Mount.
11. Right-click on the databases to get Properties on the database.
12. Go to the Database tab, and then click to clear the check from the "Do not
mount the store at start-up" box
Additional query words: x2ksetupht x2kgentop x2ktranstop x2ksetuptop xmrp
======================================================================
Keywords :
Component : SRVRSetup
Version : :
Issue type : kbhowto
=============================================================================
Copyright Microsoft Corporation 2000.
PSS ID Number: Q276206
Article last modified on 11-15-2000
:
======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Exchange 2000 Server
- Microsoft Exchange 2000 Conference Server
-------------------------------------------------------------------------------
SUMMARY
=======
This article covers some of the most frequently asked questions about Exchange
2000 evaluation edition products.
MORE INFORMATION
================
General Product Questions
-------------------------
1. Q: What products can I evaluate for 120 days?
A: Microsoft Exchange 2000 Enterprise Server and Microsoft Exchange 2000
Conferencing Server.
2. Q: Where can the 120-day evaluation versions be downloaded from?
A: You can download the 120-day evaluation versions from the following
Microsoft Web site:
http://www.microsoft.com/exchange/productinfo/Eval.htm
3. Q: What is the Product Key for each evaluation product?
A: The Product Key field is prepopulated for evaluation products.
Exchange 2000 Server Standard Version Questions
-----------------------------------------------
1. Q: Is the standard version of Exchange 2000 Server available for evaluation?
A: No. Only Exchange 2000 Enterprise Server is available.
2. Q: Can I upgrade from the Release to Market (RTM) evaluation edition of
Exchange 2000 Enterprise Server to the RTM standard version of Exchange 2000
Server?
A: No. Currently there is not a downgrade path for the evaluation edition of
Exchange 2000 Enterprise Server to the RTM standard version of Exchange 2000
Server.
Exchange 2000 Enterprise Server Questions
-----------------------------------------
1. Q: Can I upgrade from the evaluation edition of Exchange 2000 Enterprise
Server to the RTM standard version of Exchange 2000 Server?
A: No. Currently there is not a downgrade path for the evaluation edition of
Exchange 2000 Enterprise Server to the RTM standard version of Exchange 2000
Server.
2. Q: What happens during setup when I upgrade from an RTM evaluation product to
a RTM full product?
A: A full setup is performed again, but Setup is optimized because all the
files and registry entries are already on the computer. Setup tries to copy
all the files again, but because the files on the hard disk are identical to
what is on the CD, the file copy is unnecessary. Setup still counts through
the percentage status, but Setup performs a very fast installation. Setup
makes some minor changes to the server, and then finishes.
3. Q: How can you tell if you are running an evaluation copy of Exchange 2000
Enterprise Server versus the full product?
A: The user interface (UI) does not indicate that you are running an
evaluation copy. The Exchange 2000 Setup log file displays an entry that is
similar to the following:
09/21/2000
[16:19:37] Setup configuration information:
[16:19:37] This is a(n) Enterprise version of Microsoft Exchange 2000
[16:19:37] This is an evaluation copy of Microsoft Exchange 2000; it expires
in 120 days
4. Q: How can you tell how many days remain until the evaluation copy of
Exchange 2000 Server expires?
A: The UI does not indicate how many days remain until the evaluation copy of
Exchange 2000 Server expires. View the Setup log file to determine when the
evaluation copy of Exchange 2000 Server was installed. (See the preceding
question.)
5. Q: What happens when the 120-day evaluation period expires on an RTM version
of Exchange 2000 Enterprise Server?
A: The information store shuts down and the following error message is logged
in the application event log:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 1182
Description: Thank you for your participation in the Microsoft Exchange Server
beta program. Your license to use this beta version of the Microsoft Exchange
Server software has expired. Contact Microsoft Corporation.
6. Q: Are the expired RTM evaluation version databases still usable?
A: Yes. You can still use the expired server by installing the full Exchange
2000 Enterprise Server product over the expired RTM evaluation version. You
cannot install the full Exchange 2000 Server standard version over the
evaluation Exchange 2000 Enterprise Server version.
For additional information, click the article number below to view the article in
the Microsoft Knowledge Base:
Q272082 XADM: How to Upgrade from Exchange 2000 RC2 to RTM
Exchange 2000 Conferencing Server Questions
-------------------------------------------
Q: Can I upgrade from the evaluation version of Exchange 2000 Conferencing Server
to the full version of Exchange 2000 Conferencing Server?
A: No. Currently there is not an upgrade path for Exchange 2000 Conferencing
Server from the evaluation version to the RTM version.
You can obtain more information about Exchange 2000 Server and Exchange 2000
Conferencing Server from the following Microsoft Web site:
http://www.microsoft.com/exchange
Additional query words: conference exchange 2000 eval evaluation
======================================================================
Keywords : kbfaq
Version : :
Hardware : x86
Issue type : kbinfo
Solution Type : kbpending
=============================================================================
Copyright Microsoft Corporation 2000.
De username van de oorspronkelijke plaatser van deze posting is bij Big Crash 3 eind mei 2001 verloren gegaan. Om toch de posting zelf terug te kunnen plaatsen is de user BC3 Victim in het leven geroepen
/u/750/crop566153961c02a_cropped.png?f=community)
:strip_icc():strip_exif()/u/12778/lotus.jpg?f=community)
</edit>
.....ongelooflijk 
