Leak in AcctCrt component
Hi, I have written an application in C++ for NT user association with Exchange mailboxes. This application makes use of functions provided by the AcctCrt component available with Exchange SDK. However, I find a leak in the 'GenerateSecDescriptor' interface of this AcctCrt component. Can anyone help me with this? Is this a known leak or it has got to do something with my usage of the interface? Thanks, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: NT user Exchange mailbox association
I am working on a synchronization tool that will synchronize recipient entries between Exchange and any other directory server. Now, consider the case, where my tool needs to add a new mailbox into Exchange, then it also need to associate an NT user on the machine where Exchange is installed with the Exchange mailbox. Take the following scenario: a. Domain A b. Machine B (domain controller) where Exchange is installed c. Machine C (in domain A) where my tool is installed. Is it possible for me sitting on machine C, to create users in Machine B ? I came across an AcctMgmt COM component in MSDN, which does the same, but was not able to achieve the desired result. Thanks and regards, -Rajalakshmi Iyer -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 2:24 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association A brief description of the DSM in relation to Exchange: All objects in Exchange will have an ACL (Access Control List) as part of it's Security Descriptor the same as any other object in NT. The discretionary ACL (for it is he that we are talking about), will contain all users who have (or perhaps explicitly do not have access) to this object (the mailbox in this case) and what their rights are (each entry is contained in an ACE or Access Control Entry). When you log in to NT you get a token which, when you try and access any object (including logging on to a mailbox) is compared against it's ACL. If there is a match you get the designated access to that object. Kevin -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 10 January 2002 06:26 To: MS-Exchange Admin Issues Subject: NT user Exchange mailbox association Hi, What is the significance of associating an NT user with an Exchange 5.5 mailbox? Consider the following situation: a) Exchange Server 5.5 which needs to be on a domain controller machine b) I have an NT user on the same machine where Exchange is installed and it is associated with a mailbox. Now, what are steps in authenticating a mail client like Outlook (from a different machine) with the mail server like Exchange with the help of this NT user association? Thanks and regards, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: NT user Exchange mailbox association
Please find answers inline. -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 5:33 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association A few questions in-line: -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 10 January 2002 08:20 To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association I am working on a synchronization tool that will synchronize recipient entries between Exchange and any other directory server. Now, consider the case, where my tool needs to add a new mailbox into Exchange, then it also need to associate an NT user on the machine where Exchange is installed with the Exchange mailbox. Take the following scenario: a. Domain A b. Machine B (domain controller) where Exchange is installed. I assume this is the DC for Domain A? - Yes machine B is the domain controller for domain A c. Machine C (in domain A) where my tool is installed. Is this a DC also or a member server? - This is not a domain controller. It is a member server. Is it possible for me sitting on machine C, to create users in Machine B ? Create NT users or mailboxes?? Are you just asking whether you can run a program on Machine C which will be capable of associating NT accounts with mailboxes? The NT accounts will be created on the DC (not on a member server). Therefore, when you attempt to associate an NT account you will get the SID read from your DC. You can create mailboxes on any Exchange server, in any container to which you have access. - I want to create a new mailbox in Exchange. Correspondingly, I need to create an NT user who shall be associated with this mailbox by populating the assoc-nt-account and nt-security-descriptor attributes of the mailbox entry. So will my tool sitting on machine C be able to create an NT user in machine B ? Is some kind of trust relationship required to be established between Machine B and C, for C to be able to create user accounts in B. I came across an AcctMgmt COM component in MSDN, which does the same, but was not able to achieve the desired result. Thanks and regards, -Rajalakshmi Iyer -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 2:24 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association A brief description of the DSM in relation to Exchange: All objects in Exchange will have an ACL (Access Control List) as part of it's Security Descriptor the same as any other object in NT. The discretionary ACL (for it is he that we are talking about), will contain all users who have (or perhaps explicitly do not have access) to this object (the mailbox in this case) and what their rights are (each entry is contained in an ACE or Access Control Entry). When you log in to NT you get a token which, when you try and access any object (including logging on to a mailbox) is compared against it's ACL. If there is a match you get the designated access to that object. Kevin -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 10 January 2002 06:26 To: MS-Exchange Admin Issues Subject: NT user Exchange mailbox association Hi, What is the significance of associating an NT user with an Exchange 5.5 mailbox? Consider the following situation: a) Exchange Server 5.5 which needs to be on a domain controller machine b) I have an NT user on the same machine where Exchange is installed and it is associated with a mailbox. Now, what are steps in authenticating a mail client like Outlook (from a different machine) with the mail server like Exchange with the help of this NT user association? Thanks and regards, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: NT user Exchange mailbox association
I do understand that I have to create an NT account before I can populate the Assoc-NT-Account and NT-Security-Descriptor fields of the LDAP entry. With reference to the discussion below: When my application is installed on machine B (domain controller, where Exchange is installed), new NT users are created and associations established properly. When my application is installed on machine C (the member server), I am not able to access machine B's User information. My application makes use of the AcctMgmt CoClass provided by Microsoft. This CoClass exposes interfaces like NTAccountCreate, NTAccountDelete, GetSidFromName etc. We chose to use this component instead of the normal Win32 APIs to retrieve the SID and Security Information, because we couldnt obtain the binary format of Security Descriptor attribute that needs to be populated for NT-Security-Descriptor of LDAP mailbox entry. -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 6:52 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association I'm still not sure I understand what you're asking.You seem to indicate that you think an NT account is created when you create a mailbox. Simply populating the Assoc-Nt-Account DOES NOT create an NT account. You have to create the NT account first then associate it with the mailbox. Your application will access a DC to get a list of NT accounts which you can then associate with a mailbox. It doesn't really matter where the application runs. As long as you're logged into the domain you can access the DC's list of NT users. Kevin -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 10 January 2002 12:14 To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association Please find answers inline. -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 5:33 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association A few questions in-line: -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 10 January 2002 08:20 To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association I am working on a synchronization tool that will synchronize recipient entries between Exchange and any other directory server. Now, consider the case, where my tool needs to add a new mailbox into Exchange, then it also need to associate an NT user on the machine where Exchange is installed with the Exchange mailbox. Take the following scenario: a. Domain A b. Machine B (domain controller) where Exchange is installed. I assume this is the DC for Domain A? - Yes machine B is the domain controller for domain A c. Machine C (in domain A) where my tool is installed. Is this a DC also or a member server? - This is not a domain controller. It is a member server. Is it possible for me sitting on machine C, to create users in Machine B ? Create NT users or mailboxes?? Are you just asking whether you can run a program on Machine C which will be capable of associating NT accounts with mailboxes? The NT accounts will be created on the DC (not on a member server). Therefore, when you attempt to associate an NT account you will get the SID read from your DC. You can create mailboxes on any Exchange server, in any container to which you have access. - I want to create a new mailbox in Exchange. Correspondingly, I need to create an NT user who shall be associated with this mailbox by populating the assoc-nt-account and nt-security-descriptor attributes of the mailbox entry. So will my tool sitting on machine C be able to create an NT user in machine B ? Is some kind of trust relationship required to be established between Machine B and C, for C to be able to create user accounts in B. I came across an AcctMgmt COM component in MSDN, which does the same, but was not able to achieve the desired result. Thanks and regards, -Rajalakshmi Iyer -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 2:24 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association A brief description of the DSM in relation to Exchange: All objects in Exchange will have an ACL (Access Control List) as part of it's Security Descriptor the same as any other object in NT. The discretionary ACL (for it is he that we are talking about), will contain all users who have (or perhaps explicitly do not have access) to this object (the mailbox in this case) and what their rights are (each entry is contained in an ACE or Access Control Entry). When you log in to NT you get a token which, when you try and access any object (including logging on to a mailbox) is compared against it's ACL. If there is a match you get the designated access to that object. Kevin -Original Message- From: Rajalakshmi Iyer
RE: Exchange 5.5 on Windows 2000
I have Windows 2000 Advanced Server installed. I also have Active Directory on my machine. Now I need to install Exchange 5.5. Are there any issues in this scenario? -Original Message- From: Jim Holmgren [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 6:10 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on Windows 2000 I run Exchange 5.5 on Win2k servers here with no problems at all, in fact I believe it runs better on Win2K than it did on NT. We are still an NT domain, haven't finished our AD migration - but your post doesn't specify whether you are NT or AD. So - if you are an NT domain - no real issues, just make sure you apply all the appropriate Service Packs and security hot fixes. -Jim Jim Holmgren MCSE, CCNA [EMAIL PROTECTED] Network Engineer Advertising.com We bring innovation to interactive communication. Advertising.com -- Superior Technology. Superior Performance. -Original Message- From: Anthony Getor [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 3:45 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on Windows 2000 I am also very interested in this. Particularly about DNS/AD issues. Do you still need to deploy AD? I have browsed MS's sites, but the info I got was either scanty or not very clear. This is about a small office of not more than 30 users. Thanks, Tony G. -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 5:19 AM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on Windows 2000 Hi, What are the issues with having an Exchange 5.5 server on Windows 2000 machine? Thanks and regards, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm *** The information transmitted in this email is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this email in error, please contact the sender and permanently delete the email from any computer. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: NT user Exchange mailbox association
I would like to have a look at them. Which language are they written in? Do they make use of the same AcctMgmt component? -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 9:13 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association I have some routines that will do this, if you need them. You said in a previous message I came across an AcctMgmt COM component in MSDN, which does the same, but was not able to achieve the desired result -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 10 January 2002 12:53 To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association I do understand that I have to create an NT account before I can populate the Assoc-NT-Account and NT-Security-Descriptor fields of the LDAP entry. With reference to the discussion below: When my application is installed on machine B (domain controller, where Exchange is installed), new NT users are created and associations established properly. When my application is installed on machine C (the member server), I am not able to access machine B's User information. My application makes use of the AcctMgmt CoClass provided by Microsoft. This CoClass exposes interfaces like NTAccountCreate, NTAccountDelete, GetSidFromName etc. We chose to use this component instead of the normal Win32 APIs to retrieve the SID and Security Information, because we couldnt obtain the binary format of Security Descriptor attribute that needs to be populated for NT-Security-Descriptor of LDAP mailbox entry. -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 6:52 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association I'm still not sure I understand what you're asking.You seem to indicate that you think an NT account is created when you create a mailbox. Simply populating the Assoc-Nt-Account DOES NOT create an NT account. You have to create the NT account first then associate it with the mailbox. Your application will access a DC to get a list of NT accounts which you can then associate with a mailbox. It doesn't really matter where the application runs. As long as you're logged into the domain you can access the DC's list of NT users. Kevin -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 10 January 2002 12:14 To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association Please find answers inline. -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 5:33 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association A few questions in-line: -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 10 January 2002 08:20 To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association I am working on a synchronization tool that will synchronize recipient entries between Exchange and any other directory server. Now, consider the case, where my tool needs to add a new mailbox into Exchange, then it also need to associate an NT user on the machine where Exchange is installed with the Exchange mailbox. Take the following scenario: a. Domain A b. Machine B (domain controller) where Exchange is installed. I assume this is the DC for Domain A? - Yes machine B is the domain controller for domain A c. Machine C (in domain A) where my tool is installed. Is this a DC also or a member server? - This is not a domain controller. It is a member server. Is it possible for me sitting on machine C, to create users in Machine B ? Create NT users or mailboxes?? Are you just asking whether you can run a program on Machine C which will be capable of associating NT accounts with mailboxes? The NT accounts will be created on the DC (not on a member server). Therefore, when you attempt to associate an NT account you will get the SID read from your DC. You can create mailboxes on any Exchange server, in any container to which you have access. - I want to create a new mailbox in Exchange. Correspondingly, I need to create an NT user who shall be associated with this mailbox by populating the assoc-nt-account and nt-security-descriptor attributes of the mailbox entry. So will my tool sitting on machine C be able to create an NT user in machine B ? Is some kind of trust relationship required to be established between Machine B and C, for C to be able to create user accounts in B. I came across an AcctMgmt COM component in MSDN, which does the same, but was not able to achieve the desired result. Thanks and regards, -Rajalakshmi Iyer -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 2:24 PM To: MS-Exchange Admin Issues Subject: RE: NT user Exchange mailbox association A brief
Exchange 5.5 Directory hierarchy
Hi, For a huge organization, how are the recipient containers nodes in an Exchange directory organized? From an Exchange Administrator point of view, what should be the criteria for distributing recipient entries amongst various container nodes. Also, how about container nodes within container nodes. What should be the depth of the tree? e.g. could I have: o=company |_ou=Site1,o=company |_cn=Container1,ou=Site1,o=company |_cn=Container2,cn=Container1,ou=Site1,o=company |_ cn=Container3,.. and so on.. These questions are aimed at understanding the general Exchange directory hierarchy as created by the Administrator, as I am into developing of a tool over Exchange that uses LDAP for access. Thanks and regards, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Adding mailboxes to Exchange thru LDAP
Hi, I want to know if addition of a new mailbox in Exchange 5.5 directory through LDAP automatically creates the placeholder for the corresponding information store space for storing the mailbox contents or is there some explicit call that needs to be made. This doubt arose because, I read somewhere that when you delete a mailbox entry in Exchange directory using LDAP, only the mailbox entry gets deleted, the corresponding information store contents remain as they are. Is there a similar limitation on addition through LDAP? Thanks, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Adding mailboxes to Exchange thru LDAP
Thanks a lot Kevin, for the instant replies. -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 6:21 PM To: MS-Exchange Admin Issues Subject: RE: Adding mailboxes to Exchange thru LDAP I believe the LDAP create will effectively make a mailbox in the IS which will contain Default folders. When Outlook logs in for the first time it creates the other folders. With a delete, the Directory entry is not deleted. It is merely marked for deletion and when something called the Tombstone timer expires the Directory entry is deleted. The System Attendant will mop these entries up. Kevin -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 09 January 2002 11:19 To: MS-Exchange Admin Issues Subject: Adding mailboxes to Exchange thru LDAP Hi, I want to know if addition of a new mailbox in Exchange 5.5 directory through LDAP automatically creates the placeholder for the corresponding information store space for storing the mailbox contents or is there some explicit call that needs to be made. This doubt arose because, I read somewhere that when you delete a mailbox entry in Exchange directory using LDAP, only the mailbox entry gets deleted, the corresponding information store contents remain as they are. Is there a similar limitation on addition through LDAP? Thanks, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Adding mailboxes to Exchange thru LDAP
Hi, You could add an entry by populating the LDAP attributes of the mailbox. For e.g. the LDAP entry could be of the form dn: cn=JoeT,cn=recipients,ou=Site,o=org cn: Joe sn: Triviani mailpreferenceoption: 0 objectclass: organizationalperson,person,top rfc822Mailbox: [EMAIL PROTECTED] In order to associate this mailbox entry with an NT user account, you need to populate the Assoc-NT-Account and NT-security-descriptor attributes which contains the SID and security descriptor of the NT user in binary format. You could use any LDAP client like 'ldp' etc to try this. For more information on the directory attribute names for the mailbox attributes, you have to refer to MSDN. Hope this helps. Regards, Rajalakshmi Iyer -Original Message- From: Rodney Li [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 8:30 PM To: MS-Exchange Admin Issues Subject: RE: Adding mailboxes to Exchange thru LDAP Can you share how you create a mailbox using LDAP? Or can you point me to a web site where there is help on using ldap with exchange objects? Thanks, Rodney Li Thanks a lot Kevin, for the instant replies. -Original Message- From: Snook, Kevin S (ITD) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 6:21 PM To: MS-Exchange Admin Issues Subject: RE: Adding mailboxes to Exchange thru LDAP I believe the LDAP create will effectively make a mailbox in the IS which will contain Default folders. When Outlook logs in for the first time it creates the other folders. With a delete, the Directory entry is not deleted. It is merely marked for deletion and when something called the Tombstone timer expires the Directory entry is deleted. The System Attendant will mop these entries up. Kevin -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: 09 January 2002 11:19 To: MS-Exchange Admin Issues Subject: Adding mailboxes to Exchange thru LDAP Hi, I want to know if addition of a new mailbox in Exchange 5.5 directory through LDAP automatically creates the placeholder for the corresponding information store space for storing the mailbox contents or is there some explicit call that needs to be made. This doubt arose because, I read somewhere that when you delete a mailbox entry in Exchange directory using LDAP, only the mailbox entry gets deleted, the corresponding information store contents remain as they are. Is there a similar limitation on addition through LDAP? Thanks, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Exchange 5.5 on Windows 2000
Hi, What are the issues with having an Exchange 5.5 server on Windows 2000 machine? Thanks and regards, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: GAL duplicates
Yes, that was what I wanted. Actually, I am into development of Exchange connector. So, I would like to know from an Exchange administrator point of view, whether, u explicitly take care not to have duplicates in GAL, like u gave the example of John (CEO) and John (mailroom). Because, if I start to synchronize between Exchange GAL and some other messaging system, I would then have no idea of how to handle duplicates. Thanks for the opinion. -Rajalakshmi Iyer -Original Message- From: Sargent, Rob [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 02, 2002 6:53 PM To: MS-Exchange Admin Issues Subject: RE: GAL duplicates The GAL uses the Display field to list names. Having identical Display Names for different mailboxes would eventually result in e-mails being sent to the wrong person. I know it gets messy here when confidential info gets into the wrong hands. Is this what you're asking? In terms of the database, there are no issues. To distinguish between people with identical names, like having 2 people named John Smith in the company, we add a descriptor in brackets following their name in their mailbox's Display field. i.e. it would look like: Smith, John (CEO) Smith, John (mailroom) Rob Sargent -Original Message- From: Rajalakshmi Iyer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 01, 2002 4:56 AM To: MS-Exchange Admin Issues Subject: GAL duplicates Hi, I would like to know what are the problems associated with having duplicate GAL entries? Thanks, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
GAL duplicates
Hi, I would like to know what are the problems associated with having duplicate GAL entries? Thanks, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
LDAP delete on Exchange 5.5 directory
Hi, Does an LDAP delete operation on one of the recipient entries in Exchange Directory Store only delete the directory data and not the corresponding information store resources? If so, then what is the best method to delete a mailbox entry in Exchange 5.5 directory server? Also, when I add a mailbox entry from an LDAP client and not through the Exchange Administration console, then do information store resources get allocated for the same? Thanks in advance, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Exchange 5.5 Directory Access
Hi, I need to access Exchange 5.5 Directory Store information including GAL and Address Book Views etc. There seem to be many possible ways of doing so. You could write applications using MAPI, DAPI, Exchange Development Kit(EDK) or LDAP. Could someone point out the tradeoffs amongst these methods? For one, I came to know that DAPI connect requires around 10 seconds. Also, the Address Book Views, seem to violate the LDAP hierarchy structure, when viewed from an LDAP client. For e.g. the following tree structure could be seen: ou=_ABViews_,o=company |_cn=GroupByCity,ou=_ABViews_,o=company |_cn=NJ,cn=GroupByCity,ou=_ABViews_,o=company |_cn=Raj,cn=recipients,ou=site,o=company Are there any such limitations, when trying to access the directory data using any of the above methods? Thanks in advance, Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: LDAP access to Exchange GAL
Thanks. I was trying to evaluate the limitations of using LDAP to access Exchange directory store information rather than using native Exchange Directory API (DAPI). Could anyone provide some information on the same? - Rajalakshmi Iyer List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
