Innovative Solutions for Education Management

www.drakelane.co.uk

4cast Client Specification and Installation

Version 2015.00

10 November 2014

4cast Client Specification and Installation 2 of 10

System requirements The client requires Administrative rights to install (but not to run the application). An overview of the client system requirements are shown below:

Item Minimum Recommended

Operating system Windows XP SP3 Windows 7 or above

Hard disk 250 MB free space

Memory 1 GB 2 GB

Graphics 32-bit graphics with 1024*768 resolution

32-bit graphics with1280*800 resolution

Other .NET Framework 4 Client Profile Note this is downloaded automatically as part of the client install if required or can be downloaded and installed separately beforehand.

Microsoft Excel (or equivalent) Adobe Acrobat Reader (or equivalent) Note that these are optional but will facilitate the viewing of export data on the client.

4cast Client Specification and Installation 3 of 10

Installation The client installer contains digitally signed files:

• Installation bootstrapper : setup.exe • MSI (Microsoft Installer Package) : 4cast 2015.msi

The .NET Framework 4 Client Profile prerequisite can be installed using the wizard during client installation or downloaded and installed separately beforehand from: http://www.microsoft.com/en-gb/download/details.aspx?id=24872 The MSI can be run alone and silently with connection settings for SQL Server set automatically to avoid individual users having to specify the connection manually by using a connection configuration text file (connection.txt).

• An encrypted copy of the configuration file is generated automatically during the server installation.

• Before installing the client, place the configuration file in the same directory as the MSI so that once installed the client application automatically uses the connection configuration.

• During the client installation process the configuration file is installed into the application directory for access by all users.

MSI command-line examples

Install to C:\InstallDirectory in quiet mode with no user interaction. Note that in the 4cast MSI the option APPDIR replaces the standard TARGETDIR. msiexec /i setup.msi /q APPDIR="C:\InstallDirectory" msiexec /package setup.msi /quiet APPDIR="C:\InstallDirectory" Uninstall in quiet mode with no user interaction msiexec /x setup.msi /q msiexec /uninstall setup.msi /quiet For further information on MSI command-line options type msiexec at a command prompt or see: http://msdn.microsoft.com/en-us/library/aa367988.aspx http://msdn.microsoft.com/en-us/library/aa372024.aspx

Remote installation

Undertake remote installation using the MSI for deployment via Microsoft Active Directory or other commercially available tools. Outlined below is a possible method for deploying the client using Group Policy on Microsoft Windows Server.

Create a distribution point The first step in deploying a MSI through GPO is to create a distribution point on the publishing server. This can be done by following these steps:

• Log on to the server as an Administrator user. • Create a shared network folder (this folder will contain the MSI package). • Set permissions on this folder in order to allow access to the distribution package. • Copy the MSI in the shared folder.

4cast Client Specification and Installation 4 of 10

Create a Group Policy object A MSI package is deployed (distributed) through GPO as a Group Policy Object. In order to create an object for your package you can follow these steps:

• Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.

• In the console tree, right-click your domain, and then click Properties. • Click the Group Policy tab, and then click New. • Type a name for this new policy and then press Enter. • Click Properties, and then click the Security tab. • Clear the Apply Group Policy check box for the security groups that you don't want this policy

to apply to. • Select the Apply Group Policy check box for the groups that you want this policy to apply to. • When you are finished, click OK.

Assign an MSI package A package can be assigned per-user or per-machine. Also, if the package is assigned, it will automatically be installed silently. We recommend an assigned deployment type and installing the application at logon. In order to assign a package you can follow these steps:

• Click on the Start button, go to Programs, select Administrative Tools and then select Active Directory Users and Computers

• Right-click your domain name in the console tree and select the Properties context menu • Go to the Group Policy tab, select the object you want and click Edit • Expand Software Settings under Computer (or User) Configuration under Policies • Right-click Software Installation, select the New context menu and then click on Package • In the Open dialog type the full UNC path of the shared package you want to assign • Click on the Open button • Click on Assigned and then click OK (the package will be added to the right pane of the Group

Policy window) • Close the Group Policy snap-in, click OK and exit the Active Directory Users and Computers

snap-in • When the client computers start (or the user logs on), the assigned package will be installed

automatically

Deploying the configuration file The encrypted configuration file can also be deployed with the MSI using the Files preference extension in Group Policy. In order to deploy the configuration file you can follow these steps:

• Click on the Start button, go to Programs, select Administrative Tools and then select Active Directory Users and Computers

• Right-click your domain name in the console tree and select the Properties context menu • Go to the Group Policy tab, select the object you want and click Edit • Expand Files under Computer (or User) Configuration under Preferences • Right-click Files, select the New context menu and then click on File • Select Update from the drop-down list as the action • Select the connection configuration text file as the Source • Enter the path, including the file name, as the Destination

Windows XP clients C:\Program Files\Drake Lane Associates\4cast 2015\connection.txt

4cast Client Specification and Installation 5 of 10

Windows 7 and above clients 64-bit: C:\Program Files (x86)\Drake Lane Associates\4cast 2015\connection.txt 32-bit: C:\Program Files\Drake Lane Associates\4cast 2015\connection.txt

• Click OK (the file will be added to the right pane of the Group Policy window) • Close the Group Policy snap-in, click OK and exit the Active Directory Users and Computers

snap-in • When the client computers start (or the user logs on), the file will be copied automatically

4cast Client Specification and Installation 6 of 10

Standard installation

To start the installation wizard extract all files to the same location and run setup.exe (recommended) or alternatively it is possible to run the MSI alone. If you are using Windows Vista or above you will probably see a User Account Control warning similar to that shown below.

The files are digitally signed by us (the verified publisher) so you can click Yes. Once setup begins simply follow each of the wizard stages through as shown. If you agree to the licence agreement, click Next to continue.

4cast Client Specification and Installation 7 of 10

Select the installation folder.

When you’re ready, click Install to begin the installation.

4cast Client Specification and Installation 8 of 10

Wait for 4cast to be installed. A progress bar is shown.

When complete, click Finish.

4cast Client Specification and Installation 9 of 10

Once installation is complete, an icon will be placed on your Windows desktop and Start menu which you can use to login to 4cast.

The system is installed with the default password Drake for the Administrator user. We suggest that this is changed. Note that passwords are case sensitive.

4cast Client Specification and Installation 10 of 10

Uninstall Use Add/Remove Programs (Windows XP) or Programs and Features (Windows 7) in Control Panel. Alternatively it is possible to run the MSI with the /x or /uninstall command-line parameter.

For remote uninstall using Group Policy remove the software installation package.