New to Windows Server 2012 - Part 1: Server Management
I present to you the translation of the first part of the article by Michael Pietroforte about innovations in Windows Server 2012. Michael is an MVP with 28 years of system administration experience. If the article is of interest to the community, with pleasure, I will post the translation of the remaining parts.
The original can be read here: New in Windows Server 2012 - Part 1: Management
First of all, I want to apologize in advance if I miss any important innovations of Windows Server 2012. I would be grateful if you let me know in the comments and, I will add to the article. I draw your attention that I provide only a brief description of each technology. Links to the detailed description are provided at the bottom of each section
')
Windows 8 caused a lot of controversy and discussion. The culprit of most of them is the transition to the new Metro user interface. Nevertheless, I believe that Windows Server 2012 will be a very important step in the development of the Windows Server family of systems. One article was enough to list all the innovations of Windows 8 . For Windows Server 2012, I need five. Each of them will be devoted to a separate area: Server Management, Data Storage, Security, Virtualization, and Active Directory Directory Service.
The new Metro interface is undoubtedly one of the most controversial innovations of Windows 8. On the one hand, most of us agree that the growing popularity of tablets requires a new user interface for the client operating system, on the other hand, many administrators are wondering why the tablet interface is offered to us for servers in Windows Server 2012. Microsoft itself calls the main reason - the sequence. Most administrators work with both client and server machines and prefer to learn only one new interface. Moreover, the Metro Start Screen can become a popular server panel displaying various information about installed administration tools from various developers. After all, a server is a personal computer that performs many operations in the background and constantly interacts with the user. Servers and tablets are not so very different. Be that as it may, I believe that Microsoft may give administrators the choice of whether to disable the Metro interface in Windows Server 2012.
Windows 8 Metro - Disable in Windows Server 2012?
Rocking the Windows Server “8” Administrative Experience
I'm not a big fan of PowerShell, but it seems to me that the improvements in PowerShell 3.0 are huge. Windows Server 2008 R2 comes with ~ 230 cmdlets, while Windows Server 2012 has about 2.430. Many of the new features in PowerShell 3.0 are related to improvements in the WMI (Windows Management Instrumentation) service. Now you can literally automate everything. Well, almost everything. The cmdlet I’m still lacking is the one that allows you to automate automation. I believe that “developmins” will continue to write scripts manually for some time. However, there is another way to automate automation. You can install an application that someone has already developed for you that automates standard administrative tasks.
What's New in Windows PowerShell 3.0
Windows Server 2012, PowerShell 3.0 and DevOps, Part 1
Windows Server 2012, PowerShell 3.0 and DevOps, Part 2
Standards-based Management in Windows Server “8”
Windows Deployment Services (WDS) is a popular solution for centralized OS installation, designed for small and medium-sized companies. In Windows Server 2012, WDS has undergone many changes that make it a more flexible and powerful tool; I will list here a few of them. Most of the innovations associated with customization and filters that allow you to better control which images are installed. For example, WDS allows you to use filters for new installation images and control which clients can boot using the PXE server.
Innovation is also WDSclient.exe. This is a separate tool that can be used in scripts to perform Dynamic Driver Provisioning (DDP) requests, direct assignment of VHDs and metadata requests. In addition, WDS now supports separate server mode, which allows installing OS images without Active Directory domain. Also added support for the .vhdx format, support for TFTP multicasting and multicasting over IPv6 and DHCPv6, there is no need to create a local copy of the install.wim file, added the ability to apply the install.wim file in parallel with multicast loading, improved driver import, by adding driver filters and driver detection duplicates, network boot support for x86 clients with UEFI has been implemented.
What's New for Windows Deployment Services
The main innovations of the server management snap-in are support for connecting to multiple servers, a Metro-style work pane, more customization settings, filters, and easier access to administrative tasks via context menus. The Windows Server 2012 Server Management snap-in allows you to connect to servers running Windows Server 2008 and Windows Server 2008 R2.
Rocking the Windows Server “8” Administrative Experience
IP Address Management (IPAM) is a generic term that refers to server management tasks related to monitoring and scheduling an address space on a network. Windows Server 2012 offers us a new powerful tool - IPAM Server, which helps automate the management of IPAM. It supports the management of automatic configuration of network parameters (DHCP server, DNS server and domain controllers), display and creation of reports on custom IP address spaces, audit of changes in server settings, management and monitoring of DHCP and DNS services.
IP Address Management (IPAM) in Windows Server 2012
IP Address Management (IPAM)
<p5> DHCP failover
Failover DHCP offers two modes of operation in Windows Server 2012: Standby Mode and Load Sharing Mode. In standby mode, the auxiliary DHCP server issues IP addresses only when the primary DHCP server is unavailable. In load balancing mode, both DHCP servers issue IP addresses in parallel, based on custom load balancing parameters.
DHCP Failover in Windows Server 2012
Step-by-Step: Configure DHCP for Failover
Understand and Troubleshoot DHCP Failover
A DHCP server running Windows Server 2012 can issue IP addresses to clients, depending on various criteria (manufacturer class, user class, MAC address, client ID, or information from the relay agent service).
Step-by-Step: Configure DHCP Policy-based Assignment
The new Task Manager in Windows Server 2012 provides more information about running applications and processes in the updated user interface.
Overview of the Task Manager in Windows Server 2012
In the next article, I will look at new storage management features in Windows Server 2012.
The original can be read here: New in Windows Server 2012 - Part 1: Management
First of all, I want to apologize in advance if I miss any important innovations of Windows Server 2012. I would be grateful if you let me know in the comments and, I will add to the article. I draw your attention that I provide only a brief description of each technology. Links to the detailed description are provided at the bottom of each section
Metro style Windows Server 2012
')
Windows 8 caused a lot of controversy and discussion. The culprit of most of them is the transition to the new Metro user interface. Nevertheless, I believe that Windows Server 2012 will be a very important step in the development of the Windows Server family of systems. One article was enough to list all the innovations of Windows 8 . For Windows Server 2012, I need five. Each of them will be devoted to a separate area: Server Management, Data Storage, Security, Virtualization, and Active Directory Directory Service.
Metro
The new Metro interface is undoubtedly one of the most controversial innovations of Windows 8. On the one hand, most of us agree that the growing popularity of tablets requires a new user interface for the client operating system, on the other hand, many administrators are wondering why the tablet interface is offered to us for servers in Windows Server 2012. Microsoft itself calls the main reason - the sequence. Most administrators work with both client and server machines and prefer to learn only one new interface. Moreover, the Metro Start Screen can become a popular server panel displaying various information about installed administration tools from various developers. After all, a server is a personal computer that performs many operations in the background and constantly interacts with the user. Servers and tablets are not so very different. Be that as it may, I believe that Microsoft may give administrators the choice of whether to disable the Metro interface in Windows Server 2012.
Windows 8 Metro - Disable in Windows Server 2012?
Rocking the Windows Server “8” Administrative Experience
Powershell 3.0
I'm not a big fan of PowerShell, but it seems to me that the improvements in PowerShell 3.0 are huge. Windows Server 2008 R2 comes with ~ 230 cmdlets, while Windows Server 2012 has about 2.430. Many of the new features in PowerShell 3.0 are related to improvements in the WMI (Windows Management Instrumentation) service. Now you can literally automate everything. Well, almost everything. The cmdlet I’m still lacking is the one that allows you to automate automation. I believe that “developmins” will continue to write scripts manually for some time. However, there is another way to automate automation. You can install an application that someone has already developed for you that automates standard administrative tasks.
What's New in Windows PowerShell 3.0
Windows Server 2012, PowerShell 3.0 and DevOps, Part 1
Windows Server 2012, PowerShell 3.0 and DevOps, Part 2
Standards-based Management in Windows Server “8”
Windows Server 2012 - PowerShell 3.0
Windows Deployment Services (WDS)
Windows Deployment Services (WDS) is a popular solution for centralized OS installation, designed for small and medium-sized companies. In Windows Server 2012, WDS has undergone many changes that make it a more flexible and powerful tool; I will list here a few of them. Most of the innovations associated with customization and filters that allow you to better control which images are installed. For example, WDS allows you to use filters for new installation images and control which clients can boot using the PXE server.
Innovation is also WDSclient.exe. This is a separate tool that can be used in scripts to perform Dynamic Driver Provisioning (DDP) requests, direct assignment of VHDs and metadata requests. In addition, WDS now supports separate server mode, which allows installing OS images without Active Directory domain. Also added support for the .vhdx format, support for TFTP multicasting and multicasting over IPv6 and DHCPv6, there is no need to create a local copy of the install.wim file, added the ability to apply the install.wim file in parallel with multicast loading, improved driver import, by adding driver filters and driver detection duplicates, network boot support for x86 clients with UEFI has been implemented.
What's New for Windows Deployment Services
Windows Server 2012 - Windows Deployment Services (WDS)
Server manager
The main innovations of the server management snap-in are support for connecting to multiple servers, a Metro-style work pane, more customization settings, filters, and easier access to administrative tasks via context menus. The Windows Server 2012 Server Management snap-in allows you to connect to servers running Windows Server 2008 and Windows Server 2008 R2.
Rocking the Windows Server “8” Administrative Experience
Windows Server 2012 - server management snap-in
IP Address Management (IPAM)
IP Address Management (IPAM) is a generic term that refers to server management tasks related to monitoring and scheduling an address space on a network. Windows Server 2012 offers us a new powerful tool - IPAM Server, which helps automate the management of IPAM. It supports the management of automatic configuration of network parameters (DHCP server, DNS server and domain controllers), display and creation of reports on custom IP address spaces, audit of changes in server settings, management and monitoring of DHCP and DNS services.
IP Address Management (IPAM) in Windows Server 2012
IP Address Management (IPAM)
Windows Server 2012 - IPAM
<p5> DHCP failover
Failover DHCP offers two modes of operation in Windows Server 2012: Standby Mode and Load Sharing Mode. In standby mode, the auxiliary DHCP server issues IP addresses only when the primary DHCP server is unavailable. In load balancing mode, both DHCP servers issue IP addresses in parallel, based on custom load balancing parameters.
DHCP Failover in Windows Server 2012
Step-by-Step: Configure DHCP for Failover
Understand and Troubleshoot DHCP Failover
Windows Server 2012 - Failover DHCP
Policy-based IP address assignment
A DHCP server running Windows Server 2012 can issue IP addresses to clients, depending on various criteria (manufacturer class, user class, MAC address, client ID, or information from the relay agent service).
Step-by-Step: Configure DHCP Policy-based Assignment
Windows Server 2012 - Policy-based IP address assignment
Task manager
The new Task Manager in Windows Server 2012 provides more information about running applications and processes in the updated user interface.
Overview of the Task Manager in Windows Server 2012
Windows Server 2012 - Task Manager
In the next article, I will look at new storage management features in Windows Server 2012.
Source: https://habr.com/ru/post/166785/
All Articles