What’s new in Windows Server 2012 R2 networking?

What's new in Windows Server 2012 R2 (RTM)?
What's new in Windows Server 2012 R2 Storage?
What's new in Windows Server 2012 R2 Server Virtualization?
What's new in Windows Server 2012 R2 Networking?
What's new in Windows Server 2012 R2 Server Management and Automation?
What's new in Windows Server 2012 R2 VDI?
What's new in Windows Server 2012 R2 Access and Information Protection?
What's new in Windows Server 2012 R2 Web Application and Platform?
What's New in Windows Server 2012 R2 Essentials?
Whats new in Windows Server 2012 R2 in Web Application and Platform, Active Directory, Print Services and Clustering?

What’s New in Networking in Windows Server 2012 R2?

The following networking technologies are new or improved in Windows Server® 2012 R2 Preview.

802.1X Authenticated Wired Access in Windows 8.1 Preview and Windows Server 2012 R2 Preview provides new features and capabilities over previous versions.

For more information, see What’s New in 802.1X Authenticated Wired Access for Windows Server 2012 R2.

802.1X Authenticated Wireless Access in Windows 8.1 Preview and Windows Server 2012 R2 Preview provides new features and capabilities over previous versions.

For more information, see What’s New in 802.1X Authenticated Wireless Access in Windows Server 2012 R2.

Domain Name System (DNS) in Windows Server 2012 R2 Preview provides new features and capabilities over previous versions.

For more information, see What’s New in DNS Server in Windows Server 2012 R2.

Dynamic Host Configuration Protocol (DHCP) in Windows Server 2012 R2 Preview provides new features and capabilities over previous versions.

For more information, see What’s New in DHCP in Windows Server 2012 R2.

Hyper-V Network Virtualization (HNV) has many important updates that enable hybrid cloud and private cloud solutions.

For more information, see What’s New in Hyper-V Network Virtualization in Windows Server 2012 R2.

Hyper-V Virtual Switch provides new features and capabilities over previous versions.

For more information, see What’s New in Hyper-V Virtual Switch in Windows Server 2012 R2.

IP Address Management (IPAM) is a feature that was first introduced in Windows Server 2012 that provides highly customizable administrative and monitoring capabilities for the IP address infrastructure on a corporate network. IPAM in Windows Server 2012 R2 Preview includes many enhancements.

For more information, see What’s New in IPAM in Windows Server 2012 R2.

Remote Access provides new features and capabilities over previous versions.

For more information, see What’s New in Remote Access in Windows Server 2012 R2.

New in Windows Server 2012 R2 Preview, virtual Receive-side Scaling (vRSS) enables network adapters to distribute network processing load across multiple virtual processors in multi-core virtual machines (VMs).

For more information, see Virtual Receive-side Scaling in Windows Server 2012 R2.

New in Windows Server 2012 R2 Preview, Windows Server Gateway is a virtual machine (VM)-based software router that allows Cloud Service Providers (CSPs) and Enterprises to enable datacenter and cloud network traffic routing between virtual and physical networks, including the Internet.

Windows Server Gateway routes network traffic between the physical network and VM network resources, regardless of where the resources are located. You can use Windows Server Gateway to route network traffic between physical and virtual networks at the same physical location or at many different physical locations, providing network traffic flow in private and hybrid cloud scenarios.

For more information, see Windows Server Gateway.

 

What’s New in IPAM in Windows Server 2012 R2?

Feature/functionality New or improved Description
Role based access control New Role based access control enables you to customize the types of operations and access permissions for users and groups of users on specific objects.
Virtual address space management New IPAM streamlines management of physical and virtual IP address space in System Center Virtual Machine Manager.
Enhanced DHCP server management Improved Several new operations are available in IPAM to enhanced the monitoring and management of the DHCP Server service on the network.
External database support New In addition to Windows Internal Database (WID), IPAM also optionally supports the use of a Microsoft SQL database.
Upgrade and migration support New If you installed IPAM on Windows Server 2012, your data is maintained and migrated when you upgrade to Windows Server 2012 R2 Preview.
Enhanced Windows PowerShell support Improved Windows PowerShell support for IPAM is greatly enhanced to provide extensibility, integration, and automation support.

What’s New in DHCP in Windows Server 2012 R2?

Feature/functionality New or improved Description
DNS registration enhancements New You can use DHCP policies to configure conditions based on the fully qualified domain name (FQDN) of DHCP clients, and to register workgroup computers using a guest DNS suffix.
DNS PTR registration options New You can enable DNS registration of address (A) and pointer (PTR) records, or just enable registration of A records.
Windows PowerShell for DHCP server Improved New Windows PowerShell cmdlets are available.

What’s New in DNS Server in Windows Server 2012 R2

Feature/functionality New or improved Description
Enhanced zone level statistics Improved Zone level statistics are available for different resource record types, zone transfers, and dynamic updates.
Enhanced DNSSEC support Improved DNSSSEC key management and support for signed file-backed zones is improved.
Enhanced Windows PowerShell support Improved New Windows PowerShell parameters are available for DNS Server.

How to Configure DNS Reverse Lookup Zone in Windows Server 2012

Hi Community,

before we start with DHCP let us complette the DNS config by creating a Reverse Lookup Zone on our current DNS server.

1. The first thing we have to do is to open the “Server Manager” and than click “DNS” under “Tools”.

2. In the DNS MMC we click right on “Revers Loopup Zone” and select “New Zone…”.

3. Now the configuration wizzard starts. Klick “Next” to beginn.

4. Now you can select the zone type. In our case we select “Primary zone” and we want to store the information in Active Directory. So please select also “Store the zone in Active Directory”.

To learn more about DNS, feel free to visite Wiki page http://en.wikipedia.org/wiki/Domain_Name_System

5. Now we configure Zone replication. To prevent us from to much network traffic because of DNS replication, we do not replicate the zone over the complette forest, we replicate only in this domain.

6. After this you have to select the IP Version that will be handled by this zone.

7. Then enter the Network ID the musst be identified.

8. Now you have to set Dynamic Update for DNS entry’s. In a pure Windows Server DNS environment you should select “Allow only secure dynamic updates” otherwise you should select “Do not allow dynamic updates”. “Allow both nonsecure and secure dynamic updates” could be a entrace for Haks (DNS spoofing).

9. Now you get a short summary and you can create the zone by clicking “Finish”.

10. If all works fine you should see the new zone in you DNS MMC.

How to configure the first Domain Controller in a Windows Server 2012 Domain incl. DNS

Hello Community,

today I will explain how to configure the first Domain Controller in new Windows Server 2012 forest in Windows Server 2012 pure mode.

1. Open the Server Manager and klick on “Add roles and features”

2. The default page will open, click “Next”.

3. select “Role-based or feature-based installation” and click “Next”.

4. Select “Select a server from the server pool” and than select you local system. In my case FLO-SVR-DC01.

5. Now you can select the roles to install. Befor you go on with selecting roles please check if:

– you configured a static IP, Default Gateway, Subnet and DNS on the Network Interface to you client LAN

– Networkcable is connected to your switch

– you have no other Domaincontroller, DHCP- or DNS Server in your network

6. Please select for the first DC

– Active Directory Domain Services

– DNS Server

For every option Windows will ask you to install the “Remote Server Administration Tools” (RSAT). DO THIS otherwise it will be harder to finish the configuration. With later installations you can try to administrate the systems from remote or PowerShell.

7. Now the menu should look nearly like this. If this is the fact, you can click “Next”.

8. Now you have the “Feature selection”. You don’t need to install more features at the moment. Click “Next”

9. Now the Wizzard to configure ADDS starts.

10. Now you can select which operation the DC will perform. We plan to create a new forrest, so please click on “Add a new forest”.

11. Than typ in the name of your Root domain that you have planed e.g. local.company.com. After this click “Next”.

12. In the next Step you have have to select Forest function and domain level. You have to be carefull by selecting the level because some Active Directory Integrated Software e.g. some LDAP connectors, cannot work with Windows Server 2012 Domain Level. So please contact your software vendors first.

Create and set the Directory Services Restore Mode Password. Please also notice it down because you need it for a DC disaster recovery.

After this you can click next.

13. Normaly you could select in this Wizzard a DNS delegation but currently we have no DNS Server in this domain, so we have no option to delegate.

14. Now the NetBIOS Name will created. You are able to change it but you don’t have to do it.

15. After this you can set the Database folder, Log files path and SYSVOLL folder for ADDS Service. You can change the default path but I wouldn’t do this, you only force problems with this.

16. At next you get a install summary and you are able to view the PowerShell Script the will be executed (I love this option!!)

17. After this the Wizzard runs a validation check and when all is ok you can install ADDS.

18. Service installs.

19. After installation is finished you should see ADDS and DNS in your Server Manager

20. Please also look if the DNS Forward lookup Zone for your domain was created.

For this click on “Tools” in the the upper right Corner and select “DNS”.

21. Under Forward Lookup Zones you should the your Domain and there should be a NS, SOA and two A records for your DC.

22. Go back to Server Manager and select “Active Directory Users and Computers” under “Tools”

There your Domain should be listed and in “Domain Controllers” should be the “Computer Account” for your DC

23. Congratulations you installed your DC. In the next Blogs I will explain you how to install and configure DHCP and how to create a Reverse Lookup Zone in DNS.