Topic Last Modified: 2011-02-16

In a multi-forest topology, returns information about user accounts from forests other than your home forest; these are users who have been replicated as contact objects by Microsoft Forefront Identity Manager 2010 (or a previous version of the product). Get-CsAdContact returns any user who has a value configured for the msRTCSIP-OriginatorSid attribute.

Syntax


`Get-CsAdContact [-Identity <UserIdParameter>] [-Credential <PSCredential>] [-DomainController <Fqdn>] [-Filter <String>] [-LDAPFilter <String>] [-OU <OUIdParameter>] [-ResultSize <Unlimited>]`

Parameters

Parameter	Required	Type	Description
Identity	Optional	UserId Parameter	Indicates the Identity of the contact to be returned. Contact Identities can be specified by using one of three formats: 1) the contact’s SIP address; 2) the contact’s Active Directory distinguished name; and, 3) the contact’s Active Directory display name (for example, Ken Myer). You can use the asterisk () wildcard character when using the Display Name as the contact Identity. For example, the Identity " Smith" returns all the contacts with a display name that ends in the string value "Smith".
Credential	Optional	PSCredential object	Enables you to run the Get-CsAdContact cmdlet under alternate credentials; this might be required if the account you used to log on to Windows does not have the necessary privileges required to work with contact objects. To use the Credential parameter you must first create a PSCredential object using the Get-Credential cmdlet. For details, see the Help topic for Get-Credential.
DomainController	Optional	String	Enables you to connect to the specified domain controller in order to retrieve contact information. To connect to a particular domain controller, include the DomainController parameter followed by the fully qualified domain name (for example, atl-cs-001.litwareinc.com).
Filter	Optional	String	Enables you to limit the returned data by filtering on attributes specific to Microsoft Lync Server 2010. The Filter parameter uses the same Windows PowerShell filtering syntax used by the Where-Object cmdlet. For example, a filter that returns only contacts who have a SIP address that ends with "fabrikam.com" would look like this: {SipAddress -like "@fabrikam.com"}, with SipAddress representing the Active Directory attribute; -like representing the comparison operator; and "@fabrikam.com" representing the filter value.
LdapFilter	Optional	String	Enables you to limit the returned data by filtering on generic Active Directory attributes. For example, you can limit returned data to contacts who work in a specific department, or contacts who have a specified manager or job title. The LdapFilter parameter uses the LDAP query language when creating filters. For example, a filter that returns the contact that has the telephone number 1-425-555-1298 would look like this: "telephoneNumber=1-425-555-1298", with "telephoneNumber" representing the Active Directory attribute; "=" representing the comparison operator (equal to); and "1-425-555-1298" representing the filter value.
OU	Optional	Distinguished name	Enables you to limit the retrieved information from a specific Active Directory organizational unit (OU) or container. This parameter returns data from both the specified OU and any of its child OUs. For example, if the Finance OU has two child OUs: AccountsPayable and AccountsReceivable. contacts will be returned from each of these three OUs. When specifying an OU, use the distinguished name of that container; for example: OU=Finance,dc=litwareinc,dc=com.
ResultSize	Optional	Integer	Enables you to limit the number of records returned by the cmdlet. For example, to return seven contacts (regardless of the number of contacts that are in your forest) include the ResultSize parameter and set the parameter value to 7. Note that there is no way to guarantee which 7 users will be returned. The result size can be set to any whole number between 0 and 2147483647, inclusive. If set to 0 the command will run, but no data will be returned. If you set the ResultSize to 7 but you have only three contacts in your forest, the command will return those three contacts and then complete without error.

Detailed Description

In a multi-forest topology, users from other forests are represented as contacts. These contacts are not equivalent to Active Directory contacts; if you use Active Directory Users and Computers to create a new contact, that user will not be returned by the Get-CsAdContact cmdlet. Instead, Get-CsAdContact only returns information about users from forests other than your home forest. If you do not have a multi-forest topology then you will not need to call Get-CsAdContact.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Get-CsAdContact cmdlet locally: RTCUniversalUserAdmins, RTCUniversalServerAdmins, RTCUniversalReadOnlyAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Get-CsAdContact"}

Input Types

String. Get-CsAdContact accepts a pipelined string value representing the Identity of a user account.

Return Types

Get-CsAdContact returns instances of the Microsoft.Rtc.Management.ADConnect.Schema.ADContact object.

Example

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

	Copy Code
Get-CsAdContact

The command shown in Example 1 returns a collection of all the multi-forest contacts found in Active Directory Domain Services (AD DS). Calling Get-CsAdContact without any additional parameters returns all the property values for all the Active Directory contacts.

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

	Copy Code
Get-CsAdContact \| Select-Object DisplayName, SipAddress

Example 2 also returns a collection of all the Active Directory contacts. In this case, however, that collection is piped to the Select-Object cmdlet, which specifies the only two attributes that will be displayed on the screen: DisplayName and SipAddress.

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

	Copy Code
Get-CsAdContact -Identity "Ken Myer"

The preceding command returns information for a single Active Directory contact: the contact with the Identity "Ken Myer".

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

	Copy Code
Get-CsAdContact -LdapFilter "Organization=Fabrikam"

In Example 4, the command returns all the Active Directory contacts who work for Fabrikam. To do this, Get-CsAdContact is called, along with the LdapFilter parameter. In this example, the limits the returned data to contacts that have their Organization attribute set to "Fabrikam".

-------------------------- Example 5 ------------------------

	Copy Code
$x = Get-Credential -Credential "litwareinc\administrator" Get-CsAdContact -Credential $x

The two commands shown in Example 5 illustrate the use of the Credential parameter, which enables you to run Get-CsAdContact under alternate credentials. In the first command, the Get-Credential cmdlet is called in order to create a PSCredential object for the account litwareinc\administrator. This command displays a Credential Request dialog box for the user litwareinc\administrator; after you supply the password for this account, that credential information will be stored in the variable $x. In the second command, Get-CsAdContact is called along with the Credential parameter. The parameter value $x indicates that Get-CsAdContact should be run under the account litwareinc\administrator.