We use a combination of Computer and User-based Group Policy Software Installations.

In regards to some applications we distribute/deploy through Computer-based policies, these work fine on XP/Vista, however we've just put together some Windows 2008 Server machines and the Computer-based distributions fail on them with 1612:

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

We are using the same group policy object applied to an OU where the Windows 2008 Server machines reside, as the XP/Vista's and yet they install fine.

The group policy points to a UNC path (e.g \\share.domain\apps\app.msi) which is resolvable/connectable on the Windows 2008 Server machines when actually logged on.

We've tried both 'Authenticated Users' and 'Domain Computers' within Security Filtering. There is no WMI filtering in place.

The group policy objects are enabled and retrieved (as otherwise we wouldn't get 1612 errors).

As a final test, we've tried User-based group policy software installations pointing to the same UNC path, and these work fine on our Windows 2008 Server machines.

Anyone know of any issue or changes to the behaviour perhaps with the Software Installation client-side extensions on Windows 2008 Server that might be causing this with Computer-based? Otherwise, I'm at a loss to understand as to why this isn't working?

ta in advance,
0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity