# Chapter 6. Using Your System in the Stable Test Environment

This section explains how to substitute your test system into the stable four-machine test environment created in Chapter 3, "Building the Test Environment", to test it in each role as domain controller, additional server, client 1, and client 2.

For a review of the role each system plays in the test environment, refer to Chapter 3, "Building the Test Environment".

## Server Testing

Do the server testing the in the following order:

1. Test your system as additional server.

2. Test your system as domain controller.

### Testing Your System as the Additional Server

This is the state of the machines in your test environment:

- Original domain controller is powered on.

- Original additional server is powered on and cabled into the network.

- Original client 1 and client 2 are powered on.

- Test system is powered off, not yet configured, but cabled into the network.

To exercise your test system as an additional server:

1. Power off or remove the original additional server from the network.

2. If the original server is not powered off or disconnected from the network, "duplicate netbios name" errors create problems during the installation.

3. Power on your test system and follow the appropriate instructions to prepare your test system for the role of additional server.

- For OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, see: Appendix A, "Install and Configure OS/2 Warp Server for e-business or Convenience Package for OS/2 Warp Server for e-business".

- Be sure to select the option that formats the hard drive during installation.

- On each of the four systems that are powered on, use the PCM TEST and LAN TEST GUIs to run the tests for the additional server as described in:

- Chapter 4, "Running and Verifying the Base Test Cases".

- Chapter 5, "Running and Verifying the Network Test Cases".

1. After all the tests are complete, collect the results as described in Chapter 7, "Collecting and Submitting Test Results". Review and analyze any problems seen in the test report.

2. Shut down and power off the test system currently playing the role of additional server.

3. Power on the original additional server.

4. Issue the resync command on the original additional server.

### Testing Your System as the Domain Controller

This is the state of the machines in your test environment:

- Original domain controller is powered on and cabled into the network.

- Original additional server is powered on and cabled into the network.

- Original client 1 and client 2 are powered on and cabled into the network.

- Test system is powered off, cabled into the network, and currently configured for role of domain controller.

To exercise your test system as a domain controller:

1. Shut down and power off all four systems in the original test environment.

If the original domain controller is not powered off or disconnected from the network, "duplicate netbios name" errors create problems during the installation.

You may leave the original domain controller attached to the network if it remains powered off while you test the new system.

1. Power on your test system and follow the appropriate instructions to prepare your test system for the role of domain controller.

- For OS/2 Warp Server for e-business and Convenience Package for OS/2 Warp Server for e-business, see: Appendix A, "Install and Configure OS/2 Warp Server for e-business or Convenience Package for OS/2 Warp Server for e-business"

- Be sure to select the option that formats the hard drive during installation.

1. After the new domain controller is ready, power on the original additional server.

2. From an OS/2 command prompt on the additional server, issue the resync command from the \itlutil directory on the server.

3. On the additional server, run the lansetup command file in the \os2 directory. This command redefines the shared resources on the server to the domain that were lost when the original domain controller was replaced with the system being tested.

4. The system under test is now operating as the environment's domain controller.

5. Power on both client systems.

6. On each of the four systems that are powered on, use the LAN TEST GUI to run the test cases for the domain controller as described in:

- Chapter 5, "Running and Verifying the Network Test Cases".

1. After all the tests are complete, collect the results as described in Chapter 7, "Collecting and Submitting Test Results". Review and analyze any problems seen in the test report.

2. Do problem resolution and rerun tests as required.

3. After all the appropriate tests have passed, shut down and power off all four systems.

## Client Testing

Do the client testing the in the following order:

1. Test your system as client 1.

2. Test your system as client 2.

### Testing Your System as Client 1

This is the state of the machines in your test environment:

- Original domain controller is powered on and cabled into the network.

- Original additional server is powered on and cabled into the network.

- Original client 1 and client 2 systems are powered on and cabled into the network.

- Test system is powered off, not yet configured, but cabled to the network.

To exercise your test system as client 1:

1. Shut down client 1 and power it off.

If the original client 1 is not powered off or disconnected from the network, "duplicate netbios name" errors create problems during the installation.

1. Power on your test system and follow the appropriate instructions to prepare your test system for the role of client 1.

- For OS/2 Warp Version 4, see: Appendix B, "Install and Configure OS/2 Warp Version 4".

- For Convenience Package for OS/2 Warp Version 4, see: Appendix C, "Install and Configure Convenience Package for OS/2 Warp Version 4".

- Be sure to select the option that formats the hard drive during installation.

1. On each of the four systems that are powered on, use the PCM TEST and LAN TEST GUIs to run the tests for client 1 as described in:

- Chapter 4, "Running and Verifying the Base Test Cases".

- Chapter 5, "Running and Verifying the Network Test Cases".

1. After all the tests have completed, collect the test results. Review and analyze any problems seen in the test report.

2. When all appropriate tests have passed, shut down and power off client 1 (your test system).

3. Power on the original client 1.

### Testing Your System as Client 2

This is the state of the machines in your test environment:

- Original domain controller is powered on and cabled into the network.

- Original additional server is powered on and cabled into the network.

- Original client 1 and client 2 systems are powered on and cabled into the network.

- Test system is powered off, cabled into the network, and currently configured for role of client 1.

To exercise your test system as client 2:

1. Shut down client 2 and power it off.

If the original client 2 is not powered off or disconnected from the network, "duplicate netbios name" errors create problems during the installation.

1. Power on your test system and follow the appropriate instructions to prepare your test system for the role of client 2.

- For OS/2 Warp Version 4, see: Appendix B, "Install and Configure OS/2 Warp Version 4".

- For Convenience Package for OS/2 Warp Version 4, see: Appendix C, "Install and Configure Convenience Package for OS/2 Warp Version 4".

- Be sure to select the option that formats the hard drive during installation.

1. On each of the four systems that are powered on, use the LAN TEST GUI to run the tests for client 2 as described in:

- Chapter 5, "Running and Verifying the Network Test Cases".

1. After all the tests have completed, collect the test results. Review and analyze any problems seen in the test report.

2. When all appropriate tests have passed, shut down and power off client 2 (your test system).

3. Power on the original client 2.