software group policy behaviour

I want to incorporate software installation group policy into my environment.  I am familiar how to create the policy and assign it to an OU/  what I am questioning is how to actually do the implementation.  I will use XP SP2 asa an example.  I want to implement the sevice pack to all the XP pro machines so I would push the policy out to all the XP machines BUT some of them have the service pack on already, so how would I go about doing this/?  Will the policy recognize that the service pack is there already and not reinstall???

There are several other software policies that I want to implement but the software is already installed..

Again, I am familiar with the creation of the policy, just not the behaviour under certain circumstances……….
dtooth71Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dtooth71Author Commented:
to add to my post I want the poilicy to be assigned "install during logon".  My end users are assigned the "user" priveledge.  will this poilicy install with the user logged on as a "user"??
0
Rant32Commented:
As long as the software is identical to the package you are trying to install, then Windows Installer will recognize that it's already installed.

Same goes for the service pack; you see it flashing past when you start up the computer (it does try to run the update) but it recognized that SP2 is already installed and will not try again.

I would recommend to get yourself a workstation you can test your policies on, because although I'm sure about .MSI packages and the XP SP, this might not always be the case with all software in your environment. Different Windows Installer versions can complicate things, for example.

The user-assigned packages use elevated priviliges to install software upon first use, or when installed from the Add/Remove programs control panel. Administrative rights are not required, but again, test everything just so you know how your software behaves, or in case you get questions from your users.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dooleydogCommented:
Group Policy will work, but Use WSUS instead.

WSUS will allow you to specify which computers (arranged in groups) will get which updates or service packs, and only approved updates will be applied.

It is quite a bit more complicated than SUS, so make sure to read all about it before you start. I feel confident that you will find it extremely helpful.

Good luck,
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.