Admindjam
(Admin, System Center Configuration Manager)
My feedback
-
4 votes
Thanks for your feedback, updating status to Noted
We’ve made some recent improvements to the Run PowerShell Script task sequence step. The recent Technical Previews would have these changes – https://docs.microsoft.com/en-us/sccm/core/get-started/2019/technical-preview-1901
You can now directly enter a script or browse to the existing scripts in \Software Library\Scripts and select any of the approved scripts or a local file (.ps1 – provider will need access to that path).
Other changes made bring the step in line with Run Command line – you can use RunAs, there’s a timeout added etc.
Do these changes address your ask?
Admindjam
(Admin, System Center Configuration Manager)
supported this idea
·
-
10 votesAdmindjam
(Admin, System Center Configuration Manager)
supported this idea
·
-
123 votes
Martin / Chris - help me understand more what the gaps are between App Model, and Prog/Pkg model?
Admindjam
(Admin, System Center Configuration Manager)
shared this idea
·
-
2 votesAdmindjam
(Admin, System Center Configuration Manager)
shared this idea
·
-
23 votes
Thanks for the feedback, updating status to Noted
See https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/ for an explanation of values.
Make it easier to configure winpe keyboard layout (and other settings) in the default boot wim
-
35 votes
where exactly do you want to copy & paste? I just tried 5 places in the UI – and they all worked?
where exactly do you want to copy & paste? I just tried 5 places in the UI - and they all worked?
-
19 votes
Client Autoupgrade honors the maintenance windows. Maintenance windows are designed to give this kind of control for servers. Rather than create a 2nd way to do the same thing (because that's what makes products complex, is many ways to do similar things).... help me understand why you can't solve this with maintenance windows?
-
7 votes
great idea.
Admindjam
(Admin, System Center Configuration Manager)
supported this idea
·
-
17 votesAdmindjam
(Admin, System Center Configuration Manager)
supported this idea
·
-
19 votes
Updating status to started, we’ll update again when the changes are available in a Technical Preview release.
https://docs.microsoft.com/en-us/sccm/core/get-started/technical-previewProposed change is making the autorun.inf optional since it’s needed in bare metal scenarios.
Glen – makes sense, I’ll pass on the ask to remove from the CD.latest etc. (different feature team)
Admindjam
(Admin, System Center Configuration Manager)
supported this idea
·
-
20 votesAdmindjam
(Admin, System Center Configuration Manager)
supported this idea
·
-
34 votesAdmindjam
(Admin, System Center Configuration Manager)
supported this idea
·
-
6 votes
Like the idea. Does it need to fail? What if it succeeded?
-
147 votesstarted ·
AdminMark Silvey - ConfigMgr Product Team
(Admin, System Center Configuration Manager)
responded
This is now available in the 1612 Technical Preview.
Also would allow easier creating of customer web UI, and easier to require things like MFA.
-
18 votes
Add workflow type experience in the DCM/Settings UI for dealing with more complex CIs... especially for handing things like If/Else/Or, etc.
Idea from: @terencebeggs
-
0 votes
This is an issue with windows code that deals with time. 1/1/1970 will cause crashes when doing timezone adjustements (because it can become 12/31/1969) (even when simply converting to UTC)
Best to never use 1/1/1970.
-
4 votes
Yes - database name needs to be "instance\database". Are you saying SCCM created this key wrong? or someone manually edited it to break it initially?
-
18 votes
Great idea. What should the default permissions be for this role? i.e. what actions does it need, and not need?
-
259 votes
This can be done today w/ #SCCM 1802 (and previous versions too). I will mark started… and watch comments for why this doesn’t just work… before I mark this straight up completed…
Steps:
1) On the CAS (or standalone primary), go to Administration → Hierarchy Configuration → Discovery methods
2) right click on Active Directory System Discovery and bring up the Properties form. Active Directory Attributes tab, and then click on Custom. In the form that appears, type the name of the attribute. Click OK, and make sure you have added it as an attribute to discover. Run discovery after exiting properties form.
3) Now when you go to the Devices view and right click on a device and go to its Properties form, you will see the new attribute showing up there.it is the GC.
Do you just want this to see it in the UI? That's simpler that sync'ing it into the database. It's hard to copy into the database, because AD discovery is efficient when it syncs directly from the global catalog. I do not think desc is in the GC. If you just want it in the UI, perhaps the UI can sync realtime from AD when you view it.
-
21 votes
Request from @TheWMIGuy...
The ability to run cmtrace from the command line, like this:
Cmtrace /mergelogs: appdiscovery.log,appintenteval.log,smsts.log,appenforce.log
Another request I saw on twitter... parameters for merging logs.
Admindjam
(Admin, System Center Configuration Manager)
shared this idea
·
100% agree. I'm using a vote on this. Let me see what we can do.