Microsoft Virtual PC 2004

Views: 873  |  Created: 02/18/2004

Average Rating: 0
Virtual PC 2004 has 1 inventory records, 0 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (6)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 1 / 5 (Very Easy) based on 1 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (switch driven)
or cancel
117
Command Line
To install Virtual PC 2004 from Microsoft you need Supervisor rights.
The Command Line to install VPC 2004 Silent...

Examples
The following example shows how to perform an unattended installation and make the program accessible to all users of the computer. A silent installation means the setup program runs without prompting you for input. Type the following:

.\setup.exe -s -v"-qn pidkey=1234567891234567891234567 allusers=2 username=Username organization=your company"

Here are the command switch overview.
-s
Instructs the setup program to run without displaying the user interface.
-v
Passes parameters directly to the installer program, Msiexec.exe.
-qn
Instructs the installer program, Msiexec.exe, to run without displaying the user interface.

pidkey=pidkeynumber
Specifies the unique product key number that is required to perform the installation. Do not use dashes when typing the product key number.

allusers=2
Installs Virtual PC for all users of the computer. If you do not include this parameter, the program is installed for the current user only.

username=user
Specifies a user name to associate with the installation. If you do not include this parameter, the installer program retrieves the name of the current user from the
registry.

organization=organizationname
Specifies an organization name to associate with the installation. If you do not include this parameter, the installer program retrieves the name of the organization associated with the current user from the registry.

installdir=directoryname
Specifies a custom directory in which to install the program. If you do not include this parameter, the program is installed in C:\Program Files.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
When you use the MSDN Version, the PID KEY is included in Package. When you make a silent install, you must add the PIDKEY switch!!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Security
We wanted to deploy VPC with the Security Options set.

I modified the following registry setting during my deployment to accomplish this.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtual PC\5.0\Security]
"Locks"=dword:0000002b

This registry setting will check the following values for the Security options.

Options
Settings
New Virtual Machine Wizard
Virtual Disk Wizard

This will require administrative permissions to configure any of the above items (great for that locked down environment where you don't want users messing with stuff).
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
You might not be able to install VPC 2004 by using msiexec /i directly. The setup.exe contains an Install Shield scripting engine that is needed by the MSI file. If you try to install just the MSI file without having the Install Shield scripting engine, it will fail to install. I was able to steal ISscript8.msi from %tmp% while setup.exe was running, then install that MSI and then the VPC msi file. This seems to be the only way to get it to work in a full unattended installation.

To install SP1, you can run msiexec /i directly on the SP1 MSI, however, you MUST include the same options that you put into the base install of VPC, including the product key or it won't work. Trying to use setup.exe -v"..." for sp1 doesn't seem to work well for scripting since setup.exe exits asynchronously and doesn't wait for the msiexec process to complete.

If things go wrong, check %tmp% for status logs.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note

The only modification I made was AgreeToLicense = Yes using Orca in the Property Table.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
3
Command Line
It should be noted that the command line needs to be entered in the ordered listed in the deployment guide (don't mix up the order or it will give you errors upon startup).

I successfully used the following command line:

[server\share\folder\]setup.exe -s -v"-qn pidkey=xxxxxxxxxxxxxxxxxxxxxxxxx allusers=2 username=\"Some User\" Organization=\"Some Org\" InstallDir=\"%ProgramFiles%\Microsoft Virtual PC\""

(note the "\". This allows for entries which have spaces to be used)

Alternately, the installation can be launched using msiexec with the following command line:

msiexec.exe /i "\\server\share\folder\Microsoft Virtual PC 2004.msi" -qn pidkey=xxxxxxxxxxxxxxxxxxxxxxxxx allusers=2 username="Some User" Organization="Some Org" InstallDir="%ProgramFiles%\Microsoft Virtual PC"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Virtual PC 2004

Version

1

Questions & Answers (0)

Questions & Answers related to Microsoft Virtual PC 2004

Blogs (0)

Blog posts related to Microsoft Virtual PC 2004

Reviews (0)

Reviews related to Microsoft Virtual PC 2004