Stephen Owen
My feedback
-
13 votes
An error occurred while saving the comment Stephen Owen
supported this idea
·
-
88 votes
An error occurred while saving the comment Stephen Owen
commented
To clarify, assuming I've installed CM to E:\CM, I have to import the module running
import-module E:\CM\AdminConsole\bin\ConfigurationManager.psd1
However, if the path were registed as I recommend above, I could run simply
Import-Module ConfigurationManager
And it would automatically import. Even better, you don't NEED to import a module first. Module Autodiscovery will import the module for you at the first time that you attempt to use a CM cmdlet on that system. It really *IS* great.
Stephen Owen
shared this idea
·
-
19 votesStephen Owen
shared this idea
·
-
320 votes
An error occurred while saving the comment Stephen Owen
commented
If you can create an item with Compliance Items, you should be able to delete it to. This is basic CRUD stuff so let's make it happen
-
18 votesStephen Owen
supported this idea
·
An error occurred while saving the comment Stephen Owen
commented
This suggestion needs WAY more attention. I often swap between customer's SCCM environments, and when I get a request like 'Deploy App X to User Y' I have to go to applications and look up the app, then see where it is deployed, then find the colleciton, then change the collection membership.
Instead, it would be awesome to be able to Right-Click a Collection in the Deployments Screen and have an option of 'Add Computers to Collection', or 'Modify Collection Membership'. Or, it could open the Collection properties instead.
Take all of my votes, please make this happen.
-
17 votesStephen Owen
shared this idea
·
-
8 votes
Thanks for the feedback. Updating to Noted
https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
Stephen Owen
shared this idea
·
-
9 votes
An error occurred while saving the comment Stephen Owen
commented
I very, very commonly have to just into a particular package's source files to adjust scripts, add new files, etc. Just today for instance.
My work flow today is to go to Software Library\packages\Find the package\Right-click\choose 'Properties' and then I get the Package Source Location from there.
Today, the summary page for packages and applications is pretty barren. Let's put a link to the package source location right here!
-
24 votes
An error occurred while saving the comment Stephen Owen
commented
Would love to be able to customize multiple highlighting rules. Furthermore, we should have a shortcut for highlight, and filter. I propose Ctrl+H be switched to controlling highlighting, while CTLT+I be made for filter.
-
110 votesstarted ·
AdminAdam Meltzer (ConfigMgr Product Team)
(Software Engineer, Microsoft Endpoint Configuration Manager)
responded
Quick links to status message queries from the UI has been added in 2010, and this is something we’re continuing to improve upon in future releases.
An error occurred while saving the comment Stephen Owen
commented
I'd like to see this linked from the Task Sequences list under OSD. Let me see a direct link from the Summary tab to hop into the status messages view/report.
-
98 votes
An error occurred while saving the comment Stephen Owen
commented
Also, you're welcome to use my glorious, MS Paint design of this feature, if you'd like ;-)
Stephen Owen
supported this idea
·
An error occurred while saving the comment Stephen Owen
commented
Add a list of the Computer or User collections to the 'Summary' pane, under Assets And Compliance \ Devices or Users.
Every time I install SCCM for a customer, I'm asked 'how do I see collections for a device or user'. I don't want to have to tell them to install third party tools, or to run a report, or the other kind of bad solutions we have today.
-
68 votesStephen Owen
shared this idea
·
The syntax to get speed improvments for the new Add-CMDeviceCollectionDirectRuleMembership cmdlet is super weird, and it's not covered in the help examples.
Speaking of which, the copy in the help examples on 1806 has some very esoteric verbiage.
I'd like to see the help updated with easier to read wordings, and an example should be added to demonstrate the quicker syntax.
On that topic, why does the cmdlet now take both a -Resource or -ResourceID paramsets? The cmdlet has become kind of weird, maybe the old operation mode should just be removed to make it easier to understand.
The speed gains ARE REAL though, and super impressive. Awesome work team!