A company has an Active Directory Domain Services (AD DS) domain. All client computers are joined to the domain and run Window 8.1. You set up a management computer named COMPUTER1.
You plan to administer COMPUTER1 by using Windows Remote Shell (WinRS) from your client computer. You are unable to connect to COMPUTER1 by running the winrs command.
You need to ensure that you can manage only COMPUTER1 by using WinRS. What should you do?
A. Run the winrsnetdom join command on all client computers.
B. Run the winrsnetdom join command only on COMPUTER1.
C. Run the winrmquickconfig command on all client computers.
D. Run the winrmquickconfig command only on COMPUTER1.
E. Run the winrs /ad /u:administrator command on COMPUTER1.
Correct Answer: D
Explanation/Reference:
http://clintboessen.blogspot.com/2010/01/what-is-winrm.html What is WinRM?
…
The easiest way to start the WinRM server unless you want to do custom configuration is by using the "winrm quickconfig" command.
Hit "Y" to make the change. Next it asks you if you want to allow it to make a HTTP listener and create a windows firewall exception.
Hit "Y" to make the change. WinRM is now running and can be remotely managed by WinRS (the WinRM client).
Now re-run the "winrm enumerate winrm/config/listener" command to see if WinRM is working:
We see it listening on port 5985, this is because I’m running Windows 7 on this PC so its using WinRM 2.0.
Now from another PC I can use the WinRS client to remotely execute commands against that workstation/server by using "winrs -r:https:// myserver.com" command. Please note that you need to run the command as a user in the remote computers "Administrators" group. By default WinRS will use your active windows credentials. However I do not run my computer as administrator for security purposes so I will need to specify a user account with Domain Admins rights to ensure I have correct access by using the
-u: switch.
http://msdn.microsoft.com/en-us/library/aa384372%28v=vs.85%29.aspx Installation and Configuration for Windows Remote Management The winrm quickconfig command (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.
Note: The winrm quickconfig command creates a firewall exception only for the current user profile. If the firewall profile is changed for any reason, winrm quickconfig should be run to enable the firewall exception for the new profile; otherwise, the exception might not be enabled.
