Creates a new role and matching view group on the connected VMS. Permissions are
associated with roles, and roles can have any number of users and groups, or
"members".
REQUIREMENTS
Requires VMS connection and will attempt to connect automatically
Connect-Vms-AcceptEulaNew-VmsRole-Name"My new role"-AllowMobileClientLogOn-AllowSmartClientLogOn-AllowWebClientLogOn
Logs in to a management server, then creates a new role named "My new role" with
permission to logon to the mobile client, smart client, and web client. Note
that the role does not yet have any members, and it has not been assigned
permissions to any cameras.
Specifies which smart client profile to use with the new role. Use Get-VmsClientProfile
to retrieve smart client profile objects, or enter the client profile by name.
Specifies that the new role should be returned to the caller. Normal behavior
for a "New-*" cmdlet is to return the new item by default. However, when
creating a large number of roles, the added time to make an extra API call to
retrieve the new role, or to enumerate through the cached role collection to
find it may not be preferred.
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
When you create a new role with the New-VmsRole cmdlet, a new view group is created with the same name. This is a part
of the MIP SDK and the Management Server APIs, and matches the experience when creating roles in Management Client.
These automatically-created view groups are not required and can be deleted at any time using the Remove-VmsViewGroup
cmdlet. For example Get-VmsViewGroup -Name 'viewgroup name' | Remove-VmsViewGroup -Recurse.