A Forum reader recently asked:
“I’m desperately looking for a working solution for creating Exchange mailboxes using IDM 3.01. So far I have been able to succesfully create a user in AD, make this user a member of the correct distributionlist/group, and synchronize his/her password with eDirectory. But the final step, creating an Exchange mailbox, is still not possible. I’ve searched this forum and sent a few emails, but to date, no success.
Perhaps my request is an unusual one, but there must be more people who are using Novell NetWare 6.5, Windows 2000 Advanced Server and Exchange 2000 Enterprise Edition. All I need is a working example of a policy or entitlement that creates an Exchange mailbox.”
In my example, I have created groups in eDirectory that represent homeMDBs. I have set group attributes equal to the Exchange server name and homeMDB name. I then query for them, depending on the country where the user is. If you’re only dealing with one country, your job will be easier – just plug in the names.
Here is a sample homeMDB name:
cn=Mailbox Store (US01LABEXCH),cn=First Storage Group,cn=InformationStore,cn=US01LABEXCH,cn=Servers,cn=US01 AdministrativeGroups,cn=Administrative Groups,cn=companyname,cn=Microsoft Exchange,cn=Services, cn=Configuration, dc=domain,dc=com
You have to get the homeMDB and exchange server name exactly right, and that isn’t easy:
<add-attr attr-name="mDBUseDefaults"> <value type="string"> <xsl:value-of select="'TRUE'"/> </value> </add-attr> <add-attr attr-name="mailNickname"> <value type="string"> <xsl:value-of select="$user-cn-param"/> </value> </add-attr> <add-attr attr-name="msExchHomeServerName"> <value> <xsl:value-ofselect="$grpquery-param//instance[$homeMDB-sequence-param]/attr[@attr-name='L']/value/text()"/> </value> </add-attr> <add-attr attr-name="homeMDB"> <value> <xsl:value-ofselect="$grpquery-param//instance[$homeMDB-sequence-param]/attr[@attr-name='Description']/value/text()"/> </value> </add-attr>-- ptown
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.