wsus silverlight product classification and which update actual does the install?

-

under product , classifications, unchecking silverlight (to not updates) nothing (is bug?)... silverlight install/update still shows every pc.  i not install silverlight on machines still updates pc's have silverlight.  i cannot tell difference between updates , actual install on wsus.  if can decline install , approve update great.  do know id?

selecting/deseleting products , classification forward-looking only. once you've synchronized update product category or update classification, it's on machine -- unselecting product or classification not remove system.

theoreticaly, if don't want have full-installer package available clients on system, then appropriate action decline full installation package, and leave product category selected might updates, , approve updates.

however, it's not simple silverlight concerned, , it helps immensely in situation to understand packaging of silverlight, , doing expose fact there aren't "updates" silverlight separated installers.

silverlight 1.0 (kb946609) released on 1/25/08 (and on 2/26/08 vista). subsequent that, 2 additional repackaged installers silverlight 1.0 released, superceded previous installers. on 5/19/08, kb951213 released, superceded kb946609, ergo kb951213 becamse de facto installer silverlight 1.0; on 8/18/08, kb955305 released, superceded kb951213, making kb955305 de facto installer silverlight 1.0. both of these packages released in multiple update classifications (feature packs , update rollups) -- these packages contained updated functionality. say, these silverlight 1.0 packages, there no way separate full-installer updates.

silverlight 2.0 (kb957938) released on 10/20/08, superceded of silverlight 1.0 packages. package, also, released in both feature packs , update rollups. kb960353 released on 2/23/09, package supercedes of others. package was, again, released in both feature packs , update rollups.

so, of date, there 1 current silverlight package, kb960353, released on 2/23/09. package exists in feature packs , update rollups, , full installer silverlight 2.0. package has capability update of released silverlight 1.0 packages, the 10/2008 release of silverlight 2.0.  there no standalone "update" packages available silverlight @ time.

so, if don't want install silverlight on machines don't have silverlight, but you want ensure of existing silverlight installations updated feb 2009 release of silverlight 2.0, you'll need create 2 wsus target groups -- 1 update, , 1 won't update, , approve kb960353 accordingly. mitigating factor, may find several of existing target groups (like contains servers), don't have, , never going get, silverlight, need ensure groups never have these packages approved. need consider existing groups have both -- , won't -- , create subgroups split haves , wontgets.
lawrence garvin, m.s., mcitp:ea, mcdba
principal/cto, onsite technology solutions, houston, texas
microsoft mvp - software distribution (2005-2009)


Windows Server  >  WSUS



Comments

Post a Comment

Popular posts from this blog

some help on Event 540

-
does event 540 me distinguish between user , administrator access?    this event generated ypon successfull logon, logon exactly? successful logon on system?   is there other way log administrator access system using event viewer?   thank valuable response   georges hi,   as far know, cannot distinguish between user , administrator access event 540. more information, please refer to:   event id: 540 http://www.microsoft.com/technet/support/ee/transform.aspx?prodname=windows+operating+system&prodver=5.0&evtid=540&evtsrc=security&lcid=1033   events 528 , 540 http://blogs.msdn.com/b/ericfitz/archive/2004/12/09/279282.aspx   regards, bruce this posting provided "as is" no warranties, , confers no rights. please remember click "mark answer" on post helps you, , click "unmark answer" if marked post not answer question. can beneficial other community members reading thread.
Read more

WMI Repository 4GB limit - Win 2003 Ent Question

-
Image
hi there, i've question size limit on wmi repository (being 4gb). if isn't correct place post this, apologies , can let me know wheere post this? i've come across few servers running citrix have reached limit on wmi repository size , need install ibm director agent hw monitoring. during install getting 'out of disk space' errors entered in mofcomp.log: "(mon apr 02 04:10:36 2012.172843) : error occurred while processing item 4: (mon apr 02 04:10:36 2012.172843) : error number: 0x8004103b, facility: wmi description: out of disk space" when error number http://msdn.microsoft.com/en-us/library/windows/desktop/aa394559%28v=vs.85%29.aspx i see this: wbem_e_out_of_disk_space 2147749947 (0x8004103b) disk out of space or 4 gb limit on wmi repository (cim repository) size reached. windows xp , windows 2000/nt:   disk out of space. i'm wondering if there reason why limit set 4gb or can increase needs be? can't seem find reas
Read more

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file

-
Image
hello. we @ step 0 of migration frs dfsr sysvol replication on windows 2008r2 dc. every time run powershell dfsrmig / getmigrationstate says: "unable create dfsr migration log file. error 1307. all domain controllers have migrated global state 'start'. migration has reached consistent state on domain controllers. succeeded." it creates event id 1302 in "dfs replication" event log, explaining error 1307 means: "this security id may not assigned ownder of object ". i already checked space limits, quotas, permissions on c:\windows\debug according microsoft support article unable fix it. although, there new entries added dfsr00095.txt log file despite error. dfsrxxxx file has not been archived .gz format, and, beleive, contains dfsr diagnostics , events. here of latest entries: 20150908 08:47:27.867 11616 sysm  3354 migration::sysvolmigration::getsysvolreadyflag [mig] sysvol ready 20150908 08:47:27.867 11616 sysm   456 migrati
Read more