|
|
Windows Desktop Search Administration GuideOn This PageThis document is provided for informational purposes only and Microsoft makes no warranties, expressed or implied, with respect to this document or the information contained in it. This document pertains to Windows Desktop Search Version 02.06.0000.2057 and later. Note Some features are not available in all markets. OverviewWindows Desktop Search (WDS) helps your business users find almost anything on their computers — e-mail messages, calendar appointments, photos, documents, and more. Searching a computer with WDS is virtually as fast and easy as searching the Web. Additionally, the Desktop Search results window includes rich Windows Explorer features so that your users can quickly preview, filter, and act on search results. The latest version of WDS is optimized with features that help enterprise information technology (IT) managers deploy and manage the installation of WDS across all users and computers in their organizations. IT managers can expect the following benefits:
Best of all, WDS is free with your Microsoft Windows license (View Windows Supplemental License). Microsoft Corporation, or one of our affiliates depending on where you live, licenses this supplement to you. You may use a copy of this supplement with each validly licensed copy of Microsoft Windows software identified for use with it (the 'software'). You may not use it if you do not have a license for the software. The license terms for the software apply to your use of this supplement. This document contains information about how to set up WDS in an enterprise environment. This document targets an audience of IT managers and administrators. Pre-installation considerationsBefore you install Windows Desktop Search, consider the following factors:
In this section, we review these factors and the methods that you can use to manage them. Reviewing these issues and methods before you install WDS can help ensure a successful and painless roll-out. System requirementsA system must meet or exceed the following requirements to run Windows Desktop Search:
Full preview of Microsoft Office documents in Desktop Search results is available only for Microsoft Office XP or later versions of Microsoft Office. System recommendations
Localization optionsIf your organization requires localized builds for users who speak different languages, you can either deploy localized versions of WDS, or deploy the English version of WDS and use a Multilingual User Interface Pack (MUI) to switch user interfaces based on the user’s language preference. You can use the English .adm file to create Group Policy objects (GPOs) for non-English speaking users. For settings that require that you enter text, such as the name of the intranet scope, you should enter the information in the appropriate language. For your convenience, the WDS .adm file is available in eight languages, including English. This lets local IT administrators read the explanation text in their native languages. It does not matter which localized version of the .adm file you use to create the GPOs. Group Policy settingsAlthough you do not have to use Group Policy settings to deploy this software, they can be a very powerful tool to help control access to resources and the functionality of this product. Group Policy settings are supported by WDS version 2.6 or later. To plan and deploy effective Group Policy settings, your organizational units and groups must be structured logically. A well planned and implemented organizational structure provides far-reaching benefits when you manage security, users, and resources. Group Policy settings can be especially useful when you plan how to most efficiently deploy WDS. It is likely that different organizations in your company have very needs for information and resources. For example, the accounting department may have access to more systems and require more security than the shipping and receiving department. When you deploy software, the more time that you spend organizing and planning how to best meet the different needs of your users, the better the outcome will be. With WDS you can customize the product to search different resources for each group. By using Group Policy settings, you can quickly and easily adjust the resources and functionality of WDS. For detailed information about how to use Group Policy settings with WDS, please see the "Customizing WDS using Group Policy settings" section. Assigning network resources to groupsBecause each department and group searches for data differently, you may want to add different search capabilities to different departments. Doing this requires a unique Group Policy setting for each configuration of resources. By using Group Policy settings, you can give users access to various data sources, including Share Point Servers, Share Point Services, Intranet sites, and other data stores. For detailed information about specific settings and how to correctly configure these settings, please see the Windows Desktop Search Policies section, and the Index Policies section later in this document. Network performanceIn typical environments, users can index network shares, e-mail, public folders, and other resources. However, this functionality can come at a cost. When you enable users to index network shares or e-mail and public folders, the network traffic to these locations may increase when these resources are indexed. You may see the most impact to network traffic during the initial index and during incremental index, when the user logs on. The impact on servers is partially reduced by the back-off functionality that is built into WDS. See the Smart Indexer in the Additional Information section for more information about this back-off functionality. You can use Group Policy settings to modify various aspects of the product and help limit the impact to network traffic. For example, you can disable indexing at startup, disable certain network paths to high volume servers, disable indexing of Public folders, or allow indexing of Microsoft Office Outlook 2003 only in cached mode. These Group Policy settings can help lessen the impact on a network. Group Policy options are also available that limit the impact on network traffic while still letting your users index the information that they need. For more information about Group Policy options, see the Windows Desktop Search Policies section. Roaming profilesWindows Desktop Search does not support Roaming profiles. You may be able to work around this limitation by storing the account profiles of these users on a terminal server. When you do this, users can access their documents, desktop and applications from virtually any computer on the network. Terminal serversWindows Desktop Search is supported on terminal servers. However, when you use WDS on a terminal server, consider the following information:
We recommend that IT departments test these scenarios in-house before they deploy them to production environments. Legacy systemsBy using the (.adm) Group Policy file, you can create a Group Policy setting that reduces the impact on system performance while letting users of older computers maintain access to WDS functionality. Remember that indexing lots of information requires more system resources. Therefore, we recommend that you limit how many resources are indexed on these systems. Installing Windows Desktop SearchThe WDS installer is based on the package installer technology. The package installer is used to install software updates for Microsoft Windows operating systems and Windows components. In the past, the package installer was named Update.exe. If you are an IT administrator and are interested in learning more about the package installer, you can review the package installer documentation. Upgrading earlier versions of WDSThe user or administrator must uninstall earlier versions of Windows Desktop Search before installing the latest version. This affects only version 02.05.xxxx.xxxx or earlier, which is typically installed along with Toolbar. The installation will fail if the earlier versions are on the destination computer. These earlier versions can be uninstalled through remote system management methods. If the current version of Windows Desktop Search is 02.06.0000.xxxx or later, this issue does not occur. Uninstalling the suite and installing WDS enabled for the enterprise edition will not restore the functionality of Toolbar. To ensure that Toolbar is correctly reinstalled after WDS is installed, install the latest version of the Toolbar suite. To find out which version of WDS is installed on your computer, by right-click the WDS icon in the notification area, click Desktop Search Options, and then click the General option in the tree display. The version number is listed in the Version Information box. You can use the file name at a command line to uninstall the software. For example, type msiexec /x MSNSearchToolbar.msi at a command line to uninstall the MSN Search Toolbar. Version history tableThe following table lists recent versions of Windows Desktop Search.
Installation packageWDS is released as a software package that is a single, self-executable file. The actual name of the WDS installation package is WindowsDesktopSearch-KB907371-V2-x86-XXX.exe, where XXX is the language code. For example, you would use WindowsDesktopSearch-KB907371-V2-x86-ENU.exe for U.S. English. In an enterprise environment, WDS is typically deployed to multiple desktops across an organization through one of the following deployment tools:
When WDS is installed, a shortcut is added to the Start menu and to the taskbar for all users of the system. The Windows Deskbar is automatically made available to all users on their taskbars unless it is turned off through Group Policy. WDS runs automatically for each user on the computer whenever that user logs on to the computer. Individual users maintain their own index and search parameters. What's includedWDS includes the following major components:
Adding functionality with MSN ToolbarTo provide desktop search entry points from inside Microsoft Office Outlook or Microsoft Internet Explorer, you have to deploy the MSN Search Toolbar separately. MSN Search Toolbar adds a new toolbar in Internet Explorer and a new toolbar in Outlook. Both toolbars let users perform a desktop search if WDS is installed. MSN Search Toolbar also provides features to optimize corporate deployments. Deployment modesWDS can be deployed in attended mode or unattended mode, depending on the level of interaction you want your users to have with the computer while the installation is in progress. Installations for both modes can be performed through a combination of command-line options. See the package installer command-line options for a full list of supported command-line options. NOTE: To test command-line options and the behavior of the installation package, click Start, click Run, type cmd, and then click OK. This opens a Command Prompt window where you can test the installer package with various options. We recommend that you uninstall WDS before you try to install it again by using different command-line options. Command-line options
Attended modeAttended mode is the typical installation method for an individually managed environment that requires end-user interaction. If you plan to make WDS available on-demand through an internal IT software download site, you can deploy WDS in attended mode. In this mode, the Software Update Installation Wizard is started. Your end users must then accept the Microsoft Software License Terms (EULA) and quit open applications when they are prompted to do so. Your end users must restart their computer, as necessary, at the end of the installation process. When no command-line options are specified, WDS installs in attended mode by default. Unattended modeUnattended mode enables the automated installation of software updates. This mode does not require end-user interaction. If you specify the /quiet or /q command-line option, the WDS installation can be completely silent. If a restart is required, the restart occurs automatically. The WDS deskbar appears automatically after the unattended installation finishes. You should also enable the Prevent First Run Customization Wizard Group Policy setting if you do not want users to see the First Run Customization Wizard. You can hide the wizard either by enabling the Prevent First Run Customization Wizard Group Policy setting or by using the /WDSNOLAUNCH command-line switch. If you enable the Group Policy setting, the wizard will not run during installation or during first run. The /WDSNOLAUNCH command-line switch disables the First Run Customization Wizard by preventing WDS from starting at the end of the installation process. However, this command-line switch doesn’t stop the wizard from running the next time that the user logs in to the system. You can also specify the /passive or /u command-line option. This provides you with a progress bar and warns you that a restart will occur if one is necessary. Additionally, passive mode installation will display any errors that you may encounter. You should also disable the “Prevent First Run Customization Wizard.” If Outlook is running while WDS is being installed in unattended mode, Outlook will not quit as part of the installation process. The WDS installation process will continue. However, indexing will not start until you quit and then restart Outlook. Use the /WDSCLOSEOL command-line switch if you want Outlook to close while WDS installs in silent or passive mode. There are several ways to accomplish unattended installation. These include developing custom batch installations by using the previously mentioned command-line options, or by using automation software, such as SMS or Windows Update Services, to install software updates on all computers across a network. If you manually install a software update, the installation runs in the user context. You should be an administrator with the user permissions that are specified in the “Required User Right” section of the package installer documentation. If a software update is deployed through SMS or Windows Update Services, the package installer is spawned in the System context because the parent process runs as a service. Examples of commonly used extraction optionsThe table in the Command-line options section details common extraction options and their functions. After extraction, the files reside in the specified folder. If no folder is specified and the command-line option /extract was used with /passive or /quiet, a randomly named folder (for example, 1ed6b742f546f) is generated, and the setup files are placed there. When installation is finished, these files and the folder are removed. The following table provides examples of commands you can use to extract the contents of a software update package.
Deploying WDS through Group PolicyYou cannot directly deploy package installer/update.exe based Windows components through Group Policy. If you need to use Group Policy, you must write a deployment wrapper, such as an MSI package, that contains the WDS executable file. Note: Microsoft does not support repackaging software updates with a different installer. This includes modifying the current update.exe package headers, files, or installation information to conform to another deployment method. However, placing the package in a wrapper, such as an MSI wrapper, is supported. The package installer and the Windows Installer are not interchangeable. Packages that are built with one installer technology have been tested and optimized to work only with that technology. WDS software updatesTo obtain the latest versions of WDS, you must check for updates on the WDS website. If you use a WSUS server, you control when updates are applied to most Windows components. If you use SMS or other deployment technologies for updates, you have full control over updates. The Hide Check for Update Link Group Policy setting lets you hide the Check for updates link on the WDS Help menu. This setting sends the user to the WDS website. Aside from making the business decision about whether to enable this policy, there is no additional configuration required to manage your own updates to WDS in a locked enterprise environment. Enterprise search integrationWDS provides you with settings so that you can start intranet searches to your enterprise search solution from within Windows Deskbar and WDS results view. Examples of enterprise search solutions include Microsoft Share Point Portal Server or Windows SharePoint Services (WSS). Your users can benefit by:
Additionally, all web searches initiated from WDS use the default search provider of your user's default browser. All intranet-related settings are documented in the Search category in the Policy section. Encrypting your indexThe WDS index is lightly encrypted so that it is not easily readable if someone tries to open the index file. To strongly encrypt the WDS index, you will have to place it in the Encrypting File System (EFS). EFS provides the core file encryption technology that is used to store encrypted files on NTFS file system volumes. EFS helps protect files from intruders who might gain unauthorized physical access to sensitive, stored data (for example, by stealing a portable computer or an external disk drive). Windows Desktop Search extensibility and programmabilityWDS provides a number of extensibility and programmable interfaces to help enable these additional scenarios for enterprise customers:
For more information, see the WDS developer’s guide. View a list of available third-party filters and protocol handlers that can be integrated with WDS. Customizing WDS by using Group Policy settingsGroup Policy overviewThis version of WDS fully supports Windows Group Policy. Administrators can use Group Policy to deliver and apply one or more preferred configurations or policy settings to a set of targeted users and computers within an Active Directory directory service environment. The Administrative Template files (.adm files) provide the majority of available policy settings and are designed to modify specific keys in the registry. This is known as a registry-based policy. You will need to obtain the WDS .adm file to configure and enforce certain WDS settings through Group Policy. The following is a summary of the steps that you must take as a Group Policy administrator to configure WDS with Group Policy:
See Microsoft Technet for more Group Policy information. Obtaining the Windows Desktop Search Group Policy fileThe WDS .adm file is available for download here. You may have to right-click the download link and click Save Target As to download the file. Only WDS version 2.6 or later provides Group Policy support. Therefore, make sure that you are deploying WDS version 2.6 or a later version. After you have downloaded the .adm file, you can edit it in the Group Policy Management Console (GPMC). The WDS .adm file is named "DesktopSearch.adm". After you import the .adm file into GPMC, you will see a Windows Desktop Search node added under the Administrative Template tree. All WDS policies are supported as both machine and user policy settings to help provide optimum configuration flexibility. We recommend that you implement each setting as either a machine or a user policy, but not as both. WDS policies are organized into three categories:
Windows Desktop Search Policy locationAll policies are created under one of the following sections of the registry:
This key is added to the policy section only when a policy is applied. Therefore, if no policies are applied, the key will not be present. Whenever possible, all registry sub keys and values will parallel the corresponding WDS machine and user preferences sections of the registry. Installing international versionsIf your organization requires localized builds for users who speak different languages, you can either deploy localized versions of WDS or deploy the English version of WDS and then download and install the Multilingual User Interface (MUI) Pack. This allows your users to switch user interfaces based on the user’s language preference. The WDS MUI Pack cannot be installed with a non-English version of WDS. You must install the English version of WDS, and then install the WDS MUI Pack. This means that if the WDS MUI Pack is already installed on a computer, you cannot install a non-English version of WDS on the same computer. Installing Windows Desktop Search with the MUI PackWindows Desktop Search MUI works together with Windows MUI. For best results, we recommend that you install the Windows MUI before you install the WDS MUI. When the Windows UI language is changed, the WDS UI language changes to the same language. best results, follow these steps when you install WDS with the MUI Pack:
The WDS UI will use the same language that you selected in the Regional and Languages Options item in Control Panel. You can download the MUI Pack from the following Microsoft website: For more information about the Windows MUI Pack, visit the following Microsoft website: General policy setting behaviorAll WDS policy settings will be described in detail. However, WDS policies generally share the following attributes:
Adhering to system policiesIn general, WDS is built on common Windows components. Therefore, WDS adheres to system-level policies that your organization may have enabled. There are two specific system-level policies that are relevant to the Windows Deskbar, as follows.
Windows Desktop Search PoliciesThis section outlines all the policy settings available for WDS.
Providing enterprise specific defaultsPolicies are generally enforced, implying that if you enable a policy, the user is not allowed to change the setting. In this scenario, the corresponding setting typically appears dimmed or non-existent (or an error message is displayed) if the user tries to change the setting. However, in certain business scenarios, the IT administrator may only be interested in changing the out-of-box default settings to provide enterprise specific defaults that the user can later change. For example, consider the following scenario. WDS indexes e-mail attachments out-of-box. You prefer not to index e-mail attachments for some business reasons. But you don’t mind providing the choice so that users who really want to index e-mail attachments can do so. However, if you were to enable the "Prevent Indexing of E-Mail Attachments" policy, you would prevent everyone from indexing attachments. In this scenario, you can specify your enterprise default settings by providing machine preferences in the registry. You will have to publish scripts to push theses machine preference registry keys to your computers. All WDS machine preferences are located in the following section of the registry: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Desktop Search\DS Although the root is different, policy settings parallel machine preferences locations in the registry. Certain settings only make sense as enforced policy settings; therefore, they have been removed from the machine preference table below.
In general, WDS uses the following logic to determine the precedence of settings:
Troubleshooting OutlookIf your end-users run into issues with WDS that you cannot resolve, please contact Microsoft Help and Support. If you have additional questions about deploying WDS in your organization, you can use the following resources:
Here are some helpful troubleshooting tips: Outlook items are not indexed There are several reasons why Outlook items are not indexed. To troubleshoot, use the following methods:
MAPI logging Windows Desktop Search provides additional troubleshooting for Outlook by using Messaging Application Program Interface (MAPI) logging. To enable MAPI logging, create the LogLevel.MAPI registry entry in the following registry subkey: HKCU\Software\Microsoft\Windows Desktop Search\LogLevel.MAPI The registry entry is of type DWORD. To enable logging, set the Value to 0. To disable MAPI logging, set the Value to 4. When you enable this registry entry, by default, a Mapi.txt file that contains the log information is written to the following folder: C:\Documents & Settings\%username%\Local Settings\Application Data\Microsoft\Desktop Search\Logs Outlook 2003 downloads full message bodies and attachments when it is set to download only headers When Outlook 2003 runs in Exchange Server Cached mode, Outlook may download entire message bodies, even when it is set to download only headers. This behavior may occur regardless of whether the WDS indexer is active or in Snooze mode. This issue may be caused by any of the following:
We are working to resolve this issue. Troubleshooting Outlook ExpressNote: Outlook Express must be running for WDS to correctly index items in Outlook Express. WDS fails silently when you open IMAP Header items in Outlook Express When Outlook Express downloads message headers from an IMAP mail server, WDS indexes the headers and the complete mail messages. When you perform a search, the message headers appear in the search results. When you double-click a message header, WDS cannot retrieve the entire message body and does not open the message. When this issue occurs, you do not receive an error message. To work around this issue, download the entire message body, or index only folders that contain complete messages. Troubleshooting Group Policy settingsGeneral troubleshooting When you troubleshoot WDS Group Policy settings, it is a good idea to double-check the existing values against the examples in the Policies Matrix in theWindows Desktop Search Policies section. Problems are often caused by a mistyped value, an invalid value, an extra space, or by a similar error. Using the Prevent Unwanted IFilters and Protocol Handlers Group Policy setting The Prevent Unwanted IFilters and Protocol Handlers Group Policy setting can help a system administrator manage the type of content that is indexed. Different kinds of documents and stores use different kinds of filters and protocol handlers. By restricting the kinds that are allowed in your enterprise, you can effectively block certain types of content. When you apply this policy setting, you must enumerate the GUIDs to allow the filters. An item that's not in your allow list won't be used by WDS. This policy does not remove or disable the filter for use by other applications, such as Share Point Server (SPS) or Windows Share Point Services (WSS). The policy only prevents WDS from accessing the filters. The following GUIDs are used for the default file types that are provided with Windows Desktop Search:
When you use Policy Manager to edit this policy, make sure that you enter these GUIDS in the allow list. When you type the GUIDs, make sure that you include the braces { }. The braces are required. If an IFilter is associated with a file type, the file type is registered in the following registry subkeys: HKEY_CURRENT_USER\Software\Classes HKEY_CURRENT_USER\Software\Microsoft\RSSearch\ContentIndexCommon\Filters\Extension\ For example, if .EXT is the extension that you want to find, the file type will be registered in the ext entry and the .EXT entry in these subkeys. The value of .EXT is the GUID for the file type in the values of CachedFilterIID or Default ,respectively. To disable the indexing of a subset of file types that are handled by a particular IFilter or protocol handler, you can use the Prevent Indexing of Certain File Types Group Policy setting. This setting stops WDS from indexing a certain type of file, while continuing to allow the IFilter to index other file types that are handled by the IFilter or the protocol handler. Using the Prevent Indexing Certain Network Shares Group Policy setting When you use the Prevent Indexing Certain Network Shares Group Policy setting, make sure that the excluded path has a unique name. When you exclude a share, this policy matches other shares that contain the excluded path as part of their path name. For example, when you exclude \\MyServer\Share, \\MyServer\Share1 will also be unavailable in the Indexing section in Desktop Search Options. Suppose you map the share \\MyServer\Corp to the Z: drive. If you add a policy setting to prevent \\MyServer\Corp\Share from being indexed, the Share folder will be unavailable in the Indexing Options dialog for the Z: drive. Also, you will be unable to individually select Z:\Shared, Z:\Share1, and similar shares. If you then select the root of the Z: drive, all subfolders except for Z:\Share will be defined by the policy setting. Any other folder under the Z: drive that does not start with “Share” will not be affected. To work around this situation, make sure that the excluded folder has a unique name such as Z:\IShare. In this example, the “I” breaks the pattern match for the path to Z:\share1 or Z:\Shared. If you use this workaround, other peer-level folders will not match the path of the excluded folder. Using the Add Secondary Intranet Search locations Group Policy setting When you use the Add Primary Intranet Search Locations policy followed by the Add Secondary Intranet Search Locations policy, you must first close all search windows before the new locations are visible in the All Locations section of the WDS results view. Error: There is not enough disk space available on the destination drive to move the index This error message may occur if the Specify Location of Windows Desktop Search Index Group Policy setting is enabled by using the .adm file with an invalid path. In this situation, you receive the error message when you start WDS, and when any other policy setting is added or changed. To correct this situation, correct the path for the indexer, or disable the policy setting. Moving the index to a network share or mapped drive may cause the indexer to fail After the index is built, you can move it by clicking the Change button in the Index Location area in the Advanced settings of Desktop Search Options. If the new location is a network share or a mapped network drive, the indexer may fail when you click the Rebuild Index button. If the indexer fails, you may have to uninstall and then reinstall Windows Desktop Search. We recommend that you keep the index on the local computer. Keeping the index on the local computer can decrease network traffic and help prevent network issues that affect your index or your ability to access it. General troubleshooting for WDSUsing antivirus and antispyware with WDS Because WDS indexes the user's system, antispyware or antiadware applications may remove or disable parts of WDS. Although this is not a typical problem with most antivirus software packages, it is worth noting. We strongly recommend that you test WDS on a standard desktop image before you deploy WDS to your company or engage in a pilot program. This desktop image should contain all the software that is commonly used at your company. By testing WDS in a controlled environment, you can isolate and prevent conflicts between WDS and your security software. For performance reasons, we also suggest that you exclude the WDS program files, index files, and services from the list of items and places that are scanned. The Quick Launch section of the Task Bar disappears on multiuser systems On a multiuser system, the Task Bar may be hidden in some users’ profiles. This issue may occur if a user uninstalls the Quick Launch bar in Windows Desktop Search. To reinstall the Quick Launch bar, follow these steps:
WDS seems to use a lot of memory After you install WDS, you may notice that the amount of committed memory appears to increase by as much as 180 MB. This is because the indexer uses memory mapped files. When the indexer maps a large index file to its own virtual memory space, committed bytes increase. This does not affect the memory available to any other process because pages are mapped to the index and not to the paging file. These pages are loaded on demand and only when they are required. Therefore, when you view the working set of processes for WDS, they don't appear to use as much space as the committed bytes. WDS fails silently when the network connection is lost When a user successfully indexes a network resource, and then loses the connection to that resource, the indexed items on that resource still appear in WDS searches. If a user selects an indexed item that the system cannot connect to, WDS does not retrieve the item, and you do not receive error message. This issue is scheduled to be resolved in a future release. Indexes are damaged or deleted If a WDS index is damaged or deleted, it will be recreated the next time that you start WDS. However, this causes WDS to reindex the computer and other resources. Depending on how many resources must be indexed, the index may not be restored for some time. In earlier versions of WDS, when WDS cannot correctly re-create a damaged index, WDS prompts you to reinstall the product. When this occurs, we strongly recommend that you uninstall WDS before you reinstall it. Reinstalling WDS causes WDS to build new indexes. Rebuilding the indexes may take a long time, depending on how much information is indexed. The WDS add-on for Internet Explorer appears as “dsWebAllowBHO” instead of as “Windows Desktop Search” When you view add-ons in Internet Explorer, the WDS program appears as “dsWebAllowBHO” instead of as “Windows Desktop Search.” “DsWebAllowBHO” is a Browser Helper Object that lets you perform a desktop search from a web search engine. For example, at the top of the http://www.msn.com website is a search box that has a list of search types above it. If you type a search term and then click Desktop above the search box, the search parameters are passed to WDS to process. When this add-on is disabled, WDS continues to work normally. However, you cannot perform a desktop search from a web page. To view the list of add-ins in Internet Explorer, follow these steps:
Office documents sent as attachments appear in text format Office documents are indexed and searchable when they are received as attachments. However, by default, the attachments appear in a text-only format in the Preview Pane. To view these attachments in a rich preview format, follow these steps:
WDS does not return results for words in foreign languages When you use the English version of WDS with Windows 2000 to search for words that contain special characters or for words that are written by using a different character set, WDS may not return results. For example, this issue may occur when you search for words in Russian, Japanese, Arabic, or other languages. This issue does not affect Windows 2000 with Service Pack 3 (SP3) or Windows XP with SP1. To work around this issue, make sure that computers that are running Windows 2000 have the latest service pack installed. Additional informationInstalling WDS using the “Run As” option is not supported Using the “Run As” option to install WDS during download is not supported. When you use this option, parts of WDS may not run correctly. For example, if you right-click the WDS icon in the notification area, click Help, and then click Display Windows Deskbar, the deskbar may not appear. For best results, download WDS, and then install WDS by using an Administrator account or by using an automated service that runs with administrative credentials. Smart Indexer The Smart Indexer feature helps WDS enhance the user experience. Typically, the indexer runs when the system is idle. WDS monitors the system for any of the following situations:
To temporarily disable this functionality, right-click the WDS icon in the notification area, and then click Index Now. This also temporarily stops the indexer from pausing. You can permanently disable this functionality by clicking Prioritize Indexing in the Advanced section of Desktop Search options. Indexing a calendar on a SharePoint server or in Share Point Services You can index a calendar on a SharePoint server. To do this, connect to the server, click the link to display the calendar, and then click Link to Outlook on the toolbar above the calendar. Outlook will ask if you want to add the folder to Outlook. If you click Yes, the calendar will appear in your folder tree as a subfolder of "SharePoint Folders." If you click No, these folders are not added to your Outlook profile. To remove these folders from your profile, right-click SharePoint Folders, and then click Close "SharePoint Folders." You are warned that the links to the SharePoint Service data will be lost if you close the folders, and you are asked if you want to continue. If you click Yes, the "SharePoint Folders" folder and its subfolders are removed from your profile. Click No to cancel the operation and to leave the folders in your profile. Uninstalling WDS If you uninstall WDS on an individual computer, we recommend that you use the Add or Remove Programs Control Panel item. When you use Add or Remove Programs, make sure that you select the Show Updates option and uninstall the newest product or product updates first. When you use Add or Remove Programs to remove WDS 02.06.0 or a later version of WDS, you may receive a warning message that includes a list of updates that are installed on your computer. This message also includes the following text: “If Windows Desktop Search is removed, these programs may not run properly. Do you wish to continue?” This message occurs because WDS is installed as an update, and therefore appears with other Windows updates. You can ignore this message. Although some updates may not run correctly after another update is removed, none of the listed updates will be affected when you remove WDS. If you use a script or a third-party product to uninstall WDS, we recommend that you use the uninstallation package (Spuinst.exe) for the most recent version. However, we strongly recommend that you use Add or Remove Programs in Control Panel to remove WDS instead of a script or a third-party product. Although WDS creates a system restore point when you install it, we do not recommend that you use the restore point to remove WDS. To uninstall WDS, use the uninstaller package for your specific version. You can find the uninstaller package in one of the following locations:
Uninstall options
To see other command-line options, run the spuninst.exe /help command at a command prompt. Uninstalling versions 2.5.0.1082 and 2.5.0.1119 Version 02.06.X will not install correctly on a computer that is running version 02.05.0.1082 or an earlier version of WDS. Before you install the newer version, you must first uninstall the earlier version of WDS. Use the Msiexec.exe program to uninstall WDS. We recommend that you use one of the following methods. Method 1: Use the product code To find the product code in the registry, click Start, click Run, type regedit in the Open box, and then click OK. In Registry Editor, locate the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSN Apps\MSN Toolbar Suite The product code is the value of the PC registry entry. For example, when version 2.5.0.1082 of WDS is installed, the value of the PC registry entry is "7d1dcbba-f6f5-42b4-b90b-f04ace4dfd6c." Run a command that is similar to the following, including the product code in brackets. When you are uninstalling version 02.05.0.1082 of WDS, use the following command line. Note The brackets { } are required. Msiexec.exe /x {7d1dcbba-f6f5-42b4-b90b-f04ace4dfd6c} /qn The /x switch causes Msiexec to uninstall the product, and the /qn switch disables alerts during the uninstall process. For more information about Msiexec.exe command-line options, type msiexec /? at a command prompt. Method 2: Use the MSN Search Toolbar Windows Installer The MSN Search Toolbar Windows Installer is located in the following location, where <Version Number> is the version of the product being uninstalled, such as 02.05.0000.1082, and <Drive> is the letter of the disk drive where Windows is installed. <Drive>:\Documentsand Settings\All Users\Application Data\MSN Search Toolbar\<Version Number>\en-us Run the following command to uninstall WDS: msiexec.exe /x "<Drive>:\Documents and Settings\All Users\Application Data\MSN Search Toolbar\<Version Number>\en-us\MsnSearchToolbar.msi" /qn We recommend that you use Method 1. When you use Method 1, the only required variable is the product code that is stored in the registry. When you use Method 2, you must provide the letter of the disk drive where Windows is installed and the version number of WDS. Understanding the “Windows Desktop Search Indexing Status” Dialog Two counters are listed in the Windows Desktop Search Indexing Status dialog box: Items indexed so far and Items left to scan. The Items left to scan counter records the number of items that are currently queued to be scanned for updates or changes. Typically, the indexer keeps a list of folders that it has to index. The indexer starts by finding out whether anything in a folder has changed. If it doesn’t detect any changes, the indexer skips the folder and goes to the next folder. If the indexer detects changes in the next folder, it searches all the items and subfolders in that folder to determine the changes. As the indexer searches deeper in the folder path and finds new folders to search, the number in Items left to scan increases or decreases. Additional resourcesUpdate.exe command-line options Information about Group Policy on Microsoft TechNet FAQ for Windows Desktop Search Document revision history
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
