LS4D Registry Settings

Windows CE 5.0 Not SupportedWindows Embedded NavReady 2009 Supported

10/16/2008

The registry stores information that is used to configure Live Search for Devices (LS4D). This topic describes the registry keys that are used to configure Live Search for Devices (LS4D).

Local Search Provider URL

The HKEY_LOCAL_MACHINE\Software\Microsoft\LocalSearch\LocalSearchProviderURL registry subkey indicates the LS4D Web service URL address that must be provided in the registry. Queries must pass through the Web service on the LS4D server in order to submit LS4D queries and retrieve results from the Live Search Engine.

The following table shows the named value for this subkey:

Value: type Description

LocalSearchProviderUrl : [REG_SZ]

Contains a canonical URL that describes the Live Search provider to connect to; for example, "http://ls4d.search.live.com/ls4dwebsite/abc.lsd". This value is required.

This value is required. Queries will return ERROR_BAD_CONFIGURATION if a Live Search provider is not specified. No default value is provided.

Response Time Out

The HKEY_LOCAL_MACHINE\Software\Microsoft\LocalSearch\ResponseTimeOut registry subkey indicates the time-out period to wait for a response from the server. The LS4D client API waits for 30,000 milliseconds, as a default, for a server response after a request is sent to the LS4D server. This time-out period helps alleviate transaction latencies during message transactions to the server. To optimize performance of a Live Search application, you can configure this setting.

The following table shows the named value for this subkey:

Value : type Description

ResponseTimeOut : DWORD

Indicates the server response time-out period, in milliseconds. The default value is 30,000 milliseconds. This value is optional.

Device ID

The HKEY_LOCAL_MACHINE\Software\Microsoft\LocalSearch\DeviceID registry subkey uniquely identifies a portable navigation device (PND). It is added to a search request and is used by the LS4D server to verify that the search request is from a registered device and is permitted to pass through to the Live Search servers. The device ID is one component of the LS4D paired identifier.

For more information about how a Device ID is generated, see How LS4D Obtains the Device ID in the topic LS4D Device ID and Device Group ID Overview.

The following table shows the named value for this subkey:

Value : type Description

DeviceID : [REG_SZ]

A string UUID value that uniquely identifies a portable navigation device (PND). A string UUID is composed of multiple fields of hexadecimal characters. Each member has a fixed length, and fields are separated by the hyphen character; for example:

989C6ESC-2CC1-11CA-A044-08002B1BB4F5

Device Group ID

The HKEY_LOCAL_MACHINE\Software\Microsoft\LocalSearch\DeviceGroupID registry subkey uniquely identifies a group of portable navigation devices (PNDs) that belong to an OEM. It is added to a search request and is used by the LS4D server to verify that the search request is from a registered device and is permitted to pass through to the Live Search servers. Each device-group ID for Live Search for Devices (LS4D) is distributed by Microsoft for inclusion in the registry. The device-group ID is one component of the LS4D paired identifier.

The following table shows the named value for this subkey:

Value : type Description

DeviceGroupID : [REG_SZ]

An auto-generated string UUID value that uniquely identifies the group of devices that belongs to an OEM. A string UUID is composed of multiple fields of hexidecimal characters. Each member has a fixed length, and fields are separated by the hyphen character; for example:

ba209999-0c6c-11d2-97cf-00c04f8eea45

This value is required. Queries will return ERROR_BAD_CONFIGURATION if a Device Group ID is not specified. No default value is provided.

See Also

Concepts

Live Search for Devices (LS4D)
LS4D Device ID and Device Group ID Overview
How to Register for the LS4D Service