THE OFFICIAL BLOG OF THE SBS "DIVA"

Stealing this from the newsgroups from JJDavidson.....

If you've been getting errors from RWW/RDP recently, particularly "This portion of the Remote Web Workplace requires the Microsoft Remote Desktop ActiveX Control" or "An invalid server name was specified" you may have been hit by a false positive from an antispyware program, particularly Spybot S&D 1.4.  This affects the machine connecting to RDP, not the target machine.

Spybot set a registry entry to set the kill bit for the Microsoft RDP ActiveX control.  Although the latest Spybot updates no longer immunize against this control, it's apparently unable to undo the existing block, so you have to do it manually.  Some details are on the Spybot support forum here and here:

http://forums.net-integration.net/index.php?showtopic=32952

http://forums.net-integration.net/index.php?showtopic=32934

Disabling/uninstalling Spybot will NOT fix the problem!  Other antispyware programs may also have blocked RDP (AdAware has been mentioned), but the

following will fix any of them (at least temporarily).

To fix one machine, navigate to the following registry key and delete it:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX

Compatibility\{7584C670-2274-4EFB-B00B-D6AABA6D3850}

To build a file to patch several machines, save the following as a .reg file.  Remove any unwanted line breaks (the file should be six lines long including comments).  Then merge it into the registry on machines attempting to connect to RDP.

REGEDIT4

; --------------------------------------------------------------------------

; The following code will remove the ActiveX Compatibility restriction on

; CLSID = {7584C670-2274-4EFB-B00B-D6AABA6D3850}

; Microsoft RDP Client Control (redist)

; --------------------------------------------------------------------------

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{7584C670-2274-4EFB-B00B-D6AABA6D3850}]