Windows patches issue


dear team,

we facing issue windows patches. there windows 2008 x64 related patches not applied wn2k8 std edition same applying win2k8 enterprise edition. 

how happening microsoft not releasing patches standard & enterprise (edition based) separately correct me if wrong..

so can solve issue.

t&r,

sachin salvi

we facing issue windows patches. there windows 2008 x64 related patches not applied wn2k8 std edition same applying win2k8 enterprise edition.

to frank, scenario impossible because neither windows update agent, nor packages published wsus, capable of distinguishing difference between *editions* of same version of operating system.

while readily accept observing different update detection behaviors on [a] standard edition vs [b] enterprise edition, promise difference not because of *edition*. other factor @ work in case -- perhaps update missing standard edition servers; perhaps role not installed on standard edition servers?

also, because windows server 2008, keep in mind there 2 separate skus of ws2008 available - 1 hyper-v , 1 without hyper-v -- factor contributing factor in observed behavior.

the key here determine different between these 2 groups of servers other edition installed.

also, use ambiguous term "applied" in post. let's talk more distinct terms:

  • are updates in question reported not applicable to ws2008 ented systems?
  • are updates in question reported not installed to ws2008 ented systems, failing download/install expected?

lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
solarwinds head geek
microsoft mvp - software packaging, deployment & servicing (2005-2013)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin
http://www.solarwinds.com/gotmicrosoft
the views expressed on post mine , not reflect views of solarwinds.



Windows Server  >  WSUS



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

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