28-09-2017, 05:38 PM
I am using ASG-RemoteDesktop 2017 (10.1.5713.0). I have two Active Directory accounts "smith" (my everyday account) and "admsmith" (has admin rights on servers). In ASG-RD, I setup my admsmith credentials. On the connections folder I set to use the admsmith credentials.
This has been working perfectly for over a year. This week, I moved our ASG database from SQL 2012 to SQL 2016. Now my admsmith account keeps getting locked out in Active Directory.
I have tried:
- Unlocking
- deleting the admsmith credentials and readding
- Rebooting my PC
- Changing my password and unlocking; changing the password in my ASG credentials (works - I can connect)
This is what I have learned -- if my admsmith credentials are created in ASG and ASG is open, I get locked out.
As another test I deleted my admsmith credentials from ASG, created myself an admsmith2 login with same domain rights, added admsmith2 to ASG, and used admsmith2 = no lockouts! Just for kicks I added my admsmith credentials back into ASG and that account got locked out again! Bizarre!
Any suggestions? Or any ideas what is causing this?
Thank you.
This has been working perfectly for over a year. This week, I moved our ASG database from SQL 2012 to SQL 2016. Now my admsmith account keeps getting locked out in Active Directory.
I have tried:
- Unlocking
- deleting the admsmith credentials and readding
- Rebooting my PC
- Changing my password and unlocking; changing the password in my ASG credentials (works - I can connect)
This is what I have learned -- if my admsmith credentials are created in ASG and ASG is open, I get locked out.
As another test I deleted my admsmith credentials from ASG, created myself an admsmith2 login with same domain rights, added admsmith2 to ASG, and used admsmith2 = no lockouts! Just for kicks I added my admsmith credentials back into ASG and that account got locked out again! Bizarre!
Any suggestions? Or any ideas what is causing this?
Thank you.