I would think the authentication delegation may be working - you may be able to examine the security event log on the SQLServer and see if there is a successful logon from whatever user ansible is connecting as. but I think its possible that SQL Server has other requirements but worth checking the event log. Also, does the installer write a log file or write to the event log. It might be possible to determine why is failing from the installer's own logging.
Hope this helps, Jon On Monday, February 27, 2017 at 10:15:15 PM UTC, Justin Dugan wrote: > > The delegation is working (at least for Windows shares). The installer > file is copied from a Windows file share before the install occurs and this > completes successfully. Is it possible for the delegation to work for a > file share and fail for SQL Server? > > On Saturday, February 25, 2017 at 12:33:01 PM UTC-5, J Hawkesworth wrote: >> >> Rdp to the server and connecting to sql server is just one hop. >> Connecting from ansible to server and from server to sql server is a second >> hop, which is where the delegated credential becomes important. >> >> If you want to check if delegation is working, you could try writing a >> file to a share on a second machine from ansible via your windows server. >> >> It's been a while since I installed SQL Server, but if I recall there >> is/was a Surface Area configuration tool where you can set various options >> regarding things like ports and available authentication protocols. If >> that is still a thing, that might be worth looking at too. >> >> Jon >> >> -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/4eb38403-5814-4c91-85a0-8a95aa98ecfb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
