Accessing Custom Resource Properties of a Resource Mailbox in Active Directory -
(This post refers to Exchange 2010 but the capacity of resource mailbox was introduced in Exchange 2007)
The exchange allows you to create different types of mailboxes for conference rooms - resource mailboxes - and provide them custom properties, such as "Whiteboard", "A / V", these properties look boolean, e.g. Whether there is a whiteboard in a conference room or not you can assign them to a mailbox in the Exchange 2010 Management Console (or in Shell).
I am trying to figure out how to access these properties programmatically it does not appear that the Exchange Web Services API was intended for it, because all the underlying data in Active Directory Archiving.
For example, conference room mailboxes have one of the unique properties in resource properties, and you can get it from Active Directory:
child.Properties [" MsExchResourceCapacity "]
Where" child "represents a DirectoryEntry object, as you are running through the contents of an Active Directory
Active After browsing the directory schema, nothing did not jump on me Fast Custom Property ("Whiteboard", "A / V")
-contribute CN = resource schema, CN = global settings, CN = Exchange 2010, CN = Microsoft Exchange, CN = Services, CN = configuration, DC = Ex2010, dc = laboratory
. (If you connect to DC = ex2010, DC = Lab
, you will not get that information - you need to connect to the configuration partition namespace - CN = Configuration, DC = AXA 2010, DC = Lab
.) You must use the cmdlet to add custom resource properties (Example: Set-ResourceConfig -DomainController dc01.ex2010.lab -ResourcePropertySchema ( "Room / 16Seats", "Tools / Projectors", "Room / 8Seats", "Tools / Whiteboards")
)Then you need to use cmdlet (i.e., Set-MailBox roomtest -ResourceCustom "8 Seats"
) to set the resource custom property for that specific resource mailbox.
I set these exchange-specific attributes manually (i.e., through System Directory Services) because it can be an unexpected result. Use a CMDlet in a supported way. Therefore, I suggest that you call CMDlet from your NDT code. Is one.
Comments
Post a Comment