PushInfoPrint Manager to a remote system (unattended)

Important: The push installation method can seriously compromise network security if you are including principal passwords in the response files. If network security is a concern for you and if passwords are required to install InfoPrint on your systems, you should use Pull InfoPrint Manager to a remote system (unattended).
  • You must be authorized to execute commands remotely for a "push" installation to work properly.
  • The rshd and rexecd daemons must be running on the remote system to execute the remote installation scripts.
  • Configuring the rshd and rexecd daemons requires a system administrator and might impact your network security.

To perform an unattended remote push installation:

  1. Set up the InfoPrint Manager software server by following the instructions in Configuring the InfoPrint Manager software server.
  2. You must have the authority to open remote shells on each remote or target system. The root user must appear in the .rhosts file in root's home directory on each remote system (enter cd ~ to discover root's home directory). You might have to create the .rhosts file. If a .rhosts file already exists, make sure that it contains host information like 2.2 below, and then go to step 3. To create the .rhosts file, make sure that you are in root's home directory on the remote system and do this:
    1. Create the file in VI : vi .rhosts
    2. Add this line to the file: hostname usernamewhere hostname is the name of the InfoPrint Manager software server from which you are accessing the remote system, and username is your user name on the InfoPrint Manager software server. For example, if the InfoPrint Manager software server's name is linus, and you log on as root, you would enter:linusroot
    3. Save the file:
      1. Press the Escape key to clear VI's mode.
      2. Type :wq and press Enter. This will save the file and exit VI.
  3. From the InfoPrint Manager software server from which you want to push the software:
    1. Update the .netrc file in root's home directory (enter cd ~ to discover root's home directory). You might have to create this file (see the VI example above to create this file). The .netrc file should contain this:machineremote_target_serverlogin useridpassword password

      where remote_target_server is the remote or target AIX server to which you want to push the software. Supply the userid of root and root's password.

    2. From root's home directory on the InfoPrint Manager software server, specify this at the AIX command line to set the necessary permissions on the .netrc file:
      chmod 700 .netrc
    3. Copy the /ipin_response file from the /ip_remote/templates directory to the /ip_remote/auto directory by specifying this command:
      cp /ip_remote/templates/ipin_response /ip_remote/auto/remote_target_server
      where remote_target_server is the name of the target server. Do this once for each machine that you want to configure.

      For example, assume /ip_remote/auto has these contents:

      /ip_remote/auto/server1
      /ip_remote/auto/linus.east
      /ip_remote/auto/node5

      Note: The response file names above are just examples. The response files can have any file name that you want.

    4. Modify the first line of the response files to reflect the correct host names. Change hostname=ipmserver to hostname=remote_target_server, where remote_target_server is the name of the remote system to which you want to push the installation. For the purposes of our example, the server1 response file host name line would become hostname=server1.
  4. Log in to the remote or target system as root.
    1. Create the /ip_remote directory on the target system: mkdir /ip_remote.
    2. Mount the InfoPrint Manager software server as an NFS file system:
      mount Infoprint_Manager_software_server_hostname:/ip_remote /ip_remote
  5. Initiate a concurrent remote unattended install on your target systems by specifying this command:
    /ip_remote/remote_install -m
    If you have elected to give the /ip_remote file system a different mount point, you must use the optional -s flag to identify it.

Note: For troubleshooting information about the installation process, refer to the specific /var/log/pd/install/*.wlog files.