Vmware work stattion 7 Msi creation
im trying to build a MSI of vmware worksation 7
to be able to deploy in our employee pc ...
im able to build the msi but when i test it with the test pc i get an errror "could not open key"
im using msi studio to creta ethe package
any idea why i get this error ?
thanks
to be able to deploy in our employee pc ...
im able to build the msi but when i test it with the test pc i get an errror "could not open key"
im using msi studio to creta ethe package
any idea why i get this error ?
thanks
0 Comments
[ + ] Show comments
Answers (14)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
From what I recall, VMWare Workstation extracts and executes an MSI so capturing it to create another MSI is a Really Bad Idea.
For future reference, you can diagnose errors like this yourself by using a process/file/registry monitor like ProcMon. I believe you *may* have seen it mentioned once or twice here before...
EDIT:
Yup...knew it. See the 'Package KB' for details of how to extract the MSI.
For future reference, you can diagnose errors like this yourself by using a process/file/registry monitor like ProcMon. I believe you *may* have seen it mentioned once or twice here before...
EDIT:
Yup...knew it. See the 'Package KB' for details of how to extract the MSI.
Posted by:
kerm007
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
anonymous_9363
14 years ago
As I say, when you add the MSI to the GPO, you'll see the 'Modifications' tab. Click that, browse to the transform you created beforehand. For future reference:
- if using more than one MST, add them in the order that they should be applied. You can move them up and down but...
- if you click 'OK' before you've finished adding MSTs, you'll have to start again, from adding the MSI. Great UI, isn't it?
- if using more than one MST, add them in the order that they should be applied. You can move them up and down but...
- if you click 'OK' before you've finished adding MSTs, you'll have to start again, from adding the MSI. Great UI, isn't it?
Posted by:
kerm007
14 years ago
Posted by:
anonymous_9363
14 years ago
Let's try and clarify...
- You have extracted the MSI from a set-up executable
- You are using an authoring tool to create an MST. Which tool are you using? During that exercise, are you prompted for the serial number?
- When you run the package, you are prompted to enter the serial number? What command line are you using? Or are you just double-clicking the MSI?
- You have extracted the MSI from a set-up executable
- You are using an authoring tool to create an MST. Which tool are you using? During that exercise, are you prompted for the serial number?
- When you run the package, you are prompted to enter the serial number? What command line are you using? Or are you just double-clicking the MSI?
Posted by:
kerm007
14 years ago
- You have extracted the MSI from a set-up executable (yes and i took the stuff in the temp folder)
- You are using an authoring tool to create an MST. Which tool are you using? msi studio During that exercise, are you prompted for the serial number? yes but when i enter it i get no serial found
- When you run the package, you are prompted to enter the serial number?yes What command line are you using? no Or are you just double-clicking the MSI? double click
- You are using an authoring tool to create an MST. Which tool are you using? msi studio During that exercise, are you prompted for the serial number? yes but when i enter it i get no serial found
- When you run the package, you are prompted to enter the serial number?yes What command line are you using? no Or are you just double-clicking the MSI? double click
Posted by:
anonymous_9363
14 years ago
I'm not familiar with 'msi studio'. Do you mean 'Wise Package Studio' or perhaps 'AdminStudio', the InstallShield product?
In any event, double-clicking an MSI is no good. Just because it's in the same folder as the MSI doesn't mean that the transform will be processed.You need to use a command like this:
In any event, double-clicking an MSI is no good. Just because it's in the same folder as the MSI doesn't mean that the transform will be processed.You need to use a command like this:
msiexec /i [path_to_and_name_of_MSI] TRANSFORMS="[path_to_and_name_of_MST] [other_command_line arguments]
Google for the valid command line arguments for MSIEXEC.
Posted by:
kerm007
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
kerm007
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.