Microsoft 70-643 Online Practice Questions and Exam Preparation

Microsoft 70-643 Online Questions & Answers

• Question 281:

  Your company has a single Active Directory domain named contoso.com. The domain has two domain controllers and 60 member servers. All servers run Windows Server 2008 R2. One of the domain controllers has Key Management Service (KMS) installed and activated. All servers use KMS auto-discovery to find the KMS server. You need to change the port used by KMS from its default port to port 12200.

  Which two actions should you perform? (Each correct answer presents part of the solution. Choose two.)

  A. Restart the slsvc service on the KMS server.
  B. Restart the DNS Server service on the KMS server.
  C. On the KMS server at the command prompt, run the slmgr.vbs skms KMSServer: 12200 command.
  D. On the client computers at the command prompt, run the slmgr.vbs skms KMSServer: 12200 command.
  A. Restart the slsvc service on the KMS server.
  C. On the KMS server at the command prompt, run the slmgr.vbs skms KMSServer: 12200 command.

  ---

  To change the port of the KMS server:

  To set the TCP communications port on a KMS host. Replace PortNumber with the TCP port number to use. The default setting is 1688.

  slmgr.vbs /sprt PortNumber

  Source: http://technet.microsoft.com/en-us/library/ff793407.aspx Restart slsvc service: A KMS host will automatically update its SRV entries if the software licensing service (slsvc.exe) detects that the computer name or TCP port has changed

  during service startup. It will also update them once each day, in order to ensure that they are not automatically removed (scavenged) by the DNS system.

  Source: http://download.microsoft.com/download/c/3/8/c3815ed7-aee7-4435-802b- 8e855d549154/VolumeActivation2.0Step-By-StepGuide.doc Force the KMS client to update the portnumber:

  If configuring KMS clients to use auto-discovery, they automatically choose another KMS host if the original KMS host does not respond to renewal requests. If not using auto-discovery, update the KMS client computers that were assigned to

  the failed KMS host by running Slmgr.vbs /skms. To avoid this scenario, configure KMS clients to use auto-discovery. For more information, see the Volume Activation Deployment Guide.

  Source: http://technet.microsoft.com/en-us/library/ff793439.aspx OR Configuring KMS Hosts (Server)

  Sets the TCP communications port on a KMS host. Replace PortNumber with the TCP port number to use. The default setting is 1688.

  Slmgr.vbs /sprt PortNumber

  The Software Licensing Service must be restarted for any changes to take effect. To restart the Software Licensing Service, use the Microsoft Management Console (MMC) Services snap-in, or run the following command at an elevated

  command prompt:

  net stop sppsvc andand net start sppsvc

  Configuring KMS Clients

  This section describes concepts for installing and configuring computers as KMS clients. By default, Volume Licensing editions of Windows Vista, Windows 7 , Windows Server 2008, and Windows Server 2008 R2 are KMS clients. If the

  computers the organization wants to activate using KMS are using any of these operating systems and the network allows DNS auto-discovery, no further configuration is needed. If a KMS client is configured to search for a KMS host using

  DNS but does not receive SRV records from DNS, Windows 7 and Windows Server 2008 R2 log the error in the event log.

  Manually Specifying a KMS Host

  You can manually assign a KMS host to KMS clients by using KMS host caching. Manually assigning a KMS host disables auto-discovery of KMS on the KMS client. Manually assign a KMS host to a KMS client by running:

  slmgr.vbs /skms :

  where value is either the KMS_FQDN, IPv4Address, or NetbiosName of the KMS host and port is the TCP port on the KMS host.

  Source: http://technet.microsoft.com/en-us/library/ff793409.aspx "You must restart the SLSVC service (Vista/2008) or SPPSVC(Win7/R2)"

  Source: http://blogs.technet.com/b/askcore/archive/2009/03/09/kms-error-0xc004c008-activating- client.aspx

• Question 282:

  Your network contains four servers that run Windows Server 2008 R2. The servers are configured as shown in the following table:

  

  Server2 and Server3 are configured as RemoteApp sources on Server4. You need to ensure that the RemoteApp programs are listed on the RD Web Access Web page on Server1. What should you do?

  A. On Server4, add Server1 to the Session Broker Computers group.
  B. On Server1, add Server4 to the TS Web Access Administrators group.
  C. On Server4, add Server1 to the TS Web Access Computers group.
  D. On Server1, add Server2 and Server3 to the TS Web Access Administrators group.
  C. On Server4, add Server1 to the TS Web Access Computers group.

• Question 283:

  Your network contains an Active Directory domain. You deploy a server named Server1 that has the Remote Desktop Connection Broker (RD Connection Broker) role service installed. You need to ensure that all servers that have the Remote Desktop Session Host (RD Session Host) role service installed are automatically configured to use Server1 as an RD Connection Broker.

  What should you do?

  A. Register a service principal name (SPN) for Server1.
  B. Register a service location (SRV) record for Server1.
  C. Use a Group Policy to configure the Restricted Groups settings.
  D. Use a Group Policy to configure the Remote Desktop Services settings.
  D. Use a Group Policy to configure the Remote Desktop Services settings.

  ---

  RD Connection Broker

  Policy settings in this node control configuration of a Remote Desktop Session Host server that is a member of a load-balanced Remote Desktop Session Host server farm. The full path of this node in the Group Policy Management Console

  is Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\RD Connection Broker.

  Available policy settings Join RD Connection Broker

  This policy setting allows you to specify whether the RD Session Host server should join a farm in RD Connection Broker. RD Connection Broker tracks user sessions and allows a user to reconnect to their existing session in a load-balanced

  RD Session Host server farm. To participate in RD Connection Broker, the Remote Desktop Session Host role service must be installed on the server. If the policy setting is enabled, the RD Session Host server joins the farm that is specified

  in the Configure RD Connection Broker Farm Name setting. The farm exists on the RD Connection Broker server that is specified in the Configure RD Connection Broker Server name policy setting.

  If you disable this policy setting, the server does not join a farm in RD Connection Broker, and user session tracking is not performed. If the setting is disabled, you cannot use either the Remote Desktop Session Host Configuration tool or the

  Terminal Services WMI provider to join the server to RD Connection Broker.

  If the policy setting is not configured, the setting is not specified at the Group Policy level. In this case, you can configure the server to join RD Connection Broker by using the Remote Desktop Session Host Configuration tool or the Terminal

  Services WMI provider.

  If you enable this setting, you must also enable the "Configure RD Connection Broker Farm Name" and Configure RD Connection Broker Server name policy settings, or configure these settings by using either the Remote Desktop Session

  Host Configuration tool or the Terminal Services WMI provider.

  Configure RD Connection Broker farm name

  This policy setting allows you to specify the name of a farm to join in RD Connection Broker. RD Connection Broker uses the farm name to determine which RD Session Host servers are in the same RD Session Host server farm. Therefore,

  you must use the same farm name for all RD Session Host servers in the same load-balanced farm. The farm name does not have to correspond to a name in Active Directory Domain Services.

  If you specify a new farm name, a new farm is created in RD Connection Broker. If you specify an existing farm name, the server joins that farm in RD Connection ker. If you enable this policy setting, you must specify the name of a farm in

  RD Connection Broker. If you disable or do not configure this policy setting, the farm name is not specified by Group Policy. In this case, you can adjust the farm name by using the Remote Desktop Session Host Configuration tool or the

  Terminal Services WMI provider. This setting is not effective unless both the Join RD Connection Broker and the Configure RD Connection Broker server name settings are enabled and configured by using Group Policy, the Remote Desktop

  Session Host Configuration tool, or the Terminal Services WMI provider.

  Configure RD Connection Broker server name

  This policy setting allows you to specify the RD Connection Broker server that the RD Session Host server uses to track and redirect user sessions for a load-balanced RD Session Host server farm. The specified server must be running the

  Remote Desktop Connection Broker service. All RD Session Host servers in a load-balanced farm should use the same RD Connection Broker server. If you enable this policy setting, you must specify the RD Connection Broker server, using

  either its host name, IP address, or fully qualified domain name. If you specify a name or IP address for the RD Connection Broker server that is not valid, an error message is logged in Event Viewer on the RD Session Host server.

  If you disable or do not configure this policy setting, you can adjust the RD Connection Broker server name or IP address by usin the Remote Desktop Session Host Configuration tool or the Terminal Services WMI provider.

  This policy setting is not effective unless the Join RD Connection Broker policy setting is enabled or the RD Session Host server is configured to join RD Connection Broker by using the Remote Desktop Session Host Configuration tool or the

  Terminal Services WMI provider. To be an active member of an RD Connection Broker-enabled RD Session Host server farm, the computer account for each RD Session Host server in the farm must be a member of the Session Directory

  Computers local group on the RD Connection Broker server.

  Use RD Connection Broker load balancing

  This policy setting allows you to specify whether to use the RD Connection Broker load balancing feature to balance the load between servers in an RD Session Host server farm. If you enable this policy setting, RD Connection Broker

  redirects users who do not have an existing session to the RD Session Host server in the farm with the fewest sessions. Redirection behavior for users with existing sessions is not affected. If the server is configured to use RD Connection

  Broker, users who have an existing session are redirected to the RD Session Host server where their session exists.

  If you disable this policy setting, users who do not have an existing session log on to the first RD Session Host server to which they connect.

  If you do not configure this policy setting, you can configure the RD Session Host server to participate in RD Connection Broker load balancing by using the Remote Desktop Session Host Configuration tool or the Terminal Services WMI

  provider. If you enable this policy setting, you must also enable the Join RD Connection Broker, the Configure RD Connection Broker farm name, and the Configure RD Connection Broker server name policy settings.

  Source: http://technet.microsoft.com/en-us/library/ee791821.aspx

• Question 284:

  Your network contains a server named Server1 that has the Streaming Media Services server role installed.

  Windows Media Services is configured to log on as a user named User1.

  On Server1, you have a media file named File1.wmv. File1.wmv is protected by Encrypting File System (EFS).

  You create a publishing point on WMS1 and select File1.wmv as the content source.

  When you start the publishing point, you receive the error message shown in the exhibit, (Click the Exhibit button.)

  You need to enable Server1 to play the content in File1.wmv.

  What should you do?

  A. Add a certificate to the certificate store of User1.
  B. modify the NTFS permissions of File1.wmv.
  C. Modify the Authorization settings of WMS1.
  D. Add a certificate to the certificate store of Server1.
  A. Add a certificate to the certificate store of User1.

• Question 285:

  Your network contains a Web site named Web1. Web1 is configured to use an application pool named AppPool1.

  You need to ensure that the memory used by the Web site is released every 12 hours.

  The solution must minimize the amount of downtime for the Web site.

  What should you do?

  A. Modify the recycling settings for AppPool1.
  B. Modify the session state settings for Web1.
  C. Create a scheduled task that runs tskill.exe w3svc.exe.
  D. Create a scheduled task that runs iisreset.exe /noforce.
  A. Modify the recycling settings for AppPool1.

• Question 286:

  Your network contains a server named Server1 that runs a Server Core installation of Windows Server 2008 R2. The network contains a server named Server2 that runs a full installation of Windows Server 2008 R2. Server1 has the Streaming Media Services role installed. You need to administer the Streaming Media Services on Server1 from Server2.

  What should you do on Server2?

  A. Download and install Windows Media Services 2008 for Windows Server 2008 R2.
  B. Install the Remote Server Administration Tools (RSAT) feature.
  C. Download and install Microsoft IIS Media services 3.0 - 64-bit.
  D. Install the Quality Windows Audio video Experience (qWave) feature.
  A. Download and install Windows Media Services 2008 for Windows Server 2008 R2.

  ---

  Managing a Windows Media server

  Windows Media Services includes the following management interfaces:

  On the full installation option for Windows Server 2008, you can use the Windows Media Services snap-in for Microsoft Management Console (MMC) to manage the local Windows Media server. To open the snap-in, click Start, click All

  Programs, click Administrative Tools, and then click Windows Media Services.

  You can install the optional Web-based Administration role service on the local Windows Media server and then manage the server by opening the Windows Media Administration site (http://server_name:8080/default.asp) in a Web browser

  on a remote computer. For more information, see Administering Windows Media servers remotely. You can install Remote Server Administration Tools for Windows Media Services on a computer that runs Windows Vista?or Windows-7 and

  then manage your remote Windows Media server from the client computer. To start the Windows Media Services snap-in for MMC on the client computer, click Start, click Run, and then type wmsadmin.

  Source: http://technet.microsoft.com/en-us/library/ee822833.aspx

• Question 287:

  Your network contains an Active Directory domain named fabnkam.com. The domain contains a Web server named Web1 that runs Windows Server 2008 R2.

  You have a Web site named Corp.

  The content on Corp is stored on a FAT32 partition.

  Corp contains a Web page named Test.html.

  You need to ensure that only a user named Devi can access Test.html from the Corp Web site.

  All of the other content on Corp must be accessible to everyone.

  Which feature should you configure?

  A. Feature Delegation
  B. Authorization Rules
  C. IP Address and Domain Restrictions
  D. us Manager Permissions
  B. Authorization Rules

• Question 288:

  Your network contains a server that has the Remote Desktop Session Host (RD Session Host) role service installed.

  You need to ensure that each Remote Desktop connection to the server has a unique IP address.

  What should you do?

  A. Enable IP virtualization per session
  B. Enable IP virtualization per program
  C. Configure the network adapter to have multiple IP addresses
  D. Configure the network adapter to obtain an IP address automatically
  A. Enable IP virtualization per session

  ---

  Deploying Remote Desktop IP Virtualization

  In Windows Server 2008 R2, RD Session Host supports per program and per session Remote Desktop IP Virtualization for Winsock applications. When using per program Remote Desktop IP Virtualization, you choose which programs to use with Remote Desktop IP Virtualization. When using per session Remote Desktop IP Virtualization, all Winsock applications are virtualized with Remote Desktop IP Virtualization.

  Remote Desktop IP Virtualization allows you to assign a unique IP address to a user session, which helps to avoid application compatibility issues by simulating a local desktop. To configure Remote Desktop IP Virtualization for per program virtualization

  1.

  Log on to RD Session Host as an Administrator.

  2.

  Click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.

  3.

  Under the RD IP Virtualization heading, double-click IP Virtualization.

  4.

  Click the Enable IP virtualization check box.

  5.

  In the Select the network adapter to be used for IP virtualization box, select the appropriate network adapter.

  6.

  Under the IP virtualization mode heading, ensure that the Per Session option is selected. Important If your computer has more than one network adapter, you must choose per program. Using per session Remote Desktop IP Virtualization with more than one network adapter installed on the computer is not supported.

  7.

  Click OK.

  

  Source: http://technet.microsoft.com/en-us/library/ee308293.aspx

• Question 289:

  You create a managed service account.

  You need to configure a Web application pool to use the managed service account.

  What should you do first?

  A. Add the account to the IIS_IUSRS group.
  B. Run the New-WebServiceProxy cmdlet.
  C. Run the Install-ADServiceAccount cmdlet.
  D. Modify the permissions of the computer account.
  C. Run the Install-ADServiceAccount cmdlet.

  ---

  Managed service accounts and virtual accounts are two new types of accounts introduced in Windows ServerR 2008 R2 and WindowsR 7 to enhance the service isolation and manageability of network applications such as Microsoft Exchange and Internet Information Services (IIS).

  To create a new managed service account

  1.

  On the domain controller, click Start, and then click Run.

  2.

  In the Open box, type dsa.msc, and then click OK to open the Active Directory Users and Computers snapin.

  3.

  Confirm that the Managed Service Account container exists.

  4.

  Click Start, click All Programs, click Windows PowerShell 2.0, and then click the Windows PowerShell icon.

  5.

  Run the following command:

  New-ADServiceAccount [-SAMAccountName ] [-Path ] . To install a managed service account on a local computer

  1.

  Click Start, click All Programs, click Windows PowerShell 2.0, and then click the Windows PowerShell icon.

  2.

  Run the following command:

  Install-ADServiceAccount [-Identity] [-Confirm] [-WhatIf] [- Credential ].

  To use the Internet Information Services (IIS) Manager snap-in to configure a service to use a managed service account

  1.

  Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager .

  2.

  Double-click , double-click Application Pools, right-click , and click Advanced Settings.

  3.

  In the Identity box, click ..., click Custom Account, and then click Set.

  4.

  Type the name of the managed service account in the format domainname\accountname. Important: Leave the password blank, and ensure that the account name has a dollar sign ($) at the end.

  5.

  Under Application Pool Tasks, click Stop, and then click Start.

  Source: http://technet.microsoft.com/en-us/library/dd548356.aspx

• Question 290:

  You need to manually create a service location (SRV) record for a server that has the Key Management Service (KMS) installed.

  Which SRV record should you create?

  A. _kms._tcp.contoso.com
  B. _kms._tcp._msdcs.contoso.com
  C. _mskms._tcp.contoso.com
  D. _vlmcs._tcp.contoso.com
  D. _vlmcs._tcp.contoso.com

  ---

  Manually Create SRV Records in DNS

  If the environment does not support DDNS, the SRV RRs must be manually created to publish the KMS host.

  Environments that do not support DDNS should disable publishing on all KMS hosts to prevent event logs from collecting failed DNS publishing events. To disable auto-publishing, use the Slmgr.vbs script with the /cdns command-line option.

  See the "Configuring KMS" section for more information about the Slmgr.vbs script.

  Note Manually created SRV RRs can coexist with SRV RRs that KMS hosts automatically publish in other domains as long as all records are maintained to prevent conflicts. Using DNS Manager, in the appropriate forwarding lookup zone,

  create a new SRV RR using the appropriate information for the location. By default, KMS listens on TCP port 1688, and the service is _VLMCS. Table 2 contains example settings for a SRV RR.

  Table 2 SRV Resource Record