<div>
Mahesh,<br />
<br />
Thanks for the suggestions. &nbsp;We have 2008 R2 member servers, but the GPMC is unable to correctly display the Settings of any of our GPO's. &nbsp;We do not have any licenses for 2012 R2, so we can't test that.<br />
<br />
We've confirmed that the GPO is being applied correctly, but haven't yet confirmed if the specific ports are being opened.<br />
<br />
We've also provided feedback to MS regarding the hole in supporting this issue, but are not expecting any follow up.<br />
<br />
At this point, we'll manually check the open ports of systems that receive the GPO to confirm.<br />
<br />
Awarding points.<br />
<br />
Dimarc67<br />
Frederick, MD
</div>


<div>
Question was not stated concisely, so awarding full points since loose criteria were met.
</div>


<div>
OK<br />
U can download 180 days evaluation 2012 R2 standard version, install it as member server with GPMC and RSAT for AD and check <br />
Also if require install hotfix as per your original link
</div>


<div>
<div class="content wysiwyg-content">
We are having the exact issue described in Microsoft KB2934842:<br />
<a href="http://support2.microsoft.com/kb/2934842/en-us" rel="ugc"><b>The range of ports is not displayed when a Windows Firewall rule defines a local port range</b></a>.<br />
<br />
However, the article applies only to Windows Server 2008 R2 (Win7) and Windows Server 2012 R2 (Win8.1). &nbsp;We're running Windows Server 2012 (Win8.0), and neither hotfix that's prescribed is compatible with what we're running.<br />
<br />
The article also fails to explain whether the issue is merely a superficial display problem, or whether the GPO will not apply the port ranges that don't appear in the Settings pane of the GPMC.<br />
<br />
We're desperate to get out a new, large Firewall GPO, but we need to fully understand what may or may not be working. &nbsp;<br />
<br />
Can anyone shed some light on this for us?
</div>
</div>


We are having the exact issue described in Microsoft KB2934842:
The range of ports is not displayed when a Windows Firewall rule defines a local port range (http://support2.microsoft.com/kb/2934842/en-us).

However, the article applies only to Windows Server 2008 R2 (Win7) and Windows Server 2012 R2 (Win8.1).  We're running Windows Server 2012 (Win8.0), and neither hotfix that's prescribed is compatible with what we're running.

The article also fails to explain whether the issue is merely a superficial display problem, or whether the GPO will not apply the port ranges that don't appear in the Settings pane of the GPMC.

We're desperate to get out a new, large Firewall GPO, but we need to fully understand what may or may not be working.  

Can anyone shed some light on this for us?

The range of ports is not displayed when a Windows Firewall rule defines a local port range

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.