Skip to Content

A common challenge for Duet implementation teams is developing a process to deploy the required client components to the end users in a production landscape.  Duet has various prerequisites which must be met prior to the installation of the Duet client component. 

I have found it useful to think of the deployment process in 3 phases: I) Validation, II) Pre-Req Component Install, III) Duet Install.

Phases I and II could/should be run prior to the intended Duet deployment to avoid longer deployment events, i.e. installation of .NET, dealing with SP deployments prior to deployment, etc.  Phase III is the actual Duet client installation, this has an external dependency on the group policy updates being available and pushed to the user to utilize some of the parameters from the policy during the install and ensure the client is ready for use once it is installed. 

Phase I: Validation
1.  Hardware *verify with install guide 
  1.1  CPU > 2.4 GHz
  1.2  RAM > 1 GB
  1.3  Disk > 2 GB
2.  Software  
  2.1  OS One of the following OS/SP levels
    2.1.1  Windows XP Professional Edition, Service Pack 2 (SP 2) or Service Pack 3 (SP3)
    2.1.2  Windows XP Professional Tablet PC Edition, Service Pack 2 (SP 2) or Service Pack
    2.1.3  Vista Service Pack 1 (SP 1) Business or Enterprise Edition
  2.2  Office One of the following Office/SP levels
    2.2.1  Office System 2003 Professional or Enterprise Edition, Service Pack 3 (SP 3)
    2.2.2  Office Professional Plus 2007 or Office Enterprise 2007, Service Pack 1 (SP 1)

Phase II: Prerequisite Installation
1.  Patches – applied where version exists on client   
  1.1  XP   
    1.1.1  XP Security Patch – Security Update for Windows XP (KB899587) 
  1.2  Office 2003   
    1.2.1  Office Outlook 2003 Hot Fix – KB 945430 
    1.2.2  Update for Office 2003 (KB907417) 
  1.3  Office 2007   
    1.3.1  Office Outlook 2007 Hot Fix – KB 948716 
2.  Other Components   
  2.2  Office Components  
    2.2.1  Install Office 2003 Web Components, must be installed if clients are Office 2003 
    2.2.2  Set to run local – if not already 
      2.2.2.1 “.Net Programmability Support (o11, o12): Word, Excel, Outlook, InfoPath, and Office 2003 Web Components”
      2.2.2.2 Smart Tag .NET Programmability Support
      2.2.2.3 Outlook Message component => Outlook Address Book
  2.3 .NET  Framework
    2.3.1 Install .NET 2.0 (*would be installed by Duet installer) 
    2.3.2 Install .Net 3.0 SP1 (*would be installed by Duet Installer but suggested as pre-deployment item) 
  2.4 Other  
    2.4.1 Vista only – re-register vbscript.dll & jscript.dll via regsvr32.exe 

Phase III: Client Installation
1.  Install Check  
  1.1 User executing has admin rights 
  1.2 Office Applications stopped, if not dialog to close, processes below 
    1.2.1  WINWORD.EXE
    1.2.2  EXCEL.EXE
    1.2.3  MSACCESS.EXE
    1.2.4  POWERPNT.EXE
    1.2.5  OUTLOOK.EXE
    1.2.6  INFOPATH.EXE
    1.2.7  COMMUNICATOR.EXE
    1.2.8  MSPUB.EXE
    1.2.9  ONENOTE.EXE
    1.2.9  GROOVE.EXE
2.  Client Install  
  2.1   Duet Installation –  Options (key items to define in script or via group policy) 
    2.1.1 TRUSTED_SENDERS – configure this via group policy
    2.1.2 READSERVICE_URL – set to Duet Server read service URL, can be defined in Group Policy rather than install
    2.1.3 “PATH – local install path, default is %systemdrive%\\Program Files\Microsoft
Information Bridge\1.8\Framework”
    2.1.4 CHECK_SERVICE_URL – set to YES to force validation, not required in script
    2.1.5 ACCEPT_EULA – set to YES to accept terms
   2.2 Duet Install Error Codes to Catch 
     2.2.1 Error_DOTNETINSTALLFAILURE, Error_OWC11INSTALLFAILURE, Error_SQLINSTALLFAILURE, Error_VSTOINSTALLFAILURE
  2.3 Install Duet 1.5 SP1 Hot Fix (HF2)
3.  Post Install  
  3.1  Start Duet Utility 
  3.2  Client Deployment – metadata download 
  3.3  Trusting infopath forms as required 
  3.4  Potential need to trust addinloader.dll 

Sample Script 
A sample deployment script is available as a starting point to develop your own deployment script to fit your individual landscape and deployment requirements.  This is only a sample for starting your own script to fit your specific needs.  This sample script can be downloaded from the following link – download.  Thanks to the development team for providing a starter sample script.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply