JLeslie

Thanks for your reply, but that is one of the main documents I used for setting up Office Web Apps. Its troubleshooting section is fairly sparse and while it does mention the error I'm getting, their answer is something I had already checked. I've looked in the error logs on the server and based on what I'm seeing there and the results of researching those errors, I'm coming to the conclusion that the problem is with the certificate since I'm using an https site, not http (the client wants access mainly from outside the LAN). My research indicates that the internal host domain must be in the SAN of the certificate. However that is not possible because new certificate rules state that you cannot include NetBIOS names of servers and private domain names such as domain.local in the SAN of certificates anymore. And the errors on the server certainly look to me as if the private domain name is involved. So this seems to be an impasse and I don't know how to fix it. Jonathan

I've setup Office Web Apps to work with a SharePoint 2013 server but I'm still missing something as it won't quite work yet. When I try to open a document such as a Word document on the SharePoint site, it tries to open in Web Apps, but then it errors out. The error message heading is "Microsoft Word Web App" and the body of the error says "Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word." I'm not a SharePoint admin and setting up Web Apps has been a total learning experience for me. So I'm totally in the dark about how to troubleshoot this and fix it. Any help would be appreciated. Jonathan

We recently deployed an RDS server running Server 2012 Standard. It runs well with one exception. When a user(both non-admin and admin) logs in (PCs are running either Windows 7 or Windows 8), the login usually is delayed for 1-3 min during the part where the message is displayed "Applying Group Printers Policy...". The GPP is set for Update which should be the fastest to process and there is no policy for deleting printers. When the RDS server ran Server 2008 R2, this never happened. What is it in Server 2012 that would cause this delay? I once had a 2008 non-R2 server (not an RDS) that had this same delay. There was a hotfix (KB973772) for Vista/2008 that resolved it but the hotfix is for 32-bit systems only and of course not for 2012. JL