CCNA Exam Choosing a Tier Model
Now, with Windows Server 2008, you’ll face the lesser challenging of moving objects between Active Directory?capable versions of servers that aren?t so up-to-date or moving objects between overall designs that perhaps aren?t as evolved as they could be. To facilitate this transformation, you can take advantage of a very powerful administrative tool that must be installed by hand: the Active Directory Migration Tool (ADMT).
The primary tool that we use to migrate objects from one domain to another is MCITP Certification the Active Directory Migration Tool. As of the writing of this book, the Active Directory Migration Tool version most widely used at the enterprise level is ADMT 3.0. This is the version that is used with Windows Server 2003 and mostly facilitated transfers between Windows 2000, Windows NT, and Windows Server 2003.
With the release of Windows Server 2008, Microsoft introduced the ADMT version 3.1. This powerful, new version of the previous ADMT tool is designed from the ground up to support Windows Server 2008 and all previous versions of Windows Server. Because of the inherent power of this tool and how heavily it will to be used in the enterprise environment, it’s important for us as enterprise administrators to understand the capabilities of this tool. Accordingly, in this chapter we?re going to spend some time in our test exercises going over the various methods used to migrate accounts between domains, forests, and servers. Additionally, we?ll cover a few real-world scenarios where you will need to use the ADMT to facilitate an easy transition to Windows Server 2008.
THere’s a big difference between whether you can do something and whether you should do something. We all know that Windows Server 2008 is a powerful, new, and fancy operat- ing system with numerous capabilities. From the perspective of an administrator, you?d like to incorporate as many features as possible into your design. But from the perspective of a business, migrating any machine from one platform to another means two things: money and liability.
We IT professionals might like to ignore such details, but migrating to MCTS Windows 7 Configuration costs a lot of money. A business has to worry about the costs of Windows Server, which include the labor costs associated with installing the software and the cost of any additional hardware to support the upgrade with the appropriate amounts of RAM, CPU power, and other associated functionality. More often than not, this means purchasing new computers. A business must also be concerned with liability issues. Gary Olsen, a software engineer with Hewlett-Packard, once commented in an article he wrote pertaining to migration with Windows Server 2008 that a customer was potentially losing up to $1 million per hour because of incompatibility between the version of SQL Server currently in use in the office and an upgrade to another application.
Processing your request, Please wait....
