Inclusion of Windows Deployment Services - Case Study Example

Analysis of the Windows server and Introduction Technology has witnessed dynamism in therecent past. New versions of software are being released to the market with vast performance capabilities and features. More versions of user friendly, machine friendly and secure software packages are being released by vendors very now and then. For years, Microsoft has released different versions of their windows server. The different versions come with improved features and capabilities that suit the user requirements for competitive advantage. This has been marked with the release of windows server 2012, a version that came out with a mix of editions targeting various segments of their customers. Editions and Deployment The release of the Windows Sever 2012 brought about increased functionality in terms of deployment in which deploying the system is eased. This has been achieved through inclusion of Windows Deployment Services (WDS), an application that aids users while deploying the product. The Windows Deployment Service is a feature that has greatly revolutionized the windows server functionality and performance. It does not only act as a deployment platform but also as a perilous infrastructure constituent for deployment of real solutions such as Configuration Manager (Hernandez, 2013). The Windows Deployment Services feature that comes integrated with the windows server 2012 plays a critical role in the deployment of other tools that come integrated with the release, the Configuration Manager and the Microsoft Deployment Toolkit. Nevertheless, the windows deployment services on its own lack the capacity to support the operating system’s features necessary for the deployment of Windows servers and clients within an institution. Combination of the Windows Deployment Services and the Microsoft Deployment Toolkit or the Configuration Manager gives a more capable solution for deployment purposes, a feature that comes with the windows server 2012 releases. With the combination, a number of features are observed. These include real-time monitoring of the deployment activities, establishment of operating system deployment dynamic settings, auto updates deployment of windows at restart, applications deployment of all windows versions and the management of interfaces for building and managing applications within the release (Hernandez, 2013). Server Editions Different versions of Windows server 2012 are available from which different persons and organizations opt for their business and personal needs. The importance of each version is associated with the roles and the needs for which businesses choose them. The new version of the windows server was released with four different editions. These include the standard edition, the Datacenter edition, Foundation and the Essentials Edition. Each of the editions brought an additional feature to the versions making it easier for institutions to select the best version that fits their requirement. Edition Intent Major feature Licensing Clients List price Datacenter Highly virtualized environments Unlimited virtual instance rights Processor x 2 Per CAL $4,809 per 2 procs Standard Little virtualization, low density Two virtual instances Processor x 2 Per CAL $882 per 2 procs Essentials Small business Simple administration, no virtualization rights Per Server 25 accounts $425 Foundation Entry level, economy server General purpose server, no virtualization rights Per Server 15 accounts OEM only Table 1.1: a description of the different features that comes with the editions of Microsoft Windows Server 2012 (adopted from http://www.techrepublic.com/blog/data-center/microsoft-announces-four-windows-server-2012-editions-what-you-need-to-know/ ) From the table above, it is clear that each of the four editions varies in terms of pricing, number of clients, intent of use and the major functions expected to perform. For the standard as well as the datacenter editions, pricing has been presented based on two processors to give the per two processor convention. This has been articulated to the fact that most servers are currently made up of the dual processor technology (Hernandez, 2013). For those who have single processor servers, splitting the license between servers is inapplicable and buying the single processor versions is thus highly recommended. After complete transition to this version of windows server will be achieved, institutions will be in a position to make their server edition strategies simplified in their favor. It is, therefore, clear that the release of the version with different editions by Microsoft is a step ahead towards replacement of the non-discontinued versions to the modern ones. Servers needed Different servers are required for successful deployment and implementation of the windows server 2012. These vary depending on the different roles and stages of the deployment, which in some instances require combination. The most basic server environments required for successful deployment of the windows server version include the Active Directory Server and the DNS server. DNS servers are responsible for the resolution of windows domain names to IP addresses. These are a critical component within the windows Active directory that aid in location of network resources (Taft, 2012). The DNS (Domain Name Servers) have a ubiquitous nature marked with a complex hierarchical structure. This makes it complex for most administrators to master and use for their management roles. There is inclusion of the DHCP servers (Dynamic Host Configuration Protocol server) which is an Internet Engineered Task Force (IETF) standard that aims at reducing the burden of administration and eases the configuration of hosts on networks based on the TCP/IP infrastructure. This is supported in the standard and Datacenter versions of the windows server 2012. Private intranets are an example of the TCP/IP network infrastructure in which configuration of clients occurs automatically. The DHCP server for windows server 2012 contains a number of features. These include the presence of enhanced DNS registration, options for DNS PTR registration, and the Windows PowerShell for the DHCP server. The DNS enhanced registration features the FQDN (Fully Qualified Domain Name) for all DHCP clients. This feature can be used in the registration of computers for a work group by utilization of guest DNS. Using the DNS PTR registration options, one can facilitate DNS cataloging of Address and pointer records. Active Directory Name serves are also an inclusion within the windows 2012 server deployment. In the windows server 2012 environment, the Active Directory Servers and the Dynamic Naming Servers are integrated for optimal performance. File and Printer Sharing server is another type of server required during deployment of the Windows Server 2012 operating system. The Server Core The Server Core has been presented as a new implementation option that comes with the deployment of the Standard, Datacenter and the Enterprise editions of the Windows Sever 2012. They provide minimal installation capabilities where a limited server functionalities and roles are implemented. It is an important option where the Active Directory, DHCP, DNS and other servers will be implemented and utilized. It is thus a very critical component that requires inclusion whenever deployment of the Windows Server 2012 is performed. Sever location In Windows Server 2012, the Active Directory Domain Server is used in the rapid and easy deployment of domain controllers which increase flexibility in authorization and auditing of file access. There is improved performance of administrative tasks that scales through the management experiences resulting from consistency of the experts performing the exercise. It is, therefore, clear that the servers installed reside within the active directory environment. Deployment of the servers Deployment of Windows Server 2012 can be performed using a number of available options. There is the use of the Server Core as well as the use of a wizard provided in a graphical user format. The wizard leads to the installation of the full package while the Server Core Installation results to a customized installation as only the required applications are selected form the package for deployment. Counterchecking the system features and capabilities against the installation requirements leads to proper and successful deployment of the server without any challenges. The sever core installation aims at reducing disk space, which is a way of reducing chances for potential attacks. There is also servicing requirements for the windows servers are also reduced and is thus the best choice for deploying the server. However, in the case of user requiring application of the graphical user interface tools and elements anywhere while using the application, you can use the graphical user interface installation option. As a result of the benefits associated with the use of the Server Core, installation has been set to Core as the default option. The fact that there is some flexibility switching freely between the two options later, one could choose to deploy the server using the graphical tool for easy configuration of the server and later switching to the core version. It is also possible to start the installation with the GUI option and later removing the Graphical shell. This results to what is known as a Minimal interface. Lastly, after completion of the installation in any of the cases, removal of the binary cells can be executed to get rid of the features and roles not required in the server. This is a way of saving the disk space and further reducing the surface for attacks. The DNS namespace design The Domain Name System forms a hierarchical structure used to name computer systems, resources and services involved or connected through the internet. On the hierarchy is the root domain at the top. This domain lacks a formal name and is thus represented using a bare string on the hierarchy. Name resolution through the use of Domain Naming is a core course in the administration and operation of the Windows Server 2012 operating system. Proper resolution of names should be ensured therefore. Without this, the resources within a network cannot be accessed. It is thus crucial for designers of the DNS to have in mind a design that includes an Active Directory and also have in mind the namespace existing on the internet to avoid it from conflicting with the internal namespace of the organization. Deployment of the DNS infrastructure requires designing of a namespace by the DNS designer. During deployment, an external namespace can be designed which should promote visibility through the internet by the users. This should be limited to users only within the network. After deployment, the administrator manages and maintains the namespace. For the secondary sites, handling the DNS will be dependent on the namespace used while deploying the operating system. The designer controls the access and control of second site through The Active Directory With the introduction of Windows Server 2012, there has been the inclusion of new features that emphasizes on integration of the Cloud that has become a buzz phrase within the industry. The Windows family of operating systems continues to develop to maturity while including more advanced features. Such capabilities as interoperability, security, robustness and reliability are making this system more preferred than earlier versions. Deploying applications to the cloud often requires the presence of windows server active directory. The directory is required for the purpose of authentication, authorization and the management of the server identity. File and Printer Sharing A number of file and printer sharing conventions can be implemented during the deployment of windows server 2012 operating system. These include file sharing, printer sharing, sharing of the public folders as well as password protected sharing. The file sharing option allows administrators and users with privileges to share folders and files that could be saved in computers within the network. When public folder sharing is activated, all public files and folders are accessible by all the users within a network. Printer sharing, on the other hand, ensures that users are in a position to share any installed printer within the network. Allowing the printer share option also allows files sharing option. Finally, the password protected shares are a way of restricting access by the unauthorized users to files and folders stored in a computer or the main server. For access to such files, one should have access to the password and username as set by the administrator. The File Server Resource Manager (FSRM) is a feature in the Windows Server 2012 that offers the capabilities for management of advanced quota and directories. Presently, the quota system has been made based on the directories unlike the earlier versions where they were set and managed by users of the windows. There is, therefore, faster and more convenient means for restricting the amount of data and content that users upload to the system’s root directory. Configuration of the system per user is also easy to control and manage. Before utilizing the capabilities of the file server resource manager, setting the manager options should be performed. This can be achieved through proper configuration of the files, management of the quota and informed screening of the management of files. The DFS namespace implementation is most likely to take place during deployment of the windows server 2012 operating system as it gives the system an advantage where replication of files is necessary (Taft, 2012). Where new servers are to be implemented, organizations enjoy the feature of file replication. In the case of growth and expansion of businesses, there will be reduced chances of drive mappings and should thus be included during the deployment of new windows server operating system. Remote services In the windows server 2012, remote services have been seen as a source of single infrastructure and consistently great experience of user access even over Wide Area Networks and at the same time offering different choices for the deployment of the application. Some of the options provided for the deployment of the framework include Session, Personal and Pooled virtual desktop collections, all of which have the aim of collecting and reducing the costs to suit users’ needs. This simplifies administration and provides hooks that aid in the extension of partnership for value additions and problem solving. Configuring the remote services in the windows server 2012 operating system for security is very crucial. It is achieved through a number of practices as described herein: first, setting levels for the server encryption and authorization plays a great role. This can be achieved through enhancement of the Remote Desktop Services security. With this, the system is configured in a manner that it has three security layers and a certificate is used as a verification tool for the Remote Desktop sessions’ clients and hosts. The certificate is based on the TLS 1.0 layer as is described in the table below. The Remote Desktop Services have the utmost heights of encryption. With the Windows server 2012release, the levels of encryption are higher than previous releases. Table 2.0:Description of the different security layers supporting remote access control (adopted from < http://technet.microsoft.com/en-us/library/cc770833.aspx>) The remote services are also configured in a manner that the level of network authentication is regulated. Client login to access information within the remote desktop services is also an aspect to be considered while configuring security settings for the remote desktop services. Finally, permissions with regards to user access to remote services will be considered while configuring the connections. Only users with access rights and privileges can have access to remote services in a network setup and are thus a perfect way for ensuring system security. Conclusion In the modern world, organizations rely greatly on networking for their businesses and operations to thrive. System operation engineers should possess the ability, awareness, and proficiency in the planning and management of organization’s network facility in which more applications are being developed and implemented. To deploy and manage networks running on the windows server 2012 platform, technical knowhow on the way the system works is critical. Many network administrators are presently facing difficulties while attempting to avail resources to the users of their networks due insufficient knowledge on the way the operating system work. The security of resources stored within the networks is compromised putting the users of the system at the risk of possibly losing data. Using the features availed by the windows server 2012 operating system; most of these issues will be solved. It provides features for secure installation as is in the case of the Core installation, troubleshooting, easy and customized administration, and finally the centralized management of elements. Organizations should start by selecting the most appropriate edition of the Windows Server 2012 operating system to meet their organizational needs. This should be in terms of pricing, performance and features in relation to the available system capabilities. References Hernandez, P. (2013). Microsoft Releases Windows Server 2012 R2 Essentials Preview. Eweek, 6. Taft, D. K. (2012). Windows Server 8 Is Now Officially Windows Server 2012. Eweek, 16. Read More