Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback? Submit feedback. Thank you for your feedback! A user and computer account database. The directory service provides a centralized user accounts database that allows you to create user and computer accounts for people and computers that are authorized to connect to your network and access network resources, such as applications, databases, shared files and folders, and printers.
A core network also allows you to scale your network as your organization grows and IT requirements change. For example, with a core network you can add domains, IP subnets, remote access services, wireless services, and other features and server roles provided by Windows Server To successfully deploy a core network, you must deploy network hardware, including the following:. A hub, Layer 2 or 3 switch, router, or other device that performs the function of relaying network traffic between computers and devices.
Computers that meet the minimum hardware requirements for their respective client and server operating systems. The following sections provide brief overviews of the required technologies that are deployed to create a core network.
A directory is a hierarchical structure that stores information about objects on the network, such as users and computers. A directory service, such as AD DS, provides the methods for storing directory data and making this data available to network users and administrators.
For example, AD DS stores information about user accounts, including names, email addresses, passwords, and phone numbers, and enables other authorized users on the same network to access this information.
A DNS server hosts the information that enables client computers and services to resolve easily recognized, alphanumeric DNS names to the IP addresses that computers use to communicate with each other. A routable enterprise networking protocol that supports the connection of your Windows-based computer to both local area network LAN and wide area network WAN environments. Core technologies and utilities for connecting your Windows-based computer with dissimilar systems for the purpose of sharing information.
This guide also includes instructions for adding optional Network Policy Server NPS and Web Server IIS servers to your network topology to provide the foundation for secure network access solutions, such as For more information, see Deploying optional features for network access authentication and Web services. This deployment guide provides instructions for deploying a core network with two subnets separated by a router that has DHCP forwarding enabled.
You can, however, deploy a Layer 2 switch, a Layer 3 switch, or a hub, depending on your requirements and resources. The servers in this deployment are configured with static IPv4 addresses.
Planning basic configuration of all servers. Planning the deployment of DC1. Planning the deployment of DHCP1. Routers are also used to forward IP packets between each of the subnets. Determine the physical layout of your network, including the number of routers and subnets you need, before proceeding with the instructions in this guide. In addition, to configure the servers on your network with static IP addresses, you must determine the IP address range that you want to use for the subnet where your core network servers are located.
In this guide, the private IP address ranges After you select the IP address ranges that you want to use for each subnet, ensure that you configure your routers with an IP address from the same IP address range as that used on the subnet where the router is installed. For example, if your router is configured by default with an IP address of When you use the private IP address ranges as specified in RFC , you cannot connect directly to the Internet using a private IP address because requests going to or from these addresses are automatically discarded by Internet service provider ISP routers.
When using private IP addresses, you must use some type of proxy or network address translation NAT server to convert the private IP address ranges on your local network to a public IP address that can be routed on the Internet. For consistency across your network, it is a good idea to use consistent names for servers, printers, and other devices.
Computer names can be used to help users and administrators easily identify the purpose and location of the server, printer, or other device. For example, if you have three DNS servers, one in San Francisco, one in Los Angeles, and one in Chicago, you might use the naming convention server function - location - number :.
For this guide, the server naming convention is very simple, and consists of the primary server function and a number. It is recommended that you choose a naming convention before you install your core network using this guide.
Before configuring each computer with a static IP address, you must plan your subnets and IP address ranges. If you plan to install a router that provides access to other networks, such as additional subnets or the Internet, you must know the IP address of the router, also called a default gateway, for static IP address configuration.
A first step in the AD DS design process is to determine how many forests your organization requires. A forest is the top-level AD DS container, and consists of one or more domains that share a common schema and global catalog. An organization can have multiple forests, but for most organizations, a single forest design is the preferred model and the simplest to administer.
When you create the first domain controller in your organization, you are creating the first domain also called the forest root domain and the first forest. Before you take this action using this guide, however, you must determine the best domain name for your organization. In most cases, the organization name is used as the domain name, and in many cases this domain name is registered. If you are planning to deploy external-facing Internet based Web servers to provide information and services for your customers or partners, choose a domain name that is not already in use, and then register the domain name so that your organization owns it.
While installing AD DS, you must choose the forest functional level that you want to use. Domain and forest functionality, introduced in Windows Server Active Directory, provides a way to enable domain- or forest-wide Active Directory features within your network environment. Different levels of domain functionality and forest functionality are available, depending on your environment.
Forest functionality enables features across all the domains in your forest. The following forest functional levels are available:. Windows Server This forest functional level supports only domain controllers that are running Windows Server and later versions of the Windows Server operating system.
Windows Server R2. This forest functional level supports Windows Server R2 domain controllers and domain controllers that are running later versions of the Windows Server operating system. This forest functional level supports Windows Server domain controllers and domain controllers that are running later versions of the Windows Server operating system.
This forest functional level supports only Windows Server domain controllers and domain controllers that are running later versions of the Windows Server operating system. If you are deploying a new domain in a new forest and all of your domain controllers will be running Windows Server , it is recommended that you configure AD DS with the Windows Server forest functional level during AD DS installation.
After the forest functional level is raised, domain controllers that are running earlier operating systems cannot be introduced into the forest. For example, if you raise the forest functional level to Windows Server , domain controllers running Windows Server R2 or Windows Server cannot be added to the forest. A forward lookup zone allows computers and devices to query for another computer's or device's IP address based on its DNS name.
In addition to a forward lookup zone, it is recommended that you create a DNS reverse lookup zone. With a DNS reverse lookup query, a computer or device can discover the name of another computer or device using its IP address. When you create a reverse lookup zone, the in-addr.
To create the reverse namespace, subdomains within the in-addr. The in-addr. The New Zone Wizard automatically assumes that you are using this domain when you create a new reverse lookup zone. To log on to the domain, the computer must be a domain member computer and the user account must be created in AD DS before the logon attempt. Individual computers that are running Windows have a local users and groups user account database that is called the Security Accounts Manager SAM user accounts database.
When you create a user account on the local computer in the SAM database, you can log onto the local computer, but you cannot log on to a domain. Domain user accounts are created with the Active Directory Users and Computers Microsoft Management Console MMC on a domain controller, not with local users and groups on the local computer. After the first successful logon with domain logon credentials, the logon settings persist unless the computer is removed from the domain or the logon settings are manually changed.
Create user accounts in Active Directory Users and Computers. Ensure the correct IP address configuration. To join a computer to the domain, the computer must have an IP address. For this reason, the DHCP server must be deployed before you join clients to the domain. Join the computer to the domain.
Any computer that provides or accesses network resources must be joined to the domain. Because DHCP messages are broadcast messages, they are not forwarded between subnets by routers. If you have multiple subnets and want to provide DHCP service for each subnet, you must do one of the following:. In most cases, configuring routers to forward DHCP broadcast messages is more cost effective than deploying a DHCP server on each physical segment of the network.
Each subnet must have its own unique IP address range. These ranges are represented on a DHCP server with scopes. The administrator first creates a scope for each physical subnet and then uses the scope to define the parameters used by clients. Before deploying your servers, list your subnets and the IP address range you want to use for each subnet.
Each subnet mask is a bit number that uses consecutive bit groups of all ones 1 to identify the network ID and all zeroes 0 to identify the host ID portions of an IP address. For example, the subnet mask normally used with the IP address This subnet mask number is 16 one-bits followed by 16 zero-bits, indicating that the network ID and host ID sections of this IP address are both 16 bits in length.
Normally, this subnet mask is displayed in dotted decimal notation as Typically, default subnet mask values are acceptable for most networks with no special requirements and where each IP network segment corresponds to a single physical network.
In some cases, you can use customized subnet masks to implement IP subnetting. With IP subnetting, you can subdivide the default host ID portion of an IP address to specify subnets, which are subdivisions of the original class-based network ID.
By customizing the subnet mask length, you can reduce the number of bits that are used for the actual host ID. If you then go and manually configure some servers and other devices with static IP addresses from the same IP address range that the DHCP server is using, you can accidentally create an IP address conflict, where you and the DHCP server have both assigned the same IP address to different devices.
To solve this problem, you can create an exclusion range for the DHCP scope. If you create an exclusion range, the DHCP server does not assign the addresses in that range, allowing you to manually assign these addresses without creating an IP address conflict. You should use exclusions for all devices that are configured with a static IP address.
It is recommended that you configure your exclusion range with extra addresses to accommodate future network growth.
The following table provides an example exclusion range for a scope with an IP address range of In addition, you might have additional devices, such as printers, that you want to ensure always have the same IP address. List the devices that you want to configure statically for each subnet, and then plan the exclusion range you want to use on the DHCP server to ensure that the DHCP server does not lease the IP address of a statically configured device.
Exclusion ranges assure that any addresses in these ranges are not offered by the server to DHCP clients on your network. For example, if the IP address range for a subnet is In this example, you use ten of the excluded IP addresses to configure servers and other devices with static IP addresses and five additional IP addresses are left available for static configuration of new devices that you might want to add in the future.
With this exclusion range, the DHCP server is left with an address pool of Scope Name 2. Starting IP Address 3. Ending IP Address 4. Subnet Mask 5. Default Gateway optional 6. Lease duration 1. Primary Subnet 2. Deploying optional features for network access authentication and Web services.
Membership in Administrators , or equivalent, is the minimum required to perform these procedures. You can use the procedure in this section to change the name of a computer. Renaming the computer is useful for circumstances in which the operating system has automatically created a computer name that you do not want to use.
You must also replace ComputerName with the name that you want to use. In Server Manager, click Local Server. The computer Properties are displayed in the details pane. In Properties , in Computer name , click the existing computer name. The System Properties dialog box opens.
Click Change. For example, if you want to name the computer DC1, type DC1. Click OK twice, and then click Close. If you want to restart the computer immediately to complete the name change, click Restart Now. Otherwise, click Restart Later.
Expand the profile you want to change the settings and choose the available options. This will also make your computer visible to other computers in the network. You will see bunch of options related to sharing of the resources that will affect both private and public network profiles. Go back to the main screen of the Network and Sharing Center. This gives you the option to configure an access point or a router and to manually set up a dial-up or VPN connections.
On the next screen, choose an option to create a new connection. This will give you two options to connect to a workplace network remotely:. Windows 10 Network and Sharing Center gives you full control over your network connections.
It also helps to enhance resource sharing and privacy. The list above is not exhaustive. You can do much more by tweaking these settings to achieve the best performance. Editorial Staff at WebNots are team members who love to build websites and share the learning with webmasters community. Connect with us in Facebook and Twitter. Since its release in , Windows 10 has become one[ Comparison of Static and Dynamic Websites We have discussed the[
0コメント