You have finished installing Windows Server 2012 R2 on the new server for CSM Te

Question

You have finished installing Windows Server 2012 R2 on the new server for CSM Tech. Next, you need to decide what to name the server and how it will participate in the existing domain: as a domain controller, a member server, or a stand-alone server. The server will be named CSM-Server1-DC and located near the existing server in the equipment closet. List the postinstallation tasks you must perform on this server, including details on the server name and its role in the domain (if any). Don’t include installing specific server roles just yet.

Explanation / Answer

Logon using an account with administrative privileges on the Server Core system. At the Windows Server 2012 Server Core Command Prompt, type sconfig.cmd and press Enter to start the Server Configuration Tool. Type 8 and press Enter to select Network Settings from the menu. Type the Index# for the network adapter to change from the displayed list. Type 1 and press Enter to select the menu option to Set Network Adapter Address. Type S and press Enter to select the option for a Static IP. Type the IPv4 static IP address and press Enter. Type the subnet mask for the network and then press Enter. Type the default gateway for the network and then press Enter. The settings will be applied and the Network Settings menu will be redisplayed. Down the road, this server will query the existing domain controllers in the domain. It’s essential this works without any hiccups so set a DNS Server address while still in the Network Settings menu. Type 2 and press Enter to Set DNS Servers. Enter the IP address of the preferred, or primary, DNS server for the domain. Press Enter. Click OK when prompted that the Primary DNS Server has been set. If a secondary DNS server exists for the domain, enter its IP address when prompted for an alternate DNS server. If no secondary DNS server exists, leave blank. Press Enter. Click OK when prompted that the Alternate DNS Server has been set. The Network Settings menu will be redisplayed. Type 4 and press Enter to exit the Network Settings menu. Type 15 and press Enter to exit the Server Configuration Tool. An application server is a special way of providing services to a client machine. The application executes partially on the server and partially on the client. Precisely how the application works depends on where the developer determines the particular piece of code works best. The Application Server role provides this functionality to Windows Server 2012 users. the DNS Server role The Domain Name System (DNS) is a standard means of converting IP addresses into a human readable form. For example, when you want to access Microsoft’s main page. The DNS server converts this human readable name into the IP address. You must have a DNS server installed before you can promote your server to a domain controller. Fax Server role Installing the Fax Server role lets you use your server to send and receive faxes, if you have the required hardware and software installed. This role also requires that you install the Print Server role. the File Services role Installing the File Services role lets you share files on the network. This role is the one you always install on the server because a server isn’t much good if you can’t share files. Adding the File Services role provides basic file sharing only. File services haven’t changed much over the years. The first peer-to-peer network provided this basic functionality. However, file services have increased in functionality. You can install a number of role services to enhance the capability of this particular role. For example, Microsoft provides a role service that indexes content to make it easier and faster to find. the Network Policy and Access Services role The name of this particular role is a bit misleading because it provides a lot more functionality than its name implies. In fact, installing this particular role provides the following services: • Network Policy Server (NPS) • Network Access Protection (NAP) Health Policy Server • Secure Wireless Access (IEEE 802.11) • Secure Wired Access (IEEE 802.3) • Central Network Policy Management • Remote Access Dial-In User Server (RADIUS) Server and Proxy • Remote Access Service (RAS) • Routing • Health Registration Authority (HRA) • Host Credential Authorization Protocol (HCAP) • Tools Required to Manage All Access Services The scope of this particular role is incredible. It provides many of the features that modern servers must provide for outside communication. the Print Services role Providing print services is another common role for servers. At one time, printers were extremely expensive (and good printers still are), so issuing one to each user wasn’t cost effective. This role helps you manage all printers connected to the server and offers their use to any users with the required access. the Terminal Services role Terminal Services offers remote connectivity to anyone who needs to work with the server directly. In many cases, this activity means using a light client or involves an administrator performing configuration tasks. The two most common ways to use Terminal Services is by using Remote Desktop or by using RemoteApp applications. Using Terminal Services offers many benefits, including reducing client costs and ensuring that applications remain updated. Of course, many issues arise from working with Terminal Services as well, such as increased server load. The Universal Description, Discovery, and Integration (UDDI) service is the Microsoft method of making Web services and their associated applications easily accessible from the server. For the most part, you never install this role unless you have a custom application that relies on it. the Web Server (IIS) role Web servers traditionally serve content over the Internet or an intranet. Users view the content by using a browser or a special application. Modern Web servers provide fully distributed application support in addition to dynamic and static content. IIS 7.0 is a completely new version of IIS with many changes that will surprise you if you haven’t worked with it yet. Book VII provides complete details on working with IIS 7.0. the Windows Deployment Services role If you normally install Windows through your server, you need to install this role. The Windows Deployment Services lets a client log in to the server and install a complete copy of Windows without any interaction on the part of the user or administrator. Of course, you have to perform a number of configuration tasks to make this feature work.

Related Questions

Navigate

• Browse (All)
• Browse Y
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.