Fixed incorrect logging of errors that should be warnings.
Added logging to identify when Outlook is started
with a profile not configured for Duet.
During metadata upgrade, increased the time that a
user has to close running Office applications to 30 seconds.
Improved Client Protocol Handler logging to include
BoundItemType, BoundItemId, and CorrelationID values.
In a primary or a secondary computer configuration, a
metadata upgrade results in an item becoming unbound if it was created on
the secondary machine and the Sweeper did not process it yet.
Copying and pasting a bound item no longer results in a
new bound item. The new item is a standard unbound Outlook item.
Improved user feedback if Duet cannot log on to Exchange Server.
The Duet add-in for Word no longer automatically
loads unless a scenario is installed that needs Word integration.
The metadata cache on a client is no longer encrypted.
Fixed a scenario in which a Duet utility crashes with a
System.NullReferenceException during metadata deployment if calls to the
metadata server result in a time-out.
Past occurrences of a
bound recurring appointment series become unbound during Duet parallel
appointment creation.
Bound items become unbound if the OBASQLEXPRESS
instance becomes unavailable while the Sweeper is running.
Note For all installations, run the Setup.exe file or the SetupPatch.exe file.
Directly running the .msp files may skip important configuration steps that are
included in the setup packages.
If Duet 1.5 SP2 (1.8.5021.0) or an earlier version is
already installed on the computer, follow these steps. Otherwise, move to "2.
Fresh Client Install."
Starting with this update (June 2009), the
metadata cache on the client is no longer encrypted. To make this
transition, any existing metadata cache has to be deleted before installation.
You can do this by running the Client Repair tool with the /RemoveCache
option:
At a command prompt, visit the Framework directory and
then run the following command:
Confirm that the Microsoft.OBA.Tools.ClientRepair.exe
tool is included in the folder C:\Program Files\Microsoft Information
Bridge\1.8\Framework\
Open a command prompt and then visit C:\Program
Files\Microsoft Information Bridge\1.8\Framework\
At a command prompt, run the following command, and then press ENTER:
Microsoft.OBA.Tools.ClientRepair.exe /RemoveCache
Continue with the following steps for a Fresh Client
install and install any updates that are not already installed.
Fresh Client install.
32-bit client computer:
Install Duet 1.5 RTM (1.8.3139.0).
Install the Duet 1.5 April 2009 update
(http://support.microsoft.com/kb/970065) (1.8.4014.0).
Install Duet 1.5 SP2 (1.8.5021.0).
Install this June 2009 update (1.8.5030.0).
64-bit client computer:
Install Duet 1.5 SP2 MSI (Run setup.exe) from the x64
folder.
Install this June 2009 update (1.8.5030.0) by
running SetupPatch.exe from the x64 folder.
If you use group policies to configure Duet, apply the new
Group Policy template included in the IT Administrator Files folder of this
update.
A
supported hotfix is available from Microsoft. However, this hotfix is intended
to correct only the problemP1 that P2 described in this article. Apply this
hotfix only to systems that are experiencing the problemP1 described in this
article. This hotfix might receive additional testing. Therefore, if you are
not severely affected by this problem, we recommend that you wait for the next
software update that contains this hotfix.
If the hotfix is available
for download, there is a "Hotfix download available" section at the top of this
Knowledge Base article. If this section does not appear, contact Microsoft
Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. For a complete list of Microsoft Customer Service and
Support telephone numbers or to create a separate service request, visit the
following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that anguage.
Prerequisites
There are no prerequisites for
installing this hotfix.
Restart requirement
You do
not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released
hotfix.
Registry information
To use one of the hotfixes in
this package, you do not have to make any changes to the
registry.
File information
This hotfix may not contain
all the files that you must have to fully update a product to the latest build.
This hotfix contains only the files that you must have to correct the issue
that listed in this article.
The
global version of this hotfix package uses a Microsoft Windows Installer
package to install the hotfix package. The dates and the times for these files
are listed in Coordinated Universal Time (UTC) in the following table. When you
view the file information, the date is converted to local time. To find the
difference between UTC and local time, use the Time Zone tab
in the Date and Time item in Control Panel.
Back to the top
