You need to ensure that you can manage Server2 by using the Computer Management console on Server1

Your network contains an Active Directory domain named contoso.com.
The domain contains a server named Server1 that runs Windows Server 2012.
On a server named Server2, you perform a Server Core Installation of Windows Server 2012.
You join Server2 to the contoso.com domain.
You need to ensure that you can manage Server2 by using the Computer Management console on Server1.
What should you do on Server2?

A.
Run the Disable-NetFirewallRule cmdlet.

B.
Run the Enable-NetFirewallRule cmdlet.

C.
Run sconfig.exe and configure the network settings.

D.
Run sconfig.exe and configure remote management.

Explanation:
As we can see on the following screenshot, Remote Management is enabled by default on a new Server
Core installation of 2012 (so we don’t have to configure it on Server2)
BUT that’s not enough asit only enables WinRM-based remote management(and computer management
is not WinRM-based of course).
To enable theremote management from an MMC(such as server manager, or computer manager), we have
to enable exception rules in the Firewall,
which can be done, amongst other ways, using Powershell and the Enable-NetFirewallRule cmdlet.
NB : For the example, i only used Enable-NetFirewallRule -displaygroup “Remote Service Management” and
Computer Management was then able to connect to my 2012 server core.
==============
from the MSPress book “Upgrading your skills to MCSA Windows Server 2012”
Note also that in previous versions of Windows Server, remote Server Manager management required many
open ports, and Configure-SMRemoting was a Windows PowerShell script that opened all those ports. In
Windows Server 2012, remote Server Manager management relies only on WinRM for most features (such as
deploying roles, restarting, and Windows PowerShell) and on DCOM for some additional features (such as
Computer Management). Consistent with this more efficient remote management method, Configure-SMRemoting configures only WinRM in Windows Server 2012, and is now the equivalent of the command
Winrm Quickconfig. Like when you enable remote management in the interface or by using Winrm Quickconfig,
if you enable remote management by using Configure-SMRemoting,you still need to enable the DCOM
ports manually later if you want more complete remote management functionality by using MMC
consoles.
[…]
Again, like Winrm Quickconfig and Configure-SMRemoting, enabling remote management in Sconfig
configures only WinRM-based remote management.
=================
http://technet.microsoft.com/en-us/library/jj554869.aspx
Enable-NetFirewallRule
Detailed Description
The Enable-NetFirewallRule cmdlet enables a previously disabled firewall rule to be activewithin the
computer or a group policy organizational unit.
This cmdlet gets one or more firewall rules to be enabled with the Name parameter (default), the DisplayName
parameter, rule properties, or by associated filters or objects. The Enabled parameter for the resulting queried
rules is set to True.