Remote Desktop mstsc.exe slow will not start windows 7

Had a painful problem today with the mstsc.exe application in Windows 7 64 Bit Ultimate today.


An otherwise happy install suddenly failing to start, or if is started it would be very slow.

Once started, it would not close from the task manager, even if I killed the process with the end process.


I suspected that it was possibly a virus etc. However I found that there are a lot of people on the net with this exact problem.

I then set about a solution, and figured on out myself, that involves replacing some of the files use by the MSTSC.EXE application.

Basically there are 4 files that I replaced with the same version from another computer that was functional and healthy. They are:








I would create a .zip copy for download except I fear giving out some stored connection settings in the files I already have. So sorry, you will have to find your own backup files.


The Bitch of it

The annoying problem is that you cannot just copy the 4 files into the two folder locations as Windows 7 in all it’s wisdom will not let you copy files there, as you are not the “Trusted Installer”.

You might be like me, Administrator and God of your computer that at any time can take to it with a hammer and replace it with a Mac, but Windows 7 knows best… so let’s show you what you have to do to hack that crap!


Give Permissions

First, go to the folder or set of files that you need to change permissions for, right-click on them and choose Properties.


Next click on the Security tab and then click on the Advanced button at the bottom:


Next click on the Owner tab and you’ll now see that the current owner is TrustedInstaller.


Now click on the Edit button and choose who you would like to change the owner to, either your account or the Administrators. If your account is an Administrator account, I would suggest just picking Administrators.


You can also check off Replace owner on sub containers and objects if you need to delete more than one file in a folder. Go ahead and click OK. Now you will see that the Current owner is the account you picked.


Click OK until you have closed all properties windows and are back to the Windows Explorer screen. Then right-click on the folder or file again and choose Properties again.

Now click on the Security tab again, but instead of clicking on Advanced, you need to click the Edit button.


Now click on the user name in the list that you want to change the permissions for, which should be the same as who you changed the current owner too. If the user name is not in the list, click Add, type in the name and click OK.


Since I had changed the current owner to Administrators, I clicked on Administrators here and then clicked on the check box next to Full Control. When you do that, all the other boxes get checked too.

Click OK once and then click OK one more time to get back to Windows Explorer. Now you can replace those files without any UAC messages telling you that you can’t! Enjoy!

Disable SSL 2.0 IIS 7 Windows 2008 64bit with CRM 2011 for PCI Compliance

PCI Failure

Today we received notification during a PCI compliance check that our Microsoft CRM 2011 server was not PCI Compliant.


The cause of the lack of compliance was due to the server accepting connections via an SSL v 2.0 protocol.

Synopsis : The remote service encrypts traffic using a protocol with known
weaknesses . Description : The remote service accepts connections encrypted
using S S L 2.0, which reportedly suffers from several cryptographic flaws and has
been deprecated for several years . An attacker may be able to exploit these
issues to conduct man-in-the-middle attacks or decrypt communications between
the affected service and clients . See also :

Download File – ZipSource

Solution: Consult the application’s documentation to dis able S S L 2.0 and us e
S S L 3.0 or TLS 1.0 instead. Risk Factor: Medium / CVS S Bas e S core : 2

Perhaps not the worlds biggest deal, as the SSL certificates in place are using the SSL 3.0 however we needed to remove the V2.0 for compliance with PCI.

The solution turned out to be no so easy… Mostly due to the fact that we are using a 64bit Windows 2008 server and Microsoft have only appeared to provide details on fixing 32 bit servers to remove SSL v2.

We did manage to get there and this is what we had to do

Remove SSL v2

You need to run the following commands at a command prompt on the server:

REG ADD “HKLM\System\CurrentControlSet\Control\SecurityProviders\SChannel\Protocols\SSL 2.0\Server” /v Enabled /t REG_DWORD /d 0 /f
REG ADD “HKLM\System\CurrentControlSet\Control\SecurityProviders\SChannel\Protocols\SSL 2.0\Client” /v Enabled /t REG_DWORD /d 0 /f
REG ADD “HKLM\System\CurrentControlSet\Control\SecurityProviders\SChannel\Protocols\SSL 3.0\Server” /v Enabled /t REG_DWORD /d 1 /f
REG ADD “HKLM\System\CurrentControlSet\Control\SecurityProviders\SChannel\Protocols\SSL 3.0\Client” /v Enabled /t REG_DWORD /d 1 /f
REG ADD “HKLM\System\CurrentControlSet\Control\SecurityProviders\SChannel\Protocols\TLS 1.0\Server” /v Enabled /t REG_DWORD /d 1 /f
REG ADD “HKLM\System\CurrentControlSet\Control\SecurityProviders\SChannel\Protocols\TLS 1.0\Client” /v Enabled /t REG_DWORD /d 1 /f

We created a batch file to make this easier.

You can download the file here, and extract the batch file. Then double click the file called: “DisableSSLv264bit.bat”.

Then Reboot the server.

Download File – DisableSSLv264bit

All it will do is run the above commands and in the registry it will add:


and similar sets to enable SSL v3 and disable SSL v2.

Then you can use a free test service here:


to check that you are disabled.

A failure like this:


indicates something did not take correctly.

If you are using a 32 bit version of windows. (Not possible with CRM 2011) but possible otherwise, then you can use the Microsoft tool here:

Invalid data reported–Analytics Report


We have found an issue that would prevent the Google Analytics report module from rendering in certain websites under certain conditions.

The symptoms of the issue are that the module reports “invalid data” when you have configured the module settings.


If you experience this error messages, then the solution is easy…

Ensure you have a version of the module that is later than 45.06.02 – Available from our website as a download here:

Then after updating, you need to check the option that says: “Render Chart from Control”


This should allow the chart to report past the Invalid data error.

The error relates to the DotNetNuke Alias redirection settings in the DNN Site Admin settings, and appears to be when a redirection has been defined in the settings.


If the redirection is turned to none, this should also fix the error.

Alternatively it appears to have been fixed in DotNeTNuke release 06.01.01. But who is to day that the issue will not creep into later releases of the module.