CSS-COC3-STUDY-NOTES1 PDF

COC3 STUDY NOTES1 Windows Server and Services Active Directory On Windows Server 2008 R2 Active Directory Domain Services (AD DS) are the core functions in Active Directory that manage users and computers and allow sysadmins to organize the data into logical hierarchies. AD DS provides f...

COC3 STUDY NOTES1 Windows Server and Services Active Directory On Windows Server 2008 R2 Active Directory Domain Services (AD DS) are the core functions in Active Directory that manage users and computers and allow sysadmins to organize the data into logical hierarchies. AD DS provides for security certificates, Single Sign-On (SSO), LDAP, and rights management. Benefits of Active Directory Domain Services You can customize how your data is organized to meet your companies needs You can manage AD DS from any computer on the network, if necessary AD DS provides built in replication and redundancy: if one Domain Controller (DC) fails, another DC picks up the load All access to network resources goes through AD DS, which keeps network access rights management centralized Active Directory Domain Services: Terms to Know Schema: The set of user configured rules that govern objects and attributes in AD DS. Global Catalog: The container of all objects in AD DS. If you need to find the name of a user, that name is stored in the Global Catalog. Query and Index Mechanism: This system allows users to find each other in AD. A good example would be when you start typing a name in your mail client, and the mail client shows you possible matches. Replication Service: The replication service makes sure that every DC on the network has the same Global Catalog and Schema Sites: Sites are representations of the network topology, so AD DS knows what objects go together to optimize replication and indexing. Lightweight Directory Access Protocol: LDAP is a protocol that allows AD to communicate with other LDAP enabled directory services across platforms. Services are Provided in Active Directory Domain Services Domain Services: Stores data and manages communications between the users and the DC. This is the primary functionality of AD DS. Certificate Services: Allows your DC to serve digital certificates, signatures, and public key cryptography. Lightweight Directory Services: Supports LDAP for cross platform domain services, like any Linux computers in your network. Directory Federation Services: Provides SSO authentication for multiple applications in the same session, so users don’t have to keep providing the same credentials. Rights Management: Controls information rights and data access policies. For example, Rights Management determines if you can access a folder or send an email. Role of Domain Controllers with Active Directory Domain Services Kerberos Key Distribution Center (KDC): The kdc verifies and encrypts kerberos tickets that AD DS uses for authentication NetLogon: Netlogon is the authentication communication service. Windows Time (W32time): Kerberos requires all computer times to be in sync. Intersite Messaging (IsmServ): Intersite messaging allows DCs to communicate with each other for replication and site-routing. Role of Domain Controllers with Active Directory Domain Services AD must have at least one Domain Controller. DCs are the containers for the domains. Each domain is part of an AD Forest, which can include one or more domains organized in Organizational Units. AD DS manages trusts between multiple domains, so you can provide access rights to users in one domain to others in your forest. The most important concept to understand is that AD DS is a framework for domain management, and the computer that users use to access AD is the DC Modern cybersecurity depends on a deep understanding of Active Directory. Active Directory is central to attackers’ capabilities for infiltration, lateral movement, and data exfiltration. No matter how stealthy or clever they are, attackers leave breadcrumbs in AD logs as they move through your network. Varonis monitors AD for those breadcrumbs, as well as file activity, DNS calls, VPN activity, and more. Varonis correlates that data into a full picture for each user and computer in AD, compares the current activity to a normalized baseline and a catalog of data security threat models, and proactively identifies potential threats to your data DOMAIN NAME SERVICES On Windows Server 2008 R2 What is DNS? The Domain Name System (DNS) is the phonebook of the Internet. Humans access information online through domain names, like nytimes.com or espn.com. Web browsers interact through Internet Protocol (IP) addresses. DNS translates domain names to IP addresses so browsers can load Internet resources. Each device connected to the Internet has a unique IP address which other machines use to find the device. DNS servers eliminate the need for humans to memorize IP addresses such as 192.168.1.1 (in IPv4), or more complex newer alphanumeric IP addresses such as 2400:cb00:2048:1::c629:d7a2 (in IPv6). DOMAIN NAME SERVICES On Windows Server 2008 R2 How does DNS work? The process of DNS resolution involves converting a hostname (such as www.example.com) into a computer-friendly IP address (such as 192.168.1.1). An IP address is given to each device on the Internet, and that address is necessary to find the appropriate Internet device - like a street address is used to find a particular home. When a user wants to load a webpage, a translation must occur between what a user types into their web browser (example.com) and the machine-friendly address necessary to locate the example.com webpage. In order to understand the process behind the DNS resolution, it’s important to learn about the different hardware components a DNS query must pass between. For the web browser, the DNS lookup occurs “ behind the scenes” and requires no interaction from the user’s computer apart from the initial request DOMAIN NAME SERVICES On Windows Server 2008 R2 There are 4 DNS servers involved in loading a webpage: DNS recursor - The recursor can be thought of as a librarian who is asked to go find a particular book somewhere in a library. The DNS recursor is a server designed to receive queries from client machines through applications such as web browsers. Typically the recursor is then responsible for making additional requests in order to satisfy the client’s DNS query. Root nameserver - The root server is the first step in translating (resolving) human readable host names into IP addresses. It can be thought of like an index in a library that points to different racks of books - typically it serves as a reference to other more specific locations. DOMAIN NAME SERVICES On Windows Server 2008 R2 TLD nameserver - The top level domain server (TLD) can be thought of as a specific rack of books in a library. This nameserver is the next step in the search for a specific IP address, and it hosts the last portion of a hostname (In example.com, the TLD server is “com”). Authoritative nameserver - This final nameserver can be thought of as a dictionary on a rack of books, in which a specific name can be translated into its definition. The authoritative nameserver is the last stop in the nameserver query. If the authoritative name server has access to the requested record, it will return the IP address for the requested hostname back to the DNS Recursor (the librarian) that made the initial request. DOMAIN NAME SERVICES On Windows Server 2008 R2 What's the difference between an authoritative DNS server and a recursive DNS resolver? Both concepts refer to servers (groups of servers) that are integral to the DNS infrastructure, but each performs a different role and lives in different locations inside the pipeline of a DNS query. One way to think about the difference is the recursive resolver is at the beginning of the DNS query and the authoritative nameserver is at the end. DOMAIN NAME SERVICES On Windows Server 2008 R2 Recursive DNS resolver The recursive resolver is the computer that responds to a recursive request from a client and takes the time to track down the DNS record. It does this by making a series of requests until it reaches the authoritative DNS nameserver for the requested record (or times out or returns an error if no record is found). Luckily, recursive DNS resolvers do not always need to make multiple requests in order to track down the records needed to respond to a client; caching is a data persistence process that helps short-circuit the necessary requests by serving the requested resource record earlier in the DNS lookup. DOMAIN NAME SERVICES On Windows Server 2008 R2 DOMAIN NAME SERVICES On Windows Server 2008 R2 Authoritative DNS server Put simply, an authoritative DNS server is a server that actually holds, and is responsible for, DNS resource records. This is the server at the bottom of the DNS lookup chain that will respond with the queried resource record, ultimately allowing the web browser making the request to reach the IP address needed to access a website or other web resources. An authoritative nameserver can satisfy queries from its own data without needing to query another source, as it is the final source of truth for certain DNS records. DOMAIN NAME SERVICES On Windows Server 2008 R2 DOMAIN NAME SERVICES On Windows Server 2008 R2 It’s worth mentioning that in instances where the query is for a subdomain such as foo.example.com or blog.cloudflare.com, an additional nameserver will be added to the sequence after the authoritative nameserver, which is responsible for storing the subdomain’s CNAME record. DOMAIN NAME SERVICES On Windows Server 2008 R2 DOMAIN NAME SERVICES On Windows Server 2008 R2 There is a key difference between many DNS services and the one that Cloudflare provides. Different DNS recursive resolvers such as Google DNS, OpenDNS, and providers like Comcast all maintain data center installations of DNS recursive resolvers. These resolvers allow for quick and easy queries through optimized clusters of DNS-optimized computer systems, but they are fundamentally different than the nameservers hosted by Cloudflare. Cloudflare maintains infrastructure-level nameservers that are integral to the functioning of the Internet. One key example is the f-root server network which Cloudflare is partially responsible for hosting. The F-root is one of the root level DNS nameserver infrastructure components responsible for the billions of Internet requests per day. Our Anycast network puts us in a unique position to handle large volumes of DNS traffic without service interruption. DOMAIN NAME SERVICES On Windows Server 2008 R2 What are the steps in a DNS lookup? For most situations, DNS is concerned with a domain name being translated into the appropriate IP address. To learn how this process works, it helps to follow the path of a DNS lookup as it travels from a web browser, through the DNS lookup process, and back again. Let's take a look at the steps. Note: Often DNS lookup information will be cached either locally inside the querying computer or remotely in the DNS infrastructure. There are typically 8 steps in a DNS lookup. When DNS information is cached, steps are skipped from the DNS lookup process which makes it quicker. The example below outlines all 8 steps when nothing is cached. DOMAIN NAME SERVICES On Windows Server 2008 R2 The 8 steps in a DNS lookup: 1. A user types ‘example.com’ into a web browser and the query travels into the Internet and is received by a DNS recursive resolver. 2. The resolver then queries a DNS root nameserver (.). 3. The root server then responds to the resolver with the address of a Top Level Domain (TLD) DNS server (such as.com or.net), which stores the information for its domains. When searching for example.com, our request is pointed toward the.com TLD. 4. The resolver then makes a request to the.com TLD. 5. The TLD server then responds with the IP address of the domain’s nameserver, example.com. 6. Lastly, the recursive resolver sends a query to the domain’s nameserver. 7. The IP address for example.com is then returned to the resolver from the nameserver. 8. The DNS resolver then responds to the web browser with the IP address of the domain requested initially. Once the 8 steps of the DNS lookup have returned the IP address for example.com, the browser is able to make the request for the web page: 9. The browser makes a HTTP request to the IP address. 10. The server at that IP returns the webpage to be rendered in the browser (step 10). DOMAIN NAME SERVICES On Windows Server 2008 R2 What is a DNS resolver? The DNS resolver is the first stop in the DNS lookup, and it is responsible for dealing with the client that made the initial request. The resolver starts the sequence of queries that ultimately leads to a URL being translated into the necessary IP address. Note: A typical uncached DNS lookup will involve both recursive and iterative queries. It's important to differentiate between a recursive DNS query and a recursive DNS resolver. The query refers to the request made to a DNS resolver requiring the resolution of the query. A DNS recursive resolver is the computer that accepts a recursive query and processes the response by making the necessary requests. DOMAIN NAME SERVICES On Windows Server 2008 R2 DOMAIN NAME SERVICES On Windows Server 2008 R2 3 types of DNS queries: 1. Recursive query - In a recursive query, a DNS client requires that a DNS server (typically a DNS recursive resolver) will respond to the client with either the requested resource record or an error message if the resolver can't find the record. 2. Iterative query - in this situation the DNS client will allow a DNS server to return the best answer it can. If the queried DNS server does not have a match for the query name, it will return a referral to a DNS server authoritative for a lower level of the domain namespace. The DNS client will then make a query to the referral address. This process continues with additional DNS servers down the query chain until either an error or timeout occurs. 3. Non-recursive query - typically this will occur when a DNS resolver client queries a DNS server for a record that it has access to either because it's authoritative for the record or the record exists inside of its cache. Typically, a DNS server will cache DNS records to prevent additional bandwidth consumption and load on upstream servers. DOMAIN NAME SERVICES On Windows Server 2008 R2 What is DNS caching? Where does DNS caching occur? The purpose of caching is to temporarily stored data in a location that results in improvements in performance and reliability for data requests. DNS caching involves storing data closer to the requesting client so that the DNS query can be resolved earlier and additional queries further down the DNS lookup chain can be avoided, thereby improving load times and reducing bandwidth/CPU consumption. DNS data can be cached in a variety of locations, each of which will store DNS records for a set amount of time determined by a time-to- live (TTL). DOMAIN NAME SERVICES On Windows Server 2008 R2 Browser DNS caching Modern web browsers are designed by default to cache DNS records for a set amount of time. The purpose here is obvious; the closer the DNS caching occurs to the web browser, the fewer processing steps must be taken in order to check the cache and make the correct requests to an IP address. When a request is made for a DNS record, the browser cache is the first location checked for the requested record. In chrome, you can see the status of your DNS cache by going to chrome://net-internals/#dns. DOMAIN NAME SERVICES On Windows Server 2008 R2 Operating system (OS) level DNS caching The operating system level DNS resolver is the second and last local stop before a DNS query leaves your machine. The process inside your operating system that is designed to handle this query is commonly called a “stub resolver” or DNS client. hen a stub resolver gets a request from an application, it first checks its own cache to see if it has the record. If it does not, it then sends a DNS query (with a recursive flag set), outside the local network to a DNS recursive resolver inside the Internet service provider (ISP). Dynamic Host Configuration Protocol (DHCP) On Windows Server 2008 R2 Recursive resolver DNS caching When the recursive resolver inside the ISP receives a DNS query, like all previous steps, it will also check to see if the requested host-to-IP-address translation is already stored inside its local persistence layer. The recursive resolver also has additional functionality depending on the types of records it has in its cache: 1. If the resolver does not have the A records, but does have the NS records for the authoritative nameservers, it will query those name servers directly, bypassing several steps in the DNS query. This shortcut prevents lookups from the root and.com nameservers (in our search for example.com) and helps the resolution of the DNS query occur more quickly. 2. If the resolver does not have the NS records, it will send a query to the TLD servers (.com in our case), skipping the root server. 3. In the unlikely event that the resolver does not have records pointing to the TLD servers, it will then query the root servers. This event typically occurs after a DNS cache has been purged. Dynamic Host Configuration Protocol (DHCP) On Windows Server 2008 R2 Dynamic Host Configuration Protocol (DHCP) is a network management protocol used to automate the process of configuring devices on IP networks, thus allowing them to use network services such as DNS, NTP, and any communication protocol based on UDP or TCP. A DHCP server dynamically assigns an IP address and other network configuration parameters to each device on a network so they can communicate with other IP networks. DHCP is an enhancement of an older protocol called BOOTP. DHCP is an important part of the DDI solution (DNS-DHCPIPAM). Dynamic Host Configuration Protocol (DHCP) On Windows Server 2008 R2 Configuration Data Sent by DHCP Server and Key Values The basic flow is that a DHCP server hands out configuration data, based on the administrator’s policy, to a requesting client. Common network parameters (sometimes referred to as “DHCP Options“) requested include subnet mask, router, domain name server, hostname and domain name. As the requesting client has no IP address when joining the network, it broadcasts the request. The protocol is thus used in a very early stage of IP communication. If such dynamic protocol is not used to get an IP address, the client has to use a predefined IP address generally called “static IP address”, which is manually configured on the client network interface in configuration files or with a specific command. Dynamic Host Configuration Protocol (DHCP) On Windows Server 2008 R2 The DHCP service brings three key values: 1) Operation tasks are reduced: the network administrator no longer needs to manually configure each client before it can use the network 2) The IP addressing plan is optimized: addresses no longer being used are freed up and made available to new clients connecting 3) User mobility is easily managed: the administrator doesn’t need to manually reconfigure a client when its network access point changes. Dynamic Host Configuration Protocol (DHCP) On Windows Server 2008 R2 DHCP Lease Time Management The IP address information assigned by DHCP is only valid for a limited period of time, and is known as a DHCP lease. The period of validity is called the DHCP lease time. When the lease expires, the client can no longer use the IP address and has to stop all communication with the IP network unless he requests to extend the lease “rent” via the DHCP lease renewal cycle. To avoid impacts of the DHCP server not being available at the end of the lease time, clients generally start renewing their lease halfway through the lease period. This renewal process ensures robust IP address allocation to devices. Any device asking for a new IP version 4 address at arrival on the network and not receiving an answer will use automatic private internet protocol addressing (APIPA) to select an address. These addresses are in the network range 169.254.0.0/16. Dynamic Host Configuration Protocol (DHCP) On Windows Server 2008 R2 Usage Scenarios There are four key DHCP usage scenarios: 1. Initial Client Connection: the client requests from the DHCP server an IP address and other parameter values for accessing network services 2. IP Usage Extension: the client contacts the DHCP server to extend usage of its current IP address 3. Client Connection After Reboot: the client contacts the DHCP server for confirmation that it can use the same IP address being used before reboot 4. Client Disconnection: the client requests the DHCP server to release its IP address. Dynamic Host Configuration Protocol (DHCP) On Windows Server 2008 R2 DHCP Options DHCP options can be used to automatically provide clients with information on the network services it can use. This is a very efficient way to push the IP address of the time server, the mail server, the DNS server and the printer server. This can also be used to provide a file name and a file server that will be used by the client to start a specific boot process – mainly used for IP phones and Wi-Fi access points, but can also be used for auto- installing clients and servers with PXE (Preboot eXecution Environment). Dynamic Host Configuration Protocol (DHCP) On Windows Server 2008 R2 Implementation of DHCP Service The original and most comprehensive implementation of the DHCP service is offered by the Internet Systems Consortium (ISC). Supporting both IPv4 and IPv6, ISC DHCP offers a complete open source solution for implementing DHCP servers, relay agents, and clients. Other DHCP Server products include the Microsoft DHCP server. The DHCP service can be enhanced by DHCP failover to bring high availability and load balancing of traffic. The ISC DHCP Failover relies on having a pair of collaborating servers – a primary (master) server and a secondary (backup) server. A TCP-based communication channel, called a failover channel, then has to be set up between the two servers. Dynamic Host Configuration Protocol (DHCP) On Windows Server 2008 R2 Dynamic Host Configuration Protocol (DHCP) is a core infrastructure service on any network that provides IP addressing and DNS server information to PC clients and any other device. DHCP is used so that you do not have to statically assign IP addresses to every device on your network and manage the issues that static IP addressing can create. More and more, DHCP is being expanded to fit into new network services like the Windows Health Service and Network Access Protection (NAP). File Services On Windows Server 2008 R2 A file server is a central server instance in a computer network that enables connected clients to access the server’s storage capacities. The term encompasses both the hardware and software needed to implement such a server. As long as they have received the corresponding authorizations, accessing users can open, read, change, and delete files and folders on a file server as well as even upload their own files to the server. File Services On Windows Server 2008 R2 What is a file server? A file server is a central server in a computer network that provides file systems or at least parts of a file system to connected clients. File servers therefore offer users a central storage place for files on internal data media, which is accessible to all authorized clients. Here, the server administrator defines strict rules regarding which users have which access rights: For instance, the configuration or file authorizations of the respective file system enable the admin to set which files can be seen and opened by a certain user or user group, and whether data can only be viewed or also added, edited, or deleted. With file servers connected to the internet and configured accordingly, users cannot only access the files via the local network but also benefit from remote access. This enables files to be accessed and saved on the file server even when users are on the go. All modern operating systems such as Windows, Linux, or macOS can be used on a file server, although the devices available in the network need to be compatible with the operating system. But file servers are not only used for file storage and management. They are also often used as a repository for programs that have to be accessible to multiple network participants, and as a backup server. File Services On Windows Server 2008 R2 File Services On Windows Server 2008 R2 How do file servers work? The right hardware is the foundation for a reliable file server. Most importantly, of course, this includes the hard drive which needs to offer sufficient space for the files and necessary programs, as well as the respective operating system, and the software for using the clients. The server also needs enough working memory and processing power to process file and program accesses for various users as quickly and faultlessly as possible. Whether the hardware requirements can be fulfilled by a standard PC or whether a special server setup is required primarily depends on the number of users. Special network protocols are responsible for communication between file servers and clients: While the SMB protocol (Server Message Block) developed by IBM is used in local networks with Windows and macOS devices, computers with Unix-like systems – such as Linux distributions – largely work with the NFS protocol (Network File System). To combine both protocol types in a single network, clients and file servers based on Unix/Linux must be accordingly equipped with software that implements the SMB protocol in these systems – for example the free software suite Samba. File Services On Windows Server 2008 R2 Accessing the file server over the internet typically works with FTP (File Transfer Protocol) or it’s encrypted variant SFTP (Secure FTP). Alternatively, the encrypted SCP (Secure Copy) and HTTP-based WebDAV protocols are also used. Note WebDAV uses the same port (80) as HTTP. Compared to alternatives like FTP or SCP, it therefore has the advantage that the port does not usually need to be opened in the client, as it is open as standard – enabling use of the world wide web. File Services On Windows Server 2008 R2 The functions and options of a file server As already mentioned, the main functions of a file server are to enable multiple users to access the stored files and free storage space for the file repository. For this reason, these servers are especially popular as a central storage place for internal company files that are not only relevant for individual users. In many cases, companies (particularly in the open-source sector) also use a file server as a download server connected to their own web offering. This way, they allow their customers or website visitors to download select content such as programs, drivers, updates, images, or videos with ease. Note Central file access via a file server is often also linked to access to the network printers. The second major application of file servers is data backups. Unlike when saving and jointly managing relevant files, this specifically refers to the creation and maintenance of conventional backups – of system or user files (or both) depending on the need. Storing these backup copies on a file server is both an easy and inexpensive alternative to having to plan and cover the necessary additional storage requirements on each individual client. This works much like when file servers are used to host software and provide access for all authorized users: As the host terminal systems used in the past, computing power and storage capacity are conveniently outsourced, meaning the client devices only have to take on data entry and display. File Services On Windows Server 2008 R2 What are the advantages of using a file server? For many companies, using a file server is worth considering for a range of reasons. First, there is of course the advantage of centrality which ensures each authorized network participant can access the stored files. This makes shared working possible on these files. Conflicts between different versions of a document can be practically ruled out, as certain actions – such as editing or deleting – are blocked for other users as soon as you open a file. If users have to share the desired files on their own system instead, or transmit them using removable media, this would be considerably more time-consuming and cumbersome – and it would most likely result in different file versions. Another key advantage of using file servers is that it relieves the strain on client resources. With the exception of personal documents, essentially all business files and backups can be stored on the file server, depending on how the company wishes to use the file repository. And with the right organization (comprising directories, folders, etc.) users automatically have a much better overview of the entire file inventory. File Services On Windows Server 2008 R2 If the file server is configured for remote access over the internet, the files are also accessible on the go – much like an online storage service. But unlike a cloud solution, the company retains control of the files and their security at all times. This represents a clear advantage over third-party solutions. Summary of file server advantages: Easy organization of the entire file inventory High degree of clarity Convenient file sharing Collaboration without version conflicts Relief of client computers (almost unlimited storage possible) Remote access via WebDAV, (S)FTP, or SCP possible Data protection and security in your own hands File Services On Windows Server 2008 R2 File server: Practical but a challenge The advantages listed clearly show how valuable a file server can be. However, many companies make the mistake of underestimating the work involved in setting up and managing such a server. Companies often do without advance planning. As a result, not only is the hardware stretched to its limits after a short amount of time, but also many of the benefits of a file server don’t take effect. For example, if there is no clear principle for the assignment of rights, situations will likely arise in which users are unable to perform necessary actions. Problems may also occur when the directory and folder structure is unclear – or if no folder structure exists at all. If you’d like to use a file server, you should therefore consider these aspects from the very beginning, as well as a comprehensive security concept. In the case of the latter, this is important if the file server is also accessible over the internet. The installation and configuration of security software are just as critical as training the employees who access the file server. Only when they have been made aware of topics like cyber security and data protection can the configured protection mechanisms work as intended. This is also true when it comes to storing the files: Clearly communicate where and how files should be saved on the file server to prevent a chaotic data situation from occurring in the first place. File Sharing and Printer Sharing On Windows Server 2008 R2? File Sharing Definition - What does File Sharing mean? File sharing is the practice of sharing or offering access to digital information or resources, including documents, multimedia (audio/video), graphics, computer programs, images and ebooks. It is the private or public distribution of data or resources in a network with different levels of sharing privileges. File sharing can be done using several methods. The most common techniques for file storage, distribution and transmission include the following: Removable storage devices Centralized file hosting server installations on networks World Wide Web-oriented hyperlinked documents Distributed peer-to-peer networks File Sharing and Printer Sharing On Windows Server 2008 R2? Techopedia explains File Sharing File sharing is a multipurpose computer service feature that evolved from removable media via network protocols, such as File Transfer Protocol (FTP). Beginning in the 1990s, many remote file-sharing mechanisms were introduced, including FTP, hotline and Internet relay chat (IRC). Operating systems also provide file-sharing methods, such as network file sharing (NFS). Most file-sharing tasks use two basic sets of network criteria, as follows: Peer-to-Peer (P2P) File Sharing: This is the most popular, but controversial, method of file sharing because of the use of peer-to-peer software. Network computer users locate shared data with third-party software. P2P file sharing allows users to directly access, download and edit files. Some third-party software facilitates P2P sharing by collecting and segmenting large files into smaller pieces. File Hosting Services: This P2P file-sharing alternative provides a broad selection of popular online material. These services are quite often used with Internet collaboration methods, including email, blogs, forums, or other mediums, where direct download links from the file hosting services can be included. These service websites usually host files to enable users to download them. File Sharing and Printer Sharing On Windows Server 2008 R2? Once users download or make use of a file using a file-sharing network, their computer also becomes a part of that network, allowing other users to download files from the user's computer. File sharing is generally illegal, with the exception of sharing material that is not copyrighted or proprietary. Another issue with file-sharing applications is the problem of spyware or adware, as some file-sharing websites have placed spyware programs in their websites. These spyware programs are often installed on users' computers without their consent and awareness. File Sharing and Printer Sharing On Windows Server 2008 R2? Printer Sharing Definition - What does Printer Sharing mean? Printer sharing is the process of allowing multiple computers and devices connected to the same network to access one or more printers. Each node or device on the network can print to any shared printer and, to some extent, make changes to the printer settings, depending on the permissions set by the administrator for each user. File Sharing and Printer Sharing On Windows Server 2008 R2? Printer Sharing Definition - What does Printer Sharing mean? Printer sharing is the process of allowing multiple computers and devices connected to the same network to access one or more printers. Each node or device on the network can print to any shared printer and, to some extent, make changes to the printer settings, depending on the permissions set by the administrator for each user. File Sharing and Printer Sharing On Windows Server 2008 R2? Techopedia explains Printer Sharing If a printer is attached to a computer that supports printer sharing, the computer can share that printer with other computers on the same network. It does not matter whether the shared printer is old or new, as long as it is properly installed in one computer it can be shared by that computer. The sharing is facilitated by the OS, which handles the communication between computers and devices within the network and the printer itself. When a print request is sent from a networked computer, this is received by the computer where the shared printer is attached; this host computer initializes the printer and then sends the print job to it. Unfortunately, retrieval of the actual printouts still must be done manually by the initiator of the print job. In Windows 7 and 8, the printer sharing function can be activated in the Control Panel as follows: click on the Network and Sharing Center icon and then click "Change advanced sharing settings"; under "File and printer sharing", select the "Turn on file and printer sharing" radio button. File Sharing and Printer Sharing On Windows Server 2008 R2? Standard and Public File Sharing Windows Server 2008 R2 supports two types of file sharing, referred to as public file sharing and standard file sharing. In the case of public file sharing any files to be shared must be copied to the server's Public folder located at %SystemDrive%\Users\Public, which in turn contains a number of sub-folders for categories such as documents, downloads, music pictures and videos. New folders may, of course, be created to fulfill other requirements. Once placed in this folder the files are accessible to any users logged locally onto the machine and, if enabled, to any network users. Public sharing provides some control over access to the files. For example, when the server belongs to a workgroup the public folder can be password protected. In addition, network access to files within the public folder can be restricted to reading and executing only or given permission to read, write, create and delete files. Standard file sharing, which is only permitted on NTFS volumes, allows individual folders, files and volumes to be shared to specific users. This provides far greater levels of security over network access through a combination of NTFS file and folder permissions and share permissions, and avoids the necessity to move files from their existing location in order to share them. File Sharing and Printer Sharing On Windows Server 2008 R2? Standard and Public File Sharing Windows Server 2008 R2 supports two types of file sharing, referred to as public file sharing and standard file sharing. In the case of public file sharing any files to be shared must be copied to the server's Public folder located at %SystemDrive%\Users\Public, which in turn contains a number of sub-folders for categories such as documents, downloads, music pictures and videos. New folders may, of course, be created to fulfill other requirements. Once placed in this folder the files are accessible to any users logged locally onto the machine and, if enabled, to any network users. Public sharing provides some control over access to the files. For example, when the server belongs to a workgroup the public folder can be password protected. In addition, network access to files within the public folder can be restricted to reading and executing only or given permission to read, write, create and delete files. Standard file sharing, which is only permitted on NTFS volumes, allows individual folders, files and volumes to be shared to specific users. This provides far greater levels of security over network access through a combination of NTFS file and folder permissions and share permissions, and avoids the necessity to move files from their existing location in order to share them.