AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Technet applocker9/8/2023 REG ADD HKLM\SYSTEM\CurrentControlSet\Control\Srp\Gp\Msi /v EnforcementMode /t REG_DWORD /d 0 /f REG ADD HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\SrpV2\Script REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\SrpV2\Script /v EnforcementMode /t REG_DWORD /d 0 /f The workaround we use is a batch file, shown below, which makes the registry changes as suggested in the Microsoft forum, then pauses so you can separately run the Autodesk installer and then set the keys back after the install. However, if it's a new install from the CD (or a network stored copy of the CD) then the setup.exe starts to initialise and then fails with the errors mentioned. As previously mentioned, if a custom installation of the product has already been packaged for deployment using the option in your setup program then it installs with no issues and this uses the same setup.exe to run. I also know that it's not a oddity with our group policies as someone else was able to replicate the problem without knowing our set up.Īs such, I can't just say "fix your product", but I will respectfully request that you look at how your setup program initialises and works with Applocker. I'm not 100% sure if the problem is with Autodesk or Applocker, but I haven't experienced the same problems with any other product I've installed in our Windows 7 environment so that suggests to me that your installer works in a slightly different way. As you have seen, I do now have a workaround so I can get Autodesk products to install, but workarounds are never as ideal as actual fixes. Unfortunately, this is not an option to our users.Īny help would be very gratefully received. Of course, we can only get to the packaging tool through the setup program which doesn't run on our Windows 7 machines.įinally, I have seen another post similar to this that suggests taking the machine off of the domain and trying a fresh install. I can confirm that if the product has already been packaged using the packaging tool within the setup program, that the package installs ok. This policy doesn't have any actual restrictions in it, but it has been suggested elsewhere that this is a possible cause of this error. I can also confirm that I do have a Software Restriction Policy turned on that applies to all except Administrators. The Applocker event log doesn't show any errors to suggest it's blocking the program, but something must be causing a knock on effect to this install. We use Applocker policies which have been set to allow Admins to run all Windows Installer Files, Executables and Scripts on any Path. I have confirmed that this is caused by Applocker as I have tested with a machine that has all policies except Applocker and it works, but as soon as Applocker is turned on I get this error. "The installation of C:\Users\ username\AppData\Local\Temp\_ random.tmp\SetupRes\eval.msi is not permitted due to an error in software restriction policy processing. In the Application Log, I get this message: "This installation is forbidden by system policy. When I run setup.exe for 3DS Max Design 2011 or Navisworks 2011 on any of our domain connected Windows 7 machines, the program starts to initialise, but then comes up with the following message:
0 Comments
Read More
Leave a Reply. |