Archive for IE10

Block IE10 from Installing

This is from the “wish I knew about this sooner…” department.

Microsoft released earlier this year the Internet Explorer 10 Blocker Toolkit for Windows (x86 and x64) and Windows 2008 R2 SP1. This patch does not pertain to networks that are running an update management tool, such as WSUS, that provides the ability to block IE10 from being rolled out.

For all other workstations, you can download and run this tool manually from each workstation. The tool is a .EXE file that contains three files to be extracted.

  1. Create or identify a temp folder to be used (e.g. c:\temp)
  2. Download and run the IE10 Blocker Toolkit.
  3. Click Yes and then select the temp folder from step 1 to extract the three files
    image
  4. Open up an elevated command prompt, and use the CD command to switch to the temp folder
  5. Type ie10_blocker.cmd  /B and press Enter to set the block for IE10.
    image
  6. Check that you receive “The operation completed successfully” message, and then close the command prompt window.

As a reminder, IE10 is only pushed out for Windows 7/2008R2 and above. So, there’s no need to run this command script on Windows XP or Vista or Windows Server 2003.

Fix IE10 and SBS 2008 RWW error

You just upgraded your workstation to Internet Explorer 10. But when you try to remote into your SBS 2008 server, you get a “VBScript: Remote Desktop Connection” error message, like this:

image

The detail error message reads: The wizard cannot configure Remote Desktop Connection settings. Make sure that the client version of Remote Desktop Protocol (RDP) 6.0 or later is installed on this computer.

 

Solution:

The solution is so easy, you probably will miss it. After clicking OK on the error window, click on the Compatibility switch icon image at the top of your IE10 window.

image

Your RWW login screen will refresh. Log back in and try connecting to the remote computer, and it should be working as expected.

N.B. It probably is incorrect to call this a “solution”, as it is more of a “workaround”. It’s not a bug with IE10, it’s that the decision was made that it’s acceptable to have a “workaround” rather than to fix IIS to flag compat mode from the server.