I've been debugging crashes on the print spooler on a Windows 2008 x64 domain controller which is a print server. With all of the advances Microsoft has put into Vista and Windows 7 on the client side to help debug and diagnose issues such as the automated collection technology inside Performance and Reliability monitor you'd figure that they could figure out a way to isolate a fault down to a vendor driver. Thats not the case, I've had to jump through hoops for about 8 weeks to figure out what the causes of the crashes are. I think its partially related to running x64, and x64 drivers, but having mostly x86 clients printing. Its kind of a mess, but its been improving with patches and the countless dumps and other files I've been sending them.
We all are well aware of the Microsoft patches and windows update. Same goes for those of us who use itunes and iOS devices, we know Apple Software Update. Some of us may even patch our Adobe products, which we should since they have been the largest attack vector (http://goo.gl/bOQ3D) for the past 2 years hands down. This is just at home.... How do you expect the security experts to keep on top of all of these patches in a corporate environment. The number of patches for Oracle alone is daunting to understand and analyze. There are ways to do this, you can use some clever software which I will outline below, or you can read ~25 RSS feeds and analyze vendor security bulletins. I do enjoy doing some of this, but I don't have time to keep on top of all the releases. Here is some software for home and corporate use to help manage this. Corporate Patch Management: Microsoft WSUS and SCCM - This is free and a no brainer for patchi...
Comments