Metaverse Object
 Before
we get into the management agents, we need to get a better understanding
of what we are doing with MIIS and how we plan to do it! We will be
importing Mailbox, DL and contact information from Exchange 5.5 and
placing that information in a SQL database. This Metaverse will contain
a global directory of names imported from Exchange 5.5 as well as names
imported from other Active Directory domains. We have defined how these
objects will look in the Metaverse by creating a generic MV object
called a Metaverse_Contact.
This object type was created from scratch and
contains specific fields needed for our immediate needs and some fields
we think will be needed later for additional functionality.
Here are the attributes you need to add as well as
the characteristics of the attribute:
Assistant String (indexable)
Not Multi-valued
c
String (indexable) Not Multi-valued
cn
String (indexable) Not Multi-valued
co String
(indexable) Not Multi-valued
company String (indexable)
Not Multi-valued
department String (indexable)
Not Multi-valued
displayName
String (indexable) Not Multi-valued
division String (indexable)
Not Multi-valued
employeeID
String (indexable) Not Multi-valued
EmployeeStatus
String (indexable) Not Multi-valued
employeeType
String (indexable) Not Multi-valued
facsimileTelephoneNumber String (indexable)
Not Multi-valued
givenName
String (indexable) Not Multi-valued
groupType
Number Not Multi-valued
hideDLMembership
Boolean Not Multi-valued
homeMTA
Reference (DN) Not Multi-valued
homePhone
String (indexable) Not Multi-valued
info String
(indexable) Not Multi-valued
initials String (indexable)
Not Multi-valued
l
String (indexable) Not Multi-valued
legacyExchangeDN
String (indexable) Multi-valued
Indexed
locality String (indexable)
Not Multi-valued Indexed
mail String
(indexable) Not Multi-valued Indexed
mailNickname
String (indexable) Not Multi-valued
manager Reference (DN)
Not Multi-valued
MapiRecipient
Boolean Not Multi-valued
mobile String
(indexable) Not Multi-valued
msExchAssistantName String
(indexable) Not Multi-valued
msExchExpansionServerName String (non-indexable) Not
Multi-valued
msExchHideFromAddressLists
Boolean Not Multi-valued
msExchHomeServerName String
(indexable) Not Multi-valued
msExchMasterAccountSid Binary (indexable)
Not Multi-valued
msExchOriginatingForest String (indexable)
Not Multi-valued
nTGroupMembers
Binary (indexable) Multi-valued
Indexed
o
String (indexable) Not Multi-valued
otherHomePhone String
(indexable) Multi-valued Indexed
otherTelephone
String (indexable) Multi-valued
Indexed
pager String (indexable)
Not Multi-valued
physicalDeliveryOfficeName String
(indexable) Not Multi-valued
postalCode String
(indexable) Not Multi-valued
proxyAddresses String
(indexable) Multi-valued Indexed
Rfc822Mailbox String (indexable)
Not Multi-valued
sn
String (indexable) Not Multi-valued
st
String (indexable) Not Multi-valued
streetaddress
String (indexable) Not Multi-valued
targetAddress
String (indexable) Not Multi-valued
Indexed
telephoneAssistant
String (indexable) Not Multi-valued
telephoneNumber
String (indexable) Not Multi-valued
textEncodedORAddress
String (indexable) Not Multi-valued
title String
(indexable) Not Multi-valued
uid
String (non-indexable) Not Multi-valued
It is possible to clean up these entries in order
to further trim down unnecessary attributes. In some instances, you may
want to create additional attributes for specific tasks for example. You
could create an attribute to denote whether an item should be written to
the target directory and perform a filter against that field. In
addition, you could create “work” fields to hold any type of data you
wish to key upon in code.
|
