I have an issue, which is related to JavaScript Cross Browser Scripting rules. I have an Exchange 2010 server set up, with the OWA interface in an iFrame on our website. Problem is, we've got https://server.ca/ as the homepage (and secured with EV SSL), and the OWA mail interface is https://mail.server.ca/ (with regular SSL) - and this is enough difference for the js not to work when in the iFrame (works amazingly perfect outside of the iFrame) Now the only issue from this is when a user open the Options page, tries to change a password, or edit contacts, etc. I know how to solve this issue, but can't seem to figure out how to do it technically speaking; Launch the Options in a new window. Option A - Remove the Options link from the top of the OWA interface (can't figure this out anyways...) and then add a link to the page in its place Opening the options in a new window. Option B - Change the Options (and any/all links to the ECP related pages for that matter) button to Launch in a new Window. Anyone know how I can accomplish either of these solutions?

I solved Removing/adding new links. I found this in OWA/forms/premium/startpage.aspx: <div id="divAlertBarContainer"> <% RenderBreadcrumbs(); %> <% RenderingUtilities.RenderAlertBarButtons(Response.Output, OwaContext); %> </div> I removed the line <% RenderingUtilities.RenderAlertBarButtons(Response.Output, OwaContext); %> And Will add my own Hyperlinks which open in new windows, therefor bypassing the Javascript errors.