anwarmahmood

Hi Everyone, Just wondering if anyone has any fresh information on this. Specifically, if you exclude Cookies from the roaming profile, what is the [adverse] impact, if any, on the end user? Are the "contents" of the many tiny individual cookie files aggregated into the cookies.dat file? If so, could you add a logoff script that deleted the individual cookies files, but left the .dat file in, does this solve all problems; - users retain their cookies - roaming profiles don't contain hundreds/thousands of individual cookie files - logons and logoffs are faster Kind regards, Anwar

Hi Ben, Not encountered this specifically, but we do have different makes + models of PCs that *appear* to have the same "sound card" (Realtek or ADI, but I forget which). I thought I may as well get the latest generic driver from Realtek/ADI, and use that. Worked great... except that the PCs/sound cards have a feature where if you plug headphones in, the onboard speaker should be silenced. This didn't happen with the latest generic drivers. Had to go back to using manufacturer-specific drivers for each device. Perhaps something like this is happening to you...? Perhaps not...? Kind regards, Anwar

Hi All, We use System Center Configuration Manager 2007 R3 to provide on demand applications and software metering to Windows 7 SP1 X86 (WSUS, imaging is handled entirely independently). This year, we had a progressive slowdown of PCs. I've eliminated hardware, software, networking, the base image, home directory shares, WSUS/updates, etc. This leaves with applications and printer drivers. We did discover the service hosting WMI was very busy, then discovered the WMI database C:\Windows\System32\wbem\Repository\OBJECTS.DATA was large - 500Mb. (by contrast, out-of-the-box Windows 7 SP1 x86 is about 15Mb). Microsoft's WMIDIAG Download The WMI Diagnosis Utility -- Version 2.1 from Official Microsoft Download Center considers +300MB as very large. WMI is queried by and published to by lots of different parts of the system; slow WMI, slow system. We have some PCs with SSDs, but the WMI file is some sort of database that I don't think was ever engineered to scale to these sizes. Hence even a fast physical disk won't resolve this. I've been doing some deeper analysis based on Troubleshooting WMI Repository Bloat - System Center Blog by Russ Slaten - Site Home - MSDN Blogs Troubleshooting WMI Repository Bloat - System Center Blog by Russ Slaten - Site Home - MSDN Blogs I've gathered some data and wondered if I could share it with colleagues, with the hope that if I show you mine you'll show me yours... Have put up my own data, and methods to gather the data, at http://sdrv.ms/15VGdUM Would *really* appreciate replies. Am not familiar with this stuff, and only done it at my current employer, so I have no "context" of what's OK and what's not. Thanks in advance. Kind regards, Anwar