29-05-2020, 10:01 PM
(This post was last modified: 29-05-2020, 10:04 PM by hmote.
Edit Reason: Added details.
)
We have ASG working great in one of our domains running ASG RD 2020 Patch 1 with SQL Server Express. I did the same install on a different domain but with Patch 2. By the way, I don't think the issue is between Patch 1 and Patch 2 but I'm pointing out the details.
I did an rde export with every box checked and password protected. I imported the rde into the other domain installation. After exiting and adding additional users in SSMS to the database as sysadmin, I can now no longer login to that environment. I was getting the message that user does not have permissions and then it would show the user and the identifier. No one can gain access..
I looked through the forums and the only thing I noticed that might help was the SQL command on https://remotedesktop.rocketsoftware.com...?tid=10858 as it's even referenced in multiple posts. I ran the SQL command and can gain access now but I can't seem to setup users or security groups now in the application.
Could you let me know what might have went wrong and how I can fix this issue? Could it be that the import cannot be from a different domain or differences in windows login usernames (username/admin vs. username)?
I did an rde export with every box checked and password protected. I imported the rde into the other domain installation. After exiting and adding additional users in SSMS to the database as sysadmin, I can now no longer login to that environment. I was getting the message that user does not have permissions and then it would show the user and the identifier. No one can gain access..
I looked through the forums and the only thing I noticed that might help was the SQL command on https://remotedesktop.rocketsoftware.com...?tid=10858 as it's even referenced in multiple posts. I ran the SQL command and can gain access now but I can't seem to setup users or security groups now in the application.
Could you let me know what might have went wrong and how I can fix this issue? Could it be that the import cannot be from a different domain or differences in windows login usernames (username/admin vs. username)?