asked on

Group Policy Install Problem

I am trying to install several .msi's via group policy. A good number of them install without a problem but some don't. I get several errors in event viewer:

"The assignment of application <application name> from policy <policy name> failed. The error was :%%2"

"The install of application <application name> from policy <policy name> failed. The error was %%1612."

"Failed to apply changes to software installation settings. Software changes could not be applied. A previous lgo entry with details hsould exist. The error was : %%1612"

and

"Windows failed to apply the Software Installation settings. Software Installation settings might habe its own log file. Please click on the "More information" link."

this is similar to another EE post :

https://www.experts-exchange.com/questions/26240578/Group-Policy-app-assignment-error.html

I tried everything in the link that is in that post and nothing helped. Does anyone have any ideas?

The domain controller that these machines are referring to is a Windows 2k3 r2 server and the workstations are Windows 7 and Windows XP.

If I get any more info, I will post.

cantoris

Make sure the folder(s) containg the installation files have suitable permissions on them so that the files can be read and executed. Actual permissions depend on whether these files are being installed from the computer or user sections of a group policy object.
eg You might need to give Domain Computers (or a group containing machine accounts) permissions to the folder if the app is assigned to computers.

Rob Sanders

ASKER

I just added full permissions for Domain Computers on the folder containing the install packages and it didn't make a difference. I didn't think it would as other packages within the same folder do not have a problem. Any other ideas?

cantoris

Error 1612 is "The installation source for this product is not available. Verify that the source exists and that you can access it."

Check the exact paths you are specifying when assigning the MSIs and see whether the clients resolve those hostnames (whether fully qualified ot not) to the correct addresses.

Rob Sanders

ASKER

The paths do resolve correctly. However, I did notice another message in the application log:

"Product: <Product Name> -- Error 1327. Invalid Drive: I:\"

The I: drive is the network drive where the packages are located and the user can get to them through My Computer. The drives are mapped via a logon script as opposed to through Group Policy if that matters.

cantoris

Is that a user account's logon script as opposed to a computer account's startup script?
And is the package assigned to the computer rather than to the user?

Startup
- Computer authenticates
- Computer part of GPO processed
- Computer Startup scripts run
- User logs in
- User part of GPO processed
- User Login scripts run

See the problem there?

ASKER CERTIFIED SOLUTION

cantoris

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Rob Sanders

ASKER

That makes sense. I will try making that change and see if it makes a difference. Although, even when I browse to the install package via a network drive letter, when it displays it in group policy software installation, it shows the source file via its UNC path as opposed to a drive letter.

Rob Sanders

ASKER

I finally got it resolve in large part to your suggestion. While I don't think there was an issue with the group policy config per se, the install package that is dynamically created through an administrative installer was referring to the drive letter instead of the UNC path. After correcting this, the install worked. Thanks for the assistance.