Typically the installer will be on the LaborPower server in the Admin\Client directory.  The server is expected to have a Share named LaborPower with the following directory structure needed by the installer:

Default Server directory structure:

\\<LaborPowerServer>
    \LaborPower    (network share)	
        \Admin
            <lp_app>.exe & other files
            \Client
                LaborPowerSetup.exe
                install.ini
                \LaborPowerPDF
                	Setup.exe & associated files


It is important to grant Authenticated Users Read/Write permissions for both the Share and file system.

The Generic LaborPowerWorkstation.exe installer requires an install.ini file to be placed in the same directory as the installer exe.

The install.ini file should be in the following format:

	[Data]
	DatabaseServer=<laborpower server name> (no back slashes!)

	[App]
	AppName=<display name>
	Exe=LPIBEW.EXE
	DefaultDir=C:\Program Files\
	ShareName=LPDues       		(optional, default LaborPower)

Example:

	[Data]
	DatabaseServer=nooksack

	[App]
	AppName=SEA

Custom Directory Stucture:

In order to support multiple LaborPower apps on the same server, a custom server path can be specified by adding the [App] ServerDir= value to the install.ini file:

[App]
ServerDir=Referral\Admin
ShareName=LaborPower

In this example with nooksack as the data, the Vercheck.ini file will then be configured as

SOURCEPATH=\\nooksack\LaborPower\Referral\Admin

Add 

[App]
DefaultDirOnly=True

To supress the \WSI\<AppName>\App path from the installation directory

If the installer detects that the .fbk and/or the app exe's are in the same directory as the installer, it will attempt to restore the DB and put the exe's in the right place.