Microsoft Windows NT 4.0 Guide Instrukcja Użytkownika Pobierz pdf (Strona 71)

Microsoft

Windows Server

™

2003 White Paper

Windows NT 4.0 Server Upgrade Guide 66

For this scenario, suppose HGFPROPERTIES has an Exchange 5.5 Standard Edition server with

a 15.5 GB information store. This version of Exchange has a 16-GB limit on the information store.

If HGFPROPERTIES wants to upgrade their server to Exchange 2000 Enterprise with a larger

support information store, they must install Active Directory.

Server Upgrade Order

In this example, HGF Properties has decided to upgrade as many member servers as possible

before upgrading the domain controllers. The next question is what servers to upgrade in what

order. Some factors in this decision include:

• Services running on the various servers. How will the upgrade of a computer affect the

services running on that computer? For example, after the domain is upgraded to Active

Directory, DHCP servers need to be authorized before they give out addresses.

• Number of users affected by upgrading a particular server. Is there a server used by only a

handful of users? If so, this may be a good candidate to upgrade before a server that affects the

entire organization.

• Application’s dependency on Active Directory or other applications. Is there a particular

application being written or purchased that requires Active Directory? Are there any servers that

may need to be upgraded together because of their dependencies on one another?

• Server hardware. Can the server hardware support Windows Server 2003? Most Windows NT

4.0 servers have 4 GB or smaller boot partitions. Is there enough space on this drive to support

Windows Server 2003? Is the processor fast enough to do the job?

It is decided that all file and print servers will be upgraded first. That way, the company’s

administrators can start by upgrading computers that won’t affect too many other functions. One

of the main concerns during the upgrade is the print drivers. Research must be done to ensure

the printers will work with the new operating system and that all clients can still access the printers

after the upgrade. This task could be tested in a lab environment before the upgrade takes place.

Also, remember that IRVFILE must be upgraded first to SP 5.0 before being upgraded to the new

operating system.

The plan reveals that HGFSQLSERVER2 and HGFWEB essentially replace the functionality of

HGFSQLSERVER, the SQL Server 6.5 database for an internal custom application. Because the

migration to a new custom application is a process that will happen in the near future, it is decided

that HGFSQLSERVER will not be upgraded. In fact, the hardware is out-of-date as well, so it is

decided that the server will be retired after the application is upgraded in the next month or so.

HGFEXCHANGE poses a problem. If it is upgraded to Windows Server 2003, Exchange 5.5 will

not work. The information store will fail to start after the upgrade. If Exchange 5.5 is upgraded to

Exchange 2000 first, and then the server is upgraded to Windows Server 2003, the same thing

will happen. Neither Exchange 5.5 nor Exchange 2000 is supported under Windows Server 2003.

At the time this guide was written, Exchange 2003 had not yet been released, so the server must

keep Windows NT 4.0 or be upgraded to Windows 2000. If the computer is upgraded to Windows

2000, the Exchange server can be upgraded to Exchange 2000 as well. HGF Properties has

decided to take a different approach. It has been decided that a new server will be purchased to

act as the new mail server running Exchange 2000 and Windows 2000. Later, this server will be

1 2 ... 66 67 68 69 70 71 72 73 74 75 76 ... 154 155

Komentarze do niniejszej Instrukcji

Brak uwag

Microsoft Windows NT 4.0 Guide Instrukcja Użytkownika Strona 71

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Serwery Microsoft Windows NT 4.0 Guide