Microsoft 70-643 - Questions & Answers

Explanation:
Launching Apps from the Desktop For users who want to double-click documents to launch the application, terminal services now provides the ability to "install" the remote application's link to the desktop. This process effectively wraps the RemoteApp's RDP file into a Windows Installer package--an MSI file--that is later installed to desktops in the environment. At the same time, the installed MSI can modify the file extension associations on the desktop to reroute a double-clicked file to its associated RemoteApp on the terminal server. Figure 3 shows how the file extension associations have been modified on a client system after a Word RemoteApp is installed. Now, double-clicking any of the common Word file extensions will launch Word via the Remote Desktop Connection.

Figure 3 File extension associations that have been altered to launch the Remote Desktop Connection
To create a Windows Installer package out of an existing RemoteApp, first navigate to the TS RemoteApp Manager. Right-click the RemoteApp of interest and select Create Windows Installer Package. By default, all created Windows Installer packages are stored in the location C:\Program Files\Packaged Programs, but this location can be changed from within the RemoteApp Wizard. Also configurable within the wizard are the name and port for the server that will host the RemoteApp, as well as server authentication, certificate settings, and TS Gateway settings. Settings that relate to the application's location after installation to a candidate desktop are shown in Figure 4. As you can see, it is possible to create a shortcut on the desktop as well as to a location within the Start menu folder. The most important checkbox on this screen is at the very bottom. It's the checkbox for Take over client settings, and it re-associates any file extension associations for the RemoteApp from the local desktop to the terminal server. This checkbox must be selected if you want users to be able to double-click documents to launch their TS-hosted application. Click
Next and Finish to complete the wizard. Please Note: -Since Windows2008R2 Terminal Services (TS) is now rebranded to Remote Desktop Services (RDS)-
Source:
http://technet.microsoft.com/en-us/query/dd314392

Explanation:
Remote Desktop connection authorization policies (RD CAPs) allow you to specify who can connect to an RD Gateway server.
Source:
http://technet.microsoft.com/en-us/library/cc753324.aspx

Explanation:
To resolve this problem, you need to install Microsoft SQL Server 2005 server on the farm. This error message occurs when either the SQL Server does not exist or the SQL Server services id stopped.

The server farm account is used to access your configuration database. It also acts as the application pool identity for the SharePoint Central Administration application pool, and it is the account under which the Windows SharePoint Services Timer service runs. The SharePoint Products and Technologies Configuration Wizard adds this account to the SQL Server Logins, the SQL Server Database Creator server role, and the SQL Server Security Administrators server role. If SQL Server is not available then the above mentioned error message will appear.

References:
Configuration Wizard - Failed to Connect (http://blogs.msdn.com/neilth/archive/2008/04/25/failed-to-connect-or-database-name-does-not-)
exist.aspx

Explanation:
By using TS Gateway Manager, you can specify the types of events that you want to monitor, such as unsuccessful or successful connection attempts to internal network computers through a TS Gateway server.
When these events occur, you can monitor the corresponding events by using Windows Event Viewer. TS
Gateway server events are stored in Event Viewer under Application and Services Logs\Microsoft\Windows
\Terminal Services-Gateway\.
Source:
http://technet.microsoft.com/en-us/library/cc730618(WS.10).aspx

Explanation:
To migrate to SharePoint Services (WSS) 3.0. from Server1 to Server2 with all the configuration and content, you need to install WSS 2.0 on Server2. Back up the WSS 2.0 configuration and content from Server1 and restore the backup from Server1 to Server2. Perform an in-place upgrade of WSS 2.0 to WSS 3.0 on Server2.

When you run an in-place upgrade, all content and configuration data is upgraded in-place, at one time. When you start the in-place upgrade process, the Web server and Web sites remain offline until the upgrade has been installed. In-place upgrades are best for a stand-alone server and small installations as in this case

References:
Install and configure Office SharePoint Server for an in-place upgrade (http://technet.microsoft.com/en-us/library/cc263212(TechNet.10)
.aspx Reference: Determine upgrade approach (Office SharePoint Server) (http://technet.microsoft.com/en-us/library/cc263447(TechNet.10)
.aspx

Explanation:
Key Management Service
With KMS, IT pros can complete activations on their local network, eliminating the need for individual computers to connect to Microsoft for product activation.
KMS is a lightweight service that does not require a dedicated system and can easily be co-hosted on a system that provides other services. By default, volume editions of Windows 7 and Windows Server 2008 R2 connect to a system that hosts the KMS service to request activation. No action is required from the user.
KMS requires a minimum number of computers (physical or virtual machines) in a network environment.
The organization must have at least five computers to activate Windows Server 2008 R2 and at least 25 computers to activate clients that are running Windows 7.
These minimums are referred to as activation thresholds.
To use KMS activation with Windows 7, the computer must have the qualifying OS license (often obtained through OEMs as part of the new PC purchase) and contain a Windows Marker in BIOS.

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

ExplanationExplanation:
You can configure a Remote Desktop Session Host (RD Session Host) server to join a farm in RD Connection Broker, and to participate in RD Connection Broker Load Balancing, by using the Remote Desktop Session Host Configuration tool.
To configure RD Connection Broker settings 1. On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration .
2. In the Edit settings area, under RD Connection Broker, double-click Member of farm in RD Connection Broker.
3. On the RD Connection Broker tab of the Properties dialog box, click Change Settings.
4. In the RD Connection Broker Settings dialog box, click Farm member.
5. In the RD Connection Broker server name box, type the name of the RD Connection Broker server.
6. In the Farm name box, type the name of the farm that you want to join in RD Connection Broker.
7. Click OK to close the RD Connection Broker Settings dialog box.
8. To participate in RD Connection Broker Load Balancing, select the Participate in Connection Broker Load-Balancing check box.
9. Optionally, in the Relative weight of this server in the farm box, modify the server weight. By default, the value is 100. The server weight is relative. Therefore, if you assign one server a value of 50, and one a value of 100, the server with a weight of 50 will receive half the number of sessions.
10. Verify that you want to use IP address redirection. By default, the Use IP address redirection setting is enabled. If you want to use token redirection mode, select Use token redirection. For more information, see About IP Address and Token Redirection.
11. In the Select IP addresses to be used for reconnection box, select the check box next to each IP address that you want to use.
12. When you are finished, click OK.
Source:
http://technet.microsoft.com/en-us/library/cc771383.aspx

Explanation:
Explanation:
Enable and configure email settings for a library
Use this procedure to enable and configure email settings for a library to receive email messages in the SharePoint document library in a site.
Enable and configure email settings for a library 1. Open the site in which you want to receive email messages by using either of the following methods:
- In Internet Explorer, type the URL o the site.
- On the View Site Collection page, click the site collection that you want to view.
2. In the left navigation pane of the home page, click View All Site Content.
3. In the Documents section, click a document library name to open the library for which you want to enable and configure email settings.
4. On the Settings menu, click Document Library Settings, Picture Library Settings, or Form Library Settings, depending on the kind of library that you are enabling and configuring.
5. In the Communications section, click Incoming email settings.
6. In the Email section, select Yes to enable this library to receive email messages.
7. In the Email address box, type a unique name to use as part of the email address for this library.
8. In the Email Attachments section, decide where to save and how to group the email attachments in this library, and then choose whether to overwrite files that have the same name. Note: If you decide not to overwrite files that have the same name and then later try to save a file that has the same name as one that already exists in the library, four random digits are appended to the file name for the new attachment. If this action fails, a globally unique identifier (GUID) is appended to the file name. If neither of these actions can produce a unique file name, the attachment is discarded.
9. In the Email Message section, choose whether to save the original email message in this library. If you select Yes, the original message is saved as a separate item in the library.
10. In the Email Meeting Invitations section, choose whether to save the attachments to your meeting invitations in this library.
11. In the Email Security section, choose whether to archive email messages only from members of the site who can write to the library or to archive regardless of who sends the email message.
12. Click OK to save the changes that you have made in the settings.

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

Explanation:
Change user
Changes the install mode for the terminal server

Source:
http://technet.microsoft.com/en-us/library/cc730696(WS.10).aspx