6.9.5 Verifying that DCDB
Replication Was Successful
6.9.5 Verifying that DCDB
Replication Was Successful
At this point, the PDC (\\DC01) is still at the original software level. However, the new BDC (\\DC02) has been migrated to OS/2 Warp Server for e-business.
The next step (shown in Figure 121) involves changing
the LAN Server roles of both the PDC and BDC. Changing LAN Server roles is a
straightforward matter. First, the PDC (\\DC01) should be demoted to either a
Backup or Member server. Next, the BDC (\\DC02) should be promoted to Domain
Controller. The changes should occur in that order. Typically, this will be
done during off-peak hours.
Figure 121: Changing Server Roles
It is very useful to have some simple command files prepared in advance of this task. It speeds up the role change and allows you to think about other things rather than having to remember the correct syntax to use.
The command files in Figure 122 and Figure 123 illustrate the steps needed to change server roles in each direction. They will also run as simple batch programs.
The command file BU.CMD, when run on the PDC, demotes
it to a Backup DC. If you want to change the role to an Additional Server, then
the /ROLE keyword should be changed to MEMBER rather than
BACKUP. Everything else stays the same.
@ECHO OFF NET STOP NETLOGON NET STOP DCDBREPL NET ACCOUNTS /ROLE:BACKUP NET START DCDBREPL NET START NETLOGON |
The command file PR.CMD, when run on the BDC,
promotes it to the role of Primary DC.
@ECHO OFF NET STOP NETLOGON NET STOP DCDBREPL NET ACCOUNTS /ROLE:PRIMARY NET START DCDBREPL NET START NETLOGON |
| User Logon Considerations |
|---|
|
It is extremely important that logon profiles (such as PROFILE.CMD, PROFILE.BAT and other administrator-written logon scripts) do not contain hard-coded paths pointing to directories on specific servers. If this is true, then users will experience problems during logon. For this reason, we recommend that, prior to migration, an audit of user logon profiles and scripts is completed. This preparation can be of vital help in avoiding unnecessary workload immediately following migration. |
The complete installation process described above, starting in Section 6.9.1 Installing OS/2 Warp Server for e-business, lends itself perfectly to the pristine installation of \\DC01 with OS/2 Warp Server for e-business.
After installation, the server can be re-introduced to the network as a backup domain controller as described in Section 6.9.2 Adding the Backup Domain Controller to the Network.
After that step, domain D01 will have a functioning PDC (\\DC02) and BDC (\\DC01), both installed with OS/2 Warp Server for e-business. When the two freshly installed servers are replicating the DCDB properly, the first phase of the domain migration is complete.
In the next phase, we turn our attention to the file server.
6.11 Step 3: Migrating
the File Server