Microsoft Windows NT 4.0 Guide Manual de usuario descargar pdf (Pagina 128)

Microsoft

Windows Server

™

2003 White Paper

Windows NT 4.0 Server Upgrade Guide 123

Exchange 2000 reaches the end of its life cycle at the end of 2005. Technology aside, by

upgrading to Exchange 2000 at the end of 2003, only two years remain in the Exchange 2000 life

cycle. Given the fact that Exchange 5.5 is nearing the end of its life cycle, companies still running

Exchange 5.5 face a decision about the next version. A strong case can be made for Exchange

2003 based on this single factor. Keep in mind that if an organization decides to upgrade to

Windows Server 2003, Exchange 2003 becomes the default choice, because neither Exchange

5.5 nor Exchange 2000 run on Windows Server 2003. When the next version of Exchange

becomes available, time should be spent planning an upgrade. With adequate planning, most of

the upgrade should have very little impact on the current users of the system.

Many of the improvements in Exchange 2003 change the way users of Outlook 2003 work.

Outlook 2003 is the current preferred client for accessing an electronic mailbox in Exchange 2003.

One of the goals of Exchange 2003 is to present users with a common look when connecting to e-

mail either locally while in the office or from a remote location. Enhancements to remote access

features in Exchange 2003 help improve user productivity, an important consideration given the

increasing number of users working from home either after hours or as telecommuters.

By skipping Exchange 2000 in favor of Exchange 2003, an organization can use Exchange 5.5 to

the end of its life cycle. It is unrealistic nowadays to keep up with the latest versions of all

information technology software. Costs, user downtime, upgrade resources, and education are a

few of the many considerations facing organizations, influencing them to bypass new versions of

software in favor of currently stable systems. Eventually, business-driven features, time, and

product life cycles become reason enough for organizations to upgrade to newer software

releases. By waiting for Exchange 2003, organizations running Exchange 5.5 have allowed

Exchange to mature and thus provide an even greater set of features and better reliability.

Stability and Cost Factors

Many organizations decided to stay on Exchange 5.5 because of its stability and the cost to

upgrade to Exchange 2000. In many instances, businesses were unable to provide a compelling

reason to upgrade to Exchange 2000 even with its better compatibility with Active Directory.

Microsoft understands this issue and has spent a great deal of development time engineering

tools to help companies upgrade to Exchange 2003 from both Exchange 5.5 and Exchange 2000.

These tools help companies to engineer a smooth upgrade to Exchange 2003.

The META Group, a provider of information technology research, advisory services, and strategic

consulting, recommends that “organizations with current migration plans scheduled for completion

by YE03 upgrade to Exchange 2000. Those companies planning for a 2H03 migration, with

completion due in 2004, should wait for Titanium, thereby avoiding a dual-hop migration.”

META Group states that an upgrade project undertaken in late 2003 should include an upgrade to

Exchange 2003, skipping Exchange 2000. To take this one step further, organizations with no

urgent need to upgrade to Exchange 2000 should just wait until Exchange 2003 is available for

production. By waiting for Exchange 2003, companies still running Exchange 5.5 can use the time

to plan for Exchange 2003 and to test the product in a lab environment. This planning should also

allow plenty of time for administrator training. Such a plan encompasses all the ingredients of a

successful upgrade.

1 2 ... 123 124 125 126 127 128 129 130 131 132 133 ... 154 155

Comentarios a estos manuales

Sin comentarios

Microsoft Windows NT 4.0 Guide Manual de usuario Pagina 128

Comentarios a estos manuales

Relacionado con productos y manuales para Servidores Microsoft Windows NT 4.0 Guide