M
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
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