Prev | Current Page 380 | Next

Joezer Cookey-Gam, Brendan Keane, Jeffrey Rosen, and Jonathan Runyon

"Professional Windows PowerShell for Exchange Server 2007 Service Pack 1"

For the identity of
the user, any of the following are accepted for the Identity parameter:
??‘ ADObjectID: exchangeexchange.com\sales\john doe The syntax of the AD object is
domain\OU\name .
??‘ GUID Ex: (43CBD6FF - AC3B - 4A8F - 8906 - F14EB33A0B31) A GUID is a globally unique identifier.
Think of it as a serial number or a MAC address. Two GUIDs cannot be the same in an Active
Directory forest.
??‘ DN: The distinguished name can be the full name.
The distinguished name is the LDAP listing of the user. It contains the user ??™ s full name the
organizational unit (OU) that they reside in as well as the domain name. The following is an example of
a user whose full name is John Doe, resides in the Sales OU, and is in the domain exchangeexchange
.com: CN=John Doe,OU=Sales,DC=exchangeexchange,DC=com .
??‘ Domain\Account ??“ User account, and so on: Typically this is the user ??™ s logon name that is used
when the user logs in to the domain. Following a naming convention of the first initial of the
first name and the complete last name, John Doe from sales would have the following logon
name: jdoe .
??‘ UPN: The UPN, or user principal name, is default the user ??™ s logon name @ domain. So for John
Doe, it would be jdoe@exchangeexchange.com . The UPN, like the domain name and the
GUID, must be unique to the domain.


Pages:
368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392
znaki drogowe pozycjonowanie teksty piosenek poker Browar