Thank you for the response. Workstation support called MS, they are working on an individual patch, but couldn't give us an estimate of when it might be ready. I don't know what scenario is causing the patch to be incorrectly identified, but WSG has tried uninstalling/reinstalling SP1, no effect. Formatting and reinstalling the OS works, but who wants to do that. Fortunately we have only had a handful of machines affected as well, but the number seems to be growing? It's frustrating for our support personnel but, when 10 or less machines out of 2,200 plus are misbehaving, you don't want to reinvent the wheel. I'll have to look at that individual patch and perhaps make it optional or an audit?
-----Original Message----- From: Cisco Clean Access Users and Administrators [mailto:[email protected]] On Behalf Of Victor Aranda Sent: Tuesday, January 13, 2009 11:48 To: [email protected] Subject: Re: MS08-75 Vista Patch Hi Howard, Yes, we are also seeing some residents with the KB959349 issue. The problem is only affecting a few computers whose Explorer.exe datestamp does not satisfy the check even though they appear to be fully updated. We've only implemented a temporary fix by allowing residents online without checking for updates (or not requiring that they pass *all* checks), however the issue hasn't actually been solved. I have a TAC case open for this problem and so far, Cisco's response to us has effectively been "call Microsoft". Victor Aranda Network Administrator Residential Network Services, Housing IT University of California, Irvine -----Original Message----- From: Cisco Clean Access Users and Administrators [mailto:[email protected]] On Behalf Of Speight, Howard Sent: Tuesday, January 13, 2009 7:42 AM To: [email protected] Subject: MS08-75 Vista Patch Anyone experiencing problems with this patch besides us? Failed Checks: pc_vista64, Registry Check [\HKEY_CURRENT_USER\Software\Wow6432Node\ exists ] pc_KB959349_MS08-075_Vista, File Check [$SYSTEM_ROOT\Explorer.exe later than [C]10/28/2008 00:00:00] MS has not released an individual patch and it's causing problems with workstation support. Thanks, Howard
