Hi, We saw the exact same problem. The problem was caused by having a lot of (custom) Hardware Inventory Classes. After we removed a lot that was actually not used anymore, the time it took to open the Edit Query Statement, got dramatically reduced.
What happens is that every time you open Edit Query Statement, it has to load all those classes. Try looking into that. Best regards Jesper van Dyk Jess From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Dave West Sent: 12. april 2016 15:28 To: ms...@lists.myitforum.com Subject: [mssms] 2012 Console Soooo Slow! Hi, We are in the process of implementing ConfigMgr 2012 R2 SP1 CU3 and we have noticed the console can be really slow. Most of the time it is fine (not as responsive as the 2007 console but okay) but especially when trying to edit Query Statements, it takes 40-60 seconds to display the Query Properties dialogue. We have had a look around and have checked the usual index rebuild task and even implemented the CMMonitor database described here<https://stevethompsonmvp.wordpress.com/2013/05/07/optimizing-configmgr-databases/> but it hasn't made much difference. Incidentally, if we use the console on the primary site server it is more responsive, but our remote consoles are really slow, especially when viewing Query Properties. Has anyone else experienced this or does anyone have any advice how to diagnose and or resolve this issue? Dave West Senior Operations Analyst Room 301 Babbage Building | Plymouth University | Drake Circus | Plymouth | PL4 8AA | UK Tel: 01752 587247<tel://+44752587247/> | Email: dave.w...@plymouth.ac.uk<mailto:dave.w...@plymouth.ac.uk> [cid:image001.png@01D0299F.2666E200] ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.
