Anyone here was successful in pushing out MS Virtual PC 2004 through GPO?
The package comes as an MSI. During install, it extracts two msi's into temp directory. One of them is isscript.msi; another one is the msi for the program installer itself.
I can assign isscript.msi through GPO. I can NOT assign the second (main) msi through policy editor mmc. It fails to extract deployment information from the package. Search on MS renders irrelevant kb's that pertain to Windows 2000 + Office 2000.

AD 2003. Computer-based assignment.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


You have to make sure the msi is cached locally, cuz the installation of ms VMachine causes the NIC to temporarily fail while it installs virtual nics.
After that comes VPC SP1, that too is a pain in the B. It totally whipes away the installation and installs the sp'd one.
Furthermore, it's an Installshield Setup, so AD has to deal with some installshieldLogic. It seems like the only way is to install silently with setup.exe CLSwitches..

I'm still trying to break this app. for deployment by Radia.
It's terrible[>:]

However keep in mind that the assignmentissue you have with MMC does not mean per se that there is a problem with an .msi.
I've had it lots of times, the fastest way around that is to "remote desktop" to the deploymentserver and assign the msi using the MMC on the server itself..
Answered 07/27/2005 by: inert
Orange Belt

Please log in to comment
I gave up on it. The msi didn't go with the /qb switch, complaining about script errors. It's either repackage from scratch, or "hell with it". I picked "hell with it"
Answered 07/27/2005 by: revizor
Third Degree Blue Belt

Please log in to comment