Performing a customized unattended installation of Virtual Server

Performing a customized unattended installation of Virtual Server

  • Comments 2

The Virtual Server Administrator's guide outlines how to perform a basic unattended installation of Virtual Server.  However it does not tell you how to do a customized unattended install (where you only install some of the components).  You can do this with the following command (all one line):

msiexec /I "Virtual Server 2005.msi" /L*v %TEMP\VS2005Install.log ADDLOCAL=VirtualServer,VMRCClient,DevAndDoc,VSWebApp PIDKEY=#YOUR_PID_WITHOUT_DASHES# /qb-

Where you remove the components from 'ADDLOCAL' that you do not want installed.  So if you just wanted the VMRC client you would run:

msiexec /I "Virtual Server 2005.msi" /L*v %TEMP\VS2005Install.log ADDLOCAL=VMRCClient PIDKEY=#YOUR_PID_WITHOUT_DASHES# /qb-

Note: To get the .msi file with Virtual Server 2005 R2 you will need to run Setup.exe /c /t [drive letter]:\[path to the .msi file].

Cheers,
Ben

Leave a Comment
  • Please add 8 and 6 and type the answer here:
  • Post
  • Sorry if this is slightly offtopic, but I couldn't find an answer for this issue - I was installing VS2005 on a guest W2K3 OS and at some point it prompted me to replace the disk 1 with disk 2. After I replace the disk  Virtual Server does not recognize that disk 1 has been replaced. It continuously prompts me to replace the disk. Is this a problem or am I doing something wrong? I would sincerely appreciate any comments on this.
  • Hmm, I think Kris's mention of "VS2005" means Visual Studio 2005 not Virtual Server 2005.  But it's being installed in a guest machine, so it's VS2005 under Windows 2003 under that other VS2005.

    If you're installing from physical media, check the guest machine's properties in order to make sure that the guest is still controlling the physical drive.

    If you're installing from ISO images, then also check the guest machine's properties to make sure you switched which image is being controlled, instead of switching physical media or accidentally having the virtual drive get switched to control the physical drive.

    If you've done all of that, there are some physical drives with defective firmware that don't recognize when the media have been switched.  There are also some suspicious drivers which persuade Windows to see contents of media that have been ejected instead of the media currently in the drive.  Sometimes this can be solved by temporarily inserting a different kind of media (for example remove CD1, insert a DVD that you don't want to use, remove the DVD, then insert CD2).
Page 1 of 1 (2 items)