I understand that your company manages completely through the console; but at
my company, we have several different lines of business, with different
security scopes and what they can see for collections for software update
targeting. For tracking software update deployments for their collections, all
of that is done through reporting.
If that's a critical need for you, the channel to request that is called a
"Design Change Request", or DCR. You would submit the DCR, and outline what it
is you are looking for. Microsoft will review and prioritize it among the
other DCRs submitted.
On Wednesday, May 27, 2015 4:58 PM, Michael Roach <[email protected]>
wrote:
I disagree in this instance. Reporting has its place but we manage our
environment in the console not in reports.
If our environment was managed by a single team that was maintaining a single
set of SUGs that cover the entire user base then I wouldn't have a problem
because MS supports this out of the box.
What I want is for them to complete the feature so those of us in more complex
management environments can get the same ease of use as everyone else.
> On May 27, 2015, at 4:46 PM, Jason Sandys <[email protected]> wrote:
>
> That's what reporting is for.
>
> J
>
> ________________________________________
> From: [email protected] <[email protected]> on
> behalf of Michael Roach <[email protected]>
> Sent: Wednesday, May 27, 2015 3:46 PM
> To: [email protected]
> Subject: [mssms] Is this feature coming to ConfigMgr 2012?
>
> Anyone heard if Microsoft will be enhancing the Software Library > All
> Software Updates search criteria to support collection membership as a filter
> constraint?
>
> Seems like it should be an easy thing to add and would make this view much
> more useful for those of us with many different teams responsible for
> patching their own areas.
>
>
>
>
>
>
>
>
>
>
