GPO service pack deployment

[andy]

I am trying to deploy SP4 for 2k using a GPO. I have set it up
correctly and it deploys properly. However, about half of the
machines in the environment already have SP4 installed and I do not
want to kick off a reinstall on these machines but for some reason, AD
insists on doing a reinstall whether its installed or not. Any ideas
how to correct this?

Thanks

 

[Eric]

hey.

I saw your post in another group too. I was looking for an answer to the
same question. So far, all I can tell is that it will reinstall..which
really sux.

-eric

 

[andy]

My best guess for a hack is to add a CustomAction to the MSI file that
checks to see if the SP has been applied and if so, applies the
registry changes to the machine that AD makes to indicate the GPO was
applied successfully. Unless I get a better answer, I'll post the
results of the test.

 

[andy]

Not sure if this will work or not cause I am having trouble testing
it. Seems like it would work though. Create a .vbs file with the
following:

Option Explicit

Function ValidateServicePack()
Dim objWSH

Set objWSH = CreateObject("WScript.Shell")

If objWSH.RegRead("HKLM\Software\Microsoft\Windows
NT\CurrentVersion\ProductName") = "Microsoft Windows XP" _
And objWsh.RegRead("HKLM\Software\Microsoft\Windows
NT\CurrentVersion\CSDVersion") = "Service Pack 1" Then

Session.Sequence("PublishComponents")
End If

Set objWSH = nothing
End Function

open up update.msi woith orca and create a transform. add the file to
the binary table. add a customaction to call the script and update
installexecutesequence with a reference to the action. according to
MS, the action must occur between installinitialize and
installfinalize.

the update.msi file is all messed up and does not execute like a
normal .msi should execute so im stuck

 

[Jason]

Do you know specifically which computers do have it or
don't? Filter the GPO by a group whose members can apply
the GPO, all others just read. You might want to use SUS
instead of GPO as the system will only install what it
needs for the SUS server. The main idea with GPO and MSI
is you are changing it to a "managed state" which requires
a new windows installer registration based on the GUID of
the MSI and where it was installed from in this case the
GUID. I like the hack idea but it wouldn't be a good idea
seing as the companies who make third party packagers
recomend not to touch. Instead use the VB code assigned
in a startup script to gather the info for you assigned to
the computer. This way you can get the detail you want
before you release it through GPO and assign it
accordingly. It is always a better position to use GPO
when possible because it gives you a "roll back" option
without visiting workstations. Ideas to ponder I hope I
didn't run off too much.