Adding 64 bit MSI to GPO on 64 bit computer - "Add operation failed"
Hi all,
I'm trying to add a 64 bit msi from a piece of oldish software, Lego Mindstorms v2.0 64 bit drivers, to a GPO. Each time I try I get the messageĀ 'Add operation failed. Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct'. I definitely don't have the Lego software installed on my machine which is Windows 10 64 bit. Also happening when I try to add to GPO through server with 2012 R2 64 bit. Any thoughts as to what to check or to change to get this linked up? I have MSI's added with longer path names so I don't think it's anything to do with that but any suggestions welcome.
2 Comments
[ + ] Show comments
-
Could you clarify your question, I don't understand what you are trying to achieve and or the question. - rileyz 8 years ago
-
I have a piece of software called Lego Mindstorms. I'm wanting to deploy the MSI's to computers in our network which have Windows 8.1 64 bit installed. I have Windows 10 64 bit installed on my computer. When I run Group Policy from my computer, create a new Object and try to add the 64 bit MSI to the GPO, I keep getting the message 'Add operation failed. Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct'. I've seen other forums suggesting to check that I haven't the software installed on my computer as this may cause conflicts. I was just stating that I don't have the software installed. And I'm looking for anything to check as to why I cannot add the MSI to the GPO. - alphabeta 8 years ago
Answers (2)
Please log in to answer
Posted by:
rileyz
8 years ago
Posted by:
alphabeta
8 years ago
2 different error messages as follow.
1) Software Installation failed to deploy package LegoMindstormsNXTdriver64.msi. The following error was encountered: Fatal error during installation.
2)Product: LEGO MINDSTORMS NXT x64 Driver -- Internal Error 2705. Directory
Thing is I've edited the MSI to include a valid installation path which it installs to when I run it manually.
Path length shouldn't be an issue as I have successfully added longer path names. Definitely have access to the share as I've added other msi's. Anything else I could check or edit within the msi?
Comments:
-
1) Ooo, nice error, I think that might be caused by the editing of the MSI, btw we don't recommended editing the MSI directly, you should always apply it as a transform.
2) Could be anything causing that error, when deploying/testing you should turn on logging.
msiexec /i NameOfInstaller.msi /l*vx c:\Mylog.log
Is there a reason why you have edited the msi in regards to the install path - will it work without it and install to a default location?
I would go about it like this:
Start command prompt as administrator
CD to the dir where the msi is located.
Install with logging: msiexec /i blah.msi /l*vx .\mylog.log
Install as desired to the correct dir.
After completion, look at the logs for your install location 'PROPERTY' this will be at the bottom of the log.
It might look like PROPERTY: InstallPathSomething='C:\Logo'
Now we know the property, we can install like this:
msiexec /i blah.msi ALLUSERS=1 InstallPathSomething='C:\Logo' /qb /l*vx c:\Lego.log
*ALLUSERS=1 means we install for machine, and NOT per user.
You can apply this via a transform, but for what its worth you can do it via cmd line as well, as noted above.
*Update, thinking about it now, this is complex stuff I'm trying to explain. Hope you get the idea. I had a quick look at GPO deployments, looks like you need to apply it via a Transform, or do what you have done, which is write to the MSI. If you do manage to find the PROPERTY for the install path, you can create a mst via this video.
Just open the msi, then go the Transform menu, Select New Transform, add changes, then save.
https://www.youtube.com/watch?v=zIaTcc-SfkM - rileyz 8 years ago