Integrating Networks:
Integrating Networks:
As we are presented with a multi-domain Windows NT based network where there are two Primary Domain Controllers (PDC) and these are located along with two Backup Domain Controllers (BDC) under what is referred to as the Administration domain, we assume that we are dealing with the Multiple Master Domain Model. To this regard, WATCH has split their Administration domain into two domains as only one domain is possible per PDC in a Windows NT network. The case study also documents that there are several other domains. Assuming domain in this context continues to refer to a Windows NT domain, and given that there are only two PDCs, these additional domains must be resource domains. It is also assumed that the backup is controlled by a resource domain to provide the necessary trust relationship with the other domains in order to perform backups.
As we have a network with a DNS server and Internet/Intranet servers, it is assumed that the network protocols in use include the TCP/IP protocols. Another assumption is that in the Patient Records Domain, Windows NT is not installed on the AS/400 server. This assumption is made as the case study specifically mentions that data is stored on the AS/400 and the SQL server version is MS SQL 7 SP3. It is further assumed that since the system is outdated, data connectivity is done using Open Database Connectivity (ODBC). Finally, the specifications highlight an immediate need to eliminate the use of paper patient records. However, the patient records at WATCH will not be merged into SHG's database until a later date. Therefore, it is assumed that SHG's wireless patient records and tracking application is compatible with ODBC and that SHG will take responsibility for setting up the application for use by WATCH using their current database and that SHG will provide the palm devices and training on how to use them.
The WATCH Network
Administration Domain
Windows NT servers (PDC 1, PDC 2, BDC 1, BDC 2)
Linux DNS Server
Apache Web server (Intranet)
Apache Web server (Internet)
10 host computers
Bookkeeping Domain
Windows NT Resource Domain server
Oracle Database (accounts payable, payroll and benefits)
50 client machines accessing Oracle database
Billing Domain
Windows NT Resource Domain server
Patient data, accounts receivable
60 client computers
Patient Records Domain
Windows NT Resource Domain server with Microsoft SQL Server 7 SP3
AS/400 server DB2 database
Nursing Domain
Windows NT Resource Domain server
3 hosts in each of 10 nurses stations (total 30 hosts)
12 hosts distributed around hospital
Backup Domain
Windows NT Resource Domain server
DLT tape library unit
The SHG Network
- Microsoft Windows 2000/2003 Active Directory
- DB3 database on mainframes
Immediate Requirements for WATCH to SHG Network Merge
- Centralize administration domain into SHG Active Directory
- Eliminate paper patient records by utilizing wireless application at WATCH
Requirements for Presentation
- Explain how to integrate the existing WATCH networking standards, protocols, and access methods.
- The billing department, intranet server, and Internet server will be migrated later, but for now, your team needs only the migration plans for the administrative and bookkeeping functions.
Presentation Overview
The current WATCH network maintains account on two domains. These domains are Admin1 and Admin2. Each has a PDC and a BDC. All user accounts for the network are held in these domains. The resources specific to each department or function are maintained on separate resource domains. Therefore, the Multiple Master Domain Model is used for this network with each resource domain trusting each of the two master account domains. In addition each master domain has a one-way trust with the other (Cooper, Maione, & Bragg, 2002, p. 164).
The customer requirements specify that the billing department will remain untouched and only bookkeeping and administration functions will be migrated. Therefore, the resource domain and accounts will remain on Windows NT for all but bookkeeping and administration. To accommodate this, the first step will be for all billing, nursing, patient record and backup computer and user accounts will be moved to domain Admin1. Meanwhile all other user and computer accounts (Administration and Bookkeeping) will be migrated to domain Admin2. This will allow us to keep the billing department running without disruption by maintaining the current protocols and access standards.
The next step will require configuration of the WATCH network to be accessible by the SHG network. As the WATCH network is already connected to the Internet we have public IP addresses. The Wide Area Network (WAN) connectivity must be suitable for the data transfer requirements. We will continue to standardize on TCP/IP protocols.
We will then upgrade the Admin2 PDC and BDC to Windows 2003 and install into the SHG AD. To do this we will need to install the operating system, run DCPROMO to create an Active Directory, upgrade the WINS database and the DHCP database (Kouti & Seitsonen, 2004, p 78) and then merge with the SHG Active Directory Forest. The bookkeeping resource server will also be migrated to Windows 2003. However, the other resource domains will remain untouched other than setting trust relationships only with Admin2 domain as they will remain on the WATCH network for now.
References
Cooper, J. , Maione, D. , & Bragg, R. (2002). MCSE Supporting and Maintaining a Windows NT® Server 4.0 Network. New York, NY: New Riders Publishing.
Kouti, S. , & Seitsonen, M. (2004). Inside Active Directory Second Edition. Boston, MA: Addison-Wesley Professional.
