HOTSPOT
Your company is deploying 200 Windows 7 Enterprise virtual machines (VMs). The company uses
Key Management Service (KMS) for client computer activation. Two servers named Server1 and
Server2 are KMS hosts that run Windows Server 2008 R2. After deployment, the VMs are unable to
activate on Server1. You need to ensure that the VMs can activate by using KMS. On Server1, which
firewall rule should you change? To answer, select the appropriate setting in the answer area.
A.
There’s a minimum number of activations before a KMS server will start activating clients.
However, if the clients can’t even connect, make sure the firewalls on the server and client have the
Key Management Service (TCP-In) exception enabled, which allows KMS communications through
port 1688 as shown. http://www.windowsitpro.com/article/systems-management/q-i-ve-enabledkey-managementservice- kms-on-aserver-but-clients-can-t-activate-why-not
QUESTION 122
Your company has an Active Directory Domain Services (AD DS) domain. You install the Remote
Desktop Session Host (RD Session Host) role service on a server that runs Windows Server 2008 R2.
All client computers run Windows 7. You need to ensure that the current Libraries from users’
computers are available when they log
on to the RD Session Host server. What should you do?
Redirect each user’s Documents folder to a network share.
A.
There’s a minimum number of activations before a KMS server will start activating clients.
However, if the clients can’t even connect, make sure the firewalls on the server and client have the
Key Management Service (TCP-In) exception enabled, which allows KMS communications through
port 1688 as shown. http://www.windowsitpro.com/article/systems-management/q-i-ve-enabledkey-managementservice- kms-on-aserver-but-clients-can-t-activate-why-not
QUESTION 122
Your company has an Active Directory Domain Services (AD DS) domain. You install the Remote
Desktop Session Host (RD Session Host) role service on a server that runs Windows Server 2008 R2.
All client computers run Windows 7. You need to ensure that the current Libraries from users’
computers are available when they log
on to the RD Session Host server. What should you do?
Redirect each user’s Documents folder to a network share.
B.
Redirect each user’s Links folder to the RD Session Host server.
C.
Use a startup script to copy .library-ms files from the client computers to the RD Session Host
server.
D.
Use Group Policy Preferences to copy .library-ms files from the client computers to the RD Session
Host server.
Explanation:
Q. I’ve enabled Key Management Service (KMS) on a server, but clients can’t activate. Why not?Administrators can deploy customized libraries in the following ways: Using a logon script or Group
Policy Preferences (through the Default User profile) Adding custom libraries to the server where
Roaming User Profiles are redirected Deploying through a logon script or Group Policy Preferences
You can copy the .library-ms files to a local computer or copy them to a server if the users’ library
directories are redirected to a network location. You can use a logon script or Group Policy
Preferences to copy libraries to the %userprofile%\Appdata\roaming\Microsoft\Windows\Libraries
directory. The locations specified in custom libraries need to be accessible by the target users. These
locations include known folders, fixed local folders, mapped drives on the users’ computers, or
network shared resources where users have access. If a user does not have permissions to a folder,
that folder does not appear in the library and no warning appears for the user. Using the Default
User profile Administrators can edit the set of libraries associated with the Default User profile, and
then deploy the libraries to users who derive from Default User. Deploying libraries using Roaming
User Profiles Remote libraries can include content from locations that are local or remote to the
server, much as local libraries can. To support this, the user’s known folders are ideally redirected
and available in the Roaming User Profiles. Library definition files are located in the
%userprofile%\Appdata\roaming\Microsoft\Windows \Libraries directory, and they can be shared
on a server.
http://technet.microsoft.com/en-us/library/ee461108(v=ws.10).aspx