Forum Discussion

Vaalgruund's avatar
Vaalgruund
Copper Contributor
Jul 04, 2022
Solved

Problems for adding users in DIstribution Dynamics groups with ExtensionCustomAttribute

Hello everyone, I recently encouter problems for adding users in DDG with the use of extensionCustomAttribute1 In my company, we have DDG who use "tags" and theses tags are placed in the Extens...
exchange
office 365
  • LainRobertson's avatar
    LainRobertson
    Jul 13, 2022

    Vaalgruund 

     

    The problem with the example commands is that we don't have any data to compare them against.

     

    If you go back to the Get-ExoMailbox commandlet you used to fetch this data:

     

     

    With this screenshot, we can't tell if you've provided a single value or multiple values (i.e. via using an array with Set-Mailbox.).

     

    Then try running the following command (using your mailbox, of course.) If the values all come out on one line then you haven't run Set-Mailbox properly - as shown in the first example (in red) from the screenshot below.

     

    (Get-ExoMailbox -Identity test.mailbox -Properties ExtensionCustomAttribute1).ExtensionCustomAttribute1;

     

     

    If you have run Set-Mailbox properly, then you should find all of the values exist on their own separate line - as per the second example (in green.)

     

    This is what I spoke about in my previous post. But if you are seeing the values on separate lines, then something else is amiss.

     

     

    Cheers,

    Lain

Vaalgruund's avatar
Vaalgruund
Copper Contributor
Jul 13, 2022

Hello,

 

After few tests the problem is still the same but I have seen that the rule only check the first condition without taking account of the -or but take in account the -and

At least I have a little progress, the first tag is recognized by the rule !

 

For information, there is my rule :

 

 

Spoiler
((((ExtensionCustomAttribute1 -eq '#conseiller') -or (((ExtensionCustomAttribute1 -eq '#garantie_jeunes') -and (CustomAttribute15 -eq '29BRE'))))) -and (-not(Name -like 'SystemMailbox{*')) -and (-not(Name -like 'CAS_{*')) -and (-not(RecipientTypeDetailsValue -eq 'MailboxPlan')) -and (-not(RecipientTypeDetailsValue -eq 'DiscoveryMailbox')) -and (-not(RecipientTypeDetailsValue -eq 'PublicFolderMailbox')) -and (-not(RecipientTypeDetailsValue -eq 'ArbitrationMailbox')) -and (-not(RecipientTypeDetailsValue -eq 'AuditLogMailbox')) -and (-not(RecipientTypeDetailsValue -eq 'AuxAuditLogMailbox')) -and (-not(RecipientTypeDetailsValue -eq 'SupervisoryReviewPolicyMailbox')))

For information (bis), when I've created the rule, this was theses conditions, MS add the conditions above automatically, it doesn't help for the tests :lol: :

Spoiler
(ExtensionCustomAttribute1 -eq '#conseiller') -or (ExtensionCustomAttribute1 -eq '#garantie_jeunes') -and (CustomAttribute15 -eq '29BRE')
The thing that is incomprehensible is that it work well for the majority of the users, just some of them don't integrate properly on the DDG :sad:


I keep digging !

Vaalgruund






 

LainRobertson's avatar
LainRobertson
Silver Contributor
Jul 13, 2022

Vaalgruund 

 

The problem with the example commands is that we don't have any data to compare them against.

 

If you go back to the Get-ExoMailbox commandlet you used to fetch this data:

 

 

With this screenshot, we can't tell if you've provided a single value or multiple values (i.e. via using an array with Set-Mailbox.).

 

Then try running the following command (using your mailbox, of course.) If the values all come out on one line then you haven't run Set-Mailbox properly - as shown in the first example (in red) from the screenshot below.

 

(Get-ExoMailbox -Identity test.mailbox -Properties ExtensionCustomAttribute1).ExtensionCustomAttribute1;

 

 

If you have run Set-Mailbox properly, then you should find all of the values exist on their own separate line - as per the second example (in green.)

 

This is what I spoke about in my previous post. But if you are seeing the values on separate lines, then something else is amiss.

 

 

Cheers,

Lain

  • Vaalgruund's avatar
    Vaalgruund
    Copper Contributor
    Jul 29, 2022
    Hello,

    This solution seems to works well ! The problem is fixed ! Thanks a lot Lain !
    You save me lol !

    Vaalgruund
  • Vaalgruund's avatar
    Vaalgruund
    Copper Contributor
    Jul 13, 2022
    Hello Lain,

    Sorry I I understood that I only had to change the tags by "#value1", "#value2" etc.

    I've tried your PS and now the result is in the format
    Value1
    Value2
    Value3
    and the user is on all DDG !

    I just have to check with all users impacted but I guess that you just found the problem !
    I'll check every profiles and confirm that is totaly OK with theses commands (mines are surely been interpretated like a string as you said.

    Thanks Again and I try to validate this solution ASAP 😉
    Vaalgruund

Resources