You support computers that run Windows 8 Pro and are members of an Active Directory domain. Several
desktop computers are located in a subnet that is protected by a firewall. The firewall allows incoming TCP
connections only to ports 80 and 443.
You want to manage disk volumes on the desktop computers from your computer, which is located outside the
protected subnet.
You need to configure the network to support the required remote administration access.
What should you do?
A.
Enable Remote Desktop on the desktop computers.
B.
Run the winrm quickconfig command on your computer.
C.
Install Remote Server Administration Tools (RSAT)on your computer.
D.
Run the winrm quickconfig command on the desktop computers.
Explanation:
Installation and Configuration for Windows Remote Management (Windows)
Reference:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa384372(v=vs.85).aspx
Quick default configuration
Starting with Windows Vista, you can enable the WS-Management protocol on the local computer and set up
the default configuration for remote management with the following command: Winrm quickconfig.
Windows Server 2003 R2: The Winrm quickconfigcommand is not available.
The winrm quickconfigcommand (or the abbreviated version winrm qc) performs the following operations:
Starts the WinRM service, and sets the service startup type to auto-start.
Configures a listener for the ports that send and receive WS-Management protocol messages using either
HTTP or HTTPS on any IP address.
Defines ICF exceptions for the WinRM service, and opens the ports for HTTP and HTTPS.
NoteThe winrm quickconfigcommand creates a firewall exception only for the current user profile. If the
firewall profile is changed for any reason, winrm quickconfigshould be run to enable the firewall exception for
the new profile; otherwise, the exception might notbe enabled.
Reference 2:
http://blogs.technet.com/b/jonjor/archive/2009/01/09/winrm-windows-remote-management-troubleshooting.aspx
WinRM (Windows Remote Management) Troubleshooting
While WinRM listens on port80by default, it doesn’t mean traffic is unencrypted. Traffic by default is only
accepted by WinRM when it is encrypted using the Negotiate or Kerberos SSP. WinRM uses HTTP (TCP 80)
or HTTPS (TCP 443). WinRM also includes helper code that lets the WinRM listener share port 80 with IIS or
any other application that may need to use that port.
WinRM post version 1.1 (2003) is not on port 80 by default.. But that makes every option not-quite-enough… so guessing the B options is the closest, since you are only 1 simple step away from moving it to port 80.