In this course, you are introduced to general Windows Server concepts like activ

Question

In this course, you are introduced to general Windows Server concepts like active directory, group policy, security, networking and IIS, access control, and much more. Now that you understand the basic concepts, we will delve a little deeper and look in more detail, by examining the offerings of different versions. This Course Project will be a research report that will cover five of the differences between Windows Server 2008 and Windows Server 2012 that interest you the most. Be sure to provide a clear and thorough description for each of the five areas that you choose in the report.

For Week 4, you will need to submit a comprehensive outline of the report which reflects a substantial amount of research already done. The report itself will be assigned in Week 5, to be submitted at the end of Week 6.

Some example topics to be researched include, but are not limited to, the following.

Hyper-V

Active directory (including DS and RMS)

IPAM (IP address management)

ReFS (operating system)

SMB (server message block) 3.0 file storage

Network services (IIS) and support for cloud-based strategies and web applications

Dynamic access control

Please, I need help on how to write comprehensive outline on above topics,

Explanation / Answer

Hyper-V, codenamed Viridian[1] and formerly known as Windows Server Virtualization, is a native hypervisor; it can create virtual machines on x86-64 systems.[2] Starting with Windows 8, Hyper-V supersedes Windows Virtual PC as thehardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks.

Hyper-V was first released alongside Windows Server 2008 and has since become a staple of the Windows Server family.

Hyper-V in Windows Server 2012 and Windows Server 2012 R2 changes the support list above as follows:

Windows Server 2012 introduced many new features in Hyper-V.

Active directory (including DS and RMS)

Microsoft Active Directory Domain Services (AD DS) is a Windows-based directory service. AD DS stores information about objects on a network and makes this information available to users and network administrators. For example, these objects can include user and computer accounts. AD DS is a requirement for installing and implementing AD RMS.

Active Directory Domain Services (AD DS) stores directory data and manages communication between users and domains, including user logon processes, authentication, and directory searches.

Active Directory Rights Management Services (AD RMS) protects your information and works with AD RMS-enabled applications to help safeguard digital information from unauthorized use.

IPAM (IP address management)

IP Address Management (IPAM) in Windows Server® 2012 and Windows Server® 2012 R2 is an integrated suite of tools to enable end-to-end planning, deploying, managing and monitoring of your IP address infrastructure, with a rich user experience. IPAM automatically discovers IP address infrastructure servers on your network and enables you to manage them from a central interface.

IPAM includes components for:

Address Space Management

Virtual Address Space Management*

Multi-Server Management and Monitoring

Network Audit

Role-based access control**

* Virtual IP address space management is enabled through integration of IPAM with system center virtual machine manager and is available in Windows Server 2012 R2 and later operating systems. This feature is not available with IPAM in Windows Server 2012.

** Role-based access control is available in Windows Server 2012 using local user groups on the IPAM server. This feature was significantly enhanced in Windows Server 2012 R2 to include detailed built-in and custom role-based access groups.

Key features of ASM include the following.

Integrated management of dynamic and static IP address space

Detection and management of conflicts, overlaps, and duplicates in address space across systems

Highly customizable inventory view of IP address space

Centralized monitoring and reporting of address utilization statistics and trends

Support for IPv4 and stateless IPv6 address utilization monitoring

Automated discovery of IP address ranges from DHCP scopes

Export and import of IP addresses and IP address ranges with Windows PowerShell support

Windows customers want a cost-effective platform that maximizes data availability, scales efficiently to very large data sets across diverse workloads, and guarantees data integrity by means of resiliency to corruption (regardless of software or hardware failures). ReFS is a new file system that targets these needs while providing a foundation for significant future innovations. By utilizing an integrated storage stack comprising ReFS and the new Storage Spaces feature in Windows Server 2012, customers can now deploy the most cost-effective platform for available and scalable data access using commodity storage.

Storage Spaces protects data from partial and complete disk failures by maintaining copies on multiple disks. ReFS interfaces with Storage Spaces to automatically repair the corruption. For more information about Storage Spaces, see Storage Spaces Overview and the Storage Spaces Microsoft TechNet blog.

ReFS (operating system)

The key attributes of ReFS include:

Maintaining a high level of data availability and reliability, even when the individual underlying storage devices experience failures.

Providing a full, end-to-end resilient architecture when used in conjunction with Storage Spaces. When used together, ReFS and Storage Spaces provide enhanced resiliency to storage device failures.

SMB (server message block) 3.0 file storage

The Server Message Block (SMB) protocol is a network file sharing protocol that allows applications on a computer to read and write to files and to request services from server programs in a computer network. The SMB protocol can be used on top of its TCP/IP protocol or other network protocols. Using the SMB protocol, an application (or the user of an application) can access files or other resources at a remote server. This allows applications to read, create, and update files on the remote server. It can also communicate with any server program that is set up to receive an SMB client request. Windows Server 2012 introduces the new 3.0 version of the SMB protocol.

While SMB 3.0 solves many storage problems, one might wonder if Hyper-V is the motivator for this protocol investment.

Achieving all of this today with a SAN requires added protocols, techniques and management tools because today's SMB protocol doesn't support today's storage requirements. But why not just update the SMB protocol?

With SMB 3.0, it appears Microsoft has. This update, baked into both Windows 8 and Windows Server 2012, might just drive a wholesale shift away from SANs' complexities and to a simpler, NAS-like foundation.

I've long suggested that Microsoft's unnecessarily complex clustering architecture is a major hurdle to Hyper-V adoption. Since its inception, Windows Failover Clustering has been too difficult to construct, too difficult to use and too easy to break. SAN storage is a contributor to that complexity.

SMB 3.0 changes this game completely. With it, building a cluster requires pointing servers to a network file share. Everything else just happens. That's the dead-simple clustering experience a Hyper-V admin demands.

Network services (IIS) and support for cloud-based strategies and web applications

Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 runs ASP.NET applications in application pools that use the NT AUTHORITYNetwork Service account identity. This account is a least privileged machine account with limited permissions. An application that runs using this account has restricted access to the event log, registry, and file system. The account does have network credentials, which means you can use it to access network resources and remote databases by using Windows authentication. The network resources must be in the same domain as your Web server or in a trusted domain.

In some scenarios, using a custom domain service account is a better approach than using the Network Service account. You should use a custom domain service account if:

Dynamic access control

In Windows Server 2012, you can apply data governance across your file servers to control who can access information and to audit who has accessed information. Dynamic Access Control lets you:

Identify data by using automatic and manual classification of files. For example, you could tag data in file servers across the organization.

Control access to files by applying safety-net policies that use central access policies. For example, you could define who can access health information within the organization.

Audit access to files by using central audit policies for compliance reporting and forensic analysis. For example, you could identify who accessed highly sensitive information.

Apply Rights Management Services (RMS) protection by using automatic RMS encryption for sensitive Microsoft Office documents. For example, you could configure RMS to encrypt all documents that contain Health Insurance Portability and Accountability Act (HIPAA) information.

Related Questions

Navigate

• Browse (All)
• Browse I
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.