1. Manuals
  2. Brands
  3. VMware Manuals
  4. Software
  5. PACKAGE MANAGER 1.1
  6. Installation and user manual

VMware PACKAGE MANAGER 1.1 Installation And User Manual

Vcenter configuration manager software provisioning components
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
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

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PACKAGE MANAGER 1.1 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for VMware PACKAGE MANAGER 1.1

Summary of Contents for VMware PACKAGE MANAGER 1.1

  • Page 1 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.
  • Page 2 VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.

  • Page 3: Table Of Contents

    Contents About This Book Introduction to VCM Software Provisioning VMware vCenter Configuration Manager Package Studio Software Repository for Windows Package Manager for Windows Overview of Component Relationships Installing the Software Provisioning Components Software Provisioning Requirements Software Provisioning Component Software Requirements...
  • Page 4 Processing Dependencies Security Add Repository Sources Remove Repository Sources Install Packages Remove Packages Package Manager for WindowsCommand Line Options Requirements and Considerations Wasp Command Line Options Maintain Package Manager for Windows Data Package Manager Maintenance Repository Source Maintenance VMware, Inc.

  • Page 5: About This Book

    You also need to fully understand your network’s topology and resource naming conventions. Document Feedback VMware welcomes your suggestions for improving our documentation. If you have comments, send your feedback to docfeedback@vmware.com. Technical Support and Education Resources The following technical support resources are available to you.
  • Page 6 Configuration Manager Software Provisioning Components Installation and User's Guide VMware, Inc.

  • Page 7: Introduction To Vcm Software Provisioning

    Package Manager is configured to use one or more repositories as sources for packages. If you are using the software provisioning components in conjunction with VMware vCenter Configuration Manager (VCM), you can use VCM to add and remove sources, and to install and remove packages.

  • Page 8: Overview Of Component Relationships

    Configuration Manager Software Provisioning Components Installation and User's Guide Overview of Component Relationships The following diagram displays the general relationship between Package Studio, repositories, and Package Manager in a working environment. VMware, Inc.

  • Page 9: Installing The Software Provisioning Components

    Package Studio. Install the repository before installing Package Studio. VMware vCenter Configuration Manager Package Studio: Installed on the same machine as your software repository. Package Manager: Installed on all Windows machines on which you are managing software provisioning.

  • Page 10: Software Provisioning On Guests

    Requires .NET 3.5.1. Software Provisioning on Guests Any virtual machine guest on VMware ESX 3.5 and vSphere 4 (both i and non-i versions) meeting the above requirements can be used for any of the VCM Software Provisioning components.

  • Page 11: Software Repository Structure

    10. Click Finish. The repository and the virtual directory are added to the locations specified during installation. The default location for the repository is C:\Program Files\VMware\VCM\Tools\Repository (on 32-bit machines) or C:\Program Files (x86)\VMware\VCM\Tools\Repository (on 64-bit machines). The default virtual directory SoftwareRepository is added to Internet Information Services (IIS) | Web Sites | Default Web Site.
  • Page 12 Configuration Manager Software Provisioning Components Installation and User's Guide The repository and the VMware vCenter Configuration Manager Package Studio should be installed on the same machine. Prerequisites Target machine meets the supported hardware requirements, operating system, and software requirements. See "Software Provisioning Requirements"...
  • Page 13 29. Open an Internet Explorer window, and then browse to your virtual directory. For example, http://<machinename>/SoftwareRepository. The web page should display the .hive and dists folders. After you publish packages using the VMware vCenter Configuration Manager Package Studio, a crates folder is added.

  • Page 14: Configure Mirrored Repositories

    27. Open an Internet Explorer window, and then browse to your virtual directory. For example, http://<machinename>/SoftwareRepository. The web page should display the .hive and dists folders. After you publish packages using the VMware vCenter Configuration Manager Package Studio, a crates folder is added.
  • Page 15 21. Add the new repository entry to the machine registry. On a 64-bit machine, go to HKEY_LOCAL_ MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\LocalRepositories. On a 32-bit machine, go to HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\LocalRepositories. 22. Right-click LocalRepositories, and then select New | String Value.
  • Page 16 17. Add the new repository entry to the machine registry. On a 64-bit machine, go to HKEY_LOCAL_ MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\LocalRepositories. On a 32-bit machine, go to HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\LocalRepositories. 18. Right-click LocalRepositories, and then select New | String Value.

  • Page 17: Install Package Studio

    Install Package Studio The VMware vCenter Configuration Manager Package Studio and the repository must be installed on the same machine. The process installs the application files and specifies the repository to which Package Studio will publish packages.
  • Page 18 C:\Program Files\VMware\VCM\Tools\Package Studio (on 32-bit machines) or C:\Program Files (x86)\VMware\VCM\Tools\Package Studio (on 64-bit machines). To start Package Studio, select Start | All Programs | VMware vCenter Configuration Manager | Tools | Package Studio, or open the Package Studio folder and double-click PackageStudio.exe.

  • Page 19: Manually Uninstall Package Studio

    The process installs Package Manager application files and the cratecache folder. Package Manager can be run using command line options or using VMware vCenter Configuration Manager. Cratecache is the local folder to which software packages are downloaded before they are installed.

  • Page 20: Manually Uninstall The Package Manager For Windows

    The default location is C:\Program Files\VMware\VCM\Tools. Procedure (unattended using .msi) 1. On your Collector, navigate to C:\Program Files\VMware\VCM\AgentFiles\Products. 2. Locate the PackageManager.msi file, and then copy it to the target machine. 3. On the target machine, run the .msi file using the following command line syntax.

  • Page 21: Using Package Studio To Create Software Packages And Publish To Repositories

    (sqlserver), with Version and Architecture specified in the required fields, the file name is sqlserver_9.00.1399.06_x86.crate. Package Manager uses the specified version when checking if a package is installed, when checking if a dependency is installed, and when uninstalling a package. VMware, Inc.

  • Page 22: Correct Versioning Practices

    Version: (Optional) Provided to allow you to add package versions to the UpstreamVersion based on changes or edits to the base package. For example, you need to modify a command parameter to improve the installation process. Valid Version characters are 0-9, a-z, A-Z, . (period), - (dash), + (plus), and ~ (tilde). VMware, Inc.

  • Page 23: How Package Names And Versions Are Processed By Package Manager

    This metadata is used to determine if the necessary dependencies are in place so that an installation is successful, and if not, what is necessary to make the installation successful. This use of metadata is similar to rpm on Linux. VMware, Inc.
  • Page 24 General Process 1. Start the VMware vCenter Configuration Manager Package Studio. Select Start | All Programs All | VMware vCenter Configuration Manager | Tools | Package Studio.

  • Page 25: Create Packages With Dependencies

    Procedure 1. Start the VMware vCenter Configuration Manager Package Studio. 2. Click Manage Packages. The package configuration tabs appear. 3. On the Properties tab, click the Depends sub-tab.

  • Page 26: Create Packages As Dependency Containers

    In the following procedure, a collection of packages are added to one package to install on a newly configured server. The dependency packages are backuptools, sqlserver, and antivirus. VMware, Inc.

  • Page 27: Specify Package Conflicts

    Using Package Studio to Create Software Packages and Publish to Repositories Procedure 1. Start the VMware vCenter Configuration Manager Package Studio. 2. Click Manage Packages. The package configuration tabs appear. 3. On the Properties tab, click the Depends sub-tab. (Examples of other dependencies, such as Conflicts or Provides are described later and in the online Help.)
  • Page 28 2. In the Package Name text box, type the name of the package. The package name type in the text box must match the name of the package as it exists in the software repositories. 3. Click Add. The value is added to the dependency list. 4. Add other dependencies as needed. VMware, Inc.

  • Page 29: Specify Provides For Packages

    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.

  • Page 30: Add Commands, Arguments, And Scripts To Packages

    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". VMware, Inc.
  • Page 31 Package Studio begins postinst*.*. To see all files, type *.* in the File name text box. Click Open to select the file. The file is renamed postinst.<extension> and is displayed after the Post- Command File label. VMware, Inc.

  • Page 32: Using Signing Certificates With Software Packages

    If you are unfamiliar with certificates, you should have a network administrator who is familiar with certificate management assign you one with a private key. You can publish unsigned packages to repositories, but this is not recommended. VMware, Inc.
  • Page 33 6. Clear or select the Requires Password check box, depending on whether the selected certificate file has a password. If you select the check box, type the password in the text box. 7. Click Select. 8. Review the Package Signature and Security Status area. The following values indicate a successfully VMware, Inc.

  • Page 34: Editing Packages

    2. Use one of the following methods, depending on the type of file with which you want to work: Project (*.prj): a. Click Open. The Choose a project dialog box appears. b. Select the project (*.prj). c. Click Open. The Properties, Files, and Signing tabs now display the settings of the source project. VMware, Inc.
  • Page 35 "About Repository Platforms and Sections" on page 39 for more information. 13. Click Publish. The package is added to the repository. If it published to repository source already added to Package Manager, the package is immediately available for installation. VMware, Inc.

  • Page 36: Create New Package From Existing Projects Or Packages

    (*.crate files), and then click Save. The new version and architecture are automatically appended to the file name. 8. Click the Manage Repositories tab. 9. Select a section in a platform to which you are publishing the package. VMware, Inc.
  • Page 37 "About Repository Platforms and Sections" on page 39 for more information. 13. Click Publish. The package is added to the repository. If it published to repository source already added to Package Manager, the package is immediately available for installation. VMware, Inc.
  • Page 38 Configuration Manager Software Provisioning Components Installation and User's Guide VMware, Inc.

  • Page 39: Using Software Repository For Windows

    Providing consistent naming across all repositories is important to successfully managing multiple repositories and installing packages. For example, you may specify platforms as follows: Any_32 Any_64 Win2k3 Win2k3_32 Win2k3_64 VMware, Inc.

  • Page 40: Sections

    The following example uses the suggested platform organization and a version of the traditional IT software management structure. In VMware vCenter Configuration Manager Package Studio, the platforms and sections displayed on the Manage Repositories tab are based on your [path]\<your repository name>\.hive\repository.toc file. You can edit the file contents directly if you are configuring an initial repository with detailed structure.

  • Page 41: Publish Packages To Repositories

    Using Software Repository for Windows Procedure 1. Start the VMware vCenter Configuration Manager Package Studio. 2. Click the Manage Repositories tab. 3. Select your Repository Host in the drop-down list. 4. Select the Repository in the drop-down list. If you previously added platforms and sections to the repository, the tree view pane will display the names in a tree view.
  • Page 42 The package is added to the selected platforms and sections, and the package information is displayed in the packages list. If the section is identified as a source to the Package Manager or in VCM, the new package is now available. To add sources, see "Add Repository Sources " on page VMware, Inc.

  • Page 43: Using External Software

    This practice ensures that machines where applications are already installed will be properly processed by Package Manager at installation time. If an application has not been defined in the external software list and it was not installed by Package Manager, the following may occur: VMware, Inc.

  • Page 44: Adding Applications To An External Software List

    When creating attributes, make certain that the value entered in the Value text box correctly matches the expected value for the application on the target machines. How Package Manager Processes External Software during Installation When instructed to install a package, Package Manager processes the request in the order described below. VMware, Inc.
  • Page 45 If one or more the attributes do not match, it checks the assigned repository sources for an available package meeting the criteria. 5. Package Manager checks the available package list for a managed software package. VMware, Inc.

  • Page 46: Define External Software Attributes

    Procedure 1. Start the VMware vCenter Configuration Manager Package Studio. The default location on the Collector is C:\[installation location]\VMware\VCM\Tools\Package Studio\PackageStudio.exe. 2. Click External Software. By default, a blank list appears. If you are adding to an existing list, click Open and browse to the existing list you are editing.
  • Page 47 The Publish Options dialog box appears. 13. Select a Repository Host name in the drop-down list. 14. Select a Repository name in the drop-down list. 15. Click Publish. The file is published to your repository in the .hive folder as Repository.options. VMware, Inc.
  • Page 48 Configuration Manager Software Provisioning Components Installation and User's Guide VMware, Inc.

  • Page 49: Using Package Manager For Windows

    The repository source list to which you are adding sources is repository.xml, located in C:\Documents and Settings\All Users\Application Data\VMware\Wasp on each managed machine. Prerequisites The platforms and sections are defined in the repositories for which you are adding sources.

  • Page 50: Remove Repository Sources

    Prerequisites The repository entries exist in repository.xml, located in C:\Documents and Settings\All Users\Application Data\VMware\Wasp. Procedure 1. At the Package Manager command prompt, type wasp listrepository. The currently defined sources are displayed in a list.

  • Page 51: Remove Packages

    Using the command line options, you can manage only one machine at a time. To use the command line options, you must run the commands from the folder where wasp.exe is installed. The default location is C:\Program Files\VMware\VCM\Tools\Package Manager for Windows. VMware, Inc.

  • Page 52: Requirements And Considerations

    2. switches (in any order) 3. command 4. arguments (use double quotes around the argument (for example, "sqlserver >= 9.00.1399.06-b")) Example: wasp /q=y /AllowUnsigned=y install "sqlserver >= 9.00.1399.06-b" Wasp Command Line Options The commands, including arguments and switches, are described below: VMware, Inc.
  • Page 53 Does not download any packages, instead only uses the local cratecache copy. Example: /d=each install notepad . Default value =n. If you use =y, does not stop and prompt after displaying the installation plan. VMware, Inc.
  • Page 54 /overwrite Default value =n. If you use =y, the removal process overwrites any unfinished tasks from the previous command. The value is used only in conjunction with the /q=y value. VMware, Inc.
  • Page 55 Downloads and then uninstalls each package before downloading and uninstalling the next package. none: Does not download any packages, instead only uses the local cratecache copy. Example: /d=all remove notepad Default value =n. If you use =y, VMware, Inc.
  • Page 56 /overwrite Default value =n. If you use =y, the removal process overwrites any unfinished tasks from the previous command. The value is used only in conjunction with the /q=y value. VMware, Inc.
  • Page 57 Example: /d=all autoremove notepad Default value =n. If you use =y, does not stop and prompt after displaying the removal plan. /AllowUnsigned Default value =n. If you use =y, the package is uninstalled even if VMware, Inc.
  • Page 58 Example: wasp /v list all. Output in XML Updated Package Information Table 6-5 Update Command Line Switches and Arguments Command Line Commands Arguments Command Line Switches Comments update Retrieve updated package information from source repositories. No data is displayed after the command. VMware, Inc.
  • Page 59 Runs off of a file named tls.tls. The file's default location is %APPDATA%. List Repositories Table 6-9 Listrepository Command Line Switches and Arguments Command Line Commands Arguments Command Line Switches Comments listrepository Lists all entries in repository.xml. VMware, Inc.
  • Page 60 Format is addrepository bin <repositoryUri> <platformname> <sectionname> where bin specifies the format. Use single or double quotes around the repositoryUri if it contains spaces. Example: wasp addrepository bin http://server/softwarerepository Win7 Release. In this example, the wasp command is also displayed. VMware, Inc.
  • Page 61 0 is first. Remove Repository Table 6-12 Removerepository Command Line Switches and Arguments Command Line Commands Arguments Command Line Switches Comments removerepository Removes an entry from repository.xml RepositoryEntry Format is removerepository bin <repositoryUri> <platformname> <sectionname> VMware, Inc.

  • Page 62: Maintain Package Manager For Windows Data

    Type wasp listrepository. If, when reviewing the list, you need to remove a repository source from the list, type wasp removerepository bin <repositoryUri> <platformname> <sectionname>. See "Remove Repository Sources" on page 50 for more information. VMware, Inc.
  • Page 63 Some packages are installed as dependencies for other packages. You can remove unused dependencies using wasp autoremove. See "Package Manager for WindowsCommand Line Options" on page 51 more about the associated switches. VMware, Inc.
  • Page 64 Configuration Manager Software Provisioning Components Installation and User's Guide VMware, Inc.
  • Page 65 39-40 Package Manager for Windows sections 39-40 Package Studio repository sources packages adding repositories removing manual installation response file;Package Studio naming scripts package package sections repositories 39-40 Package Manager for Windows signing certificates command line options package installing VMware, Inc.
  • Page 66 Configuration Manager Software Provisioning Components Installation and User's Guide software signing certificates package sources, repository adding removing uninstall files package versioning package VMware, Inc.

This manual is also suitable for:

Software repository for windows 1.1Packagemanager 1.1

Table of Contents