Transcript Document

Client Deployment Strategies
Greg Wheeler – Team Lead Customer Care
Kevin Perron – ECM Services Project Manager/Business Analyst
Introductions

Greg Wheeler – Team Lead of Technical Support

Kevin Perron – Project Manager
Overview
Overview

Client software deployment analysis


Cutting through the confusion!


What do we need to know before we start?
What OnBase or Kofax clients are we working with?
What system are we working with?

System architecture considerations.

Client deployment options to consider…

Wrap up & Questions
What are we doing here?

You are upgrading your systems, congrats!

You have been given the task of getting the software deployment
strategies mapped out, great!

So where do you start?
ANALYSIS and DOCUMENTATION!
Analysis
Analysis!

What products/licenses/functionality do we own?

More importantly, which parts do we currently use?
Analysis

Are there any upcoming projects expanding the system?

How many systems/environments do we have?
This image shamelessly stolen from
every GeoCities page in the late 1990s.
Analysis


How do you deploy software?

Have you already had a large deployment of client software?

What system do you use to deploy desktop software?
Do you have standard PCs/operating systems (image-based
desktops)?
More analysis…

How many departments/users are we talking about?

How do they access the system?

How are they using the solution?
Consider…

Incremental upgrade

Client interfaces updated by department or business process
What software?
Client confusion?

OnBase

Thick client / Configuration

Web Client

Unity Client

Application Enabler

OnBase Desktop

Outlook integration

Office Business applications

Report Services

SharePoint integrations

Document Composition

…
Client confusion?

Kofax

VRS Elite

Capture

Scan

Quality Control

Validation

Kofax Express

Kofax Transformation Modules

Document Review

Correction

Validation/Validation Thin client?

Kofax Capture Advanced Reports

…
The technical stuff…
Technical Considerations

Software prerequisites

. Microsoft Visual C++ 2010 SP1 Redistributable

.NET Framework 4.0 (Client Profile)Dependencies for legacy software?

Dependencies for legacy software?

For Office Integrations: Hyland Office Integration Dependencies
must be installed (not ClickOnce deployable).

dsoframer.ocx

wiaaut.dll

Microsoft Visual Studio 2010 Tools for Office Runtime (x86) SP1 package
Client side technical considerations

What level of access do users have to install software or update
registry keys?

What anti-virus/security control software is running?
Browser considerations

Internet Explorer browser compatibility?

Dependencies for legacy software?
System Architecture

Where are the users & servers located?

In the same location as the users?

Remote data center?

Multi-location implementation
Topology

What topology are we using?

Client server?

Three tier (n-tier) architecture?

Remote desktop?
Deployment options…
Deployment options - OnBase

Thick Client local installation

MSI customization

“Features” (think Server 2008)
MSI versus EXE

If performing an interactive installation, use the EXE!


Checks prerequisites
If performing a silent installation, use the MSI!

Can be easily deployed via GPO

Allows for silent installation

Does not check prerequisites, so will fail silently
Setup.Exe

If you are running setup.exe silently from the command line you
must use the /q switch and the /CompleteCommandArgs switch,
followed by the required command-line arguments.

/q suppresses the GUI

The complete string of command-line parameters must be
included in double quotes after the /CompleteCommandArgs
switch
Core Enterprise Installers

Used to install almost all OnBase modules
Hyland Server Components

Web Server

Application Server

Diagnostics Console

Document Composition Service

Workflow Timer Service

WorkView Configuration
Hyland Client Components

Unity Client

Outlook Integration

Application Enabler

ActiveX Controls

Report Services

Disconnected Scanning

Document Composition
Hyland Office Products Installers

Office Add-In for Microsoft Word 2007/2010;

Office Add-In for Microsoft PowerPoint 2007/2010;

Office Add-In for Microsoft Excel 2007/2010;

Report Services Excel Add-In for Microsoft Office 2007/2010;

Integration for Microsoft Outlook 2007/2010;

WorkView Integration for Microsoft Outlook 2007;

Document Composition Configuration for Microsoft Office
2007/2010.
Sample Command Line

msiexec /i "Hyland Client Components.msi"
ADDLOCAL=Unity_Client,ReportServices
What can we configure?

APPLICATIONENABLER_FILES

AE_DEFAULTFILE (this is the URL)

AE_SPECIFY_DEFAULTFILE (1 = we are specifying the file)

CREATE_DESKTOP_SHORTCUTS

CREATE_MENU_SHORTCUTS (Start menu)

SERVICE_LOCATION_DATA_SOURCE (ODBC)

SERVICE_LOCATION_DISPLAY_NAME

SERVICE_LOCATION_NT_AUTH (AD authentication)

SERVICE_LOCATION_SERVICE_PATH (application Server)
An Example…

msiexec /i "Hyland Client Components.msi"
ADDLOCAL=Application_Enabler_Client
AE_DEFAULTFILE=“\\FileServer\Apps\ApplicationEnabler\
DefaultFile.xml” AE_SpecifyDefaultFile = 1
OnBase Thick Client

Can install locally

Can run from a network share

Can be run from Citrix/TS
OnBase Web Server

Web Server deployment

ActiveX controls could be deployed via Web Server

Can be preinstalled using Core Installer

Bypasses some ActiveX security issues
OnBase Unity Client

OnBase Unity Client deployment

ClickOnce (Well, maybe ClickTwice)

Can also use MSI deployment

Consider the needs of your organization!
ClickOnce

.NET technology that allows you to easily deploy WinForm and
WPF based Windows applications
ClickOnce

Designed to solve three main IT headaches:

Size and complexity of pushing out applications

Applications requiring local administrator privileges to install

Having to push out updates
*Can be deployed from a web server or network share*
ClickOnce…and Citrix

Can I use Click-Once to deploy OnBase modules to my Citrix
Farm?

This won’t work

Would have to ‘Click-Once” on each server


Settings would not follow user from server to server
500 users? Application will be installed in 500 profiles on each
server
A word of caution

Do not mix standard MSI installation and ClickOnce!

Like crossing the streams, “It would be bad.”
OnBase32.ini

C:\Documents and Settings\All Users\Application Data\Hyland
Software\OnBase32.ini

There are number of things you can pre-set for your users

Obclnt32.exe –INIFILE = “Z:\Windows\onbase32.ini”
Deployment via Group Policy
Client install testing

Setup test workstations (VMs) to represent the various desktops in
use in your environment.

Deploy the packages to verify everything installs correctly.

Test all OnBase/Kofax applications.

Test all other business applications on the PC.

Test integration points (AE, database lookups, etc)
Review
Wrap up

Perform proper analysis

Ask us if you have questions!

Document your findings

Define the install approach, packages, testing approach,
timeline…

Create install package(s)

Test, test, test…

Document procedures for adding new employees.
Questions?