Solved

Group Policy Install Problem

Posted on 2011-03-21
8
4,440 Views
Last Modified: 2012-05-11
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 :

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_26240578.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.
0
Comment
Question by:Rob Sanders
  • 4
  • 4
8 Comments
 
LVL 16

Expert Comment

by:cantoris
ID: 35185355
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.
0
 
LVL 1

Author Comment

by:Rob Sanders
ID: 35189723
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?
0
 
LVL 16

Expert Comment

by:cantoris
ID: 35194295
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.
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 1

Author Comment

by:Rob Sanders
ID: 35194387
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.
0
 
LVL 16

Expert Comment

by:cantoris
ID: 35194605
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?
0
 
LVL 16

Accepted Solution

by:
cantoris earned 500 total points
ID: 35194612
Therefore, specify your MSI source by an UNC path - perhaps via DFS.
0
 
LVL 1

Author Comment

by:Rob Sanders
ID: 35194657
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.
0
 
LVL 1

Author Comment

by:Rob Sanders
ID: 35194758
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.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing.  You will be panic as there are no back…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question