1. Silent Installations and PI SDK Redistribution

You will find the following information helpful if you are licensed to re-distribute the PI SDK and wish to package the PI SDK setup within your own installation program. You can install the PI SDK silently if you provide all the information necessary as command arguments (see the previous section "Modifying the Setup Process") and if the required system components are already installed and of the proper version.

The PI SDK setup validates that the following system components are installed:

Because setup.exe is a wrapper program that launches other install modules, those modules may provide a user interface or request a reboot outside the control of setup.exe. Therefore, for a silent install you must be certain these modules are already installed. Your current configuration management may already mandate their presence or you may write detection code in your setup. The setup executables for installing these modules are delivered via the OSIsoft Prerequisite Installation Kits http://techsupport.osisoft.com/Products/Prerequisite+Kits/

Note several prerequisite modules often require a reboot to complete installation. The delivered setup program handles this reboot and setup.exe restarts automatically but if you are writing your own setup you need to handle this situation.

Be sure to check the version of the PI SDK already on the end user's machine. If the version of PI SDK on the user's machine is less than that contained in the pisdk.msi then run:

msiexec.exe /i pisdk.msi

The setup wrapper program displays an initial dialog indicating the status of all the setup modules it will install or upgrade (SUPPRESSHEADERMESSAGE). There is also a final dialog indicating completion of the setup (SUPPRESSCOMPLETIONMESSAGE). Additionally, error messages may generate a dialog box (SUPPRESSDIALOGS). In the setup.ini file, optional settings under the SETUPKIT section may be used to suppress these dialogs. The settings should be set to


Known issues with Various Operating Systems

Windows 2008

Due to current limitations in the Microsoft implementation of Role Management, Microsoft's .NET Framework 3.0 or later comes installed, but not preconfigured on Windows 2008. If .NET Framework 3.0 or later is not configured before running the OSI prerequisites kit, the presence of .NET on the target platform will cause the OSI prerequisite kit to fail prematurely, not installing all required parts (and therefore, preventing the PI SDK from installing correctly).

To properly configure .NET Framework 3.0 or later on Windows 2008, go to Control Panel\Administrative Tools\Server Manager. Within the Server Manager, select the "Features" option on the left hand frame. Select "Add Features" on the right hand side of the "Features" frame. Within the "Add Features Wizard", select the check box for your version of .NET Framework (for example, ".NET Framework 3.0 Features"). Click the "Next" button to get to the confirmation screen, and then click the "Install" button to confirm the installation. Close the dialog and Server Manager application once the .NET Framework Features installation is finished.

Windows Vista and later

Due to the implementation of side by side run time distributions in Vista and later operating systems, an update to the runtime libraries, and in particular ATL, may prevent the PISDK COM libraries from registering. If the pisdk.msi is run by itself, and the included merge module updates to the Microsoft runtime libraries must be updated, then the Windows side by side components cannot be used in the same install session, thus generating the registration errors. This is mitigated by installing the runtimes libraries before the PISDK Windows installer package in the setup sequence.

This WinSxS (side by side) issue may be by passed by ignoring the error reports (do not exit setup) and repairing the installation after completing the setup.

Enabling Operational Intelligence