Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1163
  • Last Modified:

Software Deployment via GPO brings back Application Error 102

Afternoon,
I've setup a new GPO.
In this GPO I've assigned a software package under "Computer Configuration/Software Settings/Software installation"
The permissions on the GPO grant "Domain Computers" Read access.
The software packages is using a UNC path.
The share has read permissions and read NTFS security permissions for "Domain Computers".

The computer i'm testing is the only object in this particular OU, it is a member of "Domain Computers"
The GPO is linked and enforced to the OU.

I can't think of anything else that can be causing the following error...

"The install of application Adobe Reader 9 from policy Software Deployment Policy failed. The error was: The installation source for this product is not available. Verify that the source exists and that you can access it."

Any help will be highly appreciated!
0
Antonio King
Asked:
Antonio King
  • 5
  • 4
1 Solution
 
Joseph DalyCommented:
Try setting the unc path that the install is in to have anonymous access. The reason for this being is that the software installation occurs before windows can fully authenicate.  By adding anonymous access to the share where the install is located you should be able to resolve this.
0
 
Joseph DalyCommented:
Also
As per Microsoft: "The machine account for the workstation does not have permissions to the share or file system that holds the source files for the package. When a workstation runs Group Policy, it does so in the context of the machine system account for the workstation." See M278472 for more details and resolution.  

http://support.microsoft.com/kb/278472
0
 
Antonio KingIT ManagerAuthor Commented:
I've mentioned in my question that I have covered permissions for the actual computer.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Antonio KingIT ManagerAuthor Commented:
Ok, I've added anonymous to the shares permissions. Redeployed the package, forced a gpupdate and tried again.

The same error has popped up! Very strange one this is, no doubt it's something simple, always is!
0
 
Joseph DalyCommented:
Are you sure that the package itself is not the problem?
0
 
Antonio KingIT ManagerAuthor Commented:
How can I test the package?
The actual msi file works fine.
0
 
Joseph DalyCommented:
Any other errors or warnings in the event log that look like they apply?

A few other thoughts I have. Does the install attempt to create any files within the UNC path? If so having read only access might mess it up.

Just for the sake of trying what happens if you give anonymous and everyone full control to the share?

0
 
Antonio KingIT ManagerAuthor Commented:
I've given full anonymous access.
Still fails.
There are no other errors in the event log.
0
 
Antonio KingIT ManagerAuthor Commented:
Actually the first log in the Application Event log says...

"The assignment of application Adobe Reader 9 from policy Software Deployment Policy succeeded."

The next says...
"The install of application Adobe Reader 9 from policy Software Deployment Policy failed. The error was: The installation source for this product is not available. Verify that the source exists and that you can access it."

The next says...
"The removal of the assigment of application Adobe Reader 9 from policy Software Deployment Policy succeeded."

The next says...
"Failed to apply changes to software installation settings. Software changes could not be applied. A previous log entry with details should exist. The error was: The installation source for this product is not available. Verify that the source exists and that you can access it."

The next says...
"The Group Policy client-side extension Software Installation failed to execute. Please look for any errors reported earlier by that extension."
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now