Which type of networking component is file and printer sharing for Microsoft Network?
On this page: Show
Verify that the sharing component is installedTo verify that File and Printer Sharing is on your computer (typically installed by default):
Once File and Printer Sharing is installed, to share a folder or drive:
To share a printer:
Access a shared folder or printerTo find and access a shared folder or printer:
If you know the exact name of the computer and the share, or the exact name of the printer, you can enter it directly:
If you need to repeatedly access a shared folder or network drive, you can map to it. Mapping creates a persistent link to the share, allowing you to double-click its icon in Back to top
This is document ahrs in the Knowledge Base. Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Core network components
In this article
This guide provides instructions on how to plan and deploy the core components required for a fully functioning network and a new Active Directory domain in a new forest. This guide contains the following sections.
About this guideThis guide is designed for network and system administrators who are installing a new network or who want to create a domain-based network to replace a network that consists of workgroups. The deployment scenario provided in this guide is particularly useful if you foresee the need to add more services and features to your network in the future. It is recommended that you review design and deployment guides for each of the technologies used in this deployment scenario to assist you in determining whether this guide provides the services and configuration that you need. A core network is a collection of network hardware, devices, and software that provides the fundamental services for your organization's information technology (IT) needs. A Windows Server core network provides you with many benefits, including the following.
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 2016. Network hardware requirementsTo successfully deploy a core network, you must deploy network hardware, including the following:
What this guide does not provideThis guide does not provide instructions for deploying the following:
Note Computers running Windows client operating systems are configured by default to receive IP address leases from the DHCP server. Therefore, no additional DHCP or Internet Protocol version 4 (IPv4) configuration of client computers is required. Technology OverviewsThe following sections provide brief overviews of the required technologies that are deployed to create a core network. Active Directory Domain ServicesA 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. DNSDNS is a name resolution protocol for TCP/IP networks, such as the Internet or an organization network. 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. DHCPDHCP is an IP standard for simplifying the management of host IP configuration. The DHCP standard provides for the use of DHCP servers as a way to manage dynamic allocation of IP addresses and other related configuration details for DHCP-enabled clients on your network. DHCP allows you to use a DHCP server to dynamically assign an IP address to a computer or other device, such as a printer, on your local network. Every computer on a TCP/IP network must have a unique IP address, because the IP address and its related subnet mask identify both the host computer and the subnet to which the computer is attached. By using DHCP, you can ensure that all computers that are configured as DHCP clients receive an IP address that is appropriate for their network location and subnet, and by using DHCP options, such as default gateway and DNS servers, you can automatically provide DHCP clients with the information that they need to function correctly on your network. For TCP/IP-based networks, DHCP reduces the complexity and amount of administrative work involved in reconfiguring computers. TCP/IPTCP/IP in Windows Server 2016 is the following:
TCP/IP provides basic TCP/IP utilities that enable Windows-based computers to connect and share information with other Microsoft and non-Microsoft systems, including:
Core Network OverviewThe following illustration shows the Windows Server Core Network topology. Note 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 802.1X wired and wireless deployments that you can implement using Core Network Companion guides. For more information, see Deploying optional features for network access authentication and Web services. Core Network ComponentsFollowing are the components of a core network. RouterThis 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. If you deploy a switch, the switch must be capable of DHCP forwarding or you must place a DHCP server on each subnet. If you deploy a hub, you are deploying a single subnet and do not need DHCP forwarding or a second scope on your DHCP server. Static TCP/IP configurationsThe servers in this deployment are configured with static IPv4 addresses. Client computers are configured by default to receive IP address leases from the DHCP server. Active Directory Domain Services global catalog and DNS server DC1Both Active Directory Domain Services (AD DS) and Domain Name System (DNS) are installed on this server, named DC1, which provides directory and name resolution services to all computers and devices on the network. DHCP server DHCP1The DHCP server, named DHCP1, is configured with a scope that provides Internet Protocol (IP) address leases to computers on the local subnet. The DHCP server can also be configured with additional scopes to provide IP address leases to computers on other subnets if DHCP forwarding is configured on routers. Client computersComputers running Windows client operating systems are configured by default as DHCP clients, which obtain IP addresses and DHCP options automatically from the DHCP server. Core Network PlanningBefore you deploy a core network, you must plan the following items.
The following sections provide more detail on each of these items. Planning subnetsIn Transmission Control Protocol/Internet Protocol (TCP/IP) networking, routers are used to interconnect the hardware and software used on different physical network segments called subnets. 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 10.0.0.1 - 10.0.0.254 and 10.0.1.1 - 10.0.1.254 are used as examples, but you can use any private IP address range that you prefer. Important 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 192.168.1.1, but you are installing the router on a subnet with an IP address range of 10.0.0.0/24, you must reconfigure the router to use an IP address from the 10.0.0.0/24 IP address range. The following recognized private IP address ranges are specified by Internet Request for Comments (RFC) 1918:
When you use the private IP address ranges as specified in RFC 1918, 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. To add Internet connectivity to your core network later, you must contract with an ISP to obtain a public IP address. Important 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. Most routers provide NAT services, so selecting a router that is NAT-capable should be fairly simple. For more information, see Planning the deployment of DHCP1. Planning basic configuration of all serversFor each server in the core network, you must rename the computer and assign and configure a static IPv4 address and other TCP/IP properties for the computer. Planning naming conventions for computers and devicesFor 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. For example, the domain controller is named DC1 and the DHCP server is named DHCP1. It is recommended that you choose a naming convention before you install your core network using this guide. Planning static IP addressesBefore configuring each computer with a static IP address, you must plan your subnets and IP address ranges. In addition, you must determine the IP addresses of your DNS servers. 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. The following table provides example values for static IP address configuration.
Note If you plan on deploying more than one DNS server, you can also plan the Alternate DNS Server IP address. Planning the deployment of DC1Following are key planning steps before installing Active Directory Domain Services (AD DS) and DNS on DC1. Planning the name of the forest root domainA 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. Planning the forest functional levelWhile installing AD DS, you must choose the forest functional level that you want to use. Domain and forest functionality, introduced in Windows Server 2003 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:
If you are deploying a new domain in a new forest and all of your domain controllers will be running Windows Server 2016, it is recommended that you configure AD DS with the Windows Server 2016 forest functional level during AD DS installation. Important 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 2016, domain controllers running Windows Server 2012 R2 or Windows Server 2008 cannot be added to the forest. Example configuration items for AD DS are provided in the following table.
Planning DNS zonesOn primary, Active Directory-integrated DNS servers, a forward lookup zone is created by default during installation of the DNS Server role. 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. Deploying a reverse lookup zone typically improves DNS performance and greatly increases the success of DNS queries. When you create a reverse lookup zone, the in-addr.arpa domain, which is defined in the DNS standards and reserved in the Internet DNS namespace to provide a practical and reliable way to perform reverse queries, is configured in DNS. To create the reverse namespace, subdomains within the in-addr.arpa domain are formed, using the reverse ordering of the numbers in the dotted-decimal notation of IP addresses. The in-addr.arpa domain applies to all TCP/IP networks that are based on Internet Protocol version 4 (IPv4) addressing. The New Zone Wizard automatically assumes that you are using this domain when you create a new reverse lookup zone. While you are running the New Zone Wizard, the following selections are recommended:
Planning domain accessTo 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. Note 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. Before you log on to the domain:
Planning the deployment of DHCP1Following are key planning steps before installing the DHCP server role on DHCP1. Planning DHCP servers and DHCP forwardingBecause 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. Planning IP address rangesEach subnet must have its own unique IP address range. These ranges are represented on a DHCP server with scopes. A scope is an administrative grouping of IP addresses for computers on a subnet that use the DHCP service. The administrator first creates a scope for each physical subnet and then uses the scope to define the parameters used by clients. A scope has the following properties:
Before deploying your servers, list your subnets and the IP address range you want to use for each subnet. Planning subnet masksNetwork IDs and host IDs within an IP address are distinguished by using a subnet mask. Each subnet mask is a 32-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 131.107.16.200 is the following 32-bit binary number:
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 255.255.0.0. The following table displays subnet masks for the Internet address classes.
When you create a scope in DHCP and you enter the IP address range for the scope, DHCP provides these default subnet mask values. 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. To prevent addressing and routing problems, you should make sure that all TCP/IP computers on a network segment use the same subnet mask and that each computer or device has an unique IP address. Planning exclusion rangesWhen you create a scope on a DHCP server, you specify an IP address range that includes all of the IP addresses that the DHCP server is allowed to lease to DHCP clients, such as computers and other devices. 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. An exclusion range is a contiguous range of IP addresses within the scope's IP address range that the DHCP server is not allowed to use. 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 can exclude IP addresses from distribution by the DHCP server by creating an exclusion range for each scope. You should use exclusions for all devices that are configured with a static IP address. The excluded addresses should include all IP addresses that you assigned manually to other servers, non-DHCP clients, diskless workstations, or Routing and Remote Access and PPP clients. 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 10.0.0.1 - 10.0.0.254 and a subnet mask of 255.255.255.0.
Planning TCP/IP static configurationCertain devices, such as routers, DHCP servers, and DNS servers, must be configured with a static IP address. 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. An exclusion range is a limited sequence of IP addresses within a scope, excluded from DHCP service offerings. 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 192.168.0.1 through 192.168.0.254 and you have ten devices that you want to configure with a static IP address, you can create an exclusion range for the 192.168.0.x scope that includes ten or more IP addresses: 192.168.0.1 through 192.168.0.15. 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 192.168.0.16 through 192.168.0.254. Additional example configuration items for AD DS and DNS are provided in the following table.
Core Network DeploymentTo deploy a core network, the basic steps are as follows:
Note
Configuring All ServersBefore installing other technologies, such as Active Directory Domain Services or DHCP, it is important to configure the following items.
You can use the following sections to perform these actions for each server. Membership in Administrators, or equivalent, is the minimum required to perform these procedures. Rename the computerYou 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. Note To perform this procedure by using Windows PowerShell, open PowerShell and type the following cmdlets on separate lines, and then press ENTER. You must also replace ComputerName with the name that you want to use.
Configure a static IP addressYou can use the procedures in this topic to configure the Internet Protocol version 4 (IPv4) properties of a network connection with a static IP address for computers running Windows Server 2016. Note To perform this procedure by using Windows PowerShell, open PowerShell and type the following cmdlets on separate lines, and then press ENTER. You must also replace interface names and IP addresses in this example with the values that you want to use to configure your computer.
Deploying DC1To deploy DC1, which is the computer running Active Directory Domain Services (AD DS) and DNS, you must complete these steps in the following order:
Administrative privileges If you are installing a small network and are the only administrator for the network, it is recommended that you create a user account for yourself, and then add your user account as a member of both Enterprise Admins and Domain Admins. Doing so will make it easier for you to act as the administrator for all network resources. It is also recommended that you log on with this account only when you need to perform administrative tasks, and that you create a separate user account for performing non-IT related tasks. If you have a larger organization with multiple administrators, refer to AD DS documentation to determine the best group membership for organization employees. Differences between domain user accounts and user accounts on the local computer One of the advantages of a domain-based infrastructure is that you do not need to create user accounts on each computer in the domain. This is true whether the computer is a client computer or a server. Because of this, you should not create user accounts on each computer in the domain. Create all user accounts in Active Directory Users and Computers and use the preceding procedures to assign group membership. By default, all user accounts are members of the Domain Users group. All members of the Domain Users group can log on to any client computer after it is joined to the domain. You can configure user accounts to designate the days and times that the user is allowed to log on to the computer. You can also designate which computers each user is allowed to use. To configure these settings, open Active Directory Users and Computers, locate the user account that you want to configure, and double-click the account. In the user account Properties, click the Account tab, and then click either Logon Hours or Log On To. Install AD DS and DNS for a New ForestYou can use one of the following procedures to install Active Directory Domain Services (AD DS) and DNS and to create a new domain in a new forest. The first procedure provides instructions on performing these actions by using Windows PowerShell, while the second procedure shows you how to install AD DS and DNS by using Server Manager. Important After you finish performing the steps in this procedure, the computer is automatically restarted. Install AD DS and DNS Using Windows PowerShell You can use the following commands to install and configure AD DS and DNS. You must replace the domain name in this example with the value that you want to use for your domain. Membership in Administrators is the minimum required to perform this procedure.
When installation has successfully completed, the following message is displayed in Windows PowerShell.
The results of this command are displayed in Windows PowerShell, and should be similar to the results in the image below. For installed technologies, the brackets to the left of the technology name contain the character X, and the value of Install State is Installed. Install AD DS and DNS Using Server Manager
Create a User Account in Active Directory Users and ComputersYou can use this procedure to create a new domain user account in Active Directory Users and Computers Microsoft Management Console (MMC). Membership in Domain Admins, or equivalent, is the minimum required to perform this procedure. Note To perform this procedure by using Windows PowerShell, open PowerShell and type the following cmdlet on one line, and then press ENTER. You must also replace the user account name in this example with the value that you want to use.
After you press ENTER, type the password for the user account. The account is created and, by default, is granted membership to the Domain Users group. With the following cmdlet, you can assign additional group memberships for the new user account. The example below adds User1 to the Domain Admins and Enterprise Admins groups. Ensure before running this command that you change the user account name, domain name, and groups to match your requirements.
Assign Group MembershipYou can use this procedure to add a user, computer, or group to a group in Active Directory Users and Computers Microsoft Management Console (MMC). Membership in Domain Admins, or equivalent is the minimum required to perform this procedure. To assign group membership
Configure a DNS Reverse Lookup ZoneYou can use this procedure to configure a reverse lookup zone in Domain Name System (DNS). Membership in Domain Admins is the minimum required to perform this procedure. Note
Joining Server Computers to the Domain and Logging OnAfter you have installed Active Directory Domain Services (AD DS) and created one or more user accounts that have permissions to join a computer to the domain, you can join core network servers to the domain and log on to the servers in order to install additional technologies, such as Dynamic Host Configuration Protocol (DHCP). On all servers that you are deploying, except for the server running AD DS, do the following:
Note To perform this procedure by using Windows PowerShell, open PowerShell and type the following cmdlet, and then press ENTER. You must also replace the domain name with the name that you want to use.
When you are prompted to do so, type the user name and password for an account that has permission to join a computer to the domain. To restart the computer, type the following command and press ENTER.
Deploying DHCP1Before deploying this component of the core network, you must do the following:
To deploy DHCP1, which is the computer running the Dynamic Host Configuration Protocol (DHCP) server role, you must complete these steps in the following order:
Note To perform these procedures by using Windows PowerShell, open PowerShell and type the following cmdlets on separate lines, and then press ENTER. You must also replace the scope name, IP address start and end ranges, subnet mask, and other values in this example with the values that you want to use.
Install Dynamic Host Configuration Protocol (DHCP)You can use this procedure to install and configure the DHCP Server role using the Add Roles and Features Wizard. Membership in Domain Admins, or equivalent, is the minimum required to perform this procedure. To install DHCP
Create and Activate a New DHCP ScopeYou can use this procedure to create a new DHCP scope using the DHCP Microsoft Management Console (MMC). When you complete the procedure, the scope is activated and the exclusion range that you create prevents the DHCP server from leasing the IP addresses that you use to statically configure your servers and other devices that require a static IP address. Membership in DHCP Administrators, or equivalent, is the minimum required to perform this procedure. To create and activate a new DHCP Scope
Important To create new scopes for additional subnets, repeat this procedure. Use a different IP address range for each subnet that you plan to deploy, and ensure that DHCP message forwarding is enabled on all routers that lead to other subnets. Joining Client Computers to the Domain and Logging OnNote To perform this procedure by using Windows PowerShell, open PowerShell and type the following cmdlet, and then press ENTER. You must also replace the domain name with the name that you want to use.
When you are prompted to do so, type the user name and password for an account that has permission to join a computer to the domain. To restart the computer, type the following command and press ENTER.
To join computers running Windows 10 to the domain
To join computers running Windows 8.1 to the domain
To log on to the domain using computers running Windows 10
Deploying optional features for network access authentication and Web servicesIf you intend to deploy network access servers, such as wireless access points or VPN servers, after installing your core network, it is recommended that you deploy both an NPS and a Web server. For network access deployments, the use of secure certificate-based authentication methods is recommended. You can use NPS to manage network access policies and to deploy secure authentication methods. You can use a Web server to publish the certificate revocation list (CRL) of your certification authority (CA) that provides certificates for secure authentication. Note You can deploy server certificates and other additional features by using Core Network Companion Guides. For more information, see Additional Technical Resources. The following illustration shows the Windows Server Core Network topology with added NPS and Web servers. The following sections provide information on adding NPS and Web servers to your network.
Deploying NPS1The Network Policy Server (NPS) server is installed as a preparatory step for deploying other network access technologies, such as virtual private network (VPN) servers, wireless access points, and 802.1X authenticating switches. Network Policy Server (NPS) allows you to centrally configure and manage network policies with the following features: Remote Authentication Dial-In User Service (RADIUS) server and RADIUS proxy. NPS is an optional component of a core network, but you should install NPS if any of the following are true:
Before deploying this role service, you must perform the following steps on the computer you are configuring as an NPS.
To deploy NPS1, which is the computer running the Network Policy Server (NPS) role service of the Network Policy and Access Services server role, you must complete this step:
Note This guide provides instructions for deploying NPS on a standalone server or VM named NPS1. Another recommended deployment model is the installation of NPS on a domain controller. If you prefer installing NPS on a domain controller instead of on a standalone server, install NPS on DC1. Planning the deployment of NPS1If you intend to deploy network access servers, such as wireless access points or VPN servers, after deploying your core network, it is recommended that you deploy NPS. When you use NPS as a Remote Authentication Dial-In User Service (RADIUS) server, NPS performs authentication and authorization for connection requests through your network access servers. NPS also allows you to centrally configure and manage network policies that determine who can access the network, how they can access the network, and when they can access the network. Following are key planning steps before installing NPS.
Install Network Policy Server (NPS)You can use this procedure to install Network Policy Server (NPS) by using the Add Roles and Features Wizard. NPS is a role service of the Network Policy and Access Services server role. Note By default, NPS listens for RADIUS traffic on ports 1812, 1813, 1645, and 1646 on all installed network adapters. If Windows Firewall with Advanced Security is enabled when you install NPS, firewall exceptions for these ports are automatically created during the installation process for both Internet Protocol version 6 (IPv6) and IPv4 traffic. If your network access servers are configured to send RADIUS traffic over ports other than these defaults, remove the exceptions created in Windows Firewall with Advanced Security during NPS installation, and create exceptions for the ports that you do use for RADIUS traffic. Administrative Credentials To complete this procedure, you must be a member of the Domain Admins group. Note To perform this procedure by using Windows PowerShell, open PowerShell and type the following, and then press ENTER.
Register the NPS in the Default DomainYou can use this procedure to register an NPS in the domain where the server is a domain member. NPSs must be registered in Active Directory so that they have permission to read the dial-in properties of user accounts during the authorization process. Registering an NPS adds the server to the RAS and IAS Servers group in Active Directory. Administrative credentials To complete this procedure, you must be a member of the Domain Admins group. Note To perform this procedure by using network shell (Netsh) commands within Windows PowerShell, open PowerShell and type the following, and then press ENTER.
For more information about Network Policy Server, see Network Policy Server (NPS). Deploying WEB1The Web Server (IIS) role in Windows Server 2016 provides a secure, easy-to-manage, modular and extensible platform for reliably hosting web sites, services, and applications. With Internet Information Services (IIS), you can share information with users on the Internet, an intranet, or an extranet. IIS is a unified web platform that integrates IIS, ASP.NET, FTP services, PHP, and Windows Communication Foundation (WCF). In addition to allowing you to publish a CRL for access by domain member computers, the Web Server (IIS) server role allows you to set up and manage multiple web sites, web applications, and FTP sites. IIS also provides the following benefits:
To deploy WEB1, which is the computer that is running the Web Server (IIS) server role, you must do the following:
Install the Web Server (IIS) server roleTo complete this procedure, you must be a member of the Administrators group. Note To perform this procedure by using Windows PowerShell, open PowerShell and type the following, and then press ENTER.
Additional Technical ResourcesFor more information about the technologies in this guide, see the following resources: Windows Server 2016, Windows Server 2012 R2 , and Windows Server 2012 Technical Library Resources
Appendices A through EThe following sections contain additional configuration information for computers that are running operating systems other than Windows Server 2016, Windows 10, Windows Server 2012 , and Windows 8. In addition, a network preparation worksheet is provided to assist you with your deployment.
Appendix A - Renaming computersYou can use the procedures in this section to provide computers running Windows Server 2008 R2, Windows 7, Windows Server 2008 , and Windows Vista with a different computer name.
Windows Server 2008 R2 and Windows 7Membership in Administrators, or equivalent, is the minimum required to perform these procedures. To rename computers running Windows Server 2008 R2 and Windows 7
Windows Server 2008 and Windows VistaMembership in Administrators, or equivalent, is the minimum required to perform these procedures. To rename computers running Windows Server 2008 and Windows Vista
Appendix B - Configuring static IP addressesThis topic provides procedures for configuring static IP addresses on computers running the following operating systems:
Windows Server 2008 R2Membership in Administrators, or equivalent, is the minimum required to perform this procedure. To configure a static IP address on a computer running Windows Server 2008 R2
Windows Server 2008Membership in Administrators, or equivalent, is the minimum required to perform these procedures. To configure a static IP address on a computer running Windows Server 2008
Appendix C - Joining computers to the domainYou can use these procedures to join computers running Windows Server 2008 R2, Windows 7, Windows Server 2008 , and Windows Vista to the domain.
Important To join a computer to a domain, you must be logged on to the computer with the local Administrator account or, if you are logged on to the computer with a user account that does not have local computer administrative credentials, you must provide the credentials for the local Administrator account during the process of joining the computer to the domain. In addition, you must have a user account in the domain to which you want to join the computer. During the process of joining the computer to the domain, you will be prompted for your domain account credentials (user name and password). Windows Server 2008 R2 and Windows 7Membership in Domain Users, or equivalent, is the minimum required to perform this procedure. To join computers running Windows Server 2008 R2 and Windows 7 to the domain
Windows Server 2008 and Windows VistaMembership in Domain Users, or equivalent, is the minimum required to perform this procedure. To join computers running Windows Server 2008 and Windows Vista to the domain
Appendix D - Log on to the domainYou can use these procedures to log on to the domain using computers running Windows Server 2008 R2, Windows 7, Windows Server 2008 , and Windows Vista.
Windows Server 2008 R2 and Windows 7Membership in Domain Users, or equivalent, is the minimum required to perform this procedure. Log on to the domain using computers running Windows Server 2008 R2 and Windows 7
Windows Server 2008 and Windows VistaMembership in Domain Users, or equivalent, is the minimum required to perform this procedure. Log on to the domain using computers running Windows Server 2008 and Windows Vista
Appendix E - Core Network Planning Preparation SheetYou can use this Network Planning Preparation Sheet to gather the information required to install a core network. This topic provides tables that contain the individual configuration items for each server computer for which you must supply information or specific values during the installation or configuration process. Example values are provided for each configuration item. For planning and tracking purposes, spaces are provided in each table for you to enter the values used for your deployment. If you log security-related values in these tables, you should store the information in a secure location. The following links lead to the sections in this topic that provide configuration items and example values that are associated with the deployment procedures presented in this guide.
Installing Active Directory Domain Services and DNSThe tables in this section list configuration items for pre-installation and installation of Active Directory Domain Services (AD DS) and DNS. Pre-installation configuration items for AD DS and DNSThe following tables list pre-installation configuration items as described in Configuring All Servers:
AD DS and DNS installation configuration itemsConfiguration items for the Windows Server Core Network deployment procedure Install AD DS and DNS for a New Forest:
Configuring a DNS Reverse Lookup Zone
Installing DHCPThe tables in this section list configuration items for pre-installation and installation of DHCP. Pre-installation configuration items for DHCPThe following tables list pre-installation configuration items as described in Configuring All Servers:
DHCP installation configuration itemsConfiguration items for the Windows Server Core Network deployment procedure Install Dynamic Host Configuration Protocol (DHCP):
Creating an exclusion range in DHCPConfiguration items to create an exclusion range while creating a scope in DHCP.
Creating a new DHCP scopeConfiguration items for the Windows Server Core Network deployment procedure Create and Activate a New DHCP Scope:
Installing Network Policy Server (optional)The tables in this section list configuration items for pre-installation and installation of NPS. Pre-installation configuration itemsThe following three tables list pre-installation configuration items as described in Configuring All Servers:
Network Policy Server installation configuration itemsConfiguration items for the Windows Server Core Network NPS deployment procedures Install Network Policy Server (NPS) and Register the NPS in the Default Domain.
FeedbackSubmit and view feedback for What is file and printer sharing for Microsoft Networks?File and printer sharing in Microsoft® Windows® allows you to share the contents of selected folders and locally attached printers with other computers.
How do I find file and printer sharing for Microsoft Networks?Here are the steps to do it:. Leave File and Printer Sharing for Microsoft Networks turned on.. Type CMD in the Search bar.. Right-click on Command Prompt, and select Run as Administrator.. Type netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=Yes, and hit Enter.. Which protocol is used by the Client for Microsoft Networks and file and printer sharing?The Server Message Block (SMB) Protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol.
What is network attached printer sharing?Printer sharing is the process of allowing multiple computers and devices connected to the same network to access one or more printers.
|