Problems with WinXP SP2 and Group Policy Software Install

[Guest]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

We got our first WinXP SP2 machine today. When it booted it skipped
through the Group Policy Software installation too quickly and did no
installation. Eventvwr yields events 301, 102 and 303 for every
package (See below for examples of our messages).

The Group Policies are configured using UNC paths to the packages and
we even tried allowing ANONYMOUS LOGON for both the share and NTFS.
Once logged in we have no problem browsing to the installation share.
We also disabled the firewall.

All that said, The same Group Policy Software installations have
always worked with all our new WinXP SP1 clients for the past year!

Our Servers are Win2k SP4. We are installing OfficeXP Pro, Media
Content, Publisher and the ISA Firewall Client. Our Group Policy
Security settings were successfully applied. Our Group Policies are
computer configured rather than user configured.



EVENT MESSAGES
EVENT 301: The assignment of application Microsoft Office XP Media
Content from policy VicNetworkedClipart succeeded.
EVENT 102: The install of application Microsoft Office XP Media
Content from policy VicNetworkedClipart 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 303: The removal of the assignment of application Microsoft
Office XP Media Content from policy VicNetworkedClipart succeeded.

 

[Guest]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

on the source folder do you have "Authenticated Users" on the ntfs
permissions?

"Luke Rohde" <lukerohde@hotmail.com> wrote in message
news:c41d3720.0410272204.1d3f0cce@posting.google.com...
> We got our first WinXP SP2 machine today. When it booted it skipped
> through the Group Policy Software installation too quickly and did no
> installation. Eventvwr yields events 301, 102 and 303 for every
> package (See below for examples of our messages).
>
> The Group Policies are configured using UNC paths to the packages and
> we even tried allowing ANONYMOUS LOGON for both the share and NTFS.
> Once logged in we have no problem browsing to the installation share.
> We also disabled the firewall.
>
> All that said, The same Group Policy Software installations have
> always worked with all our new WinXP SP1 clients for the past year!
>
> Our Servers are Win2k SP4. We are installing OfficeXP Pro, Media
> Content, Publisher and the ISA Firewall Client. Our Group Policy
> Security settings were successfully applied. Our Group Policies are
> computer configured rather than user configured.
>
>
>
> EVENT MESSAGES
> EVENT 301: The assignment of application Microsoft Office XP Media
> Content from policy VicNetworkedClipart succeeded.
> EVENT 102: The install of application Microsoft Office XP Media
> Content from policy VicNetworkedClipart 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 303: The removal of the assignment of application Microsoft
> Office XP Media Content from policy VicNetworkedClipart succeeded.

 

[Guest]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

> on the source folder do you have "Authenticated Users" on the ntfs
> permissions?

I gave that a try but still no luck. We suspect it has something to
do with WinXP SP2 because our WinXP SP1 machines and Win2k machines
have no problems. I've found other posters with the same problem with
SP2 but as yet no solutions.

 

[Guest]

Archived from groups: microsoft.public.win2000.group_policy (More info?)

This might sound crazy but I added the computer account to both the
share and NTFS permissions and it worked. How do WinXP SP2 machines
login to do GP software installation that is different from SP1
machines? We had tried Everyone, ANONYMOUS LOGON and Authenticated
Users none of which worked.

What does microsoft say it should be set as? I think we'll use the
security group we put our computers in for packages for the
permissions to the share and NTFS installation source.