All,

We use group policy to deploy service packs to our 3000 ish machines and it works fine. The problem is that some machines may have already had the service pack applied and group policy/the service pack installer, does not seem clever enough to figure this out! This results in the service pack getting applied again and an angry user on the phone to me! Has anyone else had similar problems and know of a way round this?

Cheers,

Darin
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Unfortunately thats one of the dilemmas that Group Policy faces. There's no built in logic to detect manual installs.

Your best bet is going to be either to remove the already installed service packs manually then redeploy the updated package, or find a way to query your users and not include those who already have it in the deployment group.
Answered 04/14/2005 by: Bladerun
Green Belt

Please log in to comment
0
Do you know how a machine figures out what group policy related software installs it has done? If this is stored in the registry somewhere then I could knock something up.
Answered 04/14/2005 by: darin
Yellow Belt

Please log in to comment
0
I believe that it just stores the MSI Package ID, there's no info on how it was installed.
Answered 04/14/2005 by: Bladerun
Green Belt

Please log in to comment
0
MS Service Packs are meant to install over previously installed versions. This is by default so that users with corruptions can bring workstations back to life with a fresh file set.

If this is a MAJOR problem then you can actually wrap a Service Pack in an msi so that the msi product code refuses to allow a reinstall......but this is a LAST resort.
Answered 04/15/2005 by: MSIMaker
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity