Microsoft Office Outlook cannot provide form scripting support This feature is not available

If you get the following error message in Outlook on a Terminal Server, do the following:
Run this from a command prompt: msiexec /i [GUID] ADDLOCAL=OutlookVBScript /qb

You need to find out what GUID your Office version have. The easiest way to do that is to open Regedit and start a search from this key:
HKLM/Software/Microsoft/Windows/Current Version/Uninstall

All GUID’s start with a brace ({). Search for Office and you will find the right key. So, for example, if you run Office Outlook 2007 Proffessional Plus you would run this:
msiexec /i {90120000-0011-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

Outlook 2007 / 2010 Search Criteria / Operators

The following table shows examples of searches you might find useful. The search query syntax, available when the Instant Search (Instant Search: A Search feature that provides search results quickly with word highlighting as you type. The Instant Search pane is always available in Mail, Calendar, Contacts, Tasks, Notes, Folder List, and Journal.) feature is enabled, follows this basic form: keyword:your search criteria value.

For example, from:bobby

You can also use logical operators AND, NOT, OR, <, >, =, and so forth to refine your search, and these are noted in the table. Logical operators must be typed in uppercase letters.

Note   The search query syntax is created automatically and displayed in the Instant Search box when you use the Query Builder described in the previous section.

Type this	To find this
bobby	Items containing bobby, BOBBY, BoBby, or any other combination of uppercase and lowercase letters. Instant Search is not case sensitive.
bobby moore	Items containing both bobby and moore, but not necessarily in that order.
bobby AND moore	Items containing both bobby and moore, but not necessarily in that order. Note that logical operators such as AND, NOT, and OR must be in uppercase letters.
bobby NOT moore	Items containing bobby, but not moore.
bobby OR moore	Items containing bobby, moore, or both.
"bobby moore"	Items containing the exact phrase bobby moore. Note the use of double quotes so that the search results match the exact phrase within the quotes.
from:"bobby moore"	Items sent from bobby moore. Note the use of double quotes so that the search results match the exact phrase within the quotes.
from:"bobby moore" about:”status report”	Items sent from bobby moore where status report appears in the subject line, body, and attachment contents. Note the use of double quotes so that the search results match the exact phrase within the quotes.
hasattachment:yes	Items that have attachments. You can also use hasattachment:true to get the same results.
attachments:presentation.pptx	Items that have attachments named presentation.pptx or if the attachment contains presentation.pptx within its contents.
subject:"bobby moore"	Items whose subject contains the phrase bobby moore.
subject:bobby moore	Items with bobby in the subject line and with moore anywhere else in the document.
cc:"bobby more"	Items in which the display name bobby moore is on the Cc line.
cc:bobbymoore@contoso.com	Items in which the e-mail address bobbymoore@contoso.com is on the Cc line.
bcc:bobby	Items in which bobby is on the Bcc line.
messagesize:<10 KB	Items whose size is less than 10 kilobytes. Note the use of the "less than" comparison operator (<).
messagesize:>5 MB	Items whose size is larger than 5 megabytes. Note the use of the "greater than" comparison operator (>).
received:=1/1/2006	Items that arrived on 1/1/2006. Note the use of the "equals" comparison operator (=).
received:yesterday	Items that arrived yesterday. Instant Search also recognizes the follow date values:
	Relative dates:    For example, today, tomorrow, yesterday
	Multi-word relative dates:    For example, this week, next month, last week, past month, coming year
	Days: Sunday, Monday ... Saturday
	Months: January, February ... December
received:last week	Items that arrived last week. Note that if you run this query again a month from now you will obtain different results because it is a time relative query.
due:last week	Items that are flagged for follow up a due date.
messagesize:tiny	Items whose size is less than 10 kilobytes
messagesize:small	Items whose size is between 10 and 25 kilobytes
messagesize:medium	Items whose size is between 25 and 100 kilobytes
messagesize:large	Items whose size is between 100 and 500 kilobytes
messagesize:verylarge	Items whose size is between 500 kilobytes and 1 megabyte
followupflag:follow up	Items that are flagged for follow up.
messagesize:enormous	Items whose size is larger than 5 megabytes
hasflag:true	Items that are flagged for follow up.
from:bobby (received:1/7/05 OR received:1/8/05)	Items from bobby that arrived on either 1/7/05 or 1/8/05. Note the use of parentheses to group the dates.
received:>=10/1/06 AND received:<=10/5/06	Items that arrived between 10/1/06 and 10/5/06.
received:>10/1/06 AND received:<10/5/06	Items that arrived after 10/1/06 but before 10/5/06.
sent: yesterday	Items that you sent yesterday.
to:bobby	Items that you sent to bobby when you are searching in the Sent Items folder.
read:no	Items that have not been read. You can also use read:false to get the same results.
subject:status received:May	Items received from anyone during the month of May (any year) where the subject contains status.
startdate:next week subject:status	Calendar items next week where the subject contains status.
is:recurring	Calendar items that are recurring.
organizer:bobby	Calendar items where bobby is the organizer.
category:business	Items that are categorized as business.
firstname:bobby	Contacts that contain bobby in the First Name field.
lastname:moore	Contacts that contain moore in the Last Name field.
nickname:bobby	Contacts that contain bobby in the Nickname field.
jobtitle:physician	Contacts that contain physician in the Job Title field.
pager:555-0100	Contacts that contain 555-0100 in the Pager field.
businessphone:555-0100	Contacts that contain 555-0100 in the Business Phone field.
homephone:555-0100	Contacts that contain 555-0100 in the Home Phone field.
mobilephone:555-0100	Contacts that contain 555-0100 in the Mobile Phone field.
carphone:555-0100	Contacts that contain 555-0100 in the Car Phone field.
businessfax:555-0100	Contacts that contain 555-0100 in the Business Fax field.
homefax:555-0100	Contacts that contain 555-0100 in the Home Fax field.
businessaddress:(4567 Main St., Buffalo, NY 98052)	Contacts that contain 4567 Main St., Buffalo, NY 98052 in the Business Address field. Note the use of parentheses to enclose the address.
homeaddress:(4567 Main St., Buffalo, NY 98052)	Contacts that contain 4567 Main St., Buffalo, NY 98052 in the Home Address field. Note the use of parentheses to enclose the address.
businesscity:buffalo	Contacts that contain buffalo in the Business City field.
businesspostalcode:98052	Contacts that contain 98052 in the Business Postal Code field.
street:(4567 Main St)	Contacts that contain 4567 Main St in the Business Address Street field. Note the use of parentheses to enclose the address.
homestreet:(4567 Main St)	Contacts that contain 4567 Main St in the Home Address Street field. Note the use of parentheses to enclose the address.
birthday:6/4/1960	Contacts that contain 6/4/1960 in the Birthday field.
webpage:www.contoso.com	Contacts that contain the URL www.contoso.com in the Web Page Address field.

From:

http://office.microsoft.com/en-gb/outlook-help/learn-to-narrow-your-search-criteria-for-better-searches-in-outlook-HA010238831.aspx

Restricting Outlook Client Versions in Exchange 2007

Determining Which Client Versions are in use

Before implementing client version blocking it’s a good idea to know versions are in use.  With this information you can tell which clients need to be upgraded to a newer version before blocking is implemented, or simply which clients will no longer be able to connect after it is implemented.  In Exchange 2007 client version information is retrieved using the Get-LogonStatistics cmdlet.

Get-LogonStatistics accepts a mailbox, a mailbox database, or a server name as input and returns statistics including user name, logon time, last access time, client name, and client version.

For example, to list the client versions used to access a single mailbox, the command is:

Get-LogonStatistics JSmith | ft UserName,ClientVersion,LogonTime

To list the client versions for all clients connecting to a specific server:

Get-LogonStatistics –Server SERVER01 | ft UserName,ClientVersion,LogonTime

To list the client versions for all clients on all mailbox servers, and export the results to a CSV file:

Get-MailboxServer | Get-LogonStatistics | `

Select UserName,ClientName,ClientVersion,LogonTime | `

Export-Csv -Path ExchangeClientVersions.csv

Once you have identified the clients in use in your organisation and taken any remedial action necessary you can move on to blocking any further access by unwanted clients.

Determining Which Client Versions to Block

The client version is determined by the version of Emsmdb32.dll on the client.  This is not necessarily the same as the Outlook version, or the version of any other DLL or executable files.  This table shows the version of Emsmdb32.dll for major releases or updates of Outlook since the release of Office XP.

Release

Emsmdb32.dll Version

Office XP RTM

10.0.2627.1

Office XP SP1

10.0.3416.0

Office XP SP2

10.0.4115.0

Office XP SP3

10.0.6515.0

Office 2003 RTM

11.0.5604.0

Office 2003 SP1

11.0.6352.0        

Office 2003 SP2

11.0.6555.0

Office 2003 SP3

11.0.8161.0

Office 2007 RTM

12.0.4518.1014

Office 2007 SP1

12.0.6211.1000

Office 2007 SP2

12.0.6423.1000

Table 1 - Emsmdb32.dll version by Office release

There are some important points to note:

• The MAPI client version numbers listed in Table 1, and those in the results of the Get-LogonStatistics cmdlet, are in the format x.0.y.z.  When specifying MAPI versions to be blocked you must use the format x.y.z.  For example, the version number for Outlook 2003 RTM becomes 11.5604.0.

• When setting per-server restrictions it is very important to avoid restricting clients with version numbers 6.y.z  as Exchange Server makes use of MAPI for server-side component connections and uses MAPI versions within the 6.y.z range (with the version number potentially varying by Exchange component and patch level).  This does not apply to per-mailbox restrictions.

• Microsoft recommends that at a minimum you block all MAPI clients with version numbers equal to or earlier than 5.3164.0.0.

Single versions are blocked by specifying the version in the format <version>, an open-ended range is blocked by using the format -<version1> or <version2>-, and a specific inclusive range is blocked by using the format <version3>-<version4>.  Multiple sets of client versions can be disabled using a comma or semi-colon separated list.

Range Type

Example

Effect

<version>

11.5604.0

Block the specified MAPI version.

-<version>

-11.0.0

Block the specified version number, and all previous versions.

<version>-

11.0.0-

Block the specified version number, and all newer versions.

<version>-<version>

11.0.0-11.9.9

Block the specified version numbers, and all clients between the specified versions.

Table 2 - Example client version blocking syntax

Some example blocking settings to use:

Blocking Setting

Effect

11.5604.0

Block Outlook 2003 RTM

-5.9.9;7.0.0-11.9.9

Block all clients older than Outlook 2007

12.0.0-

Block all versions of Outlook starting with Outlook 2007 and including all future versions

-5.3164.0

Block Microsoft recommended Outlook versions

-5.99;7.0.0-

Block all MAPI clients, except for Exchange Server components

Table 3 - Example client version blocking settings

Implementing the Blocking Settings

As mentioned earlier, restrictions can be implemented per-server or per-mailbox.  Per-server restrictions are implemented via a registry change, and per-mailbox restrictions are implemented via the Exchange Management Shell – it is not possible to use the Exchange Management Console.

If both server and mailbox restrictions are used the most restrictive combination of both settings applies, additionally a server restriction cannot be overridden by a mailbox setting.

For example:

Server Restriction

Mailbox Restriction

Net Effect

-5.3164.0

-11.9.9

Mailbox can only be accessed using Outlook 2007

-5.9.9;7.0.0-

11.0.0-11.9.9

Mailbox cannot be accessed by any MAPI client (which is not executing on the Exchange server)

Table 4 – Cumulative effect of restrictions

To implement a per-server restriction

Note – Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved.  Before editing the registry, back up any valuable data. 

You need to be a local administrator on the Exchange server in order to edit the registry.

1. Start the registry editor on your Exchange 2007 Mailbox server

2. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem registry key.

3. Right-click ParametersSystem, select New, and then select String value.

4. Name the new string value “Disable MAPI Clients”.

5. Right-click Disable MAPI Clients, and then click Modify.

6. Enter the restriction setting, for example -5.9.9;7.0.0-11.9.9

7. Close the registry editor

The change will be effective within 15 minutes, or to make it effective immediately you can restart the Microsoft Exchange Information Store service.  Once the change takes effect any existing client connections which do not meet the version requirements will be terminated.

To implement a per-mailbox restriction

The Set-CASMailbox cmdlet is used to implement per-mailbox restrictions.  To use the Set-CASMailbox cmdlet you must be delegated the Exchange Recipient Administrator role.

To prevent a mailbox from using Outlook clients prior to Outlook 2007 the command is:

Set-CASMailbox JSmith -MAPIBlockOutlookVersions "-11.9.9"

To remove a restriction for a mailbox:

Set-CASMailbox JSmith -MAPIBlockOutlookVersions $null

To prevent all mailboxes in a particular database from using clients other than Outlook 2007 RTM:

Get-Mailbox -Database "SERVER01\SG1\Database 1" | `

Set-CASMailbox -MAPIBlockOutlookVersions "-12.4518.1013;12.4518.1015-"

When an Outlook 2003 or Outlook 2007 user tries to connect with a restricted client version they will receive the message “Your Exchange Server administrator has blocked the version of Outlook that you are using. Contact your administrator for assistance.”

Users of older clients will receive the message “Cannot start Microsoft Outlook. The attempt to log on to the Microsoft Exchange Server computer has failed.”

More information on Get-LogonStatistics and Set-CASMailbox can be found in TechNet:

• Get-LogonStatistics - http://technet.microsoft.com/en-us/library/bb124415.aspx
• Set-CASMailbox - http://technet.microsoft.com/en-us/library/bb124415.aspx

 

Source: http://www.simple-talk.com/sysadmin/exchange/restricting-outlook-client-versions-in-exchange-2007/

If you get an error message in Outlook that reads "Could not install the custom actions.”

If you get an error message in Outlook that reads "Could not install the custom actions.” here is the fix:

1. Close Microsoft Outlook.
2. Make sure hidden files and folders are shown. This can be done in "Folder Options" within the "Control Panel" on the "View" tab.
3. Navigate to the following location:

Windows XP
C:\Documents and Settings\[User Name]\Local Settings\Application Data\Microsoft\Forms\

Windows Vista
C:\Users\[User Name]\AppData\Local\Microsoft\Form\

4. In there, there is a file called "FRMCACHE.dat". Delete this file.
5. Relaunch Microsoft Outlook.

More can be read about the fix at:
http://www.spencerkam.com/blog/2007/11/could-not-install-custom-actions.html

Major Bug in Outlook

I believe I have found a major bug in Outlook. I say major because when this issue involves sending emails as BCC. When you send an email as BCC you are sending it because you don’t want the recipient to be able to see who else it was sent to.

If you follow the steps below the recipient is able view the names of all the BCC recipients.

To reproduce the issue

Go to your ContactsRight click contact and select New Message to ContactMove the name from To field to the BCC field.
Click View->OptionsIn the Contacts field is the name of the BCC recipient which was originally the To recipient. The Contacts field should be empty instead.


This information is viewable to the recipient if they print it out or by making the message editable (forward, reply or reply to all) and clicking the message's option button. After clicking the option button the Contacts field will display the names of the BCC recipients. If the recipient prints the email out it will print the usual fields of From, Sent, To, and Subject. The print out will also display a Contacts field which contains all the BCC recipients names.

There are a couple of workarounds:

Clear the Contacts field prior to sending if using the steps above
Create a new email in Outlook by going to File->New Message and populate the BCC field by clicking the BCC button

It appears that Outlook is not correctly clearing the Contacts field after moving the name from To to BCC. This only happens when you right click a contact and select New Message to Contact.

I have researched this issue and have not found any information about it including Microsoft.

Lesson learned, be careful when you send an email BCC because it might not be blank.