COURSE: CMIT 369 WINDOWS SERVER: INSTALL AND STORAGE (2188)
INSTRUCTOR NAME: BRIAN NELSON
STUDENT NAME: DAMILARE THOMAS
WINDOWS PROJECT: WINDOWS SERVER DEPLOYMENT PROPOSAL
DATE: 11/30/2018
TABLE OF CONTENTS
Summary- 3
New Features of Windows Server 2016 – 4
• New features of Windows Server 2016 implemented
Deployment and Server Editions- 5-6
• Total servers utilized and roles that will be combined
• Edition of Windows used
• Server Core deployment
• Location of servers
• Server deployment
Active Directory- 6-7
• Number of AD domains
• Read-Only Domain Controllers
• Domain Controller Placement and Configuration
• AD Organizational Units Organization
DNS and DHCP – 7
• DHCP scope design
• DHCP reservations
• DNS Namespace Design
Application Services – 8
• Application Deployment
• Software Application
File and Printer Sharing – 8-9
• Shares
• File Permissions
Conclusion – 10
References – 11
Summary
In our contemporary world of technology, it will behoove any new organization opening business to implement a solid foundation system which is reliable and secure. Network is an important piece when building an organization. In order to choose a well-developed network server, proper planning is imperative. And planning could be based off the organization’s needs assessment; system requirements, network information, and the size and type of organization.
In this project assigned by the “We Make Windows” (WWW) Inc., I will be implementing a new windows network infrastructure for the organization. I will discuss the latest Windows features I will be using, the server edition type, and how I will deploy them. I will also talk discuss about AD domains, DNS namespace, DHCP scope, application deployment, software application, and file and printer sharing service I will be implementing in this project. This project has undergone proper analysis and planning, and the recommendations suggested will be based strictly on the organization’s budgets, needs, and requirements.
New Features of Windows Server 2016
Out of many latest features that are available with the Windows Server 2016, I will suggest that WWW utilize the following:
1. Data Deduplication: this is a feature of the Windows Server 2016 which helps to reduce data redundancy and storage cost. Also known as “Dedup”, it is designed for storage of data in less physical space using “subfile variable-size chunking and compression” (Microsoft, 2017). Since WWW will have two sites, there might be a lot of data redundancy. This feature would be the best bet to mitigate this problem and save storage space.
2. Hyper-V: another effective feature I would recommend will be Hyper-V. It can be used by the organization’s IT consultants or system administrators to create and run software versions of a physical computer which are known as virtual machines. Other benefits of Hyper-V include establishment of a private cloud environment, development of more efficient systems, and efficient use of hardware (Microsoft, 2017). These are all features that will enhance the WWW overall network infrastructure.
3. Server Manager: This is a management console in the Windows Server 2016 that helps system administrators to manage all their organization’s servers both physical, cloud, or remote based. WWW’s IT consultants and system administrators would definitely benefit from this feature due to easy access of all servers in their both sites.
Deployment and Server Editions
Servers are available in different editions. After evaluating the needs of WWW, and requirement of a network server to serve 90 workers, I would recommend the Windows Server 2016 Standard edition which is suitable for a small to medium-sized organization. However, since the WWW will be having two different locations of operations, I will be recommending the Windows server 2016 Essentials. It is suitable for a small organization and has capability with a maximum of 25 users and 50 devices (Testout, 2018). Regarding the needs for 90 people, 7 servers will be needed. 4 servers will be located in the Los Angeles site and 3 will be located in the New York site. This server will be more than enough and encourage room for expansion as the organization keeps growing. I would prefer single role on each server for security purposes since there are enough servers. But server roles that will be combined will only be the DNS and DHCP. And a feature that can be combined is the file and printing services.
Server Core will be used on some of the servers. I will recommend that the IT consultants in both WWW’s sites have their own servers with Server Core installed because the Server Core User Interface is not a friendly user interface. However, IT consultants should not have problems working with them. Deployment of Server Core will encourage improved system stability because it runs few processes and requires less maintenance (Testout, 2018).
Each of the servers will be deployed and located in the following way:
Table 1: Server deployment roles and location
Server Roles Location
1 AD / DHCP / DNS NY
2 File / Print Services NY
3 Web / Application Services NY
4 AD LA
5 DHCP/DNS LA
6 File/Print/Web Services LA
7 Application/WDS LA
All the servers will be deployed with an automated system in other to save money, time, and manpower. Servers will be deployed by using the Windows Deployment Services (WDS). WDS is a revised version of the Remote Installation Services. It enables the set-up of new clients with a network-based installation without the physical presence of system and network administrators at each site.
Active Directory
This is the central and principal database. User accounts and security information are all contents of the AD. I will deploy two AD as shown in table 1. The main and primary domain controller will be stationed at the L.A. site and the secondary will be stationed at the N.Y. site. Read-Only domain controller (RODC) will not be deployed in any of the sites because there is a stabilized domain controller in both locations already. Since L.A. is the main site and all processes have to go through L.A. site to N.Y. To create this replication from L.A. to N.Y., I will create sites for the DC in both locations. After creating these sites, I have to define a link to connect the two new sites together. I will configure the site links with the AD sites and services tool.
I will organize the AD organizational units (OU) ranging from site to department. Each of the departments will have the following branches: OU, executives, accounts and sales departments, creative media and production department, human resources and finances and IT. Group policy will be created and applied to every OU and department. Each OU and department will have permissions and rights assigned to their folders/subfolders and files. This will encourage access to files and folders by only authorized personnel. System administrators and IT consultants will have access to all departments’ files and folders to enable them to assign and manage permissions and rights.
DNS and DHCP
DHCP is a client or server protocol that automatically provides an IP host with its IP address and other configuration information like subnet mask and default gateway. DHCP is very essential in an organization for network internet connection. I will implement DHCP for both fault tolerance and load balancing. The scope design will include all the DHCP servers in both sites. I will then configure the servers in load balance mode. This allows continuation of work even if one server has a malfunction. The DHCP scope will have an IP address range of 192.168.1.2 to 192.168.1.110.
I will use DHCP reservation for all servers so that the same IP can be assigned to them in other to speed up the response time.
I will set the lease times to default to ensure that there are enough IP addresses every time.
DNS is a “hierarchical distributed database that maps logical host names to IP addresses” (TestOut LabSim, 2018). Without DNS services, users will have problems to connect to the internet. DNS server will be located at each site as shown in table 1. This will enable users to access the internet in both locations.
I will implement an internal private domain for the DNS name space design and I will assign (la.wai.localhost) as the parent while (ny.wai.localhost) as the child. I will setup the Split DNS with two different DNS Scopes. One of the scopes will be used for the internal DNS records and the other will be used as the external DNS records, and they will be hosted on the same server. This will avoid foot printing and enable secure information on the DNS servers.
Applications Services
I will deploy all applications by using group policy which enable prompt installation and limited errors. Share folders will be created and MSI file will be added to the folders. I will then create GPO; all users and computers will be assigned any application as needed and will be granted necessary access as required. And GPO will be updated to complete the process.
Some software applications I will recommend and will be needed by WWW are: AVAST antivirus or Kaspersky security to protect against malwares, Google Chrome/Mozilla/Internet Explorer to access the web, Microsoft office (Word, Excel, PowerPoint, Adobe, etc) to create, edit, design, and publish documents, and QuickBooks accounting software for the finance and accounting department.
File and Printer Sharing
As shown in table 1, there will be two file and printing services’ servers in both L.A. and N.Y. sites. I will enable file and printer sharing features on all the servers.
SMB share quick and NTFS will be needed. I will create 5 shares for the WWW departments; Executives, Accounts and Sales Department, Creative Media and Production department, Human Resources and Finances and IT. For departments that will require limited access to all users due to security of information, I will enable file and printer sharing with NTFS permissions for security measures. I will enable Access-based enumeration for all users except the system administrators. This will restrict users from accessing all files and folders that they are not permitted to access.
To organize the shared resources on the network, I will use Distributed file system (DFS). This will enable all users in both locations to access shared files and folders. DFS namespaces enables grouping of shared folders located on different servers into a more logically structured namespace. “DFS will also be used to allow efficient and well-managed data and storage sharing” (Techopedia, 2018).
I will also implement file server resource manager to manage quotas and all data stored on the file servers. I will use quota template to create quotas for all departments in WWW. Each user will be assigned and slotted a storage spaces based on their needs. Users will also get soft quotas assigned to them in case they run out of space to store important files.
I will implement the print management console to manage the print servers. V4 printer devices will be used to set up print server to eradicate the need to install print drivers on all users’ devices and to make sharing easier. Print servers will be deployed using group policy to enable all users’ access to printing services.
Conclusion
In our contemporary world of technology, it will behoove any new organization opening business to implement a solid foundation system which is reliable and secure. Network is an important piece when building an organization. In order to choose a well-developed network server, proper planning is imperative. And planning could be based off the organization’s needs assessment; system requirements, network information, and the size and type of organization.
I have implemented the latest Windows features to ease organization’s activities by making them faster, easier, and more efficient. I have also implemented AD domains which is the backbone of any organization. To give WWW the best network and internet connection, I have implemented DHCP and DNS. Also, necessary applications and software have been installed to increase users’ activities and productivity. Finally, file and print servers are readily available to save and secure files, share and accept files, and print documents. All the above implementations and recommendations are based on WWW’s required needs.
References:
1. Wmgries. “Data Deduplication Overview.” Microsoft Docs, Retrieved on 5th December 2018 from docs.microsoft.com/en-us/windows-server/storage/data-deduplication/overview.
2. KBDAzure. “Hyper-V Technology Overview.” Microsoft Docs, Retrieved on 5th December 2018 from docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview.
3. “What Is Distributed File System (DFS)? – Definition from Techopedia.” Techopedia.com, Retrieved on 5th December 2018 from www.techopedia.com/definition/1825/distributed-file-system-dfs.
4. “Data Deduplication Facts.” TestOut LabSim, Retrieved on 5th December 2018 from cdn.testout.com/client-v5-1-10-542/startlabsim.html.
5. 3. Mearian, Lucas. “Data Storage — Then and Now.” Computerworld, Computerworld, 14 Mar. 2014, Retrieved on 5th December, 2018 from www.computerworld.com/article/2473980/data-storage-solutions/data-storage-solutions-143723-storage-now-and-then.html.
6. “DHCP Facts.” TestOut LabSim, Retrieved on 5th December, 2018 from https://cdn.testout.com/client-v5-1-10-542/startlabsim.html