Policy based installation in an Active Directory Domain

[Anonymous]

I did an administrative installation of Inventor 5 and VoloView Express on
my Windows 2000 file server. I created a organizational unit, containing
some computers, and added a policy for that OU. Trying to create a Installer
Package using the setup.msi or voloviewexpress.msi in the administrative
installation point of Inventor or VVE, I get a message "Adding the package
failed. Could'nt get distribution information from package. Ensure, that the
package is correct.". Do the .MSIs by Autodesk differ from those by
Microsoft? How can I solve this?

[digijones]

It sounds like the issue is related to how Autodesk packages its MSI files—they sometimes include custom actions or metadata that standard Windows Group Policy deployment doesn’t handle the same way as Microsoft MSIs. One approach is to use the Autodesk Deployment Wizard to create a network deployment package, which tends to handle distribution info correctly. Handling software deployments properly in complex environments is kind of like managing features in apps—just as you need the right setup for desktop software, using tools like CapCut Pro APK on mobile also works best when everything is configured correctly.