BaardHermansen
My feedback
-
592 votes
-
20 votesNoted ·
AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thank you for your feedback. Folder support is something that is very limited in the cmdlet library today and something that’s in our backlog to improve in a future release. In my opinion, I think the way things should work is if you’re in a collection folder in the cmdlet drive provider, it should just create the collection in the right place.
I’ve linked this feedback to our internal work item to improve folder support so this doesn’t get lost.
Thanks!
BaardHermansen supported this idea ·
BaardHermansen commented
The folder names are different in the console and the cmdlet Move-CMObject.
Console: Applications
Cmdlet: Application
Since this is a standard folder regardless of site code, the names should be the same. -
142 votes
Updated by bobmn for sangeev/OSD
BaardHermansen supported this idea ·
-
5 votes
BaardHermansen commented
Put those computers in different OUs, create two different deployment types and set each deployment type with a Requirement that computers must be member of the different OUs.
-
98 votes
BaardHermansen commented
Any chance you can share this extension? I couldn't find it on you webpage :)
-
1 vote
BaardHermansen shared this idea ·
-
27 votes
BaardHermansen supported this idea ·
-
27 votes
BaardHermansen supported this idea ·
djam: Any progress or at least some more info on this you can share?