Scripted Installation

The BusinessPlus setup program supports a scripted install for Administrative Console, CDD, Document Capture, ELF, Workflow Designer, and the ODBC drivers.

A scripted installation will run silently and install applications based upon the choices in the script.ini. However, if a logon is required to boot up the operating system, the installation will stop until a user with administrative privileges logs back on to the PC. If this is a problem, an administrative installation of applicable products should be performed prior to installing the new version of BusinessPlus.

File Setup

A sample script is provided on the installation DVD in the tools\script subdirectory. This script must be edited to provide the correct installation code and key for the applications being installed. The script.ini is used for new installations. Additionally, the script.ini can be used for new installations performed over an old install.

Local Install

In order to run a scripted install, the installation script must be placed in the same directory as the setup.exe. Therefore, the contents of the DVD must be copied to the hard drive and the script file edited and placed in the root directory with the setup executable.

The directories from the DVD that are required for an installation are detailed as follows:

Files from the DVD root

• Btsecapi.dll
• Installpn.dll
• Setup.exe
• Setup.ico

Subdirectories

• dotNET – needed if .Net 4.5 is not installed
• Help – needed for all installs
• NativeDriver – needed for all installs
• Reports – needed on Web server installs only
• Silverlight – needed on all installs
• VC – needed for all installs
• WFModels – needed on Web server installs only

The required files and subdirectories must be copied to a shared location on a hard drive. The script.ini file is then edited and placed in the root directory. When setup.exe is run, the script file is parsed, and the installation is silently performed based upon the options given within the file.

Network Install

If the client PCs are running a network installation of a previous version of BusinessPlus software, the required files and subdirectories should be copied to a directory called "Setup" that is located in the previous installation root on the network. This directory must be named "Setup." For example, if the previous version is installed on a server in a directory named "PowerSchool," the files should be copied to PowerSchool\Setup.

After a new installation into the PowerSchool directory on the server, client PCs will detect the new files and look for a Setup directory to perform a network installation. If a script.ini script is placed in the Setup directory, an upgrade installation will be silently performed on the client PC based upon the PC's currently installed applications and the options chosen in the script.ini script.

Script Options

Codekey
The installation Code and Key are required in order to run any installation based upon the script. If the Code or Key is invalid, a new installation will fail.

Apps
An assignment of "1" will install the application providing the correct Code and Key are given for the specific application. A "0" will skip the installation of the application.

Options
"AUTOREBOOT" may be enabled to force a reboot during a silent install if it is needed. This has two options:
0 = Disabled (default)
1 = Enabled

InstallType
A "COMPLETE" install will put all the files in the local directory specified below on the PC. A "NETWORK" install will run the files from a server.

InstallDir
The "MAINDIR" is the local installation directory and the "REMOTE" is the server installation directory for network installations. 
For new installations, "default" will use <SystemDrive>\Program Files (x86)\PowerSchool for MAINDIR and <SystemDrive> for REMOTE.
Note: Using "default" on a new network installation will set application shortcuts to point to the system drive.

Shortcuts
A 1 will put a shortcut in the root of the start menu for the specific application. A 0 will not put a shortcut in the root of the start menu but shortcuts will still be placed in the PowerSchool program group.

OpenLink
A data source can be created for the Native Drivers as specified in the Datasource1, Datasource2 sections. Any number of data sources can be created as determined by "COUNT" but a Datasource# section must be included for each one.

Datasource
A Datasource# section must be included for each datasource created. The options for each datasource are as follows:
USERDSN Set to 1 for a user DSN or 0 for a system DSN
ODBC_VER Specifies the version of the ODBC driver to install
A = SQL Server Native Driver
DSN Name for the DSN - this can be any name.
DBTYPE Type of database (e.g., "SQL Server")
DB Database name – this must correspond to the name in the connection manager.
HOST Database host name. If the broker is running on a non-standard port this may be specified with the HOST parameter. For example, if the broker were listening on port 5000 then the HOST line would look: HOST="WIN2K:5000"
USER Username
TRUSTED Specify "Yes" if a trusted connection. Specify "No" if NOT a trusted connection.
PASSWORD Specify the password to be used when TRUSTED is set to "No."