 |
 |
Also note that the fixes for this issue are scheduled to be released through regular M$ channels (WSUS, AU, WU/MU) May 22nd. See the second post here http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=mi crosoft.public.windowsupdate&tid=11713832-da68-4f06-93a5-e5dd5103ebca&p= 1 to apply the patches early, and http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx for the May 22nd reference, straight from the M$ mouth. We've applied it on a few of us tech's machines and it does fix the problem. The amazing thing is that there are references to people complaining about this problem back to February 2006, or something around there. Thank Goodness M$ is taking security and patching seriously under their new initiative, or it may not have been fixed till 2009 or 2010. Whew! Brian Hoort Phys Plant Geek