Z
Ze'ev Eisenberg
Guest
Hi,
I have a successful CA environment working in a Windows 2012 R2-based domain. Recently, some user certificates expired, and when they went to the web page to get a new certificate (https://cert-server/certsrv) using IE 11 on Windows 10 Pro build 1709, they can go through the pages but the second (https://cert-server/certsrv/certrqus.asp) and third (https://cert-server/certsrv/certrqbi.asp?type=0) pages do not finish loading, no popups asking for permission happen, and when you click 'Submit', you get an error saying that you can't submit yet because the page hasn't finished loading. (This seems to be a true statement, as evidenced by no list populated if you look at the CSP dropdown box.) This is unique to build 1709. If a user on any lower version of Win 10 Pro tries the same thing, they succeed in getting their cert.
Has anyone seen this behavior before? It is not a problem with enabling Active Scripting - it is already active. Compatibility mode makes no difference. In our particular environment, web enrollment is the only thing open to us currently. Auto-enrollment through GPO or other means are not available.
Any help or ideas would be appreciated.
Continue reading...
I have a successful CA environment working in a Windows 2012 R2-based domain. Recently, some user certificates expired, and when they went to the web page to get a new certificate (https://cert-server/certsrv) using IE 11 on Windows 10 Pro build 1709, they can go through the pages but the second (https://cert-server/certsrv/certrqus.asp) and third (https://cert-server/certsrv/certrqbi.asp?type=0) pages do not finish loading, no popups asking for permission happen, and when you click 'Submit', you get an error saying that you can't submit yet because the page hasn't finished loading. (This seems to be a true statement, as evidenced by no list populated if you look at the CSP dropdown box.) This is unique to build 1709. If a user on any lower version of Win 10 Pro tries the same thing, they succeed in getting their cert.
Has anyone seen this behavior before? It is not a problem with enabling Active Scripting - it is already active. Compatibility mode makes no difference. In our particular environment, web enrollment is the only thing open to us currently. Auto-enrollment through GPO or other means are not available.
Any help or ideas would be appreciated.
Continue reading...