powershell issue with Add-VBORbacRole

[matteu]

Hello,

I try to add RBAC permission to restore portal and I find 2 issues :

1) Documentation is not up to date : https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=60
Example use :

Code: Select all

$Group = Get-VBOOrganizationGroup -Organization $org -Name "HelpDeskAgents"

Powershell says : WARNING : Obsolete parameter: Name. To filter groups by the display name, use the ‘DisplayName’ parameter. To filter groups by the group name, use the ‘GroupName’ parameter.

Code: Select all

$Group = Get-VBOOrganizationGroup -Organization $org -Name "HelpDeskAgents"
needs to be replace to 
$Group = Get-VBOOrganizationGroup -Organization $org -DisplayName "HelpDeskAgents"

2) I use this :

Code: Select all

$org = Get-VBOOrganization -Name "myOrganizationName"
$Group = Get-VBOOrganizationGroup -Organization $org -Name "HelpDeskAgents"
$restoreoperator = New-VBORbacOperator -Group $Group
Add-VBORbacRole -Organization $org -Name "ABC Restore Operators" -Operators $restoreoperator -EntireOrganization

It's working in Veeam but powershell display an error message.

Code: Select all

Add-VBORbacRole : Specified cast is not valid.
Raw:4 : 1
+ Add-VBORbacRole -Organization $org -Name "ABC Restore Operators" -Ope ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Add-VBORbacRole], FaultException
    + FullyQualifiedErrorId : System.ServiceModel.FaultException,Veeam.Archiver.PowerShell.Cmdlets.Rbac.AddVBORbacRole

How to avoid this error ?

[Mildur]

Hi Matteu

Documentation is not up to date

Thanks for reporting an issue with the Guide.
If you want to report it to the right team, then mark the wrong text in the guide and use CTRL+Enter or use the feedback button at the buttom of the page. With both methods, you can send an e-mail with the feedback directly to Veeam Documentation Feedback Team.

It's working in Veeam but PowerShell display an error message.

Can you please open a support case for that issue? That would help us to determine what's wrong.

[nielsengelen]

1. Name is indeed obsolete as listed in the user guide. It's there for legacy purposes but using DisplayName is correct.

2. It looks like this is related to $org being wrong, can you test if you get an output of all your variables? Like Write-Output $org etc?

[matteu]

1) Yes, It's written in the documentation your're right, but I think it's better to avoid using obsolete parameter in exemple. It's just for this to be updated.

2) It's a good idea. I test each variable with $variableName and I can see the object.
When I do write-host $variableName on my group it's empty because groupName is empty. I tried to create new group but the issue is still the same for the powerhell error message and groupname is not empty on this one.
I open a call.

[Mike Resseler]

@matteu Please let us know the support case ID here. Thanks

[matteu]

Hello,

Case #05387135

[matteu]

Just to keep people informed, it's confirmed it's a bug and after a fix support give me it's working fine.

[Mike Resseler]

Matteu, thanks for letting us know. We will get that fix in a CP as soon as we can for everyone