$arse1 reporting for duty. Chris has everything right here, especially about how to think of accounts and mailboxes. There are dozens of fields that you can test for to determine whether or not an account is mailbox-enabled. One such field is "msExchHomeServerName".
The other item to note here is that most of the code routines used to mailbox-enable someone will simply fail if the account is already mailbox-enabled, so you really do not have to be too concerned with it. A good example is the Exchange Migration Wizard's ability to flip contacts into mailboxes. If you happen to run it against a pre-existing mailbox, it simply does nothing. So, no harm, no foul. Ronald, I strongly urge you to read up on accounts/contacts, mail-enabled accounts/contacts and mailbox-enabled accounts. You still seem to be speaking in E55 terminology and it is a whole new ball game in E2K and AD. BTW, what HR system are you interfacing with? More and more of them are starting to provide connectors with AD. > At the risk of a moron or two trying to indicate that I'm rude in my > response, can I point that there isn't really a difference between a user > account and a mailbox per se (or at least that's a backwards way to think > about it for your purposes), instead there is a user object and that object > can be mail or mailbox enabled. > > In your instance I believe that you will first want to determine if there is > a user account for the user in question. If there is, then you want to > determine if it is a mail enabled or a mailbox enabled object. If it is > neither, you likely want to mail enable it, rather than create a contact for > it. If a user object does not exist for a user, then you have to decide if > you want to create a user account for it (and optionally mail or mailbox > enable it) or create a contact for it. > > Further risking the ire of a moron or two, I'll start first with a fishing > lesson.. and point you to two articles which show how to create mailbox and > mail enabled users respectively and hint that they provide a good starting > point for further research on your query. > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_cd > o_creating_a_mailbox_enabled_recipient.asp > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_cd > o_creating_a_contact.asp > > As an additional pointer, you might also want to take a look at ADSI Edit > which can provide some additional useful information. If after looking over > that information you have additional queries, please feel free to post a > follow-up question or three. Or, just wait for $arse1 and $arse2 to post > much more complete and helpful answers than mine. > > > -----Original Message----- > > From: Bare, Ronald A. [mailto:RABARE@;ANL.GOV] > > Sent: Monday, November 04, 2002 3:43 PM > > To: Exchange Discussions > > > > Can anyone point me to information on what Active Directory attributes are > > used to indicate that an Exchange 2000 mailbox has been associate with an > > Active Directory account. > > > > We are trying to prepare a program to synchronize the Active Directory > > with > > our HR directory and we need this information to decide for which users to > > create contact entries. We (of course) do not want to create contacts for > > the people who already Exchange enabled accounts. > > > > Thank you. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:leave-exchange@;ls.swynk.com Exchange List admin: [EMAIL PROTECTED]
