brent17123

Hi, we also had this issue. It was affecting x64 Windows 7 machines with 2GB RAM as you say. Declining unneeded superseded/expired updates on our WSUS server reduced this problem dramatically. Have a look on this post: https://social.technet.microsoft.com/Forums/windows/en-US/4a782e40-bbd8-40b7-869d-68e3dfd1a5b4/windows-update-scan-high-memory-usage?forum=w7itproperf&prof=required And the solution for us: Support Tip: ConfigMgr 2012 update scan fails and causes incorrect compliance status - The Official Configuration Manager Support Team Blog - Site Home - TechNet Blogs I believe the hotfix released also resolves the issue! Brent

Our students have started to clock on that they can change the speaker name on windows 7. I have considered removing the speaker icon etc using GPO. However users do need access to this really to change volume and such. Does anybody know of a GPO or could anybody help provide a script which could reset our playback device name to "Speakers" across the network and keep it that way or change it back at restart. I have created a script which resets the name at startup, however this only works on unchanged computers which are already named "speakers". Any machines which already have the playback device renamed will reset to the name the student changed it to at every start-up! Any help appreciated! Thanks.