Reissued updates

[John Smith]

Why are there so many Reissued updates? You dont' here about MS re-releasign
these so what's changing? and if they are Reissued then to the clients
reinstall them?

Heres my Sync log that I'm talking about

Automatic Sync Started- February 06, 2003 2:59:59 AM Successful

Updates Added:
810847: February 2003, Cumulative Patch for Internet Explorer 5.01
Service Pack 3 - q810847_B3CA04E8D113EBDE0D561AB3AFAA02EBC3922F36.exe
810847: February 2003, Cumulative Patch for Internet Explorer 5.5
Service Pack 2 - q81084102065CAD52C737EBBF4422AEF2CAC5E100B6EFA.exe
810847: February 2003, Cumulative Patch for Internet Explorer 6 Service
Pack 1 (64-bit Edition) -
q810847_E64E55070121D3002D8D52D436F1718C61C1DEC4.exe
810847: February 2003, Cumulative Patch for Internet Explorer 6 -
q810847_DDE9BE0E09FF7E261B1E32AFF6F597FA27A72B6A.exe
810847: February 2003, Cumulative Patch for Internet Explorer 6 Service
Pack 1 - q810847_C3902604B28A9E2AAD419E883ACC553FD69B84F9.exe
811630: Critical Update (Windows 2000) -
Q811630_W2K_SP4_1AE3DC420E9CD499959B50D11F76470FC6C6FA8C.exe
811630: Critical Update (Windows XP) -
Q811630_WXP_SP2_0BF7A4785E5722BDDD2CE6DAD08A30D90804ECF6.exe
810577: Security Update -
Q810577_WXP_CAF66BF8D1891D990D93004E7E020A08A5347623.exe

Updates Removed:
Security Update, February 11, 2002 (Internet Explorer 5.01 SP2) -
q316059_9BE7032F08CE83424137E826B35D644FBB1B1C38.exe
Security Update, February 11, 2002 (Internet Explorer 5.5 SP2) -
q316059_42E422837F05E4A13367B5329003C308C77F5B95.exe
Uniscribe (USP10 - CIF Only) -
USP10_40BC1A13A4E70268E625A4D799C2B4D9C5D0B6FD.CAB
Security Update, February 11, 2002 (Internet Explorer 5.5 SP1) -
q316059_00413EDFB9C17682D55BEA5848BCEF3B5700FE05.exe
Security Update, February 11, 2002 (Internet Explorer 6) -
q316059_EB66996164240089F784C6C30C91AFECA94030EC.exe

Reissued Update(s):
Q328970: November, 2002 Cumulative Patch for Internet Explorer 5.01 SP
3 - q328970_DE79642B1036EB9510661E2FECB04FDF36E48983.exe
Q328970: November, 2002 Cumulative Patch for Internet Explorer 5.5 SP
2 - q328970_FF02BE931F0918BD81DA33CB84E238663C9A4211.exe
Q324929: December 2002, Cumulative Patch for Internet Explorer 5.5
Service Pack 2 - q324929_E34CB7562E3FADE04E0FBA7A8DF20236ABFC6C46.exe
Q328970: November, 2002 Cumulative Patch for Internet Explorer 6 -
q328970_2F9D66E88E50685533DC4AD55754E92FFB3ED581.exe
Q324929: December 2002, Cumulative Patch for Internet Explorer 6 -
q324929_55049C7F14E3EFF258F10F95FE0A3C179833CB17.exe
Q328970: November, 2002 Cumulative Patch for Internet Explorer 6 SP 1 -
q328970_8ECA0FFD2190A4909BEC6BC2DC3FD5B31DE4E8DC.exe
Q324929: December 2002, Cumulative Patch for Internet Explorer 6
Service Pack 1 - q324929_A90F1A87F766965A4D0FC5F1395F3E808ABE7D27.exe
Q324929: December 2002, Cumulative Patch for Internet Explorer 6
Service Pack 1 ( Windows XP 64-bit Edition) -
q324929_D2F27DDB3DD1F41278E03B042246C69076FDDC16.exe
Q320920: Security Update (Windows Media Player 6.4) -
wm320920_64_AD2877F29FFD6A199E928861D6979496DF66952B.exe
810833: Security Update (Windows 2000) -
Q810833_W2K_SP4_7BCAD659FA326D4979A3CE9034300EA83A30F5EC.exe
Security Update, February 14, 2002 (Internet Explorer 5.5) -
vbs55nen_A76B47D34E497BB2C14BA3CBED923CC042406C8B.exe
Security Update, February 14, 2002 (Internet Explorer 6) -
vbs56nen_60DD81FED024143825A697259A3DFB0EB9F530F5.exe
Security Update, June 7, 2001 -
Q299553_C1C82B1A16A196687853760FC1372F3FD40B41F6.EXE
Security Update, February 14, 2002 (Internet Explorer 5.01) -
vbs51nen_6679B4E5AD916D6462A3AB5B4C2B81C2867CA1E6.exe
Q326830: Security Update (Windows XP) -
Q326830_WXP_SP1_8272F7A670529E654ECE7FB11CFCBEF4461E1FAF.exe
Windows XP Application Compatibility Update, April 2002 -
Q319580_7377086567F22A47D655346683359C1306DF1074.exe
Security Update, February 12, 2002 -
Q314147_4448F8C22D771895880C0CBD09491B03670C483A.exe
Q323255: Security Update (Windows XP) -
Q323255_X86_74E63DB56EC502794E37143D69010AE37C80A57F.exe
Q329390: Security Update -
Q329390_WXP_3F60064794271F0053892985402FE5B6679D3F2D.exe
Q313450: Security Update -
Q313450_WXP_D8AB65F196EA2C5E04716B37F64E6BDE52646A4B.exe
Q323172: Security Update (Windows XP) -
Q323172_DABD0569A94E7C16C903E683121E319B8F7C755A.exe
329170: Security Update (Windows XP) -
Q329170_WXP_SP2_504A5D6839378140418173C76CBAB07E166F8D3E.exe
Windows XP Update Package, October 25, 2001 -
Q309521_x86_3C970D04DED697E0DC2DADED5D10A9974534DB79.exe
System Recovered Error Message Update -
Q317277_8C5A39CF107C69CC9462B9ADF1CF511DF228C575.exe
Q318138: Security Update (Windows XP) -
Q318138_x86_0778B3715BED9BD7F1F3F6FAB13F02B7BC84073B.exe
Q329834: Security Update (Windows XP) -
Q329834_WXP_SP2_x86_3AC87C6443D5CCC79FECEAA5661130DE250A8CE6.exe
Q311967: Security Update -
Q311967_AC5EFC3697AD46F2B02646BA229F31BAC1C0CC26.exe
Critical Update, February 9, 2002 -
Q314862_A50360B6A72A72FB6B575AD8F9BB5B0AB616235C.exe
810833: Security Update (Windows XP) -
Q810833_WXP_SP2_45A2502A400329A5DB92327F4CB345A441FC1D2E.exe
Q329048: Security Update -
Q329048_xp_BDCCA3F0C06417895BF3EE93B6DB09F6D04D0282.exe
Remote Assistance Connection -
Q311889_WxP_27DBA07EDD39B4CC0B3E2C6DB90178E7396CFF1A.exe
810565: Critical Update -
Q810565_WXP_SP2_3B258C3F4F5050D25BD1BC003CE87994B6F47E00.exe
Q324096: Security Update (Windows XP) -
Q324096_WXP_SP1_16DA94962BE1EEFD024866A51316DED2EF99E620.exe
Security Update, December 17, 2001 -
Q315000_3107298CD5FCC82EC3724F62D72B28288B0D27F6.exe
Q329115: Security Update (Windows XP) -
Q329115_WXP_SP2_x86_1D09793FAF21249FEBCC160D341612338DFD3154.exe
Q324380: Security Update (Windows XP) -
Q324380_XPSP1_x86_23BD0EFEC52E12A028C70CEDCB44D5D238733858.exe
Critical Update, February 10, 2002 -
q315403_9EAE12A1A1E27D7AEA96B89AB793A5A28C680ED8.exe
Detailed item description files (Read This First and End User License
Agreement for all items) - aurtf.cab
Sync Finished- February 06, 2003 3:05:46 AM

[Don Cottam [MS]]

When updates are re-issued (they appear with an "updated" status in the SUS
Approval page) it is usually not because the actual update itself has been
re-issued by MSRC, but rather because the detection criteria (the "blob"
that defines what machines the update is applicable to) has been changed by
the Windows Update Content Management team. Modifying the detection
criteria does NOT change the update itself, and doesn't cause it to be
re-installed if it's already been installed by a client.

Hope that helps.

Don [MS]

"John Smith" <n...@na.com> wrote in message
news:uojz9r60CHA.2528@TK2MSFTNGP11...