[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

Returns information about how (or if) the Enhanced 911 (E9-1-1) location service has been configured. The E9-1-1 service enables those who answer 911 calls to determine the caller’s geographic location.


Get-CsLocationPolicy [-Identity <XdsIdentity>] [-LocalStore <SwitchParameter>]
Get-CsLocationPolicy [-Filter <String>] [-LocalStore <SwitchParameter>]


Parameter Required Type Description




The unique identifier of the location policy you want to retrieve. To retrieve the global location policy use a value of Global. For a policy created at the site scope this value will be in the form site:<site name>, where site name is the name of a site defined in the Microsoft Communications Server 2010 deployment. For example, site:Redmond. For a policy created at the per-user scope this value will simply be the name of the policy, such as Reno.




A string containing wildcard characters that will retrieve location policies based on matching the Identity value of the policy to the wildcard string.




Retrieves the location policy information from the local replica of the Central Management database, rather than the Central Management database itself.

Detailed Description

The location policy is used to apply settings that relate to E9-1-1 functionality. The location policy determines whether a user is enabled for Enhanced 911, and if so what the behavior is of an emergency call. For example, you can use the location policy to define what number constitutes an emergency call (911 in the United States), whether corporate security should be automatically notified, how the call should be routed, and so on. This cmdlet retrieves one or more location policies.

Return Types

Get-CsLocationPolicy returns instances of the Microsoft.Rtc.Management.WriteableConfig.Policy.Location.LocationPolicy object.


-------------------------- Example 1 --------------------------

Copy Code

Example 1 returns a collection of all the location policies currently in use in your organization. This is done simply by calling Get-CsLocationPolicy without any parameters.

-------------------------- Example 2 --------------------------

Copy Code
Get-CsLocationPolicy -Identity Reno

The command shown in Example 2 returns only those location policies that have an Identity equal to Reno. Because identities must be unique, this command will only return, at most, one location policy.

-------------------------- Example 3 --------------------------

Copy Code
Get-CsLocationPolicy -Filter tag:*

The preceding command uses the Filter parameter to return all the location policies that have been configured at the per-use scope. (Policies configured at the per-user scope can be directly assigned to users and groups.) The wildcard tag:* tells Get-CsLocationPolicy that the returned data should be limited to those location policies that have an Identity that begins with the string value tag:. Even though you don’t need to specify the tag: prefix when retrieving an individual policy, you can use that prefix to filter on all per-user policies.

-------------------------- Example 4 --------------------------

Copy Code
Get-CsLocationPolicy | Where-Object {$_.EnhancedEmergencyServicesEnabled -eq $False}

Example 4 returns a collection of all the location policies where the EnhancedEmergencyServicesEnabled property has been set to False. To do this, the command first uses Get-CsLocationPolicy to return a collection of all the location policies currently in use in the organization. That collection is then piped to the Where-Object cmdlet; in turn, Where-Object applies a filter that limits the returned data to those policies where the EnhancedEmergencyServicesEnabled property is equal to (-eq) False ($False).