wcscis Absent Member.
Absent Member.
223 views

Re: how to assign mailNickname to group object?

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

In your rule that is setting mailNickname change it to set it after the current operation.
Exchange has to touch the object first before you can set it from the driver.
Then you will be all set 🙂
Labels (1)
0 Likes
4 Replies
Knowledge Partner
Knowledge Partner

Re: how to assign mailNickname to group object?

On 9/5/2012 12:42 PM, Will Schneider wrote:
> On 8/2/2012 9:16 PM, ayeungied wrote:
>>
>> all attributes can be processed but only skipped mailNickname , no error
>> prompt .
>>
>>

> In your rule that is setting mailNickname change it to set it after the
> current operation.
> Exchange has to touch the object first before you can set it from the
> driver.
> Then you will be all set 🙂


Is that it, or is it that the shim is stripping them out because it
knows you are making a powershell command to do this work and Exchange
would do it for you anyway?

What was the bug number for that, you reported ages ago and has been
fixed for a while?
0 Likes
wcscis Absent Member.
Absent Member.

Re: how to assign mailNickname to group object?

The bug was https://bugzilla.novell.com/show_bug.cgi?id=587753
mailNickname is an after issue though not related to that bug but that process is specific to groups.

On 9/5/2012 12:08 PM, Geoffrey Carman wrote:
> On 9/5/2012 12:42 PM, Will Schneider wrote:
>> On 8/2/2012 9:16 PM, ayeungied wrote:
>>>
>>> all attributes can be processed but only skipped mailNickname , no error
>>> prompt .
>>>
>>>

>> In your rule that is setting mailNickname change it to set it after the
>> current operation.
>> Exchange has to touch the object first before you can set it from the
>> driver.
>> Then you will be all set 🙂

>
> Is that it, or is it that the shim is stripping them out because it knows you are making a
> powershell command to do this work and Exchange would do it for you anyway?
>
> What was the bug number for that, you reported ages ago and has been fixed for a while?


0 Likes
Knowledge Partner
Knowledge Partner

Re: how to assign mailNickname to group object?

On 9/5/2012 1:56 PM, Will Schneider wrote:
> The bug was https://bugzilla.novell.com/show_bug.cgi?id=587753
> mailNickname is an after issue though not related to that bug but that
> process is specific to groups.


Could you explain that again? That did not quite make sense to me.


> On 9/5/2012 12:08 PM, Geoffrey Carman wrote:
>> On 9/5/2012 12:42 PM, Will Schneider wrote:
>>> On 8/2/2012 9:16 PM, ayeungied wrote:
>>>>
>>>> all attributes can be processed but only skipped mailNickname , no
>>>> error
>>>> prompt .
>>>>
>>>>
>>> In your rule that is setting mailNickname change it to set it after the
>>> current operation.
>>> Exchange has to touch the object first before you can set it from the
>>> driver.
>>> Then you will be all set 🙂

>>
>> Is that it, or is it that the shim is stripping them out because it
>> knows you are making a
>> powershell command to do this work and Exchange would do it for you
>> anyway?
>>
>> What was the bug number for that, you reported ages ago and has been
>> fixed for a while?

>


0 Likes
wcscis Absent Member.
Absent Member.

Re: how to assign mailNickname to group object?

On 9/5/2012 12:57 PM, Geoffrey Carman wrote:
> On 9/5/2012 1:56 PM, Will Schneider wrote:
>> The bug was https://bugzilla.novell.com/show_bug.cgi?id=587753
>> mailNickname is an after issue though not related to that bug but that
>> process is specific to groups.

>
> Could you explain that again? That did not quite make sense to me.
>

the shim was stripping the four attributes mentioned in that bug when you provisioned a group and
they are needed for groups but not users. The mailNickname is set as an after event because the
classes aren't on the object until Exchange does its magic.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.