This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Issues setting attributes via PowerSHell

Hi all,

we are about to roll-out self-service for group management.

For that reason, I need to bulk-set primary and secondary owners.

While trying to get started I am experiencing issues in settings neccessary attributes.

I can set ManagedBy flag and that's all.

Trying to set "edsamanagercanupdatemembershiplist" or "edsvaSecondaryOwners" or "edsvaSecondaryOwnersCanUpdateMembershipList" the command seems to execute but a get still reveals unset or wrong attributes:

Set-QADGroup -Proxy <groupname> -ObjectAttributes @{edsaManagerCanUpdateMembershipList = $True }

When then querying it still remains as "False":

Get-QADGroup -Proxy jimprimary -DontUseDefaultIncludedProperties -IncludeAllProperties | select managedBy,edsaManagerCanUpdateMembershipList,edsvaSecondaryOwners,edsvaSecondaryOwnersCanUpdateMembershipList

ManagedBy edsamanagercanupdatemembershiplist edsvaSecondaryOwners edsvaSecondaryOwnersCanUpdateMembershipList
--------- ---------------------------------- -------------------- -------------------------------------------
                                       False                                                                 

Any hint what I'm doing wrong?

Thanks,


Ben

Parents
  • "Include all properties" switch doesn't actually include all properties.  I find that you often need to call out your VAs explicitly in an include.

    As far as setting the VAs goes, have you re-started your AR admin service lately?  I find that every so often, VAs refuse to be set and a service re-start makes the problem go away.

    There is also a bug around setting secondary owners.  You cannot edit the list - you have to reset it in full each time.  It's a defect with the Set-QADGroup cmdlet that I noticed somewhere around v 7.2 but may have been present earlier.

Reply
  • "Include all properties" switch doesn't actually include all properties.  I find that you often need to call out your VAs explicitly in an include.

    As far as setting the VAs goes, have you re-started your AR admin service lately?  I find that every so often, VAs refuse to be set and a service re-start makes the problem go away.

    There is also a bug around setting secondary owners.  You cannot edit the list - you have to reset it in full each time.  It's a defect with the Set-QADGroup cmdlet that I noticed somewhere around v 7.2 but may have been present earlier.

Children
  • No restart and I have some sort of movement, however, not all changes seem to come through.

    When it comes to secondary owners: If i have multiple lines, all setting a secondary owner the list *seems* to add up, no reset.

    Can you detail?