OpenInsight 9.2 Workstation Installation - Best Practices (Installation)

Article Overview

Each workstation that accesses an OpenInsight application requires several libraries and supporting MSI packages to be installed. This article presents several methods to prepare new workstations using the ClientSetup.exe program provided in the OpenInsight directory.

 

OpenInsight should be installed and shared from a network folder before following the guidelines listed. If you have not already installed OpenInsight please refer to the installation instructions and then return here to setup additional workstations.

 

Method 1: Manual Installation

Small networks without an active directory domain controller should use this method. It is the easiest option and requires no scripting or silent installations. Simply log into the workstation with administrative rights and launch the ClientSetup.exe that is located in the same directory where you installed OpenInsight. All of the libraries will be installed and any errors during installation will be immediately visible.

 

Method 2: Silent Installation FromScript

Automating the manual installation process will reduce time spent setting up new workstations and prevent inconsistent workstation configurations. If your organization's workstations are setup by hand this method will help automate the setup process. In the nextsection this process will be extended to cover installations from a domain login script.

 

To begin, determine the ClientSetup.exe silent install arguments for your environment. From a command prompt change to your OpenInsight directory and execute"ClientSetup.exe /?" to display the command line arguments for silent installation. See image blow:

 

 

Tip! The the order of the command line arguments should be consistent with the usage example above. Some arguments can be omitted but do not alter the placement order in the parameter string. For argument values with long file names or spaces do not quote the values.

 

Description of arguments:

/SSilent installation flag. If omitted a normal installation will launch.
/FName of start menu folder for shortcuts. Creation of folder can be overridden with the /G argument. Argument is optional. Default value is "OpenInsight Development Suite - Client" if not specified.
/EPath and file name to write the result of the silent install. File will be created if it doesn't exist. Useful for debugging failed silent installs. If omitted no status will be recorded.
/GBoolean argument. Enables or disables creation of the start menu group with the name specified in the /F flag. Default is to create start menu items.
/OPath to folder where oinsight.exe is located. The setup assumes the working directory is were OpenInsight is installed. This setting is required if ClientSetup.exe is not launched from the OpenInsight directory or the current working directory cannot be set.
/DPath to local directory on client where the setup will install required components. Default path if not specified is "C:\Revsoft\OIClient"

 

Command prompt examples:

 

Install from the OpenInsight directory using all default values.

clientsetup.exe /S

 

Install from UNC path.

"\server1\Revsoft\OpenInsight\clientsetup.exe"/S /O=\server1\Revsoft\OpenInsight

 

Install from the OpenInsight directory and suppress start menu.

clientsetup.exe /S /G=0

 

Install from UNC path with all command line arguments specified - no defaults.

"\server1\Revsoft\OpenInsight\clientsetup.exe"/S /F=My OI Application /E=C:\revsoft\ci_result.txt /G=1 /O=\server1\Revsoft\OpenInsight /D=C:\Revsoft\OI Client

 

 

Method 3:Silent Installation fromDomain Login Script

Small and medium networks with a active directory domain controller can silently install the ClientSetup.exe from a domain login script during workstation login. A basic understanding of VB Script is required tocomplete this method. This article assumes you have an existing login script for connecting network resources so it will not cover the setup of a new login script. Users must also have sufficient rights to install software on their local workstation.

 

To begin, determine the ClientSetup.exe silent install arguments for your environment. Please refer to the previous section for examples and usage. You will need these arguments later.

 

Instead of calling clientsetup.exe directly from the login script we will use a helper VB Script routine. This routine will first check to see if the ClientSetup.exe is installed and skip the installation if it already exists.

 

Follow these steps to adapt the scriptto your environment:

 

1.     Download and save "clientsetup9.2loginscript.vbs"to a folder that users can access during login. In our example the"clientsetup92loginscript.vbs" has been saved to"\appserver\apps\scripts\clientsetup92loginscript.vbs".

2.   {{kb0272_2.png}} 

3.    

 

4.     Open the "clientsetup92loginscript.vbs" in your favorite text editor and locate the variable strSilentInstallArgs and replace it with the command line arguments that you previously setup. The screen shot below shows an example.

5.    

 

6.     

7.     Locate the variable strWorkingDirvariable and replace it with the path to the clientsetup.exe.

8.    

 

9.    

10. 

 

11.  Save and close the script.

12. 

 

13.  Edit your login script and add the path and file name for it to your login script. Based on our example the path is:

14. 

 

15.  \appserver\apps\scripts\clientsetup92loginscript.vbs

16. 

 

17.  Note, you may need to specify the script interpreter if it does not execute. Of so, change the line to:

18. 

 

19.  wscript "\appserver\apps\scripts\clientsetup92loginscript.vbs"

20. 

 

21.  Test the login script on a fresh workstation. When completed  a messagewill appear saying the client install succeeded.

22. 

 

23.  Tip: If you don't have a fresh workstation or you want tore-test uninstall the clientsetup.exe. In "Add/Remove Programs"uninstall "OpenInsight Development Suite -Client 9…".

24. 

 

25.  Finally, open the "clientsetup92loginscript.vbs" in your favorite editor and change bSilent to"False". This will prevent the user from seeing any messages except if the installation fails.

26. 

 

You now have a VB Script wrapper to clientsetup.exe that will selectively install only if there is no existing installation.

 

.

 

  • kb/kb_articles/kb0272.txt
  • Last modified: 2024/01/30 13:36
  • by 127.0.0.1