To test these behaviors, you'll have to prepare several clean testing scenarios,
making sure that you can back up your systems to pristine status after each test cycle.
This calls for a lot of configuration work that, fortunately, can be lessened using
tools such as Ghost from Symantec. Similarly, Rational's TestFoundation for Windows
2000 can take snapshots of your Windows registry and file system before and after
installing an application, automatically documenting changes and compliance problems.
Migrating applications to a new platform can be such a tedious project that, in
many cases, the effort involved convinces IT departments not to migrate at all. But
Windows 2000 will ship with many excellent features -- with the promise of much more to
come -- that could, in the end, make your system easier to program and less expensive
1. Take an inventory of your applications. Document relationships among modules and
group your applications by OS and programming language.
2. Analyze Microsoft's application specifications for Windows 2000.
3. Define, according to the time and resources available, a minimum set of
requirements for the migration.
4. Analyze each application and define Windows 2000 compliance actions. Estimate
the time and resources required for conversion and testing.
5. Prepare test bed and start the testing cycle. Revise deployment documentation
after each cycle.