Hi, In Exchange 2003 we have ability to create the InterOrgPerson object in Active Directory, but I do not understand when I should use it? can you give a example? Thanks.

Together with Exchange, the inteorgperson object is useless. If I remember correct, th reason for Microsoft to put in in there was to fullfill some RFC's. But I could be misstaken here. lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

If I create one interorgperson account with email address, is there any difference between this account and normal account?

InetOrgPErson is more like a contact. Doesn't have a password so it cacnot be used for loggin on. lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

So its mailbox does not exist in our exhange server?

Tried to create a inetorgperson object, and it can have a password for logon and it also can have a mailbox. This is all Win 2008 R2 and Exchange 2010 and I think its different in Win2003 and Exchange 2003 days (could be wrong here). Anyway, I ahve never actually seen inetorgperson objects used at any customer. But that doesn't meen it's having a valid reason for existance.lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

Thanks for your suggestion. You are so nice.

found this. InetOrgPerson object support in Exchange 2003 http://support.microsoft.com/kb/822591 What is the purpose of InetOrgPerson http://www.pcreview.co.uk/forums/purpose-inetorgperson-t1456786.html lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

RFC 2798 I do believe.

Active Directory Domain Services (AD DS) provides support for the InetOrgPerson object class and its associated attributes as defined in Request for Comments (RFC) 2798. The InetOrgPerson object class is used in several non-Microsoft, Lightweight Directory Access Protocol (LDAP) and X.500 directory services to represent people in an organization. Support for InetOrgPerson makes migration from other LDAP directories to AD DSmore efficient. The InetOrgPerson object is derived from the user class. It can function as a security principal just like the user class. When the domain functional level is set to Windows Server 2008 or Windows Server 2008 R2, you can set the userPassword attribute on InetOrgPerson and user objects as being the effective password, just as you can with the unicodePwd attribute.