Forum Discussion
Problems for adding users in DIstribution Dynamics groups with ExtensionCustomAttribute
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
Hi LainRobertson , Thanks for your answer !
I'm currently testing this point :
Line 12: If you ran this Set-Mailbox, you would be adding a single string with the value of "#conseiller, #resp_thema, #rive_droite, #urbain". If you wanted to add the four tags as separate values (which I expect is what you're trying to do), they should be typed out like this: "#conseiller", "#resp_thema", "#rive_droite", "#urbain"".;
It seems to be the problem, it worked well few month ago but if now we have to do it like that it's OK ! 😄
I'm working on it and give my final status on the result 🙂
Here is the get-exomailbox for my test member:
Nothing seems to block the conditions so I think the problem comes from the previously mentionned point.
I keep you in touch for that, and thanks again
Vaalgruund.
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 :
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
:
I keep digging !
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
- Hello,
This solution seems to works well ! The problem is fixed ! Thanks a lot Lain !
You save me lol !
Vaalgruund - 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