1 / 46

Client Deployment Strategies

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

cliff
Download Presentation

Client Deployment Strategies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Client Deployment Strategies Greg Wheeler – Team Lead Customer Care Kevin Perron – ECM Services Project Manager/Business Analyst

  2. Introductions • Greg Wheeler – Team Lead of Technical Support • Kevin Perron – Project Manager

  3. Overview

  4. Overview • Client software deployment analysis • What do we need to know before we start? • Cutting through the confusion! • 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

  5. 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?

  6. ANALYSIS and Documentation!

  7. Analysis

  8. Analysis! • What products/licenses/functionality do we own? • More importantly, which parts do we currently use?

  9. 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.

  10. 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)?

  11. More analysis… • How many departments/users are we talking about? • How do they access the system? • How are they using the solution?

  12. Consider… • Incremental upgrade • Client interfaces updated by department or business process

  13. What software?

  14. 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 • …

  15. Client confusion? • Kofax • VRS Elite • Capture • Scan • Quality Control • Validation • Kofax Express • Kofax Transformation Modules • Document Review • Correction • Validation/Validation Thin client? • KofaxCapture Advanced Reports • …

  16. The technical stuff…

  17. 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

  18. 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?

  19. Browser considerations • Internet Explorer browser compatibility? • Dependencies for legacy software?

  20. System Architecture • Where are the users & servers located? • In the same location as the users? • Remote data center? • Multi-location implementation

  21. Topology • What topology are we using? • Client server? • Three tier (n-tier) architecture? • Remote desktop?

  22. Deployment options…

  23. Deployment options - OnBase • Thick Client local installation • MSI customization • “Features” (think Server 2008)

  24. 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

  25. Setup.Exe • If you are running setup.exe silently from the command line you must use the /q switch and the /CompleteCommandArgsswitch, 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 /CompleteCommandArgsswitch

  26. Core Enterprise Installers • Used to install almost all OnBase modules

  27. Hyland Server Components • Web Server • Application Server • Diagnostics Console • Document Composition Service • Workflow Timer Service • WorkView Configuration

  28. Hyland Client Components • Unity Client • Outlook Integration • Application Enabler • ActiveX Controls • Report Services • Disconnected Scanning • Document Composition

  29. 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; • WorkViewIntegration for Microsoft Outlook 2007; • Document Composition Configuration for Microsoft Office 2007/2010.

  30. Sample Command Line • msiexec /i "Hyland Client Components.msi" ADDLOCAL=Unity_Client,ReportServices

  31. 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)

  32. An Example… • msiexec /i "Hyland Client Components.msi" ADDLOCAL=Application_Enabler_ClientAE_DEFAULTFILE=“\\FileServer\Apps\ApplicationEnabler\DefaultFile.xml” AE_SpecifyDefaultFile = 1

  33. OnBase Thick Client • Can install locally • Can run from a network share • Can be run from Citrix/TS

  34. 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

  35. OnBase Unity Client • OnBase Unity Client deployment • ClickOnce (Well, maybe ClickTwice) • Can also use MSI deployment • Consider the needs of your organization!

  36. ClickOnce • .NET technology that allows you to easily deploy WinForm and WPF based Windows applications

  37. 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*

  38. 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

  39. A word of caution • Do not mix standard MSI installation and ClickOnce! • Like crossing the streams, “It would be bad.”

  40. 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”

  41. Deployment via Group Policy

  42. 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)

  43. Review

  44. 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.

  45. Questions?

More Related