VM Chimney, also referred to as TCP offload, has been removed and will no longer be available to guest operating systems. The WMI root\virtualization namespace is changed to just root\virtualization\ v2 and will eventually be taken out completely in future Server versions. Authorization Manager (AzMan) has also been deprecated in this version and will be phased out in future releases. Th e new management tools for virtual machines will be the new standard.
 |
| Microsoft_Windows_Server_2012 |
Virtual Desktop Infrastructure
In Windows Server 2012 R2, Microsoft has made vast improvements to the virtual desktop infrastructure (VDI), with simpler administration, increased value, and better overall user experience.Supporting mobile devices is a must in today’s market. Virtual desktop infrastructure helps bridge the compatibility gap between devices by virtualizing resources. VDI provides stronger security and higher effi ciency that improves productivity with a UI that the user is familiar
with. Windows Server 2012 R2 and VDI make it a snap to deploy virtual resources across devices.
Windows Server 2012 R2 VDI, if running in a datacenter, will allow access for mobile devices using Hyper-V and Remote Desktop Services. Microsoft offers three different deployment types in a single solution: pooled desktops, personal desktops, and remote desktop sessions.
Networking Changes
Servers are no good without the ability to talk to one another, but—of course—the downside of being able to communicate with other systems means that infected systems can try to spread their malware joy. (“Want to secure your server? Easy...disconnect the Ethernet cable!”) Server 2012 R2 offers some networking changes to make Windows networking a bit faster and a bit more secure.
EAP-TTLS
With Windows Server 2012 R2 an exclusive protocol is being introduced as an Extensible Authentication Protocol (EAP) type called Tunneled Transport Layer Security (TTLS). This protocol is used with 802.1X Authenticated Wired and Wireless access. This new standards based protocol provides a secure tunnel for client authentication. 802.1X provides a security shield that prevents unauthorized access to your intranet.
DNS
Although DNS has been around forever, the process by which it translates names seems to get better with each version. Changes in Windows Server 2012 R2 affect both DNS Server and Client. Let’s take a look at the changes for Windows Server 2012 R2. In PowerShell, DNS management has received some improvements. The DNS Server role, for example, has had some improvements to installation and removal using PowerShell. Additional
developments in PowerShell include user interface, client query, and server configuration on older operating systems. The LLMNR query time-out has been 300 msec, which was not enough time for computers in power save mode. With the new improvements to DNS Client, this timeout has been increased to 820 msec.
IP Address Management
The IP Address Management (IPAM) framework is a new set of technologies for managing, monitoring, and auditing IP address space. By monitoring DHCP and DNS, IPAM can locate IP address servers within your network and allows you to manage them from a single central UI.
NIC Teaming
NIC Teaming technology in Windows Server 2012 R2 can take multiple network interface cards and team them together to interface as one. Doing so helps with failover should one device become inoperative. Load balancing is also improved when NICs are teamed because the bandwidth is combined into a single larger bandwidth.
You can read more about these topics and new features in upcoming post,
Windows Server 2012 R2 Networking Enhancements, and
IP Address Management and DHCP Failover.
Post a Comment