Computer assigned software packages fail to install

[Mike]

I'm currently having a problem deploying software to computers
using a GPO set on an OU that I have my computer accounts in. At
first the GPO was not being applied at all to the computers. I
then added the following registry key which then got the
computers to see the assigned packages but still failed to
install.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
\Winlogon]
"GpNetworkStartTimeoutPolicyValue"=dword:00000078

When the computer first start I see it attempt to install but
then it quickly gos to the logon screen. If I check the event
log I see the following.

Event ID: 301 The assignment of application Symantec AntiVirus from policy
WS_POLICY
succeeded.
Event ID: 102 The install of application Symantec AntiVirus from policy
WS_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.
Event ID: 303 The removal of the assignment of application Symantec
AntiVirus from policy
WS_POLICY succeeded.
Event ID: 108 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.
Event ID: 1085 The Group Policy client-side extension Software Installation
failed to execute.
Please look for any errors reported earlier by that extension.

At first I thought that the issue may be that I was using a DFS path for my
install source, so I
changed the path to a regular UNC path and used the server ip address
instead of the
hostname, this did not make any difference though.
I of course made sure that my directory permissions were not causing the
problem. The share
permission is set to Everyone:Read, and NTFS is set to Authenticated
Users:Read+Execute. I
then checked the effective permissions to one of the computer accounts that
I was trying to
deploy to, and verified that it actually did have read rights. I also
verified that the computer policy
setting "Always wait for the network at computer startup and logon" was
enabled.
I know that there is not problem with the actual installs since I can map a
drive to the install
source and install the applications manually, or deploy them to user
accounts through a GPO.

I've tried just about everything I can think of at this point. I have seen
posts on message boards
complaining about the same issue but so far I haven't come across any
definite fixes, so any
advice on this would be great.

Thanks,
Mike

 

[Deploymentgeek]

Hi

It could look like a problem with the share (permissions)

Have a look at this article:
http://support.microsoft.com/kb/302430

Best Regards

Rico Raja

I'm currently having a problem deploying software to computers
using a GPO set on an OU that I have my computer accounts in. At
first the GPO was not being applied at all to the computers. I
then added the following registry key which then got the
computers to see the assigned packages but still failed to
install.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
\Winlogon]
"GpNetworkStartTimeoutPolicyValue"=dword:00000078

When the computer first start I see it attempt to install but
then it quickly gos to the logon screen. If I check the event
log I see the following.

Event ID: 301 The assignment of application Symantec AntiVirus from policy
WS_POLICY
succeeded.
Event ID: 102 The install of application Symantec AntiVirus from policy
WS_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.
Event ID: 303 The removal of the assignment of application Symantec
AntiVirus from policy
WS_POLICY succeeded.
Event ID: 108 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.
Event ID: 1085 The Group Policy client-side extension Software
Installation failed to execute.
Please look for any errors reported earlier by that extension.

At first I thought that the issue may be that I was using a DFS path for
my install source, so I
changed the path to a regular UNC path and used the server ip address
instead of the
hostname, this did not make any difference though.
I of course made sure that my directory permissions were not causing the
problem. The share
permission is set to Everyone:Read, and NTFS is set to Authenticated
Users:Read+Execute. I
then checked the effective permissions to one of the computer accounts
that I was trying to
deploy to, and verified that it actually did have read rights. I also
verified that the computer policy
setting "Always wait for the network at computer startup and logon" was
enabled.
I know that there is not problem with the actual installs since I can map
a drive to the install
source and install the applications manually, or deploy them to user
accounts through a GPO.

I've tried just about everything I can think of at this point. I have seen
posts on message boards
complaining about the same issue but so far I haven't come across any
definite fixes, so any
advice on this would be great.

Thanks,
Mike

 

[Mike]

I don't think this is an access issue since I was able to verify that the
machine accounts that I am trying to deploy to have access to the direcories
that contain the install files. I really think that the cause of this issue
is XP's fast logon configuration. I think I'll try setting up a 2000 system
and deploying to that to see if I have the same problem.

Hi

It could look like a problem with the share (permissions)

Have a look at this article:
http://support.microsoft.com/kb/302430

Best Regards

Rico Raja

I'm currently having a problem deploying software to computers
using a GPO set on an OU that I have my computer accounts in. At
first the GPO was not being applied at all to the computers. I
then added the following registry key which then got the
computers to see the assigned packages but still failed to
install.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
\Winlogon]
"GpNetworkStartTimeoutPolicyValue"=dword:00000078

When the computer first start I see it attempt to install but
then it quickly gos to the logon screen. If I check the event
log I see the following.

Event ID: 301 The assignment of application Symantec AntiVirus from
policy WS_POLICY
succeeded.
Event ID: 102 The install of application Symantec AntiVirus from policy
WS_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.
Event ID: 303 The removal of the assignment of application Symantec
AntiVirus from policy
WS_POLICY succeeded.
Event ID: 108 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.
Event ID: 1085 The Group Policy client-side extension Software
Installation failed to execute.
Please look for any errors reported earlier by that extension.

At first I thought that the issue may be that I was using a DFS path for
my install source, so I
changed the path to a regular UNC path and used the server ip address
instead of the
hostname, this did not make any difference though.
I of course made sure that my directory permissions were not causing the
problem. The share
permission is set to Everyone:Read, and NTFS is set to Authenticated
Users:Read+Execute. I
then checked the effective permissions to one of the computer accounts
that I was trying to
deploy to, and verified that it actually did have read rights. I also
verified that the computer policy
setting "Always wait for the network at computer startup and logon" was
enabled.
I know that there is not problem with the actual installs since I can map
a drive to the install
source and install the applications manually, or deploy them to user
accounts through a GPO.

I've tried just about everything I can think of at this point. I have
seen posts on message boards
complaining about the same issue but so far I haven't come across any
definite fixes, so any
advice on this would be great.

Thanks,
Mike

 

[claytical]

Same problem with computer assigned software packages failing

I'm getting the same errors in my environment. We also use Symantec which I thought could be a culprit but uninstalling that didn't change anything. I've only got the computer assigned gpo to work once (and I had played a lot with the security settings, giving Domain Computers full access) but then it stopped working. I've always had Fast Logon disabled.

If I make any progress I'll post it here, let me know if you have any success as well.

 

[claytical]

Fix for Computer Assigned Packages

Mike,

I found an article and it fixed my problem. It *is* permission related but not where you'd first look. Here's the fix from the article I found (MSI Deployment via Active Directory - May 9, 2003 by Joe Klemencic).

Appendix B: Creating Kerberos Service Principals



Since the local machine uses its local computer account Kerberos credential cache to authenticate to the server share containing the MSI Installation file, it must first request a HOST principal for the server hosting the share. Depending on the permissions set on the server computer object within Active Directory, this may be created automatically, or you may need to create it manually. If the permissions on the object allow for Full Control or Read/Write/Modify of SELF on the server computer object, after the next Active Directory registration of the server (usually after a reboot), the HOST service principal may be automatically created. One cautionary note on this: if the server is allowed to automatically update the properties on its own object, it will remove anything you had defined manually. For example, if you create the Package Object UNC path using the FQDN (\\server.domain.com\share\Install.msi), and server.domain.com is not the actual computer name of the server, the server will update Active Directory with the computer name instead (HOST/server instead of HOST/server/domain.com). In this case, there will be no HOST service principal for server.domain.com and the package installation will fail. It is probably better to not let the server auto-updates its own Active Directory object properties and instead define both the HOST/server and HOST/server.domain.com HOST service principals manually.



To create the HOST service principals manually, you need to use the ADSI editor. Open the ADSI editor and navigate to your server computer object. Navigate to the Optional servicePrincipalName attribute and add both the HOST/server and HOST/server.domain.com values. Set this value on all server computer objects that will be hosting shares for software deployment. Client workstations that are received the software deployment do not need to be modified.



Hope this helps!

Clay

 

[anees420]

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

here is how i fixed it....

this is not a exact solution... because there doesn't seem to be one solution but these are steps to help trouble shoot

start -> Run -> gpupdate /force (does this when ever you update group policy)

start -> Run -> regedit ( hkey_user.defaultcurrentcontrolsetSCRNSAVE.EXE --change to cmd.exe (this will open a command prompt before you log into windows)

start -> Run -> regedit ( hkey_user.defaultcurrentcontrolsetScreenSaveTimeOut --change to 30 (30 seconds for cmd.exe to launch)

do all your testing try accessing the file

my solution was the name of the server had to be used not the cluster name or ip address

by the way.... always use a workstation for testing not your Domain Controllers

Ciao