Windows 2000 Server
Your network is configured as shown in the exhibit. "Engineering! and Salesl have DHCP installed up them." All the servers are Windows 2000 Server computers that use TCP/IP as the only network protocol. The sales department uses one subnet and has servers named Salesl and Sales2. The engineering department uses another subnet and has servers named Engineeringl and Engineering2. Salesl and Engineeringl are configured to act as DHCP servers. The router that joins the two subnets is not RFC 1542 compliant and does not support DHCP/BOOTP relay. You want to allow Salesl and Engineeringl to support client computers on each other's subnets. What should you do?
None of above
Configure Engineering2 and Sales2 as DHCP servers without any scopes
On Engineering2 and Sales2, install and configure the DHCP Relay Agent service
On Engineering2 and Sales2, install Routing and Remote Access, and configure RIP as a routing protocol
Set the router option in the DHCP Scopes to 192.168.2.1 for Engineeringl and 192.168.1.1 for Salesl
Configure the Windows 2000 file servers, Windows 2000 print servers, Windows 2000 professional computers and Windows 2000 file servers to block unsigned drivers
Configure a Group policy for the Default Domain Controller to block all unsigned drivers
Configure a Group policy for the Domain that blocks all unsigned drivers
Start the computer by using Windows 2000 Server computer CD-ROM and choose tools to repair the installation. Select recovery console and copy the NTLDR file on the CD-ROM to the root of the system vol
None of above
Start the computer by using the Windows 2000 server CD- ROM, choose to reinstall. When the installation is complete copy the NTLDR to the root of the boot volume
Start the computer by using Windows 2000 bootable floppy disk. Run the file signature verification utility
Start the computer by using the Windows 2000 bootable floppy disk. From a command prompt run the sfc/scanboot command