Information Technology Reference
In-Depth Information
6. Click the
Include recommended updates when downloading, installing, or notifying me
about updates
check box. This option includes new drivers or application updates in the
downloaded updates. Click
OK
.
7. Under Windows Error Reporting, click the
Change Setting
button. Read the description of
this feature. Error reporting is enabled by default with the option to notify you before send-
ing the selected report. You can leave this option as is, but take note of the other choices.
Click
OK
.
8. Under Customer Experience Improvement Program, click the
Change Setting
button. By
default, you aren't enrolled in this program. Because this server is used only for lab purposes,
click to select
No, I don't want to participate
, if necessary. Read the information about this
program, and then click
OK
.
9. Click
Close
. Next, click
Download and install updates
. Windows checks for updates if
you're connected to the Internet.
10. In the Windows Update window, notice that you receive updates for Windows only, but you
can have Windows look for updates for other manufacturers' products. If updates are avail-
able, you can install them by clicking the
Install Updates
button. If you want to view infor-
mation about updates before installing them, click the
View available updates
link.
11. Close all open windows.
To view a list of installed updates, open the Programs and Features applet in Control Panel
and select the View installed updates task. In addition, you can check for updates manually by
running the Windows Update applet in Control Panel. After your computer is configured and up
to date, you can start installing server roles and additional features. If this server is the first and
only one (at least for now), you'll probably install several roles on this server. As discussed pre-
viously, most networks in a domain environment usually run these services at a minimum: Active
Directory Domain Services (AD DS), DNS, DHCP, and File Services. Other roles and features
you install depend on how the network is used and what applications are running. In Chapter 3,
you install AD DS and DNS. For now, you look at other server installation situations.
2
Many businesses that start with a single server on the network eventually find a reason to install a
second or third server and more. If your network requires two or more servers, you're almost cer-
tainly running in a domain environment, which is the perspective from which this topic is discussed.
When you're adding a server to an existing network, you must answer many of the same plan-
ning questions that you did for the first server. You need to decide on a static IP address, a server
name, and what roles this new server will play on the network. However, you probably don't need
to choose a domain name because this new server will likely be part of the existing domain or a
stand-alone server. What you must decide is whether the new server will be one of the following:
• A domain controller (DC) in the existing domain
• A read only domain controller (RODC) in the existing domain
• A member server in the existing domain
• A stand-alone server
If you're installing the second server in the network, there are some good arguments for
making it a domain controller. The second server can share the load of managing directory serv-
ices and handling user logons and provide fault tolerance for Active Directory should the first
server go offline. An RODC (discussed more later in this section) can provide some benefits of
a standard domain controller but is better suited to handling domain services for branch offices
than serving as a second DC.
A member server belongs to the domain and falls under domain management but doesn't run
Active Directory or participate in managing directory services. Making a server a member server
rather than a domain controller is best when you already have at least two DCs at a location or
Search WWH ::
Custom Search