how to assign mailNickname to group object?

[geoffc]

On 8/2/2012 10:16 PM, ayeungied wrote:
>
> all attributes can be processed but only skipped mailNickname , no error
> prompt .

There was an issue that when using Exchange provisioing Exchange was
expected to set a number of attributes, and skipped those if in the
event document, to leave for Exchange to set. I am pretty sure
mailNickName was one of them.

[Alex McHugh]

On 03.08.2012 13:21, Geoffrey Carman wrote:
> On 8/2/2012 10:16 PM, ayeungied wrote:
>>
>> all attributes can be processed but only skipped mailNickname , no error
>> prompt .
>
> There was an issue that when using Exchange provisioing Exchange was
> expected to set a number of attributes, and skipped those if in the
> event document, to leave for Exchange to set. I am pretty sure
> mailNickName was one of them.

Depending on which option is selected for the exch-api-type, the driver
shim may try to interpret changes to mailNickname and homeMDB attributes
as triggers to run powershell cmdlets related to mailbox management.
This should only apply for objects of user class.

What patch level is the AD driver shim at? Is the remote loader running
stock 4.0.1a RL & driver shim? There were several bug fixes prior to IDM
4.0 that addressed issues with exchange/mail attributes that were
incorrectly silently ignored by the AD driver shim.

Just a note. With Exchange 2007, Microsoft no longer recommends that
yous et these attributes directly (this should be done via
PowerShell/Exchange cmdlets).

Your best solution would be to upgrade to IDM 4.0.2 and use the new
support for running (some) powershell cmdlets via policy. This ensures
the solution is supported by Microsoft.

You can probably make it work the way you are trying to (seting
attributes directly) but it's going to be a lot more work / troubleshooting.