We have been seeing similar issues since our upgrade to 1706 wave 1. I haven't made time yet to upgrade to wave 2 and the hotfix to see if that fixes it.
Another theory I have wanted to test is how often are your hardware inventories, application evaluations, software update scans, etc occurring? I'm a bit of a spaz about that and have hardware inventories and software update scans every 12 hours. Application evaluations every 4 hours and Software inventories occur every 7 days. SQL has 4 cores and 24gb of ram, SCCM has 2 cores and 12gb ram. 2700 clients. Thanks, Chris Brucker > On Sep 28, 2017, at 9:06 AM, Daniel Ratliff <dratl...@humana.com> wrote: > > CAUTION: The e-mail below is from an EXTERNAL source. Please do not open > attachments or click links from an unknown or suspicious origin. > > > > Anything in smsprov.log? > > Daniel Ratliff > > -----Original Message----- > From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] > On Behalf Of Stuart Watret > Sent: Thursday, September 28, 2017 5:31 AM > To: mssms@lists.myitforum.com > Subject: [mssms] Slow Console performance for some users > > So, finished our migration to new server running 1706. > > OS 2016 / SQL 2016 Sp1 CU5 / Compatibility 130 > > Its absolutely fine for me, I have three colleagues who are also full admins, > one of them is fine, the other two have appalling console performance. > > We have removed the console and reinstalled, we have had them run the console > on the server, the results are the same. > > If they drill down to a package, then click the program tab, they have the > donut of doom, for a long time before it enumerates. > > This is repeatable. > > Any thoughts? > > Stuart Watret > > > > > > > ********************************************************************** The information contained in this message from First Financial Bancorp or its affiliates and any attachments are confidential. It is not intended for transmission to, or receipt by, anyone other than the addressee(s), or a person authorized to deliver it to the named addressee(s). If you have received this message in error, you are prohibited from copying, distributing or using the information. Please contact the sender immediately by return email and delete the original message.
