RE: [mssms] Identify who ran an update on a top-level limiting collection

2017-11-12 Thread Garth Jones
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Friday, November 10, 2017 4:28 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] Identify who ran an update on a top-level limiting collection Awesome, thanks Mike. Trying

RE: [mssms] Identify who ran an update on a top-level limiting collection

2017-11-10 Thread Daniel Ratliff
Awesome, thanks Mike. Trying it now… Daniel Ratliff From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Mike Dougherty Sent: Friday, November 10, 2017 4:17 PM To: mssms@lists.myitforum.com Subject: Re: [mssms] Identify who ran an update on a top-level

Re: [mssms] Identify who ran an update on a top-level limiting collection

2017-11-10 Thread Mike Dougherty
You could run a status message query for "All Status Messages from a specific component at a specific site". Component is: "Microsoft.ConfigurationManagement.exe" Provide the Site Code and time when prompted. The status message in question will have a description along the lines of: User "DOMAI

[mssms] Identify who ran an update on a top-level limiting collection

2017-11-10 Thread Daniel Ratliff
Short of scouring colleval.log, does anyone have a way to identify who could have updated membership on a limiting collection causing the below picture? It is from CEviewer and yes, its nearly 6000 collections. Now I am waiting 2-3 hours before the collection I need will update. This is the 2nd