Monthly Archives: February 2009

Fixes, Online Tools, Registry Hacks

More RWW woes with XP SP2 and SP3

Leave a comment
Following on from my blog regarding RWW on SBS2008 (http://blog.powerbiz.net.au/fixes/remote-web-workplace-rww-is-not-working-after-xp-sp3-is-installed/) and the need to have XP SP3 or RDC 6.1 for XP SP2.
After applying the following, I had a client who still could not connect to RWW. An error message appeared.
 
“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”
 
But it was installed!!??? Check out http://www.fixmyrww.com/
 
Go to the Internet Explorer Add-Ons, and enable the Microsoft Terminal Services Client Control ActiveX control or the Microsoft RDP client Control ActiveX control.
If this is already enabled, or after this is enabled, you will also need to re-register the ActiveX control.
 
Run the following command – regsvr32 %systemroot%\system32\mstscax.dll
 
Fixes, Office, Registry Hacks, Security, Server 2003

Microsoft Office Outlook cannot provide form scripting support

Leave a comment
I installed Trend Micro Worry Free Business Security Advanced on a server and implemented the antispam features. Trend drops detected spam messages into a folder called Spam Folder in each user’s Outlook mailbox on the Exchange server.
 
When accessing this folder on a Terminal Server, the following error message appears.
 
“Microsoft Office Outlook cannot provide form scripting support. This feature is not available. For more information, contact your support administrator.”
 
The fix to this problem is detailed in KB302003 – http://support.microsoft.com/kb/302003
 
1. Copy Outlvbs.dll from a normal client PC (not a Terminal Server). The file needs to be placed in the Program Files\Microsoft Office\Office12 folder. For Ooulook 2003, put this file in the Office11 folder.
 
2. Enable VB Script support by running the following command on the Terminal Server – msiexec /i {Product GUID} ADDLOCAL=OutlookVBScript /qb
The Product GUID can be found in the HKLM\SOFTWARE\Microsoft\Office\12.0\Common\InstalledPackages. Look for the Microsoft Office package key that is installed.