Permissions to install flash player on Terminal Server

Here is how to fix this problem when using TS. I have tested it both on the 32-bit version of Windows Server 2003 and the x64 version. Works (for me):

1. Download the latest Flash uninstaller on this page: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_14157&sliceId=1 and place it somewhere on your hard disk (C:\Temp is a good place)
2. Open a command prompt, navigate to the folder where you placed the uninstaller and run it with the "/clean" option, like this: "uninstall_flash_player.exe /clean" (without quotes - thanks Adobe for so clearly documenting any command line options for this tool...NOT !)
3. Click the Details button. If it lists any files as "Delete on reboot", then reboot now. Otherwise, just carry on.
4. Download the EXE installation package from here:
http://www.adobe.com/support/flashplayer/ts/documents/tn_19166/Install_Flash_Player_9_ActiveX.zip
5. Use the Control Panel Add/Remove programs method to install it. This ensures that the Windows install notification API triggers correctly (as opposed to executing change user /install in a command prompt).
6. Use regedit and find the following key: HKCR\CLSID\{D27CDB6E-AE6D-11cf-96B8-444553540000} (on 64-bit Windows this one is located under HKCR\Wow6432Node\CLSID\{D27CDB6E-AE6D-11cf-96B8-444553540000})
7. Remove any permissions for the Everyone group. click Advanced and tick the box to propagate the permissions to all child objects.
8. Add the Everyone group and give it "Read" permissions on the key. Again, click the Advanced button and propagate the permissions to all child objects.
9. Repeat steps 6 to 8 on the subsequent key, called HKCR\CLSID\{D27CDB70-AE6D-11cf-96B8-444553540000}

Log on as a norrmal user and test it.

Provided that the uninstaller did not report that it needed a reboot in step 3, all this can be done and will start working immediately, even with active users logged on and running several instances of IE on the Terminal Server.

CMD: How to count the number of remote users connected?

 Use command:
 query session /COUNTER

MS RDP. Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again

Problem:

i had remote desktop up and running on a PC and then i got this:
"because of a protocol error detected at the client (code 0x1104), this session will be disconnected.
please try connecting to the remote computer again"

Solution:

The most common reason why this is happening is because you are using a custom VISUAL STYLE with your computer. Set the visual style back to LUNA on XP or CLASSIC and see if the error occurs again. Most likely it will not. Not all visual styles produce this error, but if you want a custom visual style on the remote computer then you will have to find a compatible visual style that works with RDP via trial and error.

Another solution would be to set the RDP client to NOT use the visual styles by unchecking the box that says THEMES (see pic below):