- Sql anywhere 12 client deployment how to#
- Sql anywhere 12 client deployment install#
- Sql anywhere 12 client deployment Pc#
- Sql anywhere 12 client deployment mac#
In either case, /Q suppresses the completion message. Q can be used during the initial deployment and on subsequent invocations of the script when applying updates. To suppress the deployment completion message, specify the /Q parameter on the installation script during deployment. For example:įurther details about using / AdminConfig are described in Chapter 1. AdminConfig allows the features to be pre-selected by an administrator before deployment so that the user is not prompted to select the features during deployment. To prevent the prompts for selecting the features that occur during deployment, you need to customize the deployment using the /AdminConfig parameter.
Sql anywhere 12 client deployment install#
To deploy IBM i Access Client Solutions in silent mode using the provided install scripts, the following three items need to be silenced to prevent user interaction during deployment: While experimenting with various deployment options, you can start over by removing the product files and configuration.
Sql anywhere 12 client deployment mac#
Propagate a specific configuration to other users.ĭeploy IBM i Access Client Solutions on a flash drive and use it on any PC.Ĭustomize a deployment for Linux and Mac users with / AdminConfig.
Sql anywhere 12 client deployment Pc#
Here are the additional deployment options covered in this article:ĭeploy a predefined configuration for a single user and prevent the user from getting prompted, including not being prompted to accept the End-User License Agreement (EULA).Īccept End-User License Agreement (EULA) for all users on a multi-user PCĪccept the EULA for all users on a multi-user PC so they are not prompted the first time they start IBM i Access Client Solutions.Ĭhange the location where the product files get deployed on the PC.Ĭhange the location where the user’s configuration is stored. You can pick and choose the ones that suit your requirements.
To avoid being repetitive, all the various combinations are not detailed in this article. Many of the deployment options mentioned in this article can be used in combination with those just described and with each other.
Sql anywhere 12 client deployment how to#
The QuickStartGuide contains instructions about how to customize and deploy IBM i Access Client Solutions on a multi-user PC on Windows using the install_acs_xx_allusers.js deployment scripts.įor a deployment that copies the product files to a user’s PC that was previously customized by an administrator to only include specific features, see Chapter 1, Option 2: Local and Admin Customized.įor a deployment that does not copy the product files to a user’s PC and instead uses them from a remote location that has been previously customized by an administrator to only include specific features, see Chapter 1, Option 3: Remote and Admin Customized. As a variation of this option, you may also choose to deploy the product from a central location as mentioned in Chapter 1, Option 1: Local and User Customized. Single User PC The QuickStartGuide contains instructions about how a single user can deploy and customize IBM i Access Client Solutions on Microsoft Windows, Macintosh, or Linux systems.The following deployment options were covered in Chapter 1: Summary of deployment options mentioned in Chapter 1 For example, I am going to assume you know how to do an Admin Customized configuration using the install scripts with the /AdminConfig parameter as mentioned in that article. I’m going to assume you’ve read Chapter 1 and are familiar with it because some of the items in this article will reference the types of deployments mentioned there. The purpose of this article is to share some of those answers and provide the steps to implement them. Since that time, a lot of questions about deployment have been asked and answered. It was written a couple of years ago and was called, “ IBM i Access Client Solutions: Customization and deployment made easy“. You are probably wondering, “Where’s Chapter 1 ?” It wasn’t actually called Chapter 1 at the time.