Migrating to a Windows Server 2003 from NT is a demanding process

If you intend to migrate to Windows Server 2003 (as .NET Server has recently been renamed), you'd better start planning now. This is especially true for companies that have yet to t migrate to a W2K Server., Here are some pointers for simplifying the process, as well as some possible pitfalls to avoid.

As with all migrations, but especially so with server migrations, the motto should be: festina lente (hurry slowly). The better your planning, and the more thorough your testing, the smoother your migration is going to be. Also, a wait-and-see approach is always prudent, otherwise you might end up as an interesting case study as to what can go wrong.

Identify goals
The first, and arguably the most important, step on the migration road is to clearly identify your goals. Ask yourself: For what business and technical reasons do we want to migrate?Allocating sufficient time to answering this question will pay rich dividends.

Get everyone on track
It is also important to make the goal-setting process a collaborative effort among the IT department, senior management, and all of the other departments in your company. As the facilitators and guides that must make it all happen, the IT migration team needs to be fully informed of everyone's needs and well prepared to answer any questions, including questions about , what is feasible, and what the best technical options and solutions are.

To be prepared for these discussions, you should know the differences between the four different flavors of Windows Server 2003. Also, be prepared to answer the inevitable questions and concerns about cost. Remember to take into account training costs-they can be quite high depending on your team and the extent of your migration (you might also be migrating from Exchange Server 5.5 to 2000 and/or from Proxy Server 2 to ISA Server, and so on) And carefully consider whether you'll need to make use of professional services, which isa distinct possibility, especially considering the big jump from NT to Windows Server 2003. You might also want to use some of the excellent third-party migration tools that are available.

Consider cost implications
Hardware requirements can come at a hefty price, especially if you are migrating to a native Windows Server 2003 environment and all clients are to be upgraded to XP. So check the Hardware Compatibility List (HCL). Determining the compatibility with existing applications used in the company is also very important.You don't want to discover that some crucial applications don't know longer work after the migration. If there are to be application upgrades or even a migration to different applications, you need to plan for it upfront.

Another issue involving considerable cost implications is the licensing mode. Make sure you know what your licensing options are and what's best for your company. Also, you'll have to decide whether you're migrating to mixed or native (pure) mode. Your present infrastructure and needs will determine your choice.

Migrating to Windows Server 2003 from NT is a demanding process

Technical research
After you've gathered information on needs and costs, the next step in your deployment planning is to researchthe details of the migration. To make it all happen, you'll also need up-to-date and detailed information about your existing network infrastructure.

Gather and start studying the technical documents from the .NET Server Web site. Also, be sure to check out the indispensable deployment guide (although it is still incomplete at the time of this writing). The Windows 2000 Server Resource Kit will also be a great help in the planning and research phases.

Learn about the different methods of automating and customizing installations (disk imaging techniques; remote installation service; network installation points). Choosing the right one for your setup and circumstances can speed up the process considerably. Microsoft's Deployment Guide includes a section on the topic, including compatibility testing, design information for unattended installations, image-based installations, and RIS installations.

Windows Server 2003 boasts a lot of new security features, so start reviewing your security setup now and plan to take advantage of the enhancements. Also, determine what it will mean in terms of the upgrade.

Active Directory
If you're new to Active Directory (as you're likely to be if you're running on NT), research and learn all you can about it. Download Microsoft's white papers on the subject.

In Windows Server 2003 Active Directory is more powerful than in the W2K Server. Once you know what it's all about and how it works, prepare your domain structure for AD. If you have a complex domain structure, there's a lot of planning to be done.

A tip: If at all possible, standardize your network on TCP/IP.

Other issues
Don't forget the critical importance of share, file, and print access control lists (and the accompanying permissions issues), or productivity might grind to a halt after migration.

If you're not migrating applications like Exchange Server as part of your migration to Windows Server 2003—and especially if you're planning to run Windows Server 2003 in native mode—make sure which services you'll have to enable on your servers to support these legacy apps. Exchange 5.5, for example, requires WINS to run.

If you're planning on running your network in mixed mode (having Windows Server 2003 assign a domain controller to act as a PDC for NT BDCs), be aware of the limitations and possible pitfalls. For example, you can’t use all the advanced features the new operating system has to offer. Remember that only one Windows Server 2003 domain controller can act as a PDC for NT BDCs, and the first domain controller you install will perform this role.

When deciding which features of the new operating system to implement, don't be in too much of a hurry--get it on its feet before you (try to) make it dance. It will reduce the complexity of your task and make troubleshooting somewhat simpler.

Plan your test bed network properly as well. For realistic and thorough testing, your test bed should properly reflect your network, including things like a router and firewall, some workstations with the different operating systems and applications you're using, and a couple of servers. Once you think everything is working okay, bring in some users for the final testing, especially those using critical apps. If all goes well, you're ready for the big rollout.

Other helpful links:
 • Top 10 Benefits of Windows .NET Server 2003
 • System Requirements