I explained to a technical person that there was a GPO causing an issue on a system with a web based client application. Seems that ADO code was not allowed to be accessed because of the GPO.
The code in the script was:
var rs = new ActiveXObject("ADODB.Recordset");
The tech, asked me "what's a GPO, I'm not familiar with that term."
I was not surprised. For my part, I've not had to worry about what users were accessing in a large enterprise for a while. I'm becoming AD ignorant to some extent.
But have any of you controlled via a GPO what type of code can run in a browser and how can you allow some urls in trusted sites and not others.
In addition to that the GPO seemed to consider data and authentication from SQL based authentication as another domain.
Thus an error stating " Safety settings on this computer prohibit accessing a data source on another domain"