Installing IBM i Access for Windows: Preparing an installation image to install on multiple PCs

Table 1. Methods of deployment
Process you want to follow	Appropriate method of deployment
You apply PTFs to IBM i Access for Windows and your users receive updates from this location. You want users to be able to install System i® Navigator plug-ins at installation time.	Deploy from NetServer Note: Deploy the installation image from NetServer if you follow either of the listed processes.
Copy the installation image to a network share from which end users can install IBM i Access for Windows.	Deploy from a network drive
Use Group Policy Software Installation to deploy on an Active Directory environment.	Deploying on Active Directory using Group Policy
Use Microsoft's Systems Management Server.	Deploy using SMS
You want users to run setup.exe with predefined parameters. You intend to apply different transforms to different users depending on some organizational criteria.	Use batch programs
Use a different deployment tool.	Other deployment methods: Several deployment systems developed by third-party vendors are available. If you are using one of these systems, refer to the documentation provided by your independent software vendor.

Deploying from IBM i NetServer
You might want to deploy the IBM i Access for Windows installation image from IBM i NetServer if you will be applying PTFs to IBM i Access for Windows and your users will be receiving updates from this location. You can also use IBM i NetServer if you want users to be able to install System i Navigator plug-ins at install time. You can create transforms to modify the installation package so that users can install only the functions that are necessary.

Administrative installation image
You can perform an administrative installation of IBM i Access for Windows to create an administrative source image. You can put the image onto the network from which your users can install the application, or you can make it the source of a distribution package if you are using a deployment system.

Deploying from a network drive
You can set up an installation package on a network drive that your users can access.

Using command programs
You can automate the installation process by creating a command (.cmd) file to run setup.exe with predefined parameters. In this situation, users do not need to specify options at the command prompt.

Using remote scheduled tasks
You can use the scheduled tasks function of the Windows operating system with remote access to let your users install and upgrade IBM i Access for Windows, and install service packs, without administrator privileges.

Deploying on Active Directory using Group Policy
Active Directory supports distributing MSI-based applications to remote computers using the Group Policy Software Installation feature. You can create a package for a group of users or computers and then distribute the package to the group members.

Deploying using SMS
If you are using Systems Management Server (SMS) from Microsoft as your deployment method, you can distribute IBM i Access for Windows by creating a new SMS package.

Finding the installation image to be tailored
There are two installation images, based on the type of processor for the PC. There is an image for a 32-bit processor and another image for a 64-bit AMD processor.

Methods to tailor an installation package
You can control which IBM i Access for Windows features your users can install, as well as other settings that customize the behavior of the installation. You can use transforms or command line parameters to do this.

Telling your users how to install
To install IBM i Access for Windows onto their PCs, users run the setup.exe program. If you are using a software deployment method such as Active Directory, the application will be installed automatically on remote computers so you do not need to give users this information.

Windows Installer Policies
You can control the Windows Installer behavior on your client computers by using System Policies for Windows Installer. This lets you configure some settings, like preventing users from installing or uninstalling Windows Installer-based applications, and letting restricted users run installations with elevated privileges.