Solved

Group Policy Install Problem

Posted on 2011-03-21
8
4,394 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
 
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
Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 
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

[Webinar] Disaster Recovery and Cloud Management

Learn from Unigma and CloudBerry industry veterans which providers are best for certain use cases and how to lower cloud costs, how to grow your Managed Services practice in IaaS clouds, and how to utilize public cloud for Disaster Recovery

Question has a verified solution.

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

Suggested Solutions

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
On some Windows 7 (SP1) computers, Windows Update becomes super slow even the computer is reasonably fast.  There's one solution that seemed to have worked well for me (after trying a few other suggested solutions).
This Micro Tutorial will teach you how to the overview of Microsoft Security Essentials. This is a free anti-virus software that guards your PC against viruses, spyware, worms, and other malicious software. This will be demonstrated using Windows…
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

920 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

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now