Outlook Web Access“损坏” - 已验证但显示不正确且无法使用
我们有一台运行 Exchange 的 SBS 2008 服务器。我们有 5 个用户从本地连接到 Exchange 的办公室运行，一切都运行良好。我们的一位用户开始经常出差，并希望有一种方法可以从任何远程计算机访问他的电子邮件 - Outlook Web Access 似乎很有意义。
不幸的是，我根本无法让它工作。我们的用户可以连接到我们的远程域并成功登录，他们可以连接到我们的共享点站点，并且可以远程连接到本地网络上的计算机 - 但是 Outlook Web Access 无法正常工作。
选择 OWA 后，用户会看到收件箱的“损坏”版本。他们可以看到最近收到的所有电子邮件的标题等，但他们无法单击任何内容或以任何方式与界面交互。我不可能理解为什么这不起作用 - 它肯定可以成功进行身份验证和连接以进行交换，但它只是不允许任何交互。 （我在下面附上了一张图片）。我确实不知道如何处理这个问题，但这非常重要，因为我的用户需要访问他的电子邮件。
我（也许显然）不是经验丰富的系统管理员，因此，如果我没有正确描述问题或者解决方案有些明显，我深表歉意。
We have an SBS 2008 server running Exchange. We have 5 users running from an office locally connected to exchange and everything is working perfectly fine. One of our users can begun travelling extensively and would like a way to access his email from any remote machine - Outlook Web Access seems to make sense.
Unfortunately, I've been unable to get it working at all. Our users can connect to our remote domain and login successfully, they can connect to our sharepoint site and can connect remotely to computers on the local network - however Outlook Web Access fails to work correctly.
Upon selecting OWA, the user is presented with a 'broken' version of their inbox. They can see the titles of all the emails they've recently received and so on, but they cannot click on anything or interact with the interface in any way. I cannot possibly understand why this isn't working - it is definitely authenticating and connecting to exchange succesfully but it just doesnt allow any interaction. (Ive attached an image below). I literally have no idea how to proceed with this issue but it's rather important as my user needs access to his email.
I'm (perhaps obviously) not an experienced systems admin, so I apologise if I have not described the issue correctly or if the solution is somewhat obvious.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
目前已更正，敬请谅解。
我将在这里发布解决方案，以防其他人遇到此问题。
看来 OWA 的更新实际上最终破坏了它 - 它在服务器上的 OWA 目录中安装了一个新的主题和脚本文件夹，但没有用所有必要的文件填充它们。我找到了旧脚本和主题文件的备份，并将它们简单地复制到更新的主题和脚本文件夹中的相关文件夹中，现在看起来一切正常。
This is now rectified, apologies.
I'll post the solution here just incase anyone else has this issue.
It seems an update to OWA actually ended up breaking it - It installed a new themes and scripts folder into the OWA directory on the server and but didn't populate them with all of the necessary files. I located a backup of the old scripts and theme files and simply copied them into the relevant folders in the updated theme and script folders and it now appears to be all be working correctly.