VMware PACKAGE MANAGER 1.1, Software Repository for Windows 1.1 Installation And User Manual

Download

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

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

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.

VMware, Inc.

3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

2 VMware, Inc.

Contents

About This Book 5

Introduction to VCM Software Provisioning 7

VMware vCenter Configuration Manager Package Studio 7 Software Repository for Windows 7 Package Manager for Windows 7 Overview of Component Relationships 8

Installing the Software Provisioning Components 9

Software Provisioning Requirements 9

Software Provisioning Component Software Requirements 9 Software Provisioning on Guests 10

Install Software Repository for Windows 10

Software Repository Structure 11 Manually Uninstall the Repository 11 Manually Configure Repositories 11 Configure Mirrored Repositories 14

Install Package Studio 17

Manually Uninstall Package Studio 19

Installing Package Manager for Windows 19

Manually Uninstall the Package Manager for Windows 20

Using Package Studio to Create Software Packages and Publish to Repositories 21

About Package Naming and Versioning 21

Correct Naming Practices 21 Correct Versioning Practices 22 How Package Names and Versions Are Processed by Package Manager 23

Creating Packages 23

Create Packages with Dependencies 25 Create Packages as Dependency Containers 26 Specify Package Conflicts 27 Specify Provides for Packages 29 Add Commands, Arguments, and Scripts to Packages 30

Using Signing Certificates with Software Packages 32

About Signing Certificates and Installing Software Packages 32 Sign Packages with Certificates 32

Editing Packages 34

Edit Published Packages 34 Create New Package from Existing Projects or Packages 36

Using Software Repository for Windows 39

About Repository Platforms and Sections 39

Platforms 39 Sections 40

Sample Platforms and Sections 40 Add Platforms and Sections to Repositories 40 Publish Packages to Repositories 41

Using External Software 43

VMware, Inc. 3

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

About External Software 43

Best Practices 43

Adding Applications to an External Software List 44

Managing External Software Lists 44

Naming External Software Packages 44

Defining Attributes 44

How Package Manager Processes External Software during Installation 44 Define External Software Attributes 46

Using Package Manager for Windows 49

Processing Dependencies 49 Security 49 Add Repository Sources 49

Remove Repository Sources 50 Install Packages 50 Remove Packages 51 Package Manager for WindowsCommand Line Options 51

Requirements and Considerations 52

Wasp Command Line Options 52 Maintain Package Manager for Windows Data 62

Package Manager Maintenance 62

Repository Source Maintenance 62

4 VMware, Inc.

About This Book

This manual, vCenter Configuration Manager Software Provisioning Components Installation and User's Guide, describes how to install the components, use the components to create software packages, publish packages to repositories, and install software on target machines.

Intended Audience

To use the information in this guide effectively, you must have a basic understanding of how to configure network resources, install software, and administer operating systems. 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. To access the current version of this book and other books, go to http://www.vmware.com/support/pubs.

Online and Telephone Support

To use online support to submit technical support requests, view your product and contract information, and register your products, go to

http://www.vmware.com/support.

Customers with appropriate support contracts should use telephone support for priority 1 issues. Go to http://www.vmware.com/support/phone_support.html.

Support Offerings To find out how VMware support offerings can help meet your business needs,

go to http://www.vmware.com/support/services.

VMware Professional Services

VMware Education Services courses offer extensive hands-on labs, case study examples, and course materials designed to be used as on-the-job reference tools. Courses are available onsite, in the classroom, and live online. For onsite pilot programs and implementation best practices, VMware Consulting Services provides offerings to help you assess, plan, build, and manage your virtual environment. To access information about education classes, certification programs, and consulting services, go to http://www.vmware.com/services.

VMware, Inc. 5

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

6 VMware, Inc.

Introduction to VCM Software Provisioning

The VCM Software Provisioning components consist of VMware vCenter Configuration Manager Package Studio, software package repositories, and Package Manager.

VMware vCenter Configuration Manager Package Studio

Package Studio is the application used to build software packages for installation on target Windows servers and workstations.

A software package provides the files and metadata necessary to install and remove programs. One of the most useful features of a package is the metadata regarding dependencies, conflicts, and other relationships that are not represented by software installation files. 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.

Packages support commercial and custom software that may be installed using any installation technology, including .msi, .exe, or scripts (Python, VBScript, PowerShell, and others).

Once a package is created and ready for distribution, it is published to a software repository. You use Package Manager to download the package from the repository to the local machine and install it on your Windows systems.

Software Repository for Windows

Software Repository for Windows is the shared location to which packages are published by Package Studio and the location from which Package Manager downloads packages for installation.

Package Manager for Windows

Package Manager is the application installed on each machine to manage the installation and removal of the software contained in packages. 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.

VMware, Inc. 7

Overview of Component Relationships

The following diagram displays the general relationship between Package Studio, repositories, and Package Manager in a working environment.

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

8 VMware, Inc.

Installing the Software Provisioning Components

The software provisioning components should be installed on machines with the following relationships:

Software Repository for Windows: Installed on at least one Windows machine in your environment, and installed on the same machine with 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.

To uninstall the above applications using a script at a later date, you should save a copy of each of the .msi files in an archive location. To uninstall using the .msi, you must have the same version used to install the application.

Software Provisioning Requirements

VCM Software Provisioning provides the components to create software provisioning packages, publish the packages to repositories, and then install and remove software packages on target machines.

The following operating systems are supported platforms:

Supp orted Operating System Supp orted Hardware Platform

Microsoft Windows 7 x86, x64

Microsoft Windows Server 2008 R2 x64

Microsoft Windows Server 2008 SP2 x86, x64

Windows Vista SP2 x86, x64

Microsoft Windows XP SP3 x86

Microsoft Windows XP SP2 x64

Microsoft Windows Server 2003 R2 SP2 x86, x64

Microsoft Windows Server 2003 SP2 x86, x64

Table 2-1 Software Provisioning Operating System and Hardware Requirements

Software Provisioning Component Software Requirements

The following are the VCM Software Provisioning components and their software requirements:

VMware, Inc. 9

VMware vCenter Configuration Manager Package Studio: The application used to the create the software packages. Requires .NET 3.5.1.

Software Repositories: The file system used to store the shared software packages. Requires .NET 3.5.1 and IIS 6, 7, or 7.5.

Package Manager: The application on each managed machine that downloads packages from repositories, and then installs and removes the software contained in the packages. 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.

Install Software Repository for Windows

The Software Repository for Windows and the VMware vCenter Configuration Manager Package Studio should be installed on the same machine. The process installs the Repository folders and subfolders, and configures the virtual directory. The virtual directory is used by Package Manager to access the repository.

Prerequisit es

Target machine meets the supported hardware requirements, operating system, and software requirements. See "Software Provisioning Requirements" on page 9 for currently supported platforms and requirements.

Access to the Repository.msi, which is available on the VMware website or in the vCenter Configuration Manager application files.The default location in the VCMapplication files is C:\Program Files\VMware\VCM\AgentFiles\Products.

Procedu re

1. Double-click Repository.msi.

The Welcome page appears.

2. Click Next.

The License Agreement page appears.

3. Review the agreement, and then select I accept the terms of the License Agreement to continue. The

other options become available.

4. Select I am an authorized agent and/or representative of the customer/end-user and I have read the terms and conditions stated above.

5. Click Next.

The Installation Folder page appears.

6. Use the default path or click Change to modify the path. When the path is correct, click Next.

The Virtual Directory page appears.

7. Use the default name or type a new name in the text box.

8. Click Next.

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

10 VMware, Inc.

The Ready to Install page appears.

9. Click Install.

When the installation is completed, the Setup Complete page appears.

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.

Procedu re (u nat ten ded using .msi)

1. On your Collector, navigate to C:\Program Files\VMware\VCM\AgentFiles\Products.

2. Locate the Repository.msi file, and then copy it to the target machine. You can also run it from a shared location.

3. On the target machine, run the .msi file using the following command line syntax.

msiexec /i [path]\Repository.msi /qn /l*v %temp%\Repository.log

You can add the following arguments if you want to specify locations other than the default directories:

REPOSITORY_ROOT="C:\Program Files\VMware\VCM\Tools\Repository\" (defaults to this path)

VIRTUAL_DIR_NAME_REPOSITORY=SoftwareRepository (defaults to this value)

Software Repository Structure

The files for a repository consist of the main folder (for example, SoftwareRepository). In this file are the following:

.hive: Contains the repository management files, including such files as repository.index and repository.toc.

crates: Contains alphabetical sub folders. It is to this location that the packages (.crate files) are published.

dists: Contains crates.gz files. These files are metadata about the .crate files.

Manually Uninstall the Repository

Use the following script to run an unattended uninstall the software repository. To uninstall the application, you must use the version of the Repository.msi that was used to install the application.

Procedu re

1. Copy the Repository.msi to the machine on which you are uninstalling the application or point to the file in a shared directory.

2. Run the .msi file using the following command line syntax:

msiexec /x [path]\Repository.msi /l*v %temp%\Repository.log

Manually Configure Repositories

Although you can use an installation file to install a repository on a machine, it may be necessary to manually create one.

Installing the Software Provisioning Components

VMware, Inc. 11

The repository and the VMware vCenter Configuration Manager Package Studio should be installed on the same machine.

Prerequisites

Procedure for IIS 6

NOTE The steps for configuring a repository on Windows Vista, Windows 7, and Windows 2008 are different from the ones provided here. See below.

1. Create a repository directory on your desired drive. For example, C:\WindowsRepository.

2. Open Internet Information Services (IIS) Manager.

3. Expand <machine name> >Web Sites.

4. Right-click Default Web Site, and then select New > Virtual Directory. The Welcome to the Virtual Directory Creation Wizard appears.

5. Click Next. The Virtual Directory Alias page appears.

6. Type a name in the Alias text box. For example, SoftwareRepository.

7. Click Next. The Web Site Content Directory page appears.

8. Click Browse and locate the repository directory you previously created. For example, C:\WindowsRepository.

9. Click Next. The Virtual Directory Access Permissions page appears.

10. Select Read, Run scripts, and Browse.

11. Click Next. The You have successfully completed the Virtual Directory Creation Wizard page

appears.

12. Click Finish. The new repository virtual directory alias is added to the Default Web Sites list.

13. Right-click the new repository directory, and then select Properties.

The <directory name> Properties dialog box appears.

14. Click the Virtual Directory tab, and then click Remove, located to the right of Application name text box. Application name and Application pool are disabled.

15. Click the HTTP Headers tab, and then click MIME Types. The MIME Types dialog box appears.

16. Click New. The MIME Type dialog box appears.

17. Add the following MIME types with these names and settings:

Extension: .crate and MIME type: application/octet-stream

Extension: .index and MIME type: application/octet-stream

Extension: .gz and MIME type: application/octet-stream

Extension: .options and MIME type:application/octet-stream

Extension: .info and MIME type:application/octet-stream

18. Click OK to save your settings and close the MIME Types dialog box.

19. On the Properties dialog box, click OK to close the dialog box.

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

12 VMware, Inc.

20. Open a Command Prompt window, and then browse to the repository folder you previously created.

21. At the command prompt, type mkdir .hive, and then press Enter.

22. At the command prompt, type mkdir dists, and then press Enter.

23. Open a blank document in a text editing application, such as Notepad, and then add <RepositoryIndex></RepositoryIndex> to the contents.

24. Click File > Save As. The Save As dialog box appears.

25. Change the file name to repository.index, and then save the file in the previously created .hive folder.

26. Open a blank document in a text editing application, such as Notepad. Do not add any text.

27. Click File > Save As. The Save As dialog box appears.

28. Change the file name to repository.info, and then save the empty file in the previously created .hive folder.

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.

Procedure for IIS 7 and later

1. Create a repository directory on your desired drive. For example, C:\WindowsRepository.

2. Open Internet Information Services (IIS) Manager.

3. Expand <machine name> > Sites.

4. Right-click Default Web Site, and then select Add Virtual Directory. The Add Virtual Directory

dialog box appears.

5. Type a name in the Alias text box. For example, SoftwareRepository.

6. Click the Physical path ellipsis button. The Browse for Folder dialog box appears.

7. Browse for and select the repository directory you previously created. For example, C:\WindowsRepository.

8. Click OK to close the Browse for Folder dialog box.

9. Click OK to close the Add Virtual Directory dialog box.

10. Select the new virtual directory you just added, and then double-click Directory Browsing in <yourdirectoryname> Home pane. The pane displays Directory Browsing.

11. In the Actions pane, click Enable.

12. Click Back until you are again on the <yourdirectoryname> Home pane, and then click on MIME Types. The pane displays MIME Types.

13. In the Actions pane, click Add. The Add MIME Type dialog box appears.

14. Add the following MIME types with these names and settings:

File name extension: .crate and MIME type: application/octet-stream

File name extension: .index andMIME type: application/octet-stream

File name extension: .options and MIME type:application/octet-stream

File name extension: .info and MIME type:application/octet-stream

15. Close IIS.

Installing the Software Provisioning Components

VMware, Inc. 13

16. Open a Command Prompt window, and then browse to the repository folder you previously created.

17. At the command prompt, type mkdir .hive, and then press Enter.

18. At the command prompt, type mkdir dists, and then press Enter.

19. Open a blank document in a text editing application, such as Notepad, and then add <RepositoryIndex></RepositoryIndex> to the contents.

20. Click File > Save As. The Save As dialog box appears.

21. Change the file name to repository.index.

22. Change the Save as type to All Files, and then save the file in the previously created .hive folder.

23. Open a blank document in a text editing application, such as Notepad. Do not add any text.

24. Click File > Save As. The Save As dialog box appears.

25. Change the file name to repository.info.

26. Change the Save as type to All Files, and then save the file in the previously created .hive folder.

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.

Configure Mirrored Repositories

Mirrored repositories are configured where one repository is mirrored from another.

The most common use of mirrored repositories is if you have a repository in your main office and one in your satellite office. You do not want to install packages to machines in the satellite office across your wide area network. Configuring a mirrored repository will reduce the strain on your WAN, allowing the satellite office machines to install packages from a local repository.

Prerequisites

Procedure for IIS 6

NOTE The steps for configuring a repository on Windows Vista, Windows 7, and Windows 2008 are different from the ones provided here. See below.

1. Create a repository directory on your desired drive. For example, C:\WindowsRepository.

2. Open Internet Information Services (IIS) Manager.

3. Expand <machine name> >Web Sites.

4. Right-click Default Web Site, and then select New > Virtual Directory. The Welcome to the Virtual Directory Creation Wizard appears.

5. Click Next. The Virtual Directory Alias page appears.

6. Type a name in the Alias text box. For example, SoftwareRepository.

7. Click Next. The Web Site Content Directory page appears.

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

14 VMware, Inc.

8. Click Browse and locate the repository directory you previously created. For example, C:\WindowsRepository.

9. Click Next. The Virtual Directory Access Permissions page appears.

10. Select Read, Run scripts, and Browse.

11. Click Next. The You have successfully completed the Virtual Directory Creation Wizard page

appears.

12. Click Finish. The new repository virtual directory alias is added to the Default Web Sites list.

13. Right-click the new repository directory, and then select Properties.

The <directory name> Properties dialog box appears.

14. Click the Virtual Directory tab, and then click Remove, located to the right of Application name text box. Application name and Application pool are disabled.

15. Click the HTTP Headers tab, and then click MIME Types. The MIME Types dialog box appears.

16. Click New. The MIME Type dialog box appears.

17. Add the following MIME types with these names and settings:

Extension: .crate and MIME type: application/octet-stream

Extension: .index and MIME type: application/octet-stream

Extension: .gz and MIME type: application/octet-stream

Extension: .options and MIME type:application/octet-stream

Extension: .info and MIME type:application/octet-stream

18. Click OK to save your settings and close the MIME Types dialog box.

19. On the Properties dialog box, click OK to close the dialog box.

20. Copy and paste the contents of the original Repository folder, the .hive folder, the dist folder, and the crates folder, to the new repository location.

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.

23. Right-click the new value, and the select Rename. Type the name of your new repository.

24. Right-click the new repository name, and then select Modify. The Edit String dialog box appears.

25. In the Data Value text box, type the fully qualified URIfor the repository. For example, http://<machinename>/NewRepository.

26. Click OK.

27. Open an Internet Explorer window, and then browse to your new virtual directory. For example, http://<machinename>/NewRepository. The web page should display the .hive,dists, and crates folders. The crates folder contains any copied packages (*.crate files).

28. To keep the new repository synchronized with the original repository, you must continue to copy the files from the original repository to the new repository. You can use one of the following methods:

Installing the Software Provisioning Components

VMware, Inc. 15

Manually copy the files from the original repository to the new repository.

Create a VBScript to copy IIS metabase and schema from on machine to another. The following article assumes both machines are running Windows Server 2003:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/81f04967-f02f4845-9795-bad2fe1a1687.mspx?mfr=true.

Use a commercial mirroring application.

If you are using VCM, you configure the Remote Command Package Mirroring template to copy packages between repositories, or write you own VBScript to run as a remote command to copy the files specified in the configuration steps above from the old repository to the new repository.

Procedure for IIS 7 and later

1. Create a repository directory on your desired drive. For example, C:\WindowsRepository.

2. Open Internet Information Services (IIS) Manager.

3. Expand <machine name> > Sites.

4. Right-click Default Web Site, and then select Add Virtual Directory. The Add Virtual Directory

dialog box appears.

5. Type a name in the Alias text box. For example, SoftwareRepository.

6. Click the Physical path ellipsis button. The Browse for Folder dialog box appears.

7. Browse for and select the repository directory you previously created. For example, C:\WindowsRepository.

8. Click OK to close the Browse for Folder dialog box.

9. Click OK to close the Add Virtual Directory dialog box.

10. Select the new virtual directory you just added, and then double-click Directory Browsing in <yourdirectoryname> Home pane. The pane displays Directory Browsing.

11. In the Actions pane, click Enable.

12. Click Back until you are again on the <yourdirectoryname> Home pane, and then click on MIME Types. The pane displays MIME Types.

13. In the Actions pane, click Add. The Add MIME Type dialog box appears.

14. Add the following MIME types with these names and settings:

File name extension: .crate and MIME type: application/octet-stream

File name extension: .index andMIME type: application/octet-stream

File name extension: .options and MIME type:application/octet-stream

File name extension: .info and MIME type:application/octet-stream

15. Close IIS.

16. Copy and paste the contents of the original Repository folder, the .hive folder, the dist folder, and the crates folder, to the new repository location.

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.

19. Right-click the new value, and the select Rename. Type the name of your new repository.

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

16 VMware, Inc.

20. Right-click the new repository name, and then select Modify. The Edit String dialog box appears.

21. In the Data Value text box, type the fully qualified URIfor the repository. For example, http://<machinename>/NewRepository.

22. Click OK.

23. Open an Internet Explorer window, and then browse to your new virtual directory. For example, http://<machinename>/NewRepository. The web page should display the .hive,dists, and crates folders. The crates folder contains any copied packages (*.crate files).

24. To keep the new repository synchronized with the original repository, you must continue to copy the files from the original repository to the new repository. You can use one of the following methods:

Manually copy the files from the original repository to the new repository.

Use a commercial mirroring application.

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.

NOTE When Package Studio is uninstalled from a machine, the locally saved projects and .crate files remain on the machine, allowing you to copy them to another machine or to delete them manually if they are not needed.

Prerequisit es

Access to the PackageStudio.msi, which is available on the VMware website or in the vCenter Configuration Manager application files. The default location in the VCMapplication files is C:\Program Files\VMware\VCM\AgentFiles\Products.

(Recommended) Software Repository for Windows is installed. Installing the repository before installing Package Studio will reduce the manual configuration steps.

Installing the Software Provisioning Components

VMware, Inc. 17

Procedu re

1. Double-click PackageStudio.msi.

The Welcome page appears.

2. Click Next.

The License Agreement page appears.

3. Review the agreement, and then select I accept the terms of the License Agreement to continue. The

other options become available.

4. Select I am an authorized agent and/or representative of the customer/end-user and I have read the terms and conditions stated above.

5. Click Next.

The Installation Folder page appears.

6. Use the default path or click Change to modify the path. When the path is correct, click Next.

The Repository Root Folder page appears.

7. Verify the path is to your installed repository files. To modify, click Change. When the path is correct, click Next.

The Ready to Install page appears.

8. Click Install.

When the installation is completed, the Setup Complete page appears.

9. Click Finish.

The Package Studio is installed to the location specified during installation. The default location is

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.

Procedu re (u nat ten ded using .msi)

1. On your Collector, navigate to C:\Program Files\VMware\VCM\AgentFiles\Products.

2. Locate the PackageStudio.msi file, and then copy it to the target machine. You can also run it from a shared location.

3. On the target machine, run the .msi file using the following command line syntax.

msiexec /i [path]\PackageStudio.msi /qn /l*v %temp%\PackageStudio.log

You can add the following arguments if you want to specify locations other than the default directories:

REPOSITORY_ROOT=C:\Program Files\VMware\VCM\Tools\Repository\ (Defaults to this or uses the Repository’s value if it is already installed)

PACKAGESTUDIO_DIR="C:\Program Files\VMware\VCM\Tools\Package Studio\" (defaults to this path)

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

18 VMware, Inc.

Manually Uninstall Package Studio

Use the following script to run an unattended uninstall the Package Manager. To uninstall the application, you must use the version of the PackageStudio.msi that was used to install the application.

Procedu re

1. Copy the PackageStudio.msi to the machine on which you are uninstalling the application. You can also run it from a shared location.

2. Run the .msi file using the following command line syntax:

msiexec /x [path]\PackageStudio.msi /l*v %temp%\PackageStudio.log

Installing Package Manager for Windows

The Package Manager for Windows must be installed on all Windows machines on which you are managing software provisioning. 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.

NOTE If you are using the Software Provisioning Components in conjunction with VMware vCenter Configuration Manager (VCM), you should not install the Package Manager using the following instructions, it is installed as part of the VCM Agent.

Prerequisites

Access to the PackageManager.msi, which is available on the VMware website.

Procedure

1. Double-click PackageManager.msi.

The Welcome page appears.

2. Click Next.

The License Agreement page appears.

3. Review the agreement, and then select I accept the terms of the License Agreement to continue. The other options become available.

4. Select I am an authorized agent and/or representative of the customer/end-user and I have read the terms and conditions stated above.

5. Click Next.

The Installation Folder page appears.

6. Use the default path or click Change to modify the path. When the path is correct, click Next.

7. Click Next.

The Cache Folder page appears.

Installing the Software Provisioning Components

VMware, Inc. 19

8. Use the default path or click Change to modify the path where downloaded packages are saved. When the path is correct, click Next.

The Ready to Install page appears.

9. Click Install.

When the installation is completed, the Setup Complete page appears.

10. Click Finish.

The Package Manager and the cratecache folder are installed to the locations specified during installation. 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.

msiexec /i PackageManager.msi /qn /l*v %temp%\PackageManager.log

You can add the following arguments if you want to specify locations other than the default directories:

PACKAGEMANAGER_DIR="C:\Program Files\VMware\VCM\Tools\Package Manager for Windows\" (defaults to this path)

LOCAL_CRATE_CACHE="C:\Program Files\VMware\VCM\Tools\cratecache" (defaults to this path)

Manually Uninstall the Package Manager for Windows

Use the following script to run an unattended uninstall the Package Manager. To uninstall using the .msi, you must use the version of PackageManager.msi that was used to install the application.

Procedure

1. Copy the PackageManager.msi to the machine on which you are uninstalling the application

2. Run the .msi file using the following command line syntax:

msiexec /x PackageManager.msi /l*v %temp%\PackageManager.log

vCenter Configuration Manager Software Provisioning Components Installation and User's Guide

20 VMware, Inc.

+ 46 hidden pages

VMware PACKAGE MANAGER 1.1, Software Repository for Windows 1.1 Installation And User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual