Forum / Remote Desktop Manager - PowerShell Repository

Changes to attribute names

  • Create an Issue
  • Cancel

After a recent update my object creation scripts stopped working.
It appears changes have been made to attribute names.
.Kind (Which I always thought should have been .Type anyway) has changed to .ConnectionType


Is that correct?
Have any other changes been made.
I didn't notice that in the changelog?

Clock4 yrs

Hello,

The change log had one line indicating a new Powershell Module. We do not have a compiled list of changes as the two you mention.

I will ask the engineer in charge.

Best regards,



Maurice Côté

signaturesignature

Clock4 yrs

Yes please and moving forward can you request that any changes made to the powershell module are detailed as we create clients, contacts, sites, vpn, groups, rdp, and other connections all with a script as its much quicker than editing multiple pages of templates.
It will take the guess work out of figuring out what has changed.

Thank you.

Clock4 yrs

Hello,

Here's what we received, we will update the online documentation shortly


PowerShell module changes:

Cmdlets:
- Add-RDMRoleToUser
- Parameters renamed RoleObject and UserObject in the case you pass a PSRoleInfo and PSUserInfo
- New Parameters RoleName and UserName in the case you pass the Role and User name as string

- Close-RDMSession
- No changes visible to the user

- Export-RDMSession
- The ExportType doesn’t exist anymore and is replaced by Switch Parameters for each type available (CSV, HTML, XML)

- Get-RDMCurrentDataSource
- No changes visible to the user

- Get-RDMDataSource
- New Name parameter, you can get a data source by only writing the name. If you have two or more data sources with the same same, it will return all the data sources with the name written in the parameter

- Get-RDMDatasourceProperty
- No Changes to the user

- Get-RDMRole
- New Name parameter, you can get a role object (PSRoleInfo) by only writing the name.

- Get-RDMSecurityGroup
- New Name parameter, you can get a security group object (PSSecurityGroup) by only writing the name.

- Get-RDMSession
- New CaseSensitive parameter
- New GroupName parameter
- New IncludeDocumentsStoredInDatabase parameter
- New IncludeLocalPlaylists parameter
- New IncludeSubFolders parameter
- New IncludeUserSpecificSettings parameter
- New Name parameter

- Get-RDMSessionDomain
- New Session parameter to get the domain of a session with a PSConnection

- Get-RDMSessionPassword
- New Session parameter to get the password of a session with a PSConnection

- Get-RDMSessionProperty
- No changes visible to the user

- Get-RDMSessionUserName
- New Session parameter to get the username of a session with a PSConnection

- Get-RDMTemplate
- New Type parameter to specifiy the type of template to return (Both, Local, Shared)

- Get-RDMUser
- New Name parameter, you can get a role object (PSRoleInfo) by only writing the name.

- Get-RDMUsername
- New Name parameter, you can get a role object (PSUserInfo) by only writing the name.

- Import-RDMSession
- Added ValidationSet on the DuplicateAction parameter (Add, Overwrite, Ignore)

- New-RDMDataSource
- Changed the parameter Type to switch parameters for each type available (Access, DODB, Dropbox, DVLS, FTP, MySQL, S3, SFTP, SQLite, Web, XML)
- New AccessKeyID, BucketName, KeyName, SecretAccessKey parameters that are available when creating a S3 data source
- New Filename parameter that is available when creating a XMLDataSource, FTPDataSource, AccessDataSource and STPDataSource
- New FTPPath parameter that is available when creating a FTP data source
- New FTPHost parameter that is available when creating a SFTP data source
- New DatabaseID parameter that is available when creating a DODB data source
- New Server parameter that is available when creating a DVLS or SQL Server data source
- New Hostname and Schema parameters that are available when creating a MySQL data source
- New URLFilename parameter when creating a Web data source
- New SetDatasource parameter to save the data source without having to use Set-RDMDatasource

- New-RDMLogComment
- No changes visible to the user

- New-RDMRole
- New SetRole parameter to save the role into the data source without having to use Set-RDMRole

- New-RDMSecurityGroup
- New SetSecurityGroup parameter to save the SecurityGroup into the data source without having to use Set-RDMSecurityGroup

- New-RDMSession
- Renamed the Kind parameter to Type
- New SetSession parameter to save the session into the data source without having to use Set-RDMSession

- New-RDMUser
- Changed CreateSQLServerLogin to SkipCreateSQLServerLogin which means that the SQL Server login is created by default when creating a new user. Available in SQL Server data source
- New Password parameter. User password. Available when using a SQL Server data source and integrated security is not used
- New AuthentificationType parameter to specify the user’s authentification type
- New SetUser parameter to save the user in the data source without having to use Set-RDMUser
- New LoginEmail parameter. Available when email logging is allowed in the data source
- New Disable parameter. Available when disabling an user in the data source is supported
- New Email parameter. Available when the data source is Devolutions Cloud
- Open-RDMQuickConnect
- No changes visible to the user

- Open-RDMSession
- New Silent parameter to hide potential errors message when opening a session (Useful on Sync sessions)
- New ForceExternal parameter to force a session open externally

- Read-RDMSession
- No changes visible to the user

- Remove-RDMDataSource
- No changes visible to the user

- Remove-RDMRole
- No changes visible to the user

- Remove-RDMRoleToUser
- No changes visible to the user

- Remove-RDMSecurityGroup
- No changes visible to the user

- Remove-RDMsession
- No changes visible to the user

- Remove-RDMUser
- New DeleteSQLLogin parameter to delete the SQL Login when deleting the user from the data source

- Set-RDMCurrentDataSource
- New username and password parameter to login into a data source to avoid window form. If you have a two factor set in the data source you will still have a window form.

- Set-RDMDataSource
- No changes visible to the user

- Set-RDMDatasourceProperty
- No changes visible to the user

- Set-RDMPersonalCredentials
- No changes visible to the user

- Set-RDMRole
- No changes visible to the user

- Set-RDMRoleProperty
- No changes visible to the user

- Set-RDMSecurityGroup
- No changes visible to the user

- Set-RDMSecurityGroupProperty
- No changes visible to the user

- Set-RDMSession
- No changes visible to the user

- Set-RDMSessionDomain
- New Session parameter to set the domain of a session with a PSConnection

- Set-RDMSessionPassword
- New Session parameter to set the password of a session with a PSConnection

- Set-RDMSessionProperty
- No changes visible to the user

- Set-RDMSessionUsername
- New Session parameter to set the username of a session with a PSConnection

- Set-RDMUser
- No changes visible to the user

- Set-RDMUserGroupRights
- The Add, Delete, Edit and View are now nullable boolean to be able to add and remove the right according to the parameter sent.

- Set-RDMUserProperty
- No changes visible to the user

- Set-RDMUserSecurity
- New SetUser parameter to save the user into the data source without having to use Set-RDMUser

- Update-RDMUI
- No changes visible to the user




















New CmdLets:
- Copy-RDMSession
- Get-RDMOpenedSession
- Get-RDMPlaylistLocal
- Get-RDMplaylistShared
- Get-RDMPrivateSession
- Get-RDMSessionCredentials
- Get-RDMSessionDocument
- New-RDMPlaylistLocal
- New-RDMPlaylistShared
- Rename-RDMGroup
- Set-RDMPlaylistLocal
- Set-RDMPlaylistShared
- Set-RDMRoleGroupRights
- Set-RDMSessionCredentials
- Set-RDMSessionDocument
- Set-RDMTemplate
- Set-RDMUserSpecificSettings
- Start-RDMInstance
- Stop-RDMInstance



Maurice Côté

signaturesignature

Clock4 yrs