tthree.docx - Running Head ELearning Windows Server Infrastructure Redesign and Upgrade Essay Author Institution Running Head ELearning Windows Server

tthree.docx - Running Head ELearning Windows Server...

This preview shows page 1 - 4 out of 8 pages.

Running Head: ELearning Windows Server Infrastructure Redesign and Upgrade Essay Author Institution
Image of page 1
Running Head: ELearning Windows Server Infrastructure Redesign and Upgrade using scope information between the servers and failover relationships. Through load sharing, the two servers will be able to lease addresses and facilitate continuity if one of the servers fails. The DHCP split-scope will be configured to address all requirements pertaining fault- tolerance. The split scope will be set at 80/20 which allows the primary server to maintain DHCP leases for at least 80 percent of the total number of IP addresses within the specified range. If the central server has failed, the secondary server takes over and continues with the leasing of the IP addresses. Also, the DHCP interoperability will also be enabled providing further security for updates and host record registration. The DHCP interoperability will be configured with Network Access Protocol (NAP) that will give extra protection to the outdated computers on the network. The other important aspect of NAP is that it can provide automatic updates for antivirus programs, antispyware and can also automatically enable firewall for all network connections. Configuring the RRAS server with DHCP will allow all the client computers to connect remotely with the same IP address and then release the assigned IP address automatically when it loses its connection. The DCHP interoperability will also be configured with IPAM allowing the creation of group policies that will force the DHCP servers to connect to it for prompt monitoring and maintenance.
Image of page 2
Running Head: ELearning Windows Server Infrastructure Redesign and Upgrade Domain Name System One of the core principles to observe when coming up with a name resolution strategy is that all the names used must be easy to remember allowing the network users access to computers without any issues (Microsoft, 2016). To ensure scalability, the network administrator should consider distributing the workload of the name resolution across multiple servers and databases. All names should be kept consistent at all times to allow easy access to the various network resources. For fault-tolerance, efficient replication, and security, the administrator will
Image of page 3
Image of page 4

You've reached the end of your free preview.

Want to read all 8 pages?

  • Fall '09
  • Lauer

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture