Nevertheless, the majority of users is not going to appreciate them. Moreover, Microsoft uses to include some extra features into different Service Packs. In this update are included many improvements focused on the security and stability of the system. The solution is always the last thing you look at.Microsoft has launched the first big update for Windows 7: Windows 7 Service Pack 1 32 bits. So, after 5 other un-successful methods of correcting the symptom (not being able to log into /certsrv/ from another domain workstation with valid credentials) this did the trick, but only when performing the steps at the vDir level and not the web-site-root (Application Event Viewer showed 'API Remoting Web Service not working' and 'Self-Update not working' events from WSUS.) Web site that it would break WSUS communications. I found that if I adjusted the authentication mechanisms for the entire I made to the above set of recommended steps was to set the NTLM authentication first - only for the /certsrv/ virtual-directory instead of for the whole web-site. Given that WSUS invades the Default Web Site - as does CEWS - I had to make them play nicely with each other. To complicate my issue I already had WSUS installed on this same server using IIS for it's communications. I wish I could explain why this fixed the problem, but I'm completely baffled.Įncountered same issue after installing Intermediate CA on existing (internal facing only) web server (didn't want to bring another web server online and have to worry about securing it.) (the same credentials!) and the application started working. I switched it to the Application pool identity option

In my case, the Specific User option was checked (it contained the name of the credentials we configured in nfig). Opened up the Authentication, and edited the Anonymous access credentials. To solve the problem, I configured the application pool running the virtual directory to use the same credentials configured for anonymous access. To use specific credentials in the nfig file of IIS. We configured all of our anonymous access Yet, I still received the 401.2 Unauthorized error message. I had all of the correct features installed and configured on the web site and the virtual directory. I too received the 401.2 Unauthorized error message. I'm posting this so that if anyone having a similar issue to mine can solve their problem.

Microsoft windows 7 service pack 1