11 votesstarted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This is available in #SCCM 1903 TP
45 votesstarted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
In #SCCM 1904
82 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We have shipped additional log collection functionality in 1912 TP. This will allow you to collect log files on demand from a client and view them through Resource Explorer.
Please try it out and let us know what you think!
100% agree. I'm using a vote on this. Let me see what we can do.
Martin / Chris - help me understand more what the gaps are between App Model, and Prog/Pkg model?
This is complete for System Discovery but not for User Discovery.
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 votesNoted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Like the idea. Does it need to fail? What if it succeeded?
155 votesstarted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint 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.
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
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.
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?
282 votesstarted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
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…
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.
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.