With the preparation and research completed and the
compatibility testing plan verified as needed, the actual testing can
begin. The testing process should be fairly anticlimactic at this point
because the process has been discussed at length, and it will be clear
what the testing goals are and which applications will be tested. Due
diligence in terms of vendor research should be complete, and now it is
just a matter of building the test server or servers and documenting the
results.
The testing process can yield
unforeseen results because the exact combination of hardware and
software might affect the performance of a key application; but far
better to have this occur in a nonproduction environment in which
failures won’t affect the organization’s ability to deliver its
services.
During the testing
process, valuable experience with the installation and upgrade process
will be gained and will contribute to the success of the production
migration. The migration team will be familiar with—or possibly experts
at—the installation and application migration processes when it counts,
and are more likely to avoid configuration mistakes and resolve
technical issues.
Allocating and
Configuring Hardware
Ideally,
the budget will be available to purchase the same server hardware and
related peripherals (such as tape drives, UPSs, mobile devices, and
applications) that will be used in the production migration. This is
preferable to using a server machine that has been sitting in a closet
for an undetermined period of time, which might respond differently than
the eventual hardware that will be used. Using old hardware can
actually generate more work in the long run and adds more variables to
an already complex process.
If the testing process is to
exactly mirror the production environment, this would be considered to
be a prototype phase, which is generally broader in scope than
compatibility testing, and requires additional hardware, software, and
time to complete. A prototype phase is recommended for more complex
networks in which the upgrade process is riskier and more involved and
in which the budget, time, and resources are available.
Don’t forget to
allocate a representative workstation for each desktop operating system
that is supported by the organization and a sample remote access system,
such as a typical laptop or mobile device that is used by the sales
force or traveling executive.
Allocating and
Configuring Windows Server 2008 R2
By this point, the software has
been ordered, allocated, downloaded, and set aside for easy access,
along with any notes taken or installation procedures downloaded in the
research phase. If some time has elapsed since the compatibility
research with the vendors, it is worth checking to see whether any new
patches have been released.
When configuring the
servers with the appropriate operating systems, the company standards
for configurations, based on industry best practices, should be adhered
to, if they have been documented. Standards can include the level of
hard drive redundancy, separation of the application files and data
files, naming conventions, roles of the servers, approved and tested
security updates, and security configurations.
Next, Windows Server 2008
R2 should be configured to also meet company standards and then for the
essential utilities that will protect the integrity of the data and the
operating system, which typically include the backup software,
antivirus software, and management utilities and applications. After
this base configuration is completed, it can be worth performing a
complete backup of the system or taking a snapshot of the server
configuration, using an application such as Ghost, in case the
subsequent testing is problematic and a rollback is necessary.
Loading the Remaining
Applications
With Windows Server
2008 R2 configured with the core operating system and essential
utilities, the value-added applications can be tested. Value-added
applications enhance the functionality of Windows and enable the users
to perform their jobs more efficiently and drive the business more
effectively. It’s helpful to provide a project plan calendar or schedule
to
the end users who will be assisting in the testing process at this point
so they know when their services will be needed.
As a basic guideline, first test the most
essential applications and the applications that were not identified
previously as being compatible. By tackling the applications that are
more likely to be problematic early on in the process, the testing
resources will be fresh and any flags can be raised to the stakeholders
while there is still time left in the testing process for remediation.
Thorough testing by the end
users is recommended, as is inclusion of the help desk staff in the
process. Notes taken during the testing process will be valuable in
creating any configuration guides or migration processes for the
production implementation.
Note
Beyond basic functionality,
data entry, and access to application-specific data, some additional
tests that indicate an application has been successfully installed in
the test environment include printing to different standard printers,
running standard reports, exporting and importing data, and exchanging
information with other systems or devices. Testing should be done by end
users of the application and administrative IT staff who support,
maintain, and manage the application. Notes should be taken on the
process and the results because they can be very useful during the
production migration.
Certified for Windows
Server 2008 R2
Microsoft offers a program
that enables vendors to innovate on the Windows Server 2008 R2 platform
and related technologies. This program is called Innovate on Windows
Server, and it allows vendors, organizations, and partners to build,
test, and certify that their applications and products are compatible
with Windows Server 2008 R2. Once certified, a logo will be placed on
the product stating Certified for Windows Server 2008 R2.
During the analysis phase of
whether existing applications will be compatible with Windows Server
2008 R2, it is a best practice to validate that the applications do
carry the Certified for Windows Server 2008 R2 logo by contacting the
manufacturer. By having the logo, application testing and additional
analysis of a specific application is minimized when upgrading to
Windows Server 2008 R2.
The Innovate on Windows
Server partner program can be found at the following hyperlink: www.innovateonwindowsserver.com/Default.aspx.
Testing the Migration
and Upgrade Process
This section touches on the next
logical step in the testing process. After it has been verified that
the final configuration agreed upon in the planning process is stable
and which applications and utilities will be installed on which server,
the actual upgrade process can be tested.
