FAQs about OWA in Windows XP SP2

Although Service Pack 2 in Windows XP solves many problems and provides better operating system security, it also brings a lot of trouble, for example, the pop-up window blocking function added by Microsoft for Internet Explorer may cause some problems in Outlook website Access to Outlook Web Access: OWA. In Exchange 2000 and 2003, many functions of OWA must be implemented using pop-up windows. Once these pop-up windows are intercepted, these functions cannot be implemented.

The pop-up window blocking function has many problems, which cannot be listed here. A common problem is that Folder creation, attachment dialog box, send email to contact button, and contact form cannot work normally.

In addition, the pop-up window blocking function may cause the OWA script error. For example, if you double-click a user name in the "Search username" dialog box, a script error prompt will pop up, because some necessary operations are intercepted by the browser.

In this case, do we need to disable the pop-up window Interception Function to solve the OWA problems? Answer. You know, many pop-up ad Windows Hide the code for spreading Trojans and spyware. Retaining this function has a great role in protecting system security. The following describes how to solve the OWA problem while enabling this function:
Method 1:

Set privileges for your OWA site so that the pop-up blocking tool of IE ignores the pop-up window of the site.

Open the control panel, click Security Center and Internet Options, select the privacy tab in the displayed Internet Properties window, find the blocking tool section in the pop-up window, and click "set. At this time, the system will display a dialog box about setting this function. You only need to enter the URL of your OWA site in the text box in the "site address allowed in the pop-up window" section, click "add" and close the dialog box.

Method 2:

Sometimes users access the OWA site from a public computer, and they may not have the permission to change the Internet Explorer settings. In this case, you should choose to allow users to log on using form-based authentication and select the basic client instead of the advanced client.

To enable the form-based login function of the mail server, follow these steps: first open the Exchange system management tool and locate the server running the OWA site; expand the "protocol" container of the server, right-click the "HTTP" container icon, and select Properties From the shortcut menu that appears. Switch to the "Settings" tab in the properties menu, you can see a check box before "Enable form-based authentication". Select it and click "OK" to exit.

After this setting, When you log on to OWA, you will see a form called DOMAIN \ USERNAME and select either the basic client or the advanced client. In this case, you need to enter your Logon account in the form and select to use the basic client, so you are not afraid that the pop-up window blocking function will affect the normal access to OWA.
Method 3:

First of all, I do not recommend this method, because using this method will cause IE to be unable to block many malicious pop-up windows. I listed it as a solution to the problem.

If you access OWA through HTTPS, you can solve the problem by changing the filter level of the pop-up window Interception Function. By default, the filtering level of the pop-up window is set to "medium", which means it intercepts the vast majority of pop-up windows. If you set this level to "low", the blocking function will ignore the pop-up window from the security site. You can find the dialog box for setting the window blocking function according to the path I mentioned in method 1, and then you can set the filter level.

S/MIME Problems

Most OWA access problems are caused by the pop-up window Interception Function, but Microsoft acknowledges that sometimes the S/MIME Control Function in OWA may also be faulty. Although S/MIME still exists, the "Email Security" Area in OWA still tells you that S/MIME control is not installed. Therefore, you will not be able to perform moderate operations such as encrypting emails, adding digital signatures to emails, and dragging attachments to emails you are writing. Microsoft does not seem to have released a patch to fix the S/MIME issue.

If you want to know