Problem with registering servers
KatanaCS
Posts: 24 Bronze 2
Hi,
In our network, we do not have Active Directory access to all of our production servers (they're in a separate domain), so we use a SQL account to login. I just added a few servers to a distribution list, and by default Multi Script attempted to connect using Windows Authentication. Since it cannot authenticate, a Severity 20 Alert is fired from SQL Server, which is something we monitor. Any plans to modify this default behavior so we are immediately prompted for connection information instead of automatically attempting to connect with Windows Authentication?
Aside from this, this is an excellent product!
Thanks!
In our network, we do not have Active Directory access to all of our production servers (they're in a separate domain), so we use a SQL account to login. I just added a few servers to a distribution list, and by default Multi Script attempted to connect using Windows Authentication. Since it cannot authenticate, a Severity 20 Alert is fired from SQL Server, which is something we monitor. Any plans to modify this default behavior so we are immediately prompted for connection information instead of automatically attempting to connect with Windows Authentication?
Aside from this, this is an excellent product!
Thanks!
Chris
Comments
Thanks for your feedback.
There is a work around for you issue. Before you click the [+] icon to expand a SQL Server, select the server and click the "Authentication..." button. You can then set up your SQL login details.
I agree that it would be nice to turn off the 'auto login' behavior. I'll log this as a feature to be considered for future releases of SQL Multi Script.