User manual VMWARE PACKAGE MANAGER 1.1

DON'T FORGET : ALWAYS READ THE USER GUIDE BEFORE BUYING !!!

If this document matches the user guide, instructions manual or user manual, feature sets, schematics you are looking for, download it now. Diplodocs provides you a fast and easy access to the user manual VMWARE PACKAGE MANAGER 1.1. We hope that this VMWARE PACKAGE MANAGER 1.1 user guide will be useful to you.


VMWARE PACKAGE MANAGER 1.1 : Download the complete user guide (707 Ko)

Manual abstract: user guide VMWARE PACKAGE MANAGER 1.1

Detailed instructions for use are in the User's Guide.

[. . . ] vCenter Configuration Manager Software Provisioning Components Installation and User's Guide Package Studio 1. 1 Software Repository for Windows 1. 1 Package Manager 1. 1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www. vmware. com/support/pubs. EN-000455-00 vCenter Configuration Manager Software Provisioning Components Installation and User's Guide You can find the most up-to-date technical documentation on the VMware Web site at: http://www. vmware. com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware. com © 2006-2010 VMware, Inc. VMware products are covered by one or more patents listed at http://www. vmware. com/go/patents. [. . . ] For example, you create a package for McAfee (mcafee) where the Provides tab is configured with the logical package name of antivirus and the Conflicts is configured with norton. You then create a package for Norton (norton) where the Provides tab is configured with the logical package name of antivirus and the Conflicts tab is configured with mcafee. You now have two packages configured to provide anitvirus as a logical package. Now, when you create a Cisco VPN package (cisco-vpn), which requires some form of antivirus be installed first, you specify antivirus >= 0 on the Depends tab. During the installation of the cisco-vpn package, the process first checks dependencies. If no antivirus package is identified, it checks installed packages to determine if any provide antivirus. If found, it considers the antivirus Depends criteria has been met and installs. If not found in any installed packages, it reviews the repository packages for a package named antivirus. If not found, the installation stops and a message tells you that cisco-vpn depends on antivirus, and antivirus could not be found. You install mcaffee or norton, and then retry the install of cisco-vpn. This time the cisco-vpn install will find the provided antivirus and the installation will continue. VMware, Inc. 29 vCenter Configuration Manager Software Provisioning Components Installation and User's Guide Procedure 1. In the Package or Logical Package text box, type the name of the package or functionality type. Although the text box allows you to use mixed case, the dependencies and conflicts will process only lower-case names. Add other Provides as needed. Add Commands, Arguments, and Scripts to Packages To use Package Manager to install and remove packages, you must configure the Files tab with the appropriate commands, arguments, and optional pre- and post-command scripts to be run before and after the installation command. Consult the documentation issued for the application for which you are creating a package when configuring the Files tab options. Referencing Response Files Using System Environment Variables Some software installations require a response file during the install process. To accommodate the need for a response file you can add the %CrateWorkingDirectory% system variable to your arguments when you configure the installation and removal options. For example, you are creating a package where the . msi requires a response file named settings. ini. You include the settings. ini file in your Project Data Directory files, and then configure the Arguments with the correct reference. In this example, the Argument is /q settings="%CrateWorkingDirectory%\Data\settings. ini". The value %CrateWorkingDirectory%\Data\ is required, after this value you add any subdirectories that exist in your Project Data Directory. For example, the settings. ini may be in a folder named InstallSettings, in which case the argument is /q settings="%CrateWorkingDirectory%\Data\InstallSetting\settings. ini". 30 VMware, Inc. Using Package Studio to Create Software Packages and Publish to Repositories When the package begins installing, the referenced files are downloaded to the target machine's TEMP directory, and then processed by the . msi. Referencing License Files The use of license files in the package command line options varies between applications. Some can be referenced in a shared location, using the system environment variables described above, or included in a . bat file, while others may be applied on a user-by-user basis. [. . . ] The file's default location is %APPDATA%. List Repositories Table 6-9 Listrepository Command Line Switches and Arguments Commands Command Line Arguments Command Line Switches Comments listrepository Lists all entries in repository. xml. VMware, Inc. 59 vCenter Configuration Manager Software Provisioning Components Installation and User's Guide Add Repository Table 6-10 Addrepository Command Line Switches and Arguments Commands Command Line Arguments Command Line Switches Comments addrepository Adds an entry to the end of the list in repository. xml. Default location is C:\Documents and Settings\All Users\Application Data\VMware\Wasp. RepositoryEntry Format is addrepository bin <repositoryUri> <platformname> <sectionname> where bin specifies the format. Use single or double quotes around the repositoryUri if it contains spaces. [. . . ]

DISCLAIMER TO DOWNLOAD THE USER GUIDE VMWARE PACKAGE MANAGER 1.1




Click on "Download the user Manual" at the end of this Contract if you accept its terms, the downloading of the manual VMWARE PACKAGE MANAGER 1.1 will begin.

 

Copyright © 2015 - manualRetreiver - All Rights Reserved.
Designated trademarks and brands are the property of their respective owners.