All posts by Stuart Davey

[RESOLVED] You must close all dialog boxes before you can close Exchange Management Console

After installing Internet Explorer 9 on your Microsoft Exchange 2007 or Exchange 2010 mail servers you may have been noticing that the Exchange Management Console will refuse to close and simply state “You must close all dialog boxes before you can close Exchange Management Console”.

This has been a long running issue but has finally been resolved by the Microsoft Internet Explorer Developer Team.

Please note that this issue is now resolved by installing the latest cumulative security update for Internet Explorer, The fix was first included in security update 2618444 http://support.microsoft.com/kb/2618444

Information on the scope of this issue can still be found here KB 2624899 http://support.microsoft.com/kb/2624899

You can request the hotfix by visiting Microsofts website and searching for the following Knowledge Base article KB 2624899

Note: The hotfix is actually for Internet Explorer 9 rather than Microsoft Exchange but does actually resolve the issues with the Exchange Management Console not closing correctly.

Cannot Open or View PDF Files using Internet Explorer Browser

A very common issue that Internet Explorer 8 and 9 users can face is an inability to view or download PDF files from a secure site (HTTPS).  As an example you will find that if you try to view the PDF in a browser window you will simply see a blank page.  This is due to the use of cache control headers which don’t seem to work correctly with secure sites in Internet Explorer.

If you are having this particular issue then please do the following:

  • Start “regedit” the default Windows Registry Editor
  • Next you need to locate this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings
  • Click on the “Edit” menu and then click “New” and then “Dword Value”, you will need to do this twice so that you can setup both the keys below.

Name = BypassSSLNoCacheCheck Type = Dword Data = 1 (Hex or Decimal)

Name = BypassHTTPNoCacheCheck Type = Dword Data = 1 (Hex or Decimal)

  • Close Regedit and Reboot, you should now find that the issue is resolved.

Powershell Execution Policy

Are you having trouble creating or running you Powershell scripts in Windows, remember that you need to adjust the default Powershell Execution Policy to allow the running of your scripts.

You may otherwise receive an error like the one below

File scriptexample.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see “get-help about_signing” for more details.

It’s very easy to adjust so don’t panic, just find your Powershell shortcut and remember to open it by “Right Clicking” and selecting “Run as administrator”

Next simply paste the line below into powershell, hit enter and then press “Y” and hit Enter one final time.

set-executionpolicy remotesigned