MSA DOM Test Cases

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps

Pre-process

1. Count the number of physical computers in the lab.

The purpose of this test is to validate that the physical hardware 2. Count the number of computers in the network topology diagram

All computer resources are present and configured according to the

161 Network Topology BVT Computer inventory provided by the lab is equal to the required hardware documented in provided by dev.

configuration matrix.

the network topology layout diagram provided by dev. 3. Compare the totals from step 1 with step 2 and verify that they are

equal.

1. Start the servers and log into the system.

The purpose of this test is to validate that the labels on the physical

2. Shut down the system by selecting restart the system.

hardware provided by the lab is consistent with the naming All computer resources are present and configured according to the

162 Network Topology BVT Visual computer identification 3. The system should shut down completely and restart.

convention documented in the network topology layout diagram configuration matrix.

4. Log into the system and check the event viewer for any failures or

provided by dev.

warnings in the system, application, and security logs after restart.



The purpose of this test is to validate that the computer name for 1. Open a command window, type 'hostname', and press 'Enter'.

each computer provided by the lab is consistent with the naming All computer resources are present and configured according to the 2. Compare the response from step 1 with the computer name listed

163 Network Topology BVT Computer identification

convention documented in the network topology layout diagram configuration matrix. for the specified computer in the network topology layout diagram

provided by dev. provided by dev.



1. Open a command window, type 'ipconfig', and press 'Enter'.

2. Verify that an IP Address is present in the output from step 1.

The purpose of this test is to validate that all of the physical hardware All servers, clients, and network services are online and functioning

164 Network Topology BVT Network connectivity 3. Type 'ping ' (where computer name is a valid

provided by the lab have network connectivity. correctly.

name of another computer on the same subnet) and press 'Enter'.

4. Verify that a response is received from step 3.

The purpose of this test is to validate that the role (Domain Controller -

The servers designated as primary domain controllers (PDCs) are 1. Open the Server Manager and verify that, for the role of PDC, the

165 Network Topology BVT Computer role (Domain Controller - PDC) PDC) of the specified computer is consistent with the role

built and configured accordingly. local computer's name is listed.

documented in the network topology layout diagram provided by dev.



The purpose of this test is to validate that the role (Domain Controller -

The servers designated as backup domain controllers (BDCs) are 1. Open the Server Manager and verify that, for the role of BDC, the

166 Network Topology BVT Computer role (Domain Controller - BDC) BDC) of the specified computer is consistent with the role

built and configured accordingly. local computer's name is listed.

documented in the network topology layout diagram provided by dev.



For the specified computer, as documented in the network topology

layout diagram provided by dev, the purpose of this test is to validate The servers designated as DNS Servers are built and configured 1. Open the DNS Manager to verify the existence of the DNS Service

167 Core Services BVT DNS Server

that the Domain Name System (DNS) Service is installed and accordingly. on the local computer.

functioning.

For the specified computer, as documented in the network topology

layout diagram provided by dev, the purpose of this test is to validate The servers designated as WINS Servers are built and configured 1. Open the WINS Manager to verify the existence of the WINS

168 Core Services BVT WINS Server

that the Windows® Internet Naming Service (WINS) Service is accordingly. Service on the local computer.

installed and functioning.



For the specified computer, as documented in the network topology

layout diagram provided by dev, the purpose of this test is to validate The servers designated as DHCP Servers are built and configured 1. Open the DHCP Manager to verify the existence of the DHCP

169 Core Services BVT DHCP Server

that the Dynamic Host Configuration Protocol (DHCP) Service is accordingly. Service on the local computer.

installed and functioning.



For the specified computer, as documented in the network topology

The servers designated as Exchange Messaging Servers are built 1. Open the Exchange Server Administrator to verify the existence of

170 Core Services BVT Exchange Server layout diagram provided by dev, the purpose of this test is to validate

and configured accordingly. the Exchange Server service on the local computer.

that the Exchange Messaging Service is installed and functioning.



For the specified computer, as documented in the network topology

The servers designated as File Servers are built and configured 1. Open a command window, type 'net share', and press 'Enter'.

172 Core Services BVT File Server layout diagram provided by dev, the purpose of this test is to validate

accordingly. 2. Verify that non-administrative shares exist in the output above.

that the File Service is installed and functioning.



The purpose of this test is to validate that the IP address, for each 1. Open a command window, type 'ipconfig /all', and press 'Enter'.

computer (client) provided by the lab, is consistent with the IP All servers, clients, and network services are online and functioning 2. Compare the IP address from step 1 with the IP address

173 Core Services BVT IP address assignment (client)

address assignment documented in the network topology layout correctly. assignment for the specified computer in the network topology layout

diagram provided by dev. diagram provided by dev.



For the specified computer, as documented in the network topology

The servers designated as Print Servers are built and configured 1. Open the Printers Control Panel applet and verify that at least one

175 Core Services BVT Print Server layout diagram provided by dev, the purpose of this test is to validate

accordingly. printer is installed on the local computer.

that the Print Service is installed and functioning.









Page 1 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps



1. Open a command window, type 'ping ' (where

computer name is a fully qualified domain name (FQDN) of another

The purpose of this test is to validate that the DNS Client service is All servers, clients, and network services are online and functioning

176 Core Services BVT DNS Client computer on the network) and press 'Enter'. Example: foo.bar.com,

functioning. correctly.

where 'foo' is the computer name in the 'bar.com' domain.

2. Verify that a response is received from step 1.



1. Open a command window, type 'ipconfig /all', and press 'Enter'.

2. Verify that the following items from the output above are present:

The purpose of this test is to validate that the DHCP Client service is All servers, clients, and network services are online and functioning

177 Core Services BVT DHCP Client IP Address, Subnet Mask, Default Gateway, DHCP Server, DNS

functioning. correctly.

Servers, Primary WINS Server, Secondary WINS Server, Lease

Obtained, and Lease Expires.



1. From a workstation, open the messaging client.

The purpose of this test is to validate that the Exchange Messaging All servers, clients, and network services are online and functioning 2. Can the messaging client connect to its Exchange Server?

178 Core Services BVT Exchange Messaging Client

Client service is functioning. correctly. 3. Can the messaging client send email?

4. Can the messaging client receive email?



The purpose of this test is to validate that a client can access a All servers, clients, and network services are online and functioning 1. Open a command window and using the 'net use' command,

179 Core Services BVT Network resource (file)

network resource (file). correctly. connect to a network resource (file share).



The purpose of this test is to validate that a client can access a All servers, clients, and network services are online and functioning 1. Open a command window and using the 'net use' command,

180 Core Services BVT Network resource (print)

network resource (print). correctly. connect to a network resource (printer share).





1. Open the DHCP Manager.

The purpose of this test is to validate that the DHCP Scope for each

All servers, clients, and network services are online and functioning 2. Are there any DHCP scopes defined?

181 Core Services BVT DHCP Scope subnet is consistent with the DHCP Scope assignment documented

correctly. 3. Do the DHCP scopes correspond to those defined in the network

in the network topology layout diagram provided by dev.

topology layout diagram provided by dev?



The purpose of this test is to validate the creation of user accounts

within the domain(s) as documented in the functional requirements

provided by dev, as is illustrated by the following list:

All domain controllers are online and functioning correctly. Population 1. Open the User Manager for Domains on any domain controller.

• WNB-ACCT-A\user00001 - WNB-ACCT-A\user15000

182 Core Services BVT User accounts of user accounts has been completed within their respective 2. Do all of the users from the list exist within their respective

• WNB-ACCT-ROW\user14980 - WNB-ACCT-ROW\user22980

domains. domains?

• WNB-RES-A\user23001 - WNB-RES-A\user23050

• WNB-MESSAGING\user24001 - WNB-MESSAGING\user24025

• WNB-RES-SYD\user25001 - WNB-RES-SYD\user25005



The purpose of this test is to validate the creation of computer All domain controllers are online and functioning correctly. Population

1. Open the Server Manager and verify that, for each domain, the

183 Core Services BVT Computer accounts accounts within the domain(s) as documented in the functional of computer accounts has been completed within their respective

computer accounts are listed.

requirements provided by dev. domains.



The purpose of this test is to validate the creation of global groups

within the domain(s) as documented in the functional requirements

provided by dev, as is illustrated by the following list:

All domain controllers are online and functioning correctly. Population 1. Open the User Manager for Domains on any domain controller.

• WNB-ACCT-A\grp0001 - WNB-ACCT-A\grp4000

184 Core Services BVT Global groups of global/local groups has been completed within their respective 2. Do all of the groups from the list exist within their respective

• WNB-ACCT-ROW\grp3980 - WNB-ACCT-ROW\grp5980

domains. domains?

• WNB-RES-A contains no global groups

• WNB-MESSAGING\grp6001 - WNB-MESSAGING\grp6006

• WNB-RES-SYD\grp7001 - WNB-RES-SYD\grp7002



The purpose of this test is to validate the successful joining of user(s)

to their specified global group(s) as documented in the functional

requirements provided by dev, as is illustrated by the following list:

1. Pick a random sampling of users from WNB-ACCT-A\User00001 -

• WNB-ACCT-A\user00001 - WNB-ACCT-A\user00100

WNB-ACCT-A\User00100 and WNB-ACCT-ROW\User14980 - WNB-

• Random members of WNB-ACCT-A\grp0001 - grp0050

ACCT-ROW\User15080 (“working users”); is each user a member of

• Random members of WNB-ACCT-ROW\grp3980 - grp3989 All domain controllers are online and functioning correctly. Population

no less than 10 groups?

185 Core Services BVT Group membership • WNB-ACCT-ROW\user14980 - WNB-ACCT-A\user15080 of group memberships has been completed within their respective

2. Pick a random sampling of users outside the “working users” set; is

• Random members of WNB-ACCT-ROW\grp3980 - grp4030 domains.

each user a member of no less than 1 group?

• Random members of WNB-ACCT-A\grp0001 - grp0010

3. Pick a random sampling from all users; is the “primary” group for

• Each of the above users should be a member of 10 or more groups

each user the “Domain User” group?

• The remainder of the groups will have at least 1 member each, with

a user00001:grp0001 relationship.

• The 'primary' group for each use will remain 'Domain User'.









Page 2 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps

1. From a domain controller within a specific domain, open the Server

The purpose of this test is to validate that the domain membership for Manager, from the View menu select Servers, and verify the domain

each computer provided by the lab is consistent with the naming membership of the servers in the list.

186 Core Services BVT Domain membership All servers and clients are online and functioning correctly.

convention documented in the network topology layout diagram 2. From a domain controller within a specific domain, open the Server

provided by dev. Manager, from the View menu select Workstations, and verify the

domain membership of the workstations in the list.



The purpose of this test is to validate that the IP address, for each 1. *** Check the hard coded IP address ***.

computer (server) provided by the lab, is consistent with the IP 2. Compare the IP address from step 1 with the IP address

187 Core Services BVT IP address assignment (server) All servers are online and functioning correctly.

address assignment documented in the network topology layout assignment for the specified computer in the network topology layout

diagram provided by dev. diagram provided by dev.





1. From a client on each subnet, open a command window, type

The purpose of this test is to validate that the IP address, for the

'ipconfig /all', and press 'Enter'.

router provided by the lab, is consistent with the IP address

188 Core Services BVT IP address assignment (router) All network hardware resources are online and functioning correctly. 2. Compare the IP address for the 'Default Gateway' from step 1 with

assignment documented in the network topology layout diagram

the IP address assignment for the specified router in the network

provided by dev.

topology layout diagram provided by dev.



1. Open a command window, type 'ipconfig /all', and press 'Enter'.

The purpose of this test is to validate that a client on any given subnet All servers, clients, and network services are online and functioning 2. Using the output from step 1, type 'ping ', where the

189 Core Services BVT Network connectivity (default gateway)

can communicate with its default gateway. correctly. 'ip address' is the address of the 'Default Gateway'.

3. Verify that a response is received from step 2.



1. Open a command window, type 'ping ', where

The purpose of this test is to validate that a client on any given subnet

190 Core Services BVT Network connectivity (different subnet) All clients are online and functioning correctly. the 'computer name' is the name of a computer on a different subnet.

can communicate with a client of a different subnet.

2. Verify that a response is received from step 1.



The purpose of this test is to validate the SVC_Spooler account exists

The servers designated as Print Servers are built and configured 1. From the PDC in the WNB-ACCT-ROW domain, open the User

204 Core Services BVT Service account in the WNB-ACCT-ROW domain as documented in the functional

accordingly. Manager, and verify the existence of the SVC_Spooler account.

requirements provided by dev.



1. Open the Services control panel applet on SYD-WS-FPS-01 and

The purpose of this test is to validate that the Spooler service on

The servers designated as Print Servers are built and configured find the Spooler service.

212 Core Services BVT Spooler service WNB-RES-SYD\SYD-WS-FPS-01 is running under the WNB-ACCT-

accordingly. 2. Is the Spooler service on WNB-RES-SYD\SYD-WS-FPS-01

ROW\SVC_Spooler account.

running under the WNB-ACCT-ROW\SVC_Spooler account?



The purpose of this test is to validate that the network shares are

consistent with the documentation in the functional requirements

provided by dev.

All shares will be ACL’d, by default, to “Everyone: Full Control.”

Shares:

• WNB-RES-A\NYC-WA-FPS-01

1. From each of the computers in the list, open a command window,

• Data

type 'net share', and press 'Enter'.

• Home

The servers designated as File Servers are built and configured 2. Compare the output from step 1 with the list of network shares for

• Directors

213 Core Services BVT Network shares accordingly. Creation of network folder shares has been completed the local computer.

• Profile

within their respective domains. 3. Do all of the shares in the list above exist on their respective FPS

• Apps

Server?

• WNB-RES-SYD\SYD-WS-FPS-01

• Data

• HR

• Apps

• WNB-ACCT-ROW\JNB-WO-FPS-01

• Data

• Apps









Page 3 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps

The purpose of this test is to validate that the network share

permissions are consistent with the documentation in the functional

requirements provided by dev.

One share, "Directors," on WNB-RES-A\NYC-WA-FPS-01 will be

1. Are all of the shares on the File/Print Servers, with the exception of

ACL’d to WNB-ACCT-ROW\”Directors All: Change” and WNB-ACCT-

the NYC-WA-FPS-01\Directors and SYD-WS-FPS-01\HR shares,

ROW\”Domain Admins: Full Control.”

ACL’d with “Everyone: Full Control”?

One share, "HR," on WNB-RES-SYD\SYD-WS-FPS-01 will be ACL’d

2. Is the NYC-WA-FPS-01\Directors share ACL’d to WNB-ACCT-

to WNB-ACCT-ROW\”Human Resources: Full Control” and WNB-

ROW\”Directors All: Change” and WNB-ACCT-ROW\”Domain

ACCT-ROW\”Domain Admins: Full Control.”

Admins: Full Control”?

Shares: The servers designated as File Servers are built and configured

3. Is the SYD-WS-FPS-01\HR share ACL’d to WNB-ACCT-

• WNB-RES-A\NYC-WA-FPS-01 accordingly. Creation of network folder shares has been completed

ROW\”Human Resources: Full Control” and WNB-ACCT-

216 Core Services BVT Share permissions • Data within their respective domains. Assignment of share permissions has

ROW\”Domain Admins: Full Control”?

• Home been completed as per the functional requirements documented by

4. Can a member from the WNB-ACCT-ROW\”Directors All” group

• Directors dev.

access the NYC-WA-FPS-01\Directors share?

• Profile

5. Can a member from the WNB-ACCT-ROW\”Human Resources”

• Apps

group access the SYD-WS-FPS-01\HR share?

• WNB-RES-SYD\SYD-WS-FPS-01

6. Can a member from the WNB-ACCT-ROW\”Domain Admins”

• Data

group access both the NYC-WA-FPS-01\Directors and the SYD-WS-

• HR

FPS-01\HR share?

• Apps

• WNB-ACCT-ROW\JNB-WO-FPS-01

• Data

• Apps

1. Add a text file (test.txt) to the \\NYC-WA-DC-

01\C$\WINNT\System32\Repl\Export\Scripts folder.

The purpose of this test is to validate that the directory replication The servers designated as domain controllers are built and 2. Toggle the directory replication service on NYC-WA-DC-01.

282 Core Services BVT Directory replication

service is configured and operating successfully. configured accordingly. 3. Verify the existence of the test.txt file, and all other files found in

the above directory on NYC-WA-DC-01, in the NETLOGON share on

NYC-WA-DC-05.

Process

1. Open the Control Panel on NYC-WA-DC-05.

Chapter 7: The purpose of this test is to validate that the DNS Service, post Refer to the Build Note in Chapter 7 under the section "Introducing 2. Double-click on Services.

225 Account Domain Scenario DNS installation on BDC successful installation, has started and that its startup type is New Hardware and Configuring the DNS Namespace" of the 3. Locate the Microsoft® DNS Server service in the list of services.

Upgrade Automatic on the new BDC. Implementation Guide . 4. Verify that the Status of the service is Started.

5. Verify that the Startup of the service is Automatic.



1. Open the DNS Manager on NYC-WA-DC-05.

Chapter 7: Refer to the Build Note in Chapter 7 under the section "Introducing 2. Expand NYC-WA-DC-05 in the Server List.

The purpose of this test is to validate that the secondary DNS zone is

226 Account Domain Scenario Secondary DNS zone creation on BDC New Hardware and Configuring the DNS Namespace" of the 3. Double-click on the woodgrovebank.com zone.

created and replicated on the new BDC.

Upgrade Implementation Guide . 4. Verify the existence of the DNS records in the Zone Info pane for

the secondary zone and that they match those of the primary zone.



1. Open the DNS Manager on NYC-WA-DC-05.

2. Expand NYC-WA-DC-05 in the Server List.

3. Double-click on the woodgrovebank.com zone.

4. From the Zone Info pane, right-click and select New Host.

Chapter 7: Refer to the Build Note in Chapter 7 under the section "Introducing

Designating the new BDC as the host of the The purpose of this test is to validate that the new BDC (NYC-WA-DC- 5. Type 'dummy' as the Host Name and '123.123.123.1' as the Host

227 Account Domain Scenario New Hardware and Configuring the DNS Namespace" of the

primary DNS zone 05) is hosting the primary DNS zone. IP Address and click Add Host.

Upgrade Implementation Guide .

6. Right-click on NYC-WA-DC-05 in the Server List and select Update

Server Data Files.

7. Verify the replication of the 'dummy' record to the

woodgrovebank.com zone on the other servers in the Server List.

Chapter 7: 1. Open the Server Manager on NYC-WA-DC-05.

The purpose of this test is to validate that the new BDC was Refer to the Build Note in Chapter 7 under the section "Promoting the

228 Account Domain Scenario Promote new BDC to the role of PDC 2. Locate NYC-WA-DC-05 in the Computer list and verify that the

successfully promoted to the role of PDC. New Primary Domain Controller" of the Implementation Guide .

Upgrade Type value for this computer is Windows NT® 4.0 Primary.

1. Add a text file (test.txt ) to the \\NYC-WA-DC-

Chapter 7: 01\C$\WINNT\System32\Repl\Export\Scripts folder.

The purpose of this test is to validate that directory replication is Refer to the Build Note in Chapter 7 under the section "Promoting the

229 Account Domain Scenario Directory replication on the new PDC 2. Toggle the directory replication service on NYC-WA-DC-01.

functioning on the newly promoted PDC. New Primary Domain Controller" of the Implementation Guide .

Upgrade 3. Verify the existence of the test.txt file, and all other files found in

the above directory on NYC-WA-DC-01, in the NETLOGON share on









Page 4 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps



1. From a client in the WNB-ACCT-A domain (WS10), log off the

current user.

Chapter 7: 2. From the same client from Step 1, log on as the same user to the

Continued functionality of client logon scripts after The purpose of this test is to validate that the client logon scripts are Refer to the Build Note in Chapter 7 under the section "Promoting the

230 Account Domain Scenario WNB-ACCT-A domain.

the promotion of a new PDC still functioning after promoting the new BDC to the role of PDC. New Primary Domain Controller" of the Implementation Guide .

Upgrade 3. Verify that the logon scripts defined in the WNB-ACCT-A domain

for this user are still functioning as they did prior to the promotion of

the BDC to the role of PDC.





1. From a client in the WNB-ACCT-A domain (WS10), log off the

current user.

Chapter 7: The purpose of this test is to validate that the ability of clients to log

Successful client logon to the WNB-ACCT-A Refer to the Build Note in Chapter 7 under the section "Promoting the 2. From the same client from Step 1, log on as the same user to the

231 Account Domain Scenario on to the WNB-ACCT-A domain has not been impaired as the result

domain after the promotion of a new PDC New Primary Domain Controller" of the Implementation Guide . WNB-ACCT-A domain.

Upgrade of promoting the new BDC to the role of PDC.

3. Verify that logon to the WNB-ACCT-A domain was successful after

the promotion of the BDC to the role of PDC.





1. From a client in the WNB-ACCT-A domain (WS10), log on to the

WNB-ACCT-A domain.

The purpose of this test is to validate that the ability of clients to 2. After successful logon, press CTRL + ALT + DEL and select

Chapter 7:

Successful client password change within the WNB- change their passwords within the WNB-ACCT-A domain has not Refer to the Build Note in Chapter 7 under the section "Promoting the Change Password.

232 Account Domain Scenario

ACCT-A domain after the promotion of a new PDC been impaired as the result of promoting the new BDC to the role of New Primary Domain Controller" of the Implementation Guide . 3. Change the user name to 'user10000', type the old password, type

Upgrade

PDC. 'MsaDom!' as the New Password, and type 'MsaDom!' for Confirm

New Password.

4. Verify the success of the password change.





1. Open the Event Viewer on NYC-WA-DC-05.

Chapter 7: The purpose of this test is to validate that there are no errors in the 2. Verify the successful partial synchronization of all BDCs.

Domain synchronization prior to taking a BDC Refer to the Build Note in Chapter 7 under the section "Configuring

233 Account Domain Scenario System Log of the Event Viewer on both NYC-WA-DC-03 and NYC- 3. Open the Event Viewer on NYC-WA-DC-03.

offline for Domain Upgrade Fallback" of the Implementation Guide .

Upgrade WA-DC-05 after performing domain synchronization. 4. Verify the successful partial synchronization replication of the

Security Accounts Manager (SAM) database from PDC.



1. Open a command window of NYC-WA-DC-05 and type 'ipconfig

Chapter 7: /all'.

The purpose of this test is to validate (visually) that ‘ipconfig /all’ Refer to the Build Note in Chapter 7 under the section "Upgrading the

234 Account Domain Scenario Modifying the PDC to point to itself for DNS 2. Verify that the IP address of the DNS Servers in the output from

shows the correct DNS configuration on the PDC. Primary Domain Controller" of the Implementation Guide .

Upgrade Step 1 is the same as the IP address of NYC-WA-DC-05

(10.34.4.25).

1. Open the Event Viewer on NYC-WA-DC-05.

The purpose of this test is to validate that there are no errors in the 2. Verify that there are no errors with respect to the operating system

Chapter 7:

In-place upgrade of the PDC for WNB-ACCT-A Event Viewer for the operating system installation process. Verify that Refer to the Build Note in Chapter 7 under the section "Upgrading the upgrade process.

235 Account Domain Scenario

domain there are no errors in the %windir%\setuperr.log file for the operating Primary Domain Controller" of the Implementation Guide . 3. Open the %windir%\setuperr.log file on NYC-WA-DC-05.

Upgrade

system installation process. 4. Verify that there are no errors with respect to the operating system

upgrade process.



1. Open the Active Directory Users and Computers admin tool on

Chapter 7: The purpose of this test is to validate (visually) that the domain

Refer to the Build Note in Chapter 7 under the section "Upgrading the NYC-WA-DC-05.

236 Account Domain Scenario Creation of the corp.woodgrovebank.com domain corp.woodgrovebank.com is visible using the Active Directory Users

Primary Domain Controller" of the Implementation Guide . 2. Verify the existence of the corp.woodgrovebank.com Active

Upgrade and Computers admin tool.

Directory® object in the left pane of the tool.





1. Open the Active Directory Users and Computers admin tool on

Chapter 7: The purpose of this test is to validate, via the Active Directory Users NYC-WA-DC-05.

Domain Functional Level for the Refer to the Build Note in Chapter 7 under the section "Upgrading the

237 Account Domain Scenario and Computers admin tool, that the domain functional level is 2. Right-click on the corp.woodgrovebank.com domain object, select

corp.woodgrovebank.com domain Primary Domain Controller" of the Implementation Guide .

Upgrade Windows Server™ 2003 Interim. Properties, and verify that the Domain functional level is set to

Windows Server 2003 interim.





1. Open the Active Directory Domains and Trusts admin tool on NYC-

The purpose of this test is to validate, via the Active Directory WA-DC-05.

Chapter 7: Trust relationships were maintained through the

Domains and Trusts admin tool, that the pre-existing trust Refer to the Build Note in Chapter 7 under the section "Upgrading the 2. Right-click on the corp.woodgrovebank.com domain object, select

238 Account Domain Scenario upgrade from Windows NT 4.0 to Windows Server

relationships were maintained after the upgrade and dcpromo Primary Domain Controller" of the Implementation Guide . Properties, click on the Trusts tab, and verify the trusts relationships

Upgrade 2003

process. match those that existed prior to the upgrade to Windows Server

2003.







Page 5 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps





1. Open the DNS admin tool on NYC-WA-DC-05.

Chapter 7: The purpose of this test is to validate, via the DNS admin tool, that the

DNS was maintained through the upgrade from Refer to the Build Note in Chapter 7 under the section "Upgrading the 2. Expand the NYC-WA-DC-05 node, expand the Forward Lookup

239 Account Domain Scenario woodgrovebank.com zone was maintained after the upgrade and

Windows NT 4.0 to Windows Server 2003 Primary Domain Controller" of the Implementation Guide . Zones, select the woodgrovebank.com zone, and verify that the DNS

Upgrade dcpromo process.

records still exist within the zone.







1. From a client in the WNB-ACCT-A domain (WS10), log off the

current user.

Chapter 7: Successful client logon to the WNB-ACCT-A

The purpose of this test is to validate that WNB-ACCT-A users have Refer to the Build Note in Chapter 7 under the section "Upgrading the 2. From the same client from Step 1, log on as the same user to the

240 Account Domain Scenario domain after the upgrade from Windows NT 4.0 to

not lost the ability to log on to the domain. Primary Domain Controller" of the Implementation Guide . WNB-ACCT-A domain.

Upgrade Windows Server 2003

3. Verify that logon to the WNB-ACCT-A domain was successful after

the upgrade from Windows NT 4.0 to Windows Server 2003.





1. Open the Event Viewer on NYC-WA-DC-03.

Chapter 7: 2. Verify the successful partial synchronization of all BDCs.

Domain synchronization after Domain Upgrade The purpose of this test is to validate that there are no errors in the Refer to the Build Note in Chapter 7 under the section "Configuring

241 Account Domain Scenario 3. Open the Event Viewer on all BDCs.

Fallback System Log of the Event Viewer on the PDC and all BDCs. for Domain Upgrade Fallback" of the Implementation Guide .

Upgrade 4. Verify the successful partial synchronization replication of the SAM

database from the PDC.





1. From a client in the WNB-ACCT-A domain (WS10), log on to the

WNB-ACCT-A domain.

2. After successful logon, press CTRL + ALT + DEL and select

Chapter 7: The purpose of this test is to validate that the ability of clients to

Successful client password change within the WNB- Refer to the Build Note in Chapter 7 under the section "Configuring Change Password.

242 Account Domain Scenario change their passwords within the WNB-ACCT-A domain has not

ACCT-A domain after Domain Upgrade Fallback for Domain Upgrade Fallback" of the Implementation Guide . 3. Change the User name to 'user10001', type the old password, type

Upgrade been impaired as the result of a Domain Upgrade Fallback.

'MsaDom!' as the New Password, and type 'MsaDom!' for Confirm

New Password.

4. Verify the success of the password change.





1. From a client in the WNB-ACCT-A domain (WS10), log off the

current user.

Chapter 7: The purpose of this test is to validate that the ability of clients to log

Successful client logon to the WNB-ACCT-A Refer to the Build Note in Chapter 7 under the section "Configuring 2. From the same client from Step 1, log on as the same user to the

243 Account Domain Scenario on to the WNB-ACCT-A domain has not been impaired as the result

domain after Domain Upgrade Fallback for Domain Upgrade Fallback" of the Implementation Guide . WNB-ACCT-A domain.

Upgrade of a Domain Upgrade Fallback.

3. Verify that logon to the WNB-ACCT-A domain was successful after

a Domain Upgrade Fallback.



1. From a client in the WNB-ACCT-A domain (WS10), log off the

current user.

Chapter 7: 2. From the same client from Step 1, log on as the same user to the

Continued functionality of client logon scripts after a The purpose of this test is to validate that the client logon scripts are Refer to the Build Note in Chapter 7 under the section "Configuring

244 Account Domain Scenario WNB-ACCT-A domain.

Domain Upgrade Fallback still functioning after a Domain Upgrade Fallback. for Domain Upgrade Fallback" of the Implementation Guide .

Upgrade 3. Verify that the logon scripts defined in the WNB-ACCT-A domain

for this user are still functioning as they did prior to a Domain

Upgrade Fallback.

1. Open the DNS Manager on NYC-WR-DHCP-02.

2. Expand NYC-WR-DHCP-02 in the Server List.

3. Double-click on the woodgrovebank.com zone.

Chapter 7:

The purpose of this test is to validate that NYC-WR-DHCP-02 is Refer to the Build Note in Chapter 7 under the section "Configuring 4. From the Zone Info pane, delete the 'dummy' host record.

245 Account Domain Scenario DNS Recovery after a Domain Upgrade Fallback

hosting the primary DNS zone after a Domain Upgrade Fallback. for Domain Upgrade Fallback" of the Implementation Guide . 5. Right-click on NYC-WR-DHCP-02 in the Server List and select

Upgrade

Update Server Data Files.

6. Verify the replication of the deletion of the 'dummy' record in the

woodgrovebank.com zone on the other servers in the Server List.



1. Open the DNS MMC on NYC-WA-DC-05.

2. Right-click on the NYC-WA-DC-05 DNS Server node and select

Chapter 7: The purpose of this test is to validate that the Windows Server 2003 Refer to the Build Note in Chapter 7 under the section "Configuring Update Server Data Files.

Replication of the corp.woodgrovebank.com zone

246 Account Domain Scenario corp.woodgrovebank.com zone is created and replicated to the NT Replication of Windows Server 2003 DNS Zone" of the Implementation 3. Open the DNS Manager on NYC-WR-DHCP-01.

to the down level NT 4.0 DNS Servers

Upgrade 4.0 DNS Servers. Guide . 4. Refresh the woodgrovebank.com zone for each server in the

Server List and verify the existence of a corp.woodgrovebank.com

NS record and an NYC-WA-DC-05 A record in the corp zone.









Page 6 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps



1. From a client in the WNB-ACCT-A domain (WS10), log on to the

Chapter 7: DNS name resolution on NYC-WA-DC- The purpose of this test is to validate that a client workstation can Refer to the Build Note in Chapter 7 under the section "Configuring WNB-ACCT-A domain.

247 Account Domain Scenario 05.corp.woodgrovebank.com from a client successfully resolve the DNS lookup of NYC-WA-DC- Replication of Windows Server 2003 DNS Zone" of the Implementation 2. After successful logon, open a command window and type 'ping

Upgrade workstation 05.corp.woodgrovebank.com. Guide . NYC-WA-DC-05.corp.woodgrovebank.com'.

3. Verify the successful resolution of the above FQDN.





1. Add a text file (test2003.txt ) to the \\NYC-WA-DC-05\NETLOGON

share.

2. Run the LBridge scheduled task on NYC-WA-DC-05.

Chapter 7: The purpose of this test is to validate that LBridge replication between

Refer to the Build Note in Chapter 7 under the section "Scheduling 3. Verify the existence of the test2003.txt file in the \\NYC-WA-DC-

248 Account Domain Scenario LBridge Replication to the NT 4.0 Export Server the Windows Server 2003 (NYC-WA-DC-05) and the NT 4.0 Export

LBridge Replication" of the Implementation Guide. 01\C$\WINNT\System32\Repl\Export\Scripts folder.

Upgrade Server (NYC-WA-DC-01) is functioning.

4. Toggle the directory replication service on NYC-WA-DC-01.

5. Verify the existence of the test2003.txt file on the remaining BDCs

in the domain.





1. Open the "%SystemDrive%\Exchange Server Setup Progress.log"

The purpose of this test is to validate that there are no errors in the

Chapter 7: file on NYC-WA-DC-05.

Extending the Active Directory Schema in Exchange Server Setup Progress.log file at the root of the C: drive on Refer to the Build Note in Chapter 7 under the section "Extending the

249 Account Domain Scenario 2. Verify that the string "Setup completed successfully!" appears at

readiness for Microsoft Exchange 2003 NYC-WA-DC-05 after performing after extending the Active Directory Active Directory Schema" of the Implementation Guide .

Upgrade the end of the file after extending the Active Directory Schema in

Schema in readiness for Microsoft Exchange 2003.

readiness for Microsoft Exchange 2003.







1. Open the Active Directory Users and Computers admin tool on

Chapter 7: The purpose of this test is to validate (visually) that the domain

Existence of the corp.woodgrovebank.com domain Refer to the Build Note in Chapter 7 under the section "Upgrading the each Replica domain controller (NYC-WA-DC-06, SYD-WA-DC-01).

250 Account Domain Scenario corp.woodgrovebank.com is visible using the Active Directory Users

on all Replicas Remaining Backup Domain Controllers" of the Implementation Guide . 2. Verify the existence of the corp.woodgrovebank.com active

Upgrade and Computers admin tool on all Replica domain controllers.

directory object in the left pane of the tool.







1. Open the Active Directory Users and Computers admin tool on

Chapter 7: The purpose of this test is to validate, via the Active Directory Users each Replica domain controller (NYC-WA-DC-06, SYD-WA-DC-01).

Domain Functional Level for the Refer to the Build Note in Chapter 7 under the section "Upgrading the

251 Account Domain Scenario and Computers admin tool, that the domain functional level is 2. Right-click on the corp.woodgrovebank.com domain object, select

corp.woodgrovebank.com domain on all Replicas Remaining Backup Domain Controllers" of the Implementation Guide .

Upgrade Windows Server 2003 Interim on all Replica domain controllers. Properties, and verify that the Domain functional level is set to

Windows Server 2003 interim.







1. Open the Active Directory Domains and Trusts admin tool on each

The purpose of this test is to validate, via the Active Directory Replica domain controller (NYC-WA-DC-06, SYD-WA-DC-01).

Chapter 7:

Trust relationships were maintained with the Domains and Trusts admin tool, that the pre-existing trust Refer to the Build Note in Chapter 7 under the section "Upgrading the 2. Right-click on the corp.woodgrovebank.com domain object, select

252 Account Domain Scenario

addition of Replica domain controllers relationships were maintained with the addition of Replica domain Remaining Backup Domain Controllers" of the Implementation Guide . Properties, click on the Trusts tab, and verify the trusts relationships

Upgrade

controllers. match those that existed prior to the addition of Replica domain

controllers.







1. Open the Active Directory Users and Computers admin tool on

NYC-WA-DC-05.

2. Right-click on the corp.woodgrovebank.com domain object, select

Chapter 7: The purpose of this test is to validate, via the Active Directory Users

Changing the Forest and Domain Functional Level Refer to the Build Note in Chapter 7 under the section "Raising the Properties, and verify that the Forest and Domain functional level is

253 Account Domain Scenario and Computers admin tool, that the forest and domain functional level

for the corp.woodgrovebank.com domain Forest and Domain Functional Levels" of the Implementation Guide . set to Windows Server 2003.

Upgrade is Windows Server 2003.

3. Open the Event Viewer on NYC-WA-DC-05.

4. Verify that an entry exists in the System Log that the domain

operation mode has been changed to Native Mode.









Page 7 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps



1. From a client in the WNB-ACCT-A domain (WS10), log off the

current user.

2. From the same client from Step 1, log on as the administrator of

the WNB-ACCT-A domain.

3. Open a command window, type 'ipconfig /all', and note the time

Chapter 8:

Decreasing the DHCP lease duration on the NT 4.0 The purpose of this test is to validate that the client workstations Refer to the Build Note in Chapter 8 under the section "Reducing the difference between the Lease Obtained and the Lease Expires.

254 Migrating Network Scenario

DHCP Servers renew their TCP/IP configuration properties every 30 minutes. DHCP Lease Duration" of the Implementation Guide . 4. Type 'ipconfig /release && ipconfig /renew' to obtain new TCP/IP

Services

configuration properties.

5. Type 'ipconfig /all', and note the time difference between the Lease

Obtained and the Lease Expires. The difference should reflect the

decrease to the lease duration period.

6. Repeat this process for a client in each subnet.





Chapter 8: 1. Open the Event Viewer on NYC-WA-MSP-01 and 02.

The purpose of this test is to validate that there are no errors in the Refer to the Build Note in Chapter 8 under the section "Configuring

255 Migrating Network Scenario Cluster creation 2. Verify that there are no entries indicating any failures in the

Event Viewer for the cluster creation process. the Windows Server 2003 Cluster" of the Implementation Guide .

Services creation of the cluster or any of its resources.





1. Open the Cluster Administrator on NYC-WA-MSP-01.

2. Expand the NYC-WA-MSP01 node, expand Groups, and select

Chapter 8: The purpose of this test is to validate (visually) that all DHCP cluster

Refer to the Build Note in Chapter 8 under the section "Configuring DHCP Services.

256 Migrating Network Scenario Cluster Resources (DHCP) resources (DHCP Services IP Address, DHCP Services Name, Disk

the Windows Server 2003 Cluster" of the Implementation Guide . 3. Verify the existence of the following DHCP resources: DHCP

Services E:, and NYC-WA-DHCP01) are present and online.

Services IP Address, DHCP Services Name, Disk E:, and NYC-WA-

DHCP01 and that they are all Online.





1. Open the Cluster Administrator on NYC-WA-MSP-01.

2. Expand the NYC-WA-MSP01 node, expand Groups, and select

Chapter 8: The purpose of this test is to validate (visually) that all WINS cluster

Refer to the Build Note in Chapter 8 under the section "Configuring WINS Services.

257 Migrating Network Scenario Cluster Resources (WINS) resources (WINS Services IP Address, WINS Services Name, Disk

the Windows Server 2003 Cluster" of the Implementation Guide . 3. Verify the existence of the following WINS resources: WINS

Services F:, and NYC-WA-WINS01) are present and online.

Services IP Address, WINS Services Name, Disk F:, and NYC-WA-

WINS01 and that they are all Online.







1. Open the DHCP MMC on NYC-WA-MSP-01.

2. Expand the nyc-wa-dhcp01.corp.woodgrovebank.com node and

Chapter 8:

The purpose of this test is to validate that the DHCP scopes are Refer to the Build Note in Chapter 8 under the section "Adding the verify the existence of the following DHCP scopes: NYC Scope, GVA

258 Migrating Network Scenario Adding DHCP Scopes to the cluster

visible and are configured appropriately. New DHCP Scopes" of the Implementation Guide . Scope, SYD Scope, and JNB Scope.

Services

3. Click on the Address Pool for each scope and verify that the

Address Ranges and Exclusions are correct.







Chapter 8: 1. Open the DHCP MMC on NYC-WA-MSP-01.

The purpose of this test is to validate (visually) that the DHCP Server Refer to the Build Note in Chapter 8 under the section "Authorizing the

259 Migrating Network Scenario DHCP Scope Authorization 2. Verify that the NYC-WA-DHCP01.corp.woodgrovebank.com server

has been authorized. DHCP Scopes" of the Implementation Guide .

Services is authorized (little green icon on the DHCP Server node).





Chapter 8: 1. Open the DHCP MMC on NYC-WA-MSP-01.

The purpose of this test is to validate (visually) that all scopes have Refer to the Build Note in Chapter 8 under the section "Activating

260 Migrating Network Scenario DHCP Scope Activation 2. Select the NYC-WA-DHCP01.corp.woodgrovebank.com node and

been activated. Scopes" of the Implementation Guide .

Services verify that the Status of all scopes is ** Active **.



Chapter 8: The purpose of this test is to validate that all scopes have been 1. Open the DHCP Manager on NYC-WR-DHCP-01.

Refer to the Build Note in Chapter 8 under the section "Deactivating

261 Migrating Network Scenario DHCP Scope Deactivation deactivated on all DHCP Servers: NYC-WR-DHCP-01, NYC-WR- 2. Select each scope and verify that the status of each scope, lower

Windows NT 4.0 DHCP Scopes" of the Implementation Guide .

Services DHCP-02, and SYD-WS-FPS-01. right hand corner of the user interface (UI), is Not Active.









Page 8 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps





1. From a client in the WNB-ACCT-A domain (WS10), log off the

current user.

2. From the same client from Step 1, log on as the administrator of

the WNB-ACCT-A domain.

Chapter 8: The purpose of this test is to validate that the client workstations

Renewal of TCP/IP configuration properties from Refer to the Build Note in Chapter 8 under the section "Deactivating 3. Open a command window, type 'ipconfig /release && ipconfig

262 Migrating Network Scenario receive new TCP/IP configuration properties from the new DHCP

Windows Server 2003 DHCP Server Windows NT 4.0 DHCP Scopes" of the Implementation Guide . /renew'.

Services Server resource.

4. Log off and log back on as the initial user.

5. Type 'ipconfig /all' and verify that the information is consistent with

the TCP/IP configuration properties established on the Windows

Server 2003 DHCP Server.







1. Open the WINS MMC snap-in on NYC-WA-MSP-01.

Chapter 8: The purpose of this test is to validate the replication of the WINS 2. Expand the NYC-WA-WINS01 node, select Active Registrations,

WINS database replication to the Windows Server Refer to the Build Note in Chapter 8 under the section "Migrating

263 Migrating Network Scenario database from the Windows NT 4.0 WINS Server(s) to the Windows right-click and select Display Records.

2003 WINS Server WINS to Windows Server 2003" of the Implementation Guide .

Services Server 2003 WINS Server. 3. Click Find Now on the Display Records dialog and verify from the

Active Registrations node that the WINS records are populated.







1. Open the Active Directory Users and Computers MMC snap-in on

Chapter 9: all replica domain controllers in the corp.woodgrovebank.com

Restructuring The purpose of this test is to validate (visually) that the OU structure Refer to the Build Note in Chapter 9 under the section "Creating the domain.

264 Scenario Organizational Unit structure replication

Additional Account has been replicated to the other domain controllers. Target OU Structure and Delegation" of the Implementation Guide . 2. Expand the corp.woodgrovebank.com node, expand the Migrated

Domains Objects node, and verify that the OU structure matches that from

NYC-WA-DC-05.







Chapter 9: 1. From the Active Directory Migration Tool (ADMT) workstation

The purpose of this test is to validate that no errors are found in the

Restructuring Refer to the Build Note in Chapter 9 under the section "Identifying (WNB-ADMT-01), locate and open the migration.log file for the last

265 Scenario Identifying service accounts log files produced by the Service Account Migration Wizard ADMT

Additional Account Service Accounts" of the Implementation Guide . process and verify that there are no errors produced by the Service

process.

Domains Account Migration Wizard.



1. From a domain controller in the corp.woodgrovebank.com domain

(NYC-WA-DC-05), locate and open the migration.log file for the last

process and verify that there are no errors produced by the Group

Account Migration Wizard.

2. Open the Active Directory Users and Computers MMC snap-in on

NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

select the Groups OU, refresh the OU, and verify the 50 group

The purpose of this test is: to validate that no errors are found in the accounts were migrated. Double-click on one of the migrated group

log files produced by the Group Account Migration Wizard ADMT accounts, select the Members tab, and verify that there are no

process, to validate that the migration of group objects occurred, that members present in the group.

Chapter 9: the groups reside in the correct OU in the Active Directory, and that 3. From step 2, verify that each of the migrated group account objects

Restructuring no group memberships exist, to validate that the groups retained their Refer to the Build Note in Chapter 9 under the section "Performing a has retained its Name and Description.

266 Scenario Group Migration (Pilot)

Additional Account correct name and description, to validate that for groups that exist in Pilot Group Migration " of the Implementation Guide .

4. From step 2, verify that each of the migrated group account objects

Domains both the WNB-ACCT-A and WNB-ACCT-ROW domains, that the

that overlap existing objects in the corp.woodgrovebank.com domain,

groups were prefixed with WO-, to validate that group SIDHistory is

are prefixed with WO-.

retained using LDP, and to validate that the source domain groups

5. From the ADMT workstation (WNB-ADMT-01), open "Ldp,"

are not affected by the migration.

connect to the NYC-WA-DC-05 domain controller, bind using no

credentials, view the root base DN, navigate to the

corp.woodgrovebank.com\Migrated Objects\WNB-ACCT-

ROW\Groups and double-click on any group account. Verify that the

group account has a SIDHistory property with a value.

6. Open the User Manager on NYC-WO-DC-01 and verify that the

migrated group account objects still exist in the WNB-ACCT-ROW

domain.









Page 9 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps

1. From NYC-WA-DC-05, locate and open the migration.log file for

the last process and verify that there are no errors produced by the

ADMT Command Line Group Migration.

2. Open the Active Directory Users and Computers MMC snap-in on

NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

select the Groups OU, refresh the OU, and verify all of the remaining

group accounts were migrated. Double-click on one of the migrated

The purpose of this test is: to validate that no errors are found in the group accounts, select the Members tab, and verify that there are no

log files produced by the ADMT Command Line Group Migration members present in the group.

process, to validate that the migration of group objects occurred, that 3. From step 2, verify that each of the migrated group account objects

Chapter 9: the groups reside in the correct OU in the Active Directory, and that has retained its Name and Description.

Restructuring no group memberships exist, to validate that the groups retained their Refer to the Build Note in Chapter 9 under the section "ADMT v2

267 Scenario Group Migration (Actual)

Additional Account correct name and description, to validate that for groups that exist in Command Line Group Migration " of the Implementation Guide . 4. From step 2, verify that each of the migrated group account objects

Domains both the WNB-ACCT-A and WNB-ACCT-ROW domains, that the that overlap existing objects in the corp.woodgrovebank.com domain,

groups were prefixed with WO-, to validate that group SIDHistory is are prefixed with WO-.

retained using LDP, and to validate that the source domain groups 5. From the ADMT workstation (WNB-ADMT-01), open "Ldp,"

are not affected by the migration. connect to the NYC-WA-DC-05 domain controller, bind using no

credentials, view the root base DN, navigate to the

corp.woodgrovebank.com\Migrated Objects\WNB-ACCT-

ROW\Groups and double-click on a recently migrated group account.

Verify that the group account has a SIDHistory property with a value.

6. Open the User Manager on NYC-WO-DC-01 and verify that the

migrated group account objects still exist in the WNB-ACCT-ROW

domain.



1. From a domain controller in the corp.woodgrovebank.com domain

(NYC-WA-DC-05), locate and open the migration.log file for the last

process and verify that there are no errors produced by the User

Account Migration Wizard.

2. Open the Active Directory Users and Computers MMC snap-in on

NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

select the Users OU, refresh the OU, and verify the 50 user accounts

were migrated and that they are disabled.

3. From step 2, verify that each of the migrated user account objects

has retained its Name and Description.

The purpose of this test is: to validate that no errors are found in the 4. From step 2, verify that each of the migrated user account objects

log files produced by the User Account Migration Wizard ADMT that overlap existing objects in the corp.woodgrovebank.com domain,

process, to validate that the migration of user objects occurred, that are not migrated.

5. From the ADMT workstation (WNB-ADMT-01), open "Ldp",

the users reside in the correct OU in the Active Directory, and that the

Chapter 9: connect to the NYC-WA-DC-05 domain controller, bind using no

user objects are disabled, to validate that the users retained their

Restructuring Refer to the Build Note in Chapter 9 under the section "Performing a credentials, view the root base DN, navigate to the

268 Scenario User Migration (Pilot) correct name and description, to validate that for users that exist in

Additional Account Pilot User Account Migration " of the Implementation Guide . corp.woodgrovebank.com\Migrated Objects\WNB-ACCT-ROW\Users

both the WNB-ACCT-A and WNB-ACCT-ROW domains, that the

Domains and double-click on any user account. Verify that the user account

users were not migrated, to validate that user SIDHistory is retained

has a SIDHistory property with a value.

using LDP, to validate that the source domain users are not affected

6. Open the User Manager on NYC-WO-DC-01 and verify that the

by the migration, to validate that the users' group membership is

migrated user account objects still exist in the WNB-ACCT-ROW

migrated, and to validate that the users' passwords are migrated.

domain.

7. Open the Active Directory Users and Computers MMC snap-in on

NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

select the Users OU, refresh the OU, and verify the 50 user accounts

were migrated. Double-click on one of the migrated user accounts,

select the Member Of tab, and verify that the users' group

memberships are present.

8. Enable USER22980 in the corp.woodgrovebank.com domain.

From the ADMT workstation (WNB-ADMT-01), attempt to map a

network resource using USER22980. Verify the success of mapping

the network resource.









Page 10 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps



1. From a domain controller in the corp.woodgrovebank.com domain

(NYC-WA-DC-05), locate and open the migration.log file for the last

process and verify that there are no errors produced by the ADMT

Command Line User Account Migration.

2. Open the Active Directory Users and Computers MMC snap-in on

NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

select the Users OU, refresh the OU, and verify all of the remaining

user accounts were migrated. and that they are disabled.

3. From step 2, verify that each of the migrated user account objects

The purpose of this test is: to validate that no errors are found in the has retained its Name and Description.

log files produced by the ADMT Command Line User Account 4. From step 2, verify that each of the migrated user account objects

Migration process, to validate that the migration of user objects that overlap existing objects in the corp.woodgrovebank.com domain,

occurred, that the users reside in the correct OU in the Active are not migrated.

Chapter 9: Directory, and that the user objects are disabled, to validate that the 5. From the ADMT workstation (WNB-ADMT-01), open "Ldp,"

Restructuring users retained their correct name and description, to validate that for Refer to the Build Note in Chapter 9 under the section "ADMT v2 connect to the NYC-WA-DC-05 domain controller, bind using no

269 Scenario User Migration (Actual)

Additional Account users that exist in both the WNB-ACCT-A and WNB-ACCT-ROW Command Line User Account Migration " of the Implementation Guide . credentials, view the root base DN, navigate to the

Domains domains, that the users were not migrated, to validate that user corp.woodgrovebank.com\Migrated Objects\WNB-ACCT-ROW\Users

SIDHistory is retained using LDP, to validate that the source domain and double-click on any user account. Verify that the user account

users are not affected by the migration, to validate that the users' has a SIDHistory property with a value.

group membership is migrated, and to validate that the users' 6. Open the User Manager on NYC-WO-DC-01 and verify that the

passwords are migrated. migrated user account objects still exist in the WNB-ACCT-ROW

domain.

7. Open the Active Directory Users and Computers MMC snap-in on

NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

select the Users OU, refresh the OU, and double-click on one of the

migrated user accounts, select the Member Of tab, and verify that the

users' group memberships are present.

8. Enable USER22500 in the corp.woodgrovebank.com domain.

From the ADMT workstation (WNB-ADMT-01), attempt to map a

network resource using USER22500. Verify the success of mapping

the network resource.

Chapter 9: Updating the Sid History of accounts in multiple The purpose of this test is to validate (visually) that no errors are Refer to the Build Note in Chapter 9 under the section "Merging 1. From a domain controller in the corp.woodgrovebank.com domain

270 Restructuring Scenario produced during this process and that user SIDHistory is migrated (NYC-WA-DC-05), open "Ldp," connect to the NYC-WA-DC-05

domains Accounts" of the Implementation Guide .

Additional Account using LDP. domain controller, bind using no credentials, view the DN of



1. Open a command window on NYC-WA-DC-05 and type the

Chapter 10: following command: netdom trust corp.woodgrovebank.com

The purpose of this test is to validate that the two-way trusts setup

Restructuring Refer to the Build Note in Chapter 10 under the section "Establishing /Domain: /verify.

271 Scenario Two-way trust creation to resource domains between corp.woodgrovebank.com and the resource domains (WNB-

Resource Trust Relationships" of the Implementation Guide . 2. Verify the following output from step 1: "The trust between

ACCT-ROW, WNB-RES-A, and WNB-RES-SYD) are functioning.

Domains corp.woodgrovebank.com and has been

successfully verified. The command completed successfully."





1. From an ADMT workstation in the NYC site (WNB-ADMT-01), log

on as the WNB-ACCT-ROW migrator account (ADMT_WNB-ACCT-

ROW), install the adminpak.msi (if necessary), open the Active

Directory Users and Computers snap-in, select a domain controller in

the NYC site in the corp.woodgrovebank.com domain, and navigate

to the Migrated Objects\WNB-ACCT-ROW\Computers OU.

2. Right-click on the Computers OU, select New, and verify that the

"Computer" option is available. NOTE: Due to special privileges in the

Chapter 10: WNB-ACCT-ROW\Domain Admins group, more than just "Computer"

The purpose of this test is to validate that the delegation of control for

Restructuring Creation of objects in a delegated organizational Refer to the Build Note in Chapter 9 under the section "Creating the will be available to this user.

272 Scenario specific organizational units in the corp.woodgrovebank.com is

Resource unit (OU) structure Target OU Structure and Delegation " of the Implementation Guide . 3. Click on Computer and create a new Computer object.

functioning.

Domains 4. Verify that the Computer object was created successfully.



5. Repeat this process for the Migrated Objects\WNB-ACCT-

ROW\Servers OU.

6. Remove the "dummy" Computer object when done and verify that

the object is deleted from the domain.

7. Repeat this process for ADMT_WNB-RES-A on WNB-ADMT-01.

8. Repeat this process for ADMT_WNB-RES-SYD on WNB-ADMT-02

and select a domain controller in the SYD site in the

corp.woodgrovebank.com domain.





Page 11 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps

Chapter 10: The purpose of this test is to validate that the SID Mapping file is in Refer to the Build Note in Chapter 10 under the section "Generating a 1. Locate and open the SID Mapping file. Verify that the file is in the

273 Restructuring Scenario SID Mapping file creation

the correct format. SID Mapping File" of the Implementation Guide . following format: -,\.

Resource

1. From the ADMT workstation (WNB-ADMT-01), locate and open the

migration.log file for the last process and verify that there are no

errors produced by the Security Translation Wizard.

2. Log on to the workstation(s) that were selected for the above

Chapter 10: The purpose of this test is to validate that no errors are found in the

process as the local Administrator. Open the local Administrators

Restructuring log files produced by the Security Translation Wizard ADMT process Refer to the Build Note in Chapter 10 under the section "Performing

274 Scenario Security Translation (Workstation - Pilot) group and verify that the following groups exist: WNB-ACCT-

Resource and that the security translation is visible on the workstations that the Pilot Workstation Security Translation" of the Implementation Guide .

A\Domain Admins, WNB-ACCT-A\Windows Server Admin, WNB-

Domains were selected for the above process.

ACCT-A\_Domain Admins, WNB-ACCT-

ROW\Domain Admins, WNB-ACCT-ROW\Windows Server Admin.

3. Repeat this process for all resource domains (WNB-ACCT-ROW,

WNB-RES-A, and WNB-RES-SYD).





1. From the ADMT workstation (WNB-ADMT-01), locate and open the

migration.log file for the last process and verify that there are no

errors produced by the ADMT Command Line Security Translation

process.

Chapter 10: The purpose of this test is to validate that no errors are found in the 2. Log on to the workstation(s) that were selected for the above

Refer to the Build Note in Chapter 10 under the section "ADMT v2

Restructuring log files produced by the ADMT Command Line Security Translation process as the local Administrator. Open the local Administrators

275 Scenario Security Translation (Workstation - Actual) Command Line Workstation Security Translation" of the Implementation

Resource process and that the security translation is visible on the workstations group and verify that the following groups exist: WNB-ACCT-

Guide .

Domains that were selected for the above process. A\Domain Admins, WNB-ACCT-A\Windows Server Admin, WNB-

ACCT-A\_Domain Admins, WNB-ACCT-

ROW\Domain Admins, WNB-ACCT-ROW\Windows Server Admin.

3. Repeat this process for all resource domains (WNB-ACCT-ROW,

WNB-RES-A, and WNB-RES-SYD).



1. From the ADMT workstation (WNB-ADMT-01), locate and open the

migration.log file for the last process and verify that there are no

errors produced by the Computer Migration Wizard.

2. From the workstation(s) that were selected for the above process,

verify at the Windows Logon dialog box that the WNB-ACCT-A

domain is listed in the domain combo box.

3. Log on to the workstation(s) that were selected for the above

process as the local Administrator. Open the Event Viewer and verify,

The purpose of this test is: to validate that no errors are found in the at approximately the time of migration, that the following entries exist:

log files produced by the Computer Migration Wizard ADMT process, "The Event log service was stopped" and "The Event log service was

to validate that the WNB-ACCT-A domain is visible in the domain started".

combo box on the Windows Logon dialog box, to validate that the 4. From step 3, verify that the workstation(s) membership is to the

workstation(s) was rebooted for the domain membership to take WNB-ACCT-A domain. NOTE: The way in which to do this will vary

effect, to validate that the workstation(s) domain membership is depending on the operating system.

updated, to validate that the user associated with the workstation(s) 5. From step 4, log on to the workstation(s) with the associated user

Chapter 10:

can log on with their newly migrated WNB-ACCT-A account, to to the WNB-ACCT-A domain and verify that this operation is

Restructuring Refer to the Build Note in Chapter 9 under the section "Performing the

276 Scenario Computer Migration (Pilot) validate that the user associated with the workstation(s) has successful.

Resource Pilot Computer Migration on Workstations " of the Implementation Guide .

maintained their password, to validate that the user associated with 6. From step 5, change the password of the user logging on and

Domains

the workstation(s) can change their password, to validate that the verify that the previous password was accepted and that the

user associated with the workstation(s) has maintained their user password change was successful.

environment (profile), to validate that the migration of computer 7. From step 6, verify that the user's profile was maintained.

objects occurred and that the computers reside in the correct OU in 8. Open the Active Directory Users and Computers MMC snap-in on

the Active Directory, to validate that the computers retained their NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

correct name, and to validate that the source domain computers are expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

not affected by the migration. select the Computers OU, refresh the OU, and verify the computer

accounts were migrated.

9. From step 8, verify that each of the migrated group account objects

has retained its Name.

10. Open the Server Manager on NYC-WO-DC-01 and verify that the

migrated computer account objects still exist in the WNB-ACCT-ROW

domain.

11. Repeat this process for all resource domains (WNB-ACCT-ROW,

WNB-RES-A, and WNB-RES-SYD).









Page 12 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps

1. From the ADMT workstation (WNB-ADMT-01), locate and open the

migration.log file for the last process and verify that there are no

errors produced by the ADMT Command Line Computer Migration

process.

2. From the workstation(s) that were selected for the above process,

verify at the Windows Logon dialog box that the WNB-ACCT-A

domain is listed in the domain combo box.

3. Log on to the workstation(s) that were selected for the above

The purpose of this test is: to validate that no errors are found in the process as the local Administrator. Open the Event Viewer and verify,

log files produced by the ADMT Command Line Computer Migration at approximately the time of migration, that the following entries exist:

process, to validate that the WNB-ACCT-A domain is visible in the "The Event log service was stopped" and "The Event log service was

domain combo box on the Windows Logon dialog box, to validate that started."

4. From step 3, verify that the workstation(s) membership is to the

the workstation(s) was rebooted for the domain membership to take

effect, to validate that the workstation(s) domain membership is WNB-ACCT-A domain. NOTE: The way in which to do this will vary

depending on the operating system.

updated, to validate that the user associated with the workstation(s)

Chapter 10: 5. From step 4, log on to the workstation(s) with the associated user

can log on with their newly migrated WNB-ACCT-A account, to

Restructuring Refer to the Build Note in Chapter 9 under the section "ADMT v2 to the WNB-ACCT-A domain and verify that this operation is

277 Scenario Computer Migration (Actual) validate that the user associated with the workstation(s) has

Resource Command Line Computer Migration " of the Implementation Guide . successful.

maintained their password, to validate that the user associated with

Domains 6. From step 5, change the password of the user logging on and

the workstation(s) can change their password, to validate that the

verify that the previous password was accepted and that the

user associated with the workstation(s) has maintained their user

password change was successful.

environment (profile), to validate that the migration of computer

7. From step 6, verify that the user's profile was maintained.

objects occurred and that the computers reside in the correct OU in

8. Open the Active Directory Users and Computers MMC snap-in on

the Active Directory, to validate that the computers retained their

NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

correct name, and to validate that the source domain computers are

expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

not affected by the migration.

select the Computers OU, refresh the OU, and verify the computer

accounts were migrated.

9. From step 8, verify that each of the migrated group account objects

has retained its Name.

10. Open the Server Manager on NYC-WO-DC-01 and verify that the

migrated computer account objects still exist in the WNB-ACCT-ROW

domain.

11. Repeat this process for all resource domains (WNB-ACCT-ROW,

WNB-RES-A, and WNB-RES-SYD).

1. From the ADMT workstation (WNB-ADMT-01), locate and open the

migration.log file for the last process and verify that there are no

errors produced by the Security Translation Wizard.

2. Log on to the member server(s) selected for the above process as

the local Administrator. Open the local Administrators group and

verify that the following groups exist: WNB-ACCT-A\Domain Admins,

WNB-ACCT-A\Windows Server Admin, WNB-ACCT-A\_Domain Admins, WNB-ACCT-ROW\Domain Admins,

WNB-ACCT-ROW\Windows Server Admin.

3. Log on to the member server(s) selected for the above process as

the Administrator for its associated domain. Open Windows Explorer,

The purpose of this test is to validate that no errors are found in the navigate to a shared folder, right-click on the shared folder, select

Chapter 10: Properties, click on the Security tab, click on Permissions, and verify

log files produced by the Security Translation Wizard ADMT process

Restructuring Refer to the Build Note in Chapter 9 under the section "Performing the that the following groups exist: WNB-ACCT-A\Domain Admins, WNB-

278 Scenario Security Translation (Member Server - Pilot) and that the security translation (group memberships, network

Resource Pilot Member Server Security Translation " of the Implementation Guide . ACCT-A\Windows Server Admin, WNB-ACCT-A\_Domain Admins, WNB-ACCT-ROW\Domain Admins, WNB-

the above process.

ACCT-ROW\Windows Server Admin.



4. From step 3, Open Windows Explorer, navigate to a shared folder,

locate a file, right-click on said file, select Properties, click on the

Security tab, click on Permissions, and verify that the following groups

exist: WNB-ACCT-A\Domain Admins, WNB-ACCT-A\Windows Server

Admin, WNB-ACCT-A\_Domain Admins,

WNB-ACCT-ROW\Domain Admins, WNB-ACCT-ROW\Windows

Server Admin.

5. Repeat this process for all resource domains (WNB-ACCT-ROW,

WNB-RES-A, and WNB-RES-SYD).









Page 13 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps

1. From the ADMT workstation (WNB-ADMT-01), locate and open the

migration.log file for the last process and verify that there are no

errors produced by the ADMT Command Line Security Translation

process.

2. Log on to the member server(s) selected for the above process as

the local Administrator. Open the local Administrators group and

verify that the following groups exist: WNB-ACCT-A\Domain Admins,

WNB-ACCT-A\Windows Server Admin, WNB-ACCT-A\_Domain Admins, WNB-ACCT-ROW\Domain Admins,

WNB-ACCT-ROW\Windows Server Admin.

3. Log on to the member server(s) selected for the above process as

The purpose of this test is to validate that no errors are found in the the Administrator for its associated domain. Open Windows Explorer,

Chapter 10:

log files produced by the ADMT Command Line Security Translation navigate to a shared folder, right-click on the shared folder, select

Restructuring Refer to the Build Note in Chapter 9 under the section "Performing the

279 Scenario Security Translation (Member Server - Actual) process and that the security translation (group memberships, Properties, click on the Security tab, click on Permissions, and verify

Resource Member Server Security Translation " of the Implementation Guide .

network shares, files) is visible on the member servers that were that the following groups exist: WNB-ACCT-A\Domain Admins, WNB-

Domains

selected for the above process. ACCT-A\Windows Server Admin, WNB-ACCT-A\_Domain Admins, WNB-ACCT-ROW\Domain Admins, WNB-

ACCT-ROW\Windows Server Admin.

4. From step 3, Open Windows Explorer, navigate to a shared folder,

locate a file, right-click on said file, select Properties, click on the

Security tab, click on Permissions, and verify that the following groups

exist: WNB-ACCT-A\Domain Admins, WNB-ACCT-A\Windows Server

Admin, WNB-ACCT-A\_Domain Admins,

WNB-ACCT-ROW\Domain Admins, WNB-ACCT-ROW\Windows

Server Admin.

5. Repeat this process for all resource domains (WNB-ACCT-ROW,

WNB-RES-A, and WNB-RES-SYD).

1. From the ADMT workstation (WNB-ADMT-01), locate and open the

migration.log file for the last process and verify that there are no

errors produced by the Computer Migration Wizard.

2. From the member server(s) that were selected for the above

process, verify at the Windows Logon dialog box that the WNB-ACCT-

A domain is listed in the domain combo box.

3. Log on to the member server(s) that were selected for the above

process as the local Administrator. Open the Event Viewer and verify,

The purpose of this test is: to validate that no errors are found in the

at approximately the time of migration, that the following entries exist:

log files produced by the Computer Migration Wizard ADMT process,

"The Event log service was stopped" and "The Event log service was

to validate that the WNB-ACCT-A domain is visible in the domain

started."

combo box on the Windows Logon dialog box, to validate that the

Chapter 10: 4. From step 3, verify that the member server(s) membership is to the

member server(s) was rebooted for the domain membership to take

Restructuring Refer to the Build Note in Chapter 9 under the section "Performing the WNB-ACCT-A domain. NOTE: The way in which to do this will vary

280 Scenario Computer Migration (Member Server - Pilot) effect, to validate that the member server(s) domain membership is

Resource Pilot Member Server Computer Migration " of the Implementation Guide . depending on the operating system.

updated, to validate that the migration of computer objects occurred

Domains 5. Open the Active Directory Users and Computers MMC snap-in on

and that the member server(s) reside in the correct OU in the Active

NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

Directory, to validate that the member server(s) retained their correct

expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

name, and to validate that the source domain member server(s) are

select the Servers OU, refresh the OU, and verify the computer

not affected by the migration.

accounts were migrated.

6. From step 5, verify that each of the migrated group account objects

has retained its Name.

7. Open the Server Manager on NYC-WO-DC-01 and verify that the

migrated computer account objects still exist in the WNB-ACCT-ROW

domain.

8. Repeat this process for all resource domains (WNB-ACCT-ROW,

WNB-RES-A, and WNB-RES-SYD).

1. From the ADMT workstation (WNB-ADMT-01), locate and open the

migration.log file for the last process and verify that there are no

errors produced by the ADMT Command Line Computer Migration

process.

2. From the member server(s) that were selected for the above

process, verify at the Windows Logon dialog box that the WNB-ACCT-

A domain is listed in the domain combo box.

3. Log on to the member server(s) that were selected for the above

The purpose of this test is: to validate that no errors are found in the process as the local Administrator. Open the Event Viewer and verify,

log files produced by the ADMT Command Line Computer Migration at approximately the time of migration, that the following entries exist:

process, to validate that the WNB-ACCT-A domain is visible in the "The Event log service was stopped" and "The Event log service was

domain combo box on the Windows Logon dialog box, to validate that started".

Chapter 10:

the member server(s) was rebooted for the domain membership to

Restructuring Refer to the Build Note in Chapter 9 under the section "Performing the

281 Scenario Computer Migration (Member Server - Actual) take effect, to validate that the member server(s) domain membership

Resource Member Server Computer Migration " of the Implementation Guide .

is updated, to validate that the migration of computer objects occurred

Domains

and that the member server(s) reside in the correct OU in the Active

Page 14 MSA DOM Test Cases and Results Final.xls

Directory, to validate that the member server(s) retained their correct

name, and to validate that the source domain member server(s) are

not affected by the migration.

The purpose of this test is: to validate that no errors are found in the

Domain Migration and Consolidation

log files produced by the ADMT Command Line Computer Migration Test Cases

process, to validate that the WNB-ACCT-A domain is visible in the

Test Case ID Test Area Test Type Test Title Test Purpose box on the Windows Logon dialog box, to validate that Dependencies

domain combo Test Steps

Chapter 10:

the member server(s) was rebooted for the domain membership to 4. From step 3, verify that the member server(s) membership is to the

Restructuring Refer to the Build Note in Chapter 9 under the section "Performing the

281 Scenario Computer Migration (Member Server - Actual) take effect, to validate that the member server(s) domain membership WNB-ACCT-A domain. NOTE: The way in which to do this will vary

Resource Member Server Computer Migration " of the Implementation Guide .

is updated, to validate that the migration of computer objects occurred depending on the operating system.

Domains

and that the member server(s) reside in the correct OU in the Active 5. Open the Active Directory Users and Computers MMC snap-in on

Directory, to validate that the member server(s) retained their correct NYC-WA-DC-05, expand the corp.woodgrovebank.com node,

name, and to validate that the source domain member server(s) are expand the Migrated Objects OU, expand the WNB-ACCT-ROW OU,

not affected by the migration. select the Servers OU, refresh the OU, and verify the computer

accounts were migrated.

6. From step 5, verify that each of the migrated group account objects

has retained its Name.

7. Open the Server Manager on NYC-WO-DC-01 and verify that the

migrated computer account objects still exist in the WNB-ACCT-ROW

domain.

8. Repeat this process for all resource domains (WNB-ACCT-ROW,

WNB-RES-A, and WNB-RES-SYD).

Post-process



For the specified computer, as documented in the network topology

The servers designated as Exchange Messaging Servers are built 1. Open the Exchange Server Administrator to verify the existence of

170 Core Services BVT Exchange Server layout diagram provided by dev, the purpose of this test is to validate

and configured accordingly. the Exchange Server service on the local computer.

that the Exchange Messaging Service is installed and functioning.

For the specified computer, as documented in the network topology

The servers designated as File Servers are built and configured 1. Open a command window, type 'net share', and press 'Enter'.

172 Core Services BVT File Server layout diagram provided by dev, the purpose of this test is to validate

accordingly. 2. Verify that non-administrative shares exist in the output above.

that the File Service is installed and functioning.

The purpose of this test is to validate that the IP address for each 1. Open a command window, type 'ipconfig /all', and press 'Enter'.

computer (client) provided by the lab is consistent with the IP address All servers, clients, and network services are online and functioning 2. Compare the IP address from step 1 with the IP address

173 Core Services BVT IP address assignment (client)

assignment documented in the network topology layout diagram correctly. assignment for the specified computer in the network topology layout

provided by dev. diagram provided by dev.

For the specified computer, as documented in the network topology

The servers designated as Print Servers are built and configured 1. Open the Printers Control Panel applet and verify that at least one

175 Core Services BVT Print Server layout diagram provided by dev, the purpose of this test is to validate

accordingly. printer is installed on the local computer.

that the Print Service is installed and functioning.

1. Open a command window, type 'ping ' (where

computer name is a FQDN of another computer on the network) and

The purpose of this test is to validate that the DNS Client service is All servers, clients, and network services are online and functioning

176 Core Services BVT DNS Client press 'Enter'. Example: foo.bar.com, where 'foo' is the computer

functioning. correctly.

name in the 'bar.com' domain.

2. Verify that a response is received from step 1.

1. Open a command window, type 'ipconfig /all', and press 'Enter'.

2. Verify that the following items from the output above are present:

The purpose of this test is to validate that the DHCP Client service is All servers, clients, and network services are online and functioning

177 Core Services BVT DHCP Client IP Address, Subnet Mask, Default Gateway, DHCP Server, DNS

functioning. correctly.

Servers, Primary WINS Server, Secondary WINS Server, Lease

Obtained, and Lease Expires.

1. From a workstation, open the messaging client.

The purpose of this test is to validate that the Exchange Messaging All servers, clients, and network services are online and functioning 2. Can the messaging client connect to its Exchange Server?

178 Core Services BVT Exchange Messaging Client

Client service is functioning. correctly. 3. Can the messaging client send email?

4. Can the messaging client receive email?

1. Open the DHCP Manager.

The purpose of this test is to validate that the DHCP Scope for each

All servers, clients, and network services are online and functioning 2. Are there any DHCP scopes defined?

181 Core Services BVT DHCP Scope subnet is consistent with the DHCP Scope assignment documented

correctly. 3. Do the DHCP scopes correspond to those defined in the network

in the network topology layout diagram provided by dev.

topology layout diagram provided by dev?

1. From a domain controller within a specific domain, open the Server

The purpose of this test is to validate that the domain membership for Manager, from the View menu select Servers, and verify the domain

each computer provided by the lab is consistent with the naming membership of the servers in the list.

186 Core Services BVT Domain membership All servers and clients are online and functioning correctly.

convention documented in the network topology layout diagram 2. From a domain controller within a specific domain, open the Server

provided by dev. Manager, from the View menu select Workstations, and verify the

domain membership of the workstations in the list.



The purpose of this test is to validate that the IP address for each 1. *** Check the hard coded IP address ***.

computer (server) provided by the lab is consistent with the IP 2. Compare the IP address from step 1 with the IP address

187 Core Services BVT IP address assignment (server) All servers are online and functioning correctly.

address assignment documented in the network topology layout assignment for the specified computer in the network topology layout

diagram provided by dev. diagram provided by dev.









Page 15 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Cases



Test Case ID Test Area Test Type Test Title Test Purpose Dependencies Test Steps



1. From a client on each subnet, open a command window, type

The purpose of this test is to validate that the IP address for the

'ipconfig /all', and press 'Enter'.

router provided by the lab is consistent with the IP address

188 Core Services BVT IP address assignment (router) All network hardware resources are online and functioning correctly. 2. Compare the IP address for the 'Default Gateway' from step 1 with

assignment documented in the network topology layout diagram

the IP address assignment for the specified router in the network

provided by dev.

topology layout diagram provided by dev.





1. Open a command window, type 'ipconfig /all', and press 'Enter'.

The purpose of this test is to validate that a client on any given subnet All servers, clients, and network services are online and functioning 2. Using the output from step 1, type 'ping ', where the

189 Core Services BVT Network connectivity (default gateway)

can communicate with its default gateway. correctly. 'ip address' is the address of the 'Default Gateway'.

3. Verify that a response is received from step 2.





1. Open a command window, type 'ping ', where

The purpose of this test is to validate that a client on any given subnet

190 Core Services BVT Network connectivity (different subnet) All clients are online and functioning correctly. the 'computer name' is the name of a computer on a different subnet.

can communicate with a client of a different subnet.

2. Verify that a response is received from step 1.



The purpose of this test is to validate that the network share are

consistent with the documentation in the functional requirements

provided by dev.

All shares will be ACL’d, by default, to “Everyone: Full Control.”

Shares:

• WNB-RES-A\NYC-WA-FPS-01

1. From each of the computers in the list, open a command window,

• Data

type 'net share', and press 'Enter'.

• Home

The servers designated as File Servers are built and configured 2. Compare the output from step 1 with the list of network shares for

• Directors

213 Core Services BVT Network shares accordingly. Creation of network folder shares has been completed the local computer.

• Profile

within their respective domains. 3. Do all of the shares in the list above exist on their respective FPS

• Apps

Server?

• WNB-RES-SYD\SYD-WS-FPS-01

• Data

• HR

• Apps

• WNB-ACCT-ROW\JNB-WO-FPS-01

• Data

• Apps

The purpose of this test is to validate that the network share

permissions are consistent with the documentation in the functional

requirements provided by dev.

One share, "Directors," on WNB-RES-A\NYC-WA-FPS-01 will be

1. Are all of the shares on the File/Print Servers, with the exception of

ACL’d to WNB-ACCT-ROW\”Directors All: Change” and WNB-ACCT-

the NYC-WA-FPS-01\Directors and SYD-WS-FPS-01\HR shares,

ROW\”Domain Admins: Full Control.”

ACL’d with “Everyone: Full Control”?

One share, "HR," on WNB-RES-SYD\SYD-WS-FPS-01 will be ACL’d

2. Is the NYC-WA-FPS-01\Directors share ACL’d to WNB-ACCT-

to WNB-ACCT-ROW\”Human Resources: Full Control” and WNB-

ROW\”Directors All: Change” and WNB-ACCT-ROW\”Domain

ACCT-ROW\”Domain Admins: Full Control.”

Admins: Full Control”?

Shares: The servers designated as File Servers are built and configured

3. Is the SYD-WS-FPS-01\HR share ACL’d to WNB-ACCT-

• WNB-RES-A\NYC-WA-FPS-01 accordingly. Creation of network folder shares has been completed

ROW\”Human Resources: Full Control” and WNB-ACCT-

216 Core Services BVT Share permissions • Data within their respective domains. Assignment of share permissions has

ROW\”Domain Admins: Full Control”?

• Home been completed as per the functional requirements documented by

4. Can a member from the WNB-ACCT-ROW\”Directors All” group

• Directors dev.

access the NYC-WA-FPS-01\Directors share?

• Profile

5. Can a member from the WNB-ACCT-ROW\”Human Resources”

• Apps

group access the SYD-WS-FPS-01\HR share?

• WNB-RES-SYD\SYD-WS-FPS-01

6. Can a member from the WNB-ACCT-ROW\”Domain Admins”

• Data

group access both the NYC-WA-FPS-01\Directors and the SYD-WS-

• HR

FPS-01\HR share?

• Apps

• WNB-ACCT-ROW\JNB-WO-FPS-01

• Data

• Apps

End









Page 16 MSA DOM Test Cases and Results Final.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

Pre-process

The physical hardware provided by the lab matched the required

161 Computer inventory Pass hardware documented in the network topology layout diagram

provided by dev.

The labels on the physical hardware provided by the lab was

162 Visual computer identification Pass consistent with the naming convention documented in the network

topology layout diagram provided by dev.

The computer name for each computer provided by the lab was

163 Computer identification Pass consistent with the naming convention documented in the network

topology layout diagram provided by dev.

All of the physical hardware provided by the lab had network

164 Network connectivity Pass

connectivity capability.

The role (Domain Controller - PDC) of the specified computer was

165 Computer role (Domain Controller - PDC) Pass consistent with the role documented in the network topology layout

diagram provided by dev.

The role (Domain Controller - BDC) of the specified computer was

166 Computer role (Domain Controller - BDC) Pass consistent with the role documented in the network topology layout

diagram provided by dev.

For the specified computer, as documented in the network topology

167 DNS Server Pass layout diagram provided by dev, the Domain Name System (DNS)

Service was installed and functioning.

For the specified computer, as documented in the network topology

168 WINS Server Pass layout diagram provided by dev, the Windows® Internet Naming

Service (WINS) was installed and functioning.

For the specified computer, as documented in the network topology

169 DHCP Server Pass layout diagram provided by dev, the Dynamic Host Configuration

Protocol (DHCP) Service was installed and functioning.

For the specified computer, as documented in the network topology

170 Exchange Server Pass layout diagram provided by dev, the Exchange Messaging Service

was installed and functioning.

For the specified computer, as documented in the network topology

172 File Server Pass layout diagram provided by dev, the File Service was installed and

functioning.

The IP address, for each computer (client) provided by the lab, was

173 IP address assignment (client) Pass consistent with the IP address assignment documented in the network

topology layout diagram provided by dev.

For the specified computer, as documented in the network topology

175 Print Server Pass layout diagram provided by dev, the Print Service was installed and

functioning.

176 DNS Client Pass The DNS Client service was functioning.

177 DHCP Client Pass The DHCP Client service was functioning.



Page 17 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

178 Exchange Messaging Client Pass The Exchange Messaging Client service was functioning.

179 Network resource (file) Pass A client could access a network resource (file).

180 Network resource (print) Pass A client could access a network resource (print).

The DHCP Scope for each subnet was consistent with the DHCP

181 DHCP Scope Pass Scope assignment documented in the network topology layout

diagram provided by dev.

User accounts were created within the domain(s) as documented in

the functional requirements provided by dev, as is illustrated by the

following list:

• WNB-ACCT-A\user00001 - WNB-ACCT-A\user15000

182 User accounts Pass

• WNB-ACCT-ROW\user14980 - WNB-ACCT-ROW\user22980

• WNB-RES-A\user23001 - WNB-RES-A\user23050

• WNB-MESSAGING\user24001 - WNB-MESSAGING\user24025

• WNB-RES-SYD\user25001 - WNB-RES-SYD\user25005

Computer accounts were created within the domain(s) as documented

183 Computer accounts Pass

in the functional requirements provided by dev.

Global groups were created within the domain(s) as documented in

the functional requirements provided by dev, as is illustrated by the

following list:

• WNB-ACCT-A\grp0001 - WNB-ACCT-A\grp4000

184 Global groups Pass

• WNB-ACCT-ROW\grp3980 - WNB-ACCT-ROW\grp5980

• WNB-RES-A contains no global groups

• WNB-MESSAGING\grp6001 - WNB-MESSAGING\grp6006

• WNB-RES-SYD\grp7001 - WNB-RES-SYD\grp7002

The user(s) were successfully joined to their specified global group(s)

as documented in the functional requirements provided by dev, as is

illustrated by the following list:

• WNB-ACCT-A\user00001 - WNB-ACCT-A\user00100

• Random members of WNB-ACCT-A\grp0001 - grp0050

• Random members of WNB-ACCT-ROW\grp3980 - grp3989

185 Group membership Pass • WNB-ACCT-ROW\user14980 - WNB-ACCT-A\user15080

• Random members of WNB-ACCT-ROW\grp3980 - grp4030

• Random members of WNB-ACCT-A\grp0001 - grp0010

• Each of the above users should be a member of 10 or more groups

• The remainder of the groups will have at least 1 member each, with

a user00001:grp0001 relationship.

• The 'primary' group for each use will remain 'Domain User'.

The domain membership for each computer provided by the lab was

186 Domain membership Pass consistent with the naming convention documented in the network

topology layout diagram provided by dev.





Page 18 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

The IP address, for each computer (server) provided by the lab, was

187 IP address assignment (server) Pass consistent with the IP address assignment documented in the network

topology layout diagram provided by dev.

The IP address, for the router provided by the lab, was consistent with

188 IP address assignment (router) Pass the IP address assignment documented in the network topology layout

diagram provided by dev.

A client on any given subnet could communicate with its default

189 Network connectivity (default gateway) Pass

gateway.

A client on any given subnet could communicate with a client of a

190 Network connectivity (different subnet) Pass

different subnet.

The SVC_Spooler account existed in the WNB-ACCT-ROW domain

204 Service account Pass

as documented in the functional requirements provided by dev.

The Spooler service on WNB-RES-SYD\SYD-WS-FPS-01 was

212 Spooler service Pass

running under the WNB-ACCT-ROW\SVC_Spooler account.

The network shares were consistent with the documentation in the

functional requirements provided by dev.

All shares will be ACL’d, by default, to “Everyone: Full Control.”

Shares:

• WNB-RES-A\NYC-WA-FPS-01

• Data

• Home

• Directors

213 Network shares Pass • Profile

• Apps

• WNB-RES-SYD\SYD-WS-FPS-01

• Data

• HR

• Apps

• WNB-ACCT-ROW\JNB-WO-FPS-01

• Data

• Apps









Page 19 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

The network share permissions were consistent with the

documentation in the functional requirements provided by dev.

One share, "Directors," on WNB-RES-A\NYC-WA-FPS-01 will be

ACL’d to WNB-ACCT-ROW\”Directors All: Change” and WNB-ACCT-

ROW\”Domain Admins: Full Control.”

One share, "HR," on WNB-RES-SYD\SYD-WS-FPS-01 will be ACL’d

to WNB-ACCT-ROW\”Human Resources: Full Control” and WNB-

ACCT-ROW\”Domain Admins: Full Control.”

Shares:

• WNB-RES-A\NYC-WA-FPS-01

• Data

216 Share permissions Pass

• Home

• Directors

• Profile

• Apps

• WNB-RES-SYD\SYD-WS-FPS-01

• Data

• HR

• Apps

• WNB-ACCT-ROW\JNB-WO-FPS-01

• Data

• Apps

The directory replication service was configured and operating

282 Directory replication Pass

successfully.

Process

The DNS Service, post successful installation, had started and its

225 DNS installation on BDC Pass

startup type was Automatic on the new BDC.

The secondary DNS zone was created and replicated on the new

226 Secondary DNS zone creation on BDC Pass

BDC.

Designating the new BDC as the host of the primary

227 Pass The new BDC (NYC-WA-DC-05) was hosting the primary DNS zone.

DNS zone

228 Promote new BDC to the role of PDC Pass The new BDC was successfully promoted to the role of PDC.



229 Directory replication on the new PDC Pass Directory replication was functioning on the newly promoted PDC.

Continued functionality of client logon scripts after The client logon scripts were still functioning after promoting the new

230 Pass

the promotion of a new PDC BDC to the role of PDC.

The ability of clients to log on to the WNB-ACCT-A domain had not

Successful client logon to the WNB-ACCT-A domain

231 Pass been impaired as the result of promoting the new BDC to the role of

after the promotion of a new PDC

PDC.

The ability of clients to change their passwords within the WNB-ACCT-

Successful client password change within the WNB-

232 Pass A domain had not been impaired as the result of promoting the new

ACCT-A domain after the promotion of a new PDC

BDC to the role of PDC.





Page 20 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

There were no errors in the System Log of the Event Viewer on both

233 Domain synchronization prior to taking a BDC offline Pass NYC-WA-DC-03 and NYC-WA-DC-05 after performing domain

synchronization.



234 Modifying the PDC to point to itself for DNS Pass An ‘ipconfig /all’ showed the correct DNS configuration on the PDC.

There were no errors in the Event Viewer for the operating system

In-place upgrade of the PDC for WNB-ACCT-A installation process. There were no errors in the

235 Pass

domain %windir%\setuperr.log file for the operating system installation

process.

The domain corp.woodgrovebank.com was visible using the Active

236 Creation of the corp.woodgrovebank.com domain Pass

Directory Users and Computers admin tool.

Domain Functional Level for the

237 Pass The domain functional level was Windows Server™ 2003 Interim.

corp.woodgrovebank.com domain

Trust relationships were maintained through the

The pre-existing trust relationships were maintained after the upgrade

238 upgrade from Windows NT® 4.0 to Windows Server Pass

and dcpromo process.

2003

DNS was maintained through the upgrade from The woodgrovebank.com zone was maintained after the upgrade and

239 Pass

Windows NT 4.0 to Windows Server 2003 dcpromo process.

Successful client logon to the WNB-ACCT-A domain

240 after the upgrade from Windows NT 4.0 to Windows Pass WNB-ACCT-A users had not lost the ability to log on to the domain.

Server 2003

Domain synchronization after Domain Upgrade There were no errors in the System Log of the Event Viewer on the

241 Pass

Fallback PDC and all BDCs.

The ability of clients to change their passwords within the WNB-ACCT-

Successful client password change within the WNB-

242 Pass A domain had not been impaired as the result of a Domain Upgrade

ACCT-A domain after Domain Upgrade Fallback

Fallback.

Successful client logon to the WNB-ACCT-A domain The ability of clients to log on to the WNB-ACCT-A domain had not

243 Pass

after Domain Upgrade Fallback been impaired as the result of a Domain Upgrade Fallback.

Continued functionality of client logon scripts after a The client logon scripts were still functioning after a Domain Upgrade

244 Pass

Domain Upgrade Fallback Fallback.

NYC-WR-DHCP-02 was hosting the primary DNS zone after a

245 DNS Recovery after a Domain Upgrade Fallback Pass

Domain Upgrade Fallback.

Replication of the corp.woodgrovebank.com zone to The Windows Server 2003 corp.woodgrovebank.com zone was

246 Pass

the down level NT 4.0 DNS Servers created and replicated to the NT 4.0 DNS Servers.

DNS name resolution on NYC-WA-DC-

A client workstation could successfully resolve the DNS lookup of

247 05.corp.woodgrovebank.com from a client Pass

NYC-WA-DC-05.corp.woodgrovebank.com.

workstation

Lbridge replication between the Windows Server 2003 (NYC-WA-DC-

248 LBridge Replication to the NT 4.0 Export Server Pass

05) and the NT 4.0 Export Server (NYC-WA-DC-01) was functioning.









Page 21 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

There were no errors in the Exchange Server Setup Progress.log file

Extending the Active Directory Schema in readiness at the root of the C: drive on NYC-WA-DC-05 after performing after

249 Pass

for Microsoft® Exchange 2003 extending the Active Directory® Schema in readiness for Microsoft

Exchange 2003.

The domain corp.woodgrovebank.com was visible using the Active

Existence of the corp.woodgrovebank.com domain

250 Pass Directory Users and Computers admin tool on all Replica domain

on all Replicas

controllers.



Domain Functional Level for the The domain functional level was Windows Server 2003 Interim on all

251 Pass

corp.woodgrovebank.com domain on all Replicas Replica domain controllers.

Trust relationships were maintained with the The pre-existing trust relationships were maintained with the addition

252 Pass

addition of Replica domain controllers of Replica domain controllers.

Changing the Forest and Domain Functional Level

253 Pass The forest and domain functional level was Windows Server 2003.

for the corp.woodgrovebank.com domain

Decreasing the DHCP lease duration on the NT 4.0 The client workstations renewed their TCP/IP configuration properties

254 Pass

DHCP Servers every 30 minutes.

There were no errors in the Event Viewer for the cluster creation

255 Cluster creation Pass

process.

All DHCP cluster resources (DHCP Services IP Address, DHCP

256 Cluster Resources (DHCP) Pass Services Name, Disk E:, and NYC-WA-DHCP01) were present and

online.

All WINS cluster resources (WINS Services IP Address, WINS

257 Cluster Resources (WINS) Pass Services Name, Disk F:, and NYC-WA-WINS01) were present and

online.

258 Adding DHCP Scopes to the cluster Pass The DHCP scopes were visible and are configured appropriately.



259 DHCP Scope Authorization Pass The DHCP Server had been authorized.

260 DHCP Scope Activation Pass All scopes had been activated.

All scopes had been deactivated on all DHCP Servers: NYC-WR-

261 DHCP Scope Deactivation Pass

DHCP-01, NYC-WR-DHCP-02, and SYD-WS-FPS-01.

Renewal of TCP/IP configuration properties from The client workstations received new TCP/IP configuration properties

262 Pass

Windows Server 2003 DHCP Server from the new DHCP Server resource.



WINS database replication to the Windows Server Replication of the WINS database from the Windows NT 4.0 WINS

263 Pass

2003 WINS Server Server(s) to the Windows Server 2003 WINS Server occurred.

The organizational unit (OU) structure had been replicated to the other

264 Organizational Unit structure replication Pass

domain controllers.

No errors were found in the log files produced by the Service Account

265 Identifying service accounts Pass

Migration Wizard ADMT process.









Page 22 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results



No errors were found in the log files produced by the Group Account

Migration Wizard ADMT process, the migration of group objects

occurred, the groups did reside in the correct OU in the Active

Directory, no group memberships existed, and the groups retained

266 Group Migration (Pilot) Pass

their correct name and description. For groups that existed in both the

WNB-ACCT-A and WNB-ACCT-ROW domains, the groups were

prefixed with WO-. Group SIDHistory was retained and the source

domain groups were not affected by the migration.



No errors were found in the log files produced by the ADMT

Command Line Group Migration process, the migration of group

objects occurred, the groups did reside in the correct OU in the Active

Directory, no group memberships exist and the groups retained their

267 Group Migration (Actual) Pass

correct name and description. For groups that existed in both the WNB-

ACCT-A and WNB-ACCT-ROW domains, the groups were prefixed

with WO-. Group SIDHistory was retained and the source domain

groups were not affected by the migration.



No errors were found in the log files produced by the User Account

Migration Wizard ADMT process, the migration of user objects

occurred, the users did reside in the correct OU in the Active

Directory, the user objects were disabled, and the users retained their

268 User Migration (Pilot) Pass correct name and description. For users that existed in both the WNB-

ACCT-A and WNB-ACCT-ROW domains, the users were not

migrated. User SIDHistory was retained, the source domain users

were not affected by the migration, the users' group membership was

migrated, and the users' passwords were migrated.



No errors were found in the log files produced by the ADMT

Command Line User Account Migration process, the migration of user

objects occurred, the users did reside in the correct OU in the Active

Directory, the user objects were disabled, and the users retained their

269 User Migration (Actual) Pass correct name and description. For users that existed in both the WNB-

ACCT-A and WNB-ACCT-ROW domains, the users were not

migrated. User SIDHistory was retained, the source domain users

were not affected by the migration, the users' group membership was

migrated, and the users' passwords were migrated.

Updating the SIDHistory of accounts in multiple No errors were produced during the process and user SIDHistory was

270 Pass

domains migrated.

The two-way trusts setup between corp.woodgrovebank.com and the

271 Two-way trust creation to resource domains Pass resource domains (WNB-ACCT-ROW, WNB-RES-A, and WNB-RES-

SYD) were functioning.



Page 23 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

The delegation of control for specific OUs in the

272 Creation of objects in a delegated OU structure Pass

corp.woodgrovebank.com was functioning.

273 SID Mapping file creation Pass The Security ID (SID) Mapping file was in the correct format.

No errors were found in the log files produced by the Security

274 Security Translation (Workstation - Pilot) Pass Translation Wizard ADMT process and the security translation was

visible on the workstations that were selected for this process.

No errors were found in the log files produced by the ADMT

Command Line Security Translation process and the security

275 Security Translation (Workstation - Actual) Pass

translation was visible on the workstations that were selected for this

process.

No errors were found in the log files produced by the Computer

Migration Wizard ADMT process, the WNB-ACCT-A domain was

visible in the domain combo box on the Windows Logon dialog box,

the workstation(s) were rebooted for the domain membership to take

effect, and the workstation(s) domain membership was updated. The

user associated with the workstation(s) could log on with their newly

migrated WNB-ACCT-A account, the user associated with the

276 Computer Migration (Pilot) Pass

workstation(s) had maintained their password, the user associated

with the workstation(s) could change their password, and the user

associated with the workstation(s) had maintained their user

environment (profile). The migration of computer objects occurred, the

computers did reside in the correct OU in the Active Directory, the

computers retained their correct name and the source domain

computers were not affected by the migration.



No errors were found in the log files produced by the ADMT

Command Line Computer Migration process, the WNB-ACCT-A

domain was visible in the domain combo box on the Windows Logon

dialog box, the workstation(s) were rebooted for the domain

membership to take effect, and the workstation(s) domain membership

was updated. The user associated with the workstation(s) could log on

with their newly migrated WNB-ACCT-A account, the user associated

277 Computer Migration (Actual) Pass

with the workstation(s) had maintained their password, the user

associated with the workstation(s) could change their password, and

the user associated with the workstation(s) had maintained their user

environment (profile). The migration of computer objects occurred, the

computers did reside in the correct OU in the Active Directory, the

computers retained their correct name, and the source domain

computers were not affected by the migration.









Page 24 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

No errors were found in the log files produced by the Security

Translation Wizard ADMT process and the security translation (group

278 Security Translation (Member Server - Pilot) Pass

memberships, network shares, and files) was visible on the member

servers that were selected for this process.

No errors were found in the log files produced by the ADMT

Command Line Security Translation process and the security

279 Security Translation (Member Server - Actual) Pass

translation (group memberships, network shares, files) was visible on

the member servers that were selected for this process.



No errors were found in the log files produced by the Computer

Migration Wizard ADMT process, the WNB-ACCT-A domain was

visible in the domain combo box on the Windows Logon dialog box,

the member server(s) were rebooted for the domain membership to

280 Computer Migration (Member Server - Pilot) Pass take effect, and the member server(s) domain membership was

updated. The migration of computer objects occurred, the member

server(s) did reside in the correct OU in the Active Directory, the

member server(s) retained their correct name, and the source domain

member server(s) were not affected by the migration.

No errors were found in the log files produced by the ADMT

Command Line Computer Migration process, the WNB-ACCT-A

domain was visible in the domain combo box on the Windows Logon

dialog box, the member server(s) were rebooted for the domain

membership to take effect, and the member server(s) domain

281 Computer Migration (Member Server - Actual) Pass

membership was updated. The migration of computer objects

occurred, the member server(s) did reside in the correct OU in the

Active Directory, the member server(s) retained their correct name,

and the source domain member server(s) were not affected by the

migration.

Post-process

For the specified computer, as documented in the network topology

170 Exchange Server Pass layout diagram provided by dev, the Exchange Messaging Service

was installed and functioning.

For the specified computer, as documented in the network topology

172 File Server Pass layout diagram provided by dev, the File Service was installed and

functioning.

The IP address, for each computer (client) provided by the lab, was

173 IP address assignment (client) Pass consistent with the IP address assignment documented in the network

topology layout diagram provided by dev.

For the specified computer, as documented in the network topology

175 Print Server Pass layout diagram provided by dev, the Print Service was installed and

functioning.





Page 25 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

176 DNS Client Pass The DNS Client service was functioning.

177 DHCP Client Pass The DHCP Client service was functioning.

178 Exchange Messaging Client Pass The Exchange Messaging Client service was functioning.

The DHCP Scope for each subnet was consistent with the DHCP

181 DHCP Scope Pass Scope assignment documented in the network topology layout

diagram provided by dev.

The domain membership for each computer provided by the lab was

186 Domain membership Pass consistent with the naming convention documented in the network

topology layout diagram provided by dev.

The IP address, for each computer (server) provided by the lab, was

187 IP address assignment (server) Pass consistent with the IP address assignment documented in the network

topology layout diagram provided by dev.

The IP address, for the router provided by the lab, was consistent with

188 IP address assignment (router) Pass the IP address assignment documented in the network topology layout

diagram provided by dev.

A client on any given subnet could communicate with its default

189 Network connectivity (default gateway) Pass

gateway.

A client on any given subnet could communicate with a client of a

190 Network connectivity (different subnet) Pass

different subnet.

The network shares were consistent with the documentation in the

functional requirements provided by dev.

All shares will be ACL’d, by default, to “Everyone: Full Control”.

Shares:

• WNB-RES-A\NYC-WA-FPS-01

• Data

• Home

• Directors

213 Network shares Pass • Profile

• Apps

• WNB-RES-SYD\SYD-WS-FPS-01

• Data

• HR

• Apps

• WNB-ACCT-ROW\JNB-WO-FPS-01

• Data

• Apps









Page 26 MSA DOM Test Cases and Results.xls

Domain Migration and Consolidation Test Case Results



Test Case ID Test Title Pass/Fail Test Case Results

The network share permissions were consistent with the

documentation in the functional requirements provided by dev.

One share, "Directors," on WNB-RES-A\NYC-WA-FPS-01 will be

ACL’d to WNB-ACCT-ROW\”Directors All: Change” and WNB-ACCT-

ROW\”Domain Admins: Full Control.”

One share, "HR," on WNB-RES-SYD\SYD-WS-FPS-01 will be ACL’d

to WNB-ACCT-ROW\”Human Resources: Full Control” and WNB-

ACCT-ROW\”Domain Admins: Full Control.”

Shares:

• WNB-RES-A\NYC-WA-FPS-01

• Data

216 Share permissions Pass

• Home

• Directors

• Profile

• Apps

• WNB-RES-SYD\SYD-WS-FPS-01

• Data

• HR

• Apps

• WNB-ACCT-ROW\JNB-WO-FPS-01

• Data

• Apps

End









Page 27 MSA DOM Test Cases and Results.xls