Synchronize two data sources

avatar

Hey guys,

we have a data source in a on premise database and wanna migrate to aws. I've already copied the database/roles etc to an ec2 instance with mssql running. Is there the possibility to synchronise data source 1 and data source 2 (only the windows/putty/scp entries) continously till we can shut down the old server and switch to the new one?

Regards

All Comments (9)

avatar

Hello,

What version of RDM are you currently using?


Best regards,

Mark Beausejour

avatar

Hello again,

I forgot to add that we have a data migration process that can help;
https://help.remotedesktopmanager.com/tipsandtricks_data_migration.htm

Do you feel that this is sufficient for your needs or do you prefer something like a synchronizer as you mentioned?


Best regards,

Mark Beausejour

avatar

Hey Mark,

that's alright and sufficent for me. Nevertheless, due the DB export/import to another data source, the matching between user and roles got lost. Do you know how to fix this without manual action for 100 users? ;)
Regards

avatar

Hello,

Please consult the following post on our forum. If you are familiar with PowerShell, you will find a PowerShell script to help you for the migration of you data source and this include users and roles.

https://forum.devolutions.net/topic27670-remote-desktop-manager-powershell-functions.aspx


Best regards,

Érica Poirier

avatar













Hey Erica,

I'm using your powershell functions. While importing users, I get the error:

System.Data.SqlClient.SqlException (0x80131904): Cannot find the login 'xxxDomain\xxxUser', because it does not exist or you do not have permission.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.ExecuteNonQuery(String sql, IDbConnection dbConnection, IDbDataParameter[] parameters, Int32 commandTimeout)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerSecuritySubDataSource.ce57bff8d1ddc8948a77dee461f378db8(UserEntity cf98b881282579a38f0d3820b4755fa4a)
ClientConnectionId:b65fb625-abd8-4b3d-9e1f-c6d7f25df9c3
Error Number:15151,State:1,Class:16



My user is sysadmin on the MSSQL machine and authorized via AD. The users from the export list are not created within the DB. Is there a way to resolve this issue?


Best regards

avatar

Hello Martin,

The import user function will show you the user in the User Management list in RDM. But this will not create the user in the database.

Is the user already exist in the database?

Best regards,

David Grandolfo

avatar

Hey David,

no, the user isn't existing in the database. Do I have to create every user manually?

Regards, Martin

avatar

Hi,

To create a new user we integrate the comment New-RDMUser. Once the new user has been configure you could create it with Set-RDMUser command.

I hope these link could help you.

Best regards,

David Grandolfo

avatar

Hello,

The error you're getting is because you are trying to connect to the database with a domain account. I don't have much context (such as which function you try to use) but from what I see, a connection to the database using Integrated Security is supposed to be used, but it tries to use SQL-S username/password.
Your options here are to either set a SQL-S username/password account, or make sure your powershell window (or RDM) is using the right domain credentials.
As you probably know, using Integrated Security doesn't actually send a username/password to the server, but rather an Authentication Token. thus preventing connecting with the domain credentials in a Connection String.

I hope this helps,
Do not hesitate to get back to us for more information.

Regards,

Alex Belisle