Allow Console Extensions to access the Connected Site Code and Connected Server when launched from areas in the console that aren't IResultObjects. When an extension is launched from a node such as Applications or Packages, we no longer can use the ##SUB:Server## or ##SUB:Namespace## fields. Similarly for assembly based extensions, the IResultObject is null and we can't get at the IResultObject.ConnectionManager property.8 votesNoted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This makes total sense. Great ask.
A lot of customers would like to customize their admin consoles to add some missing views, columns and actions. For example, displaying User device affinity in Devices list or vice versa.
AdminUI.ConsoleBuilder is a good tool for this but it is very unfriendly and there is zero documentation on it.
It would be great if you add docs on it and improve the tool itself14 votesNoted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager) responded
Thanks for the suggestion!
SMSTaskSequenceRunCommandLineAction uses PackageID
SMSTaskSequenceInstallApplicationAction uses AppInfo (and ApplicationName?)
SMSTaskSequenceApplyDriverPackageAction uses DriverPackageID
SMSTaskSequenceApplyOperatingSystemAction uses ImagePackageID
SMSTaskSequenceUpgradeOperatingSystemAction uses InstallPackageID
While they are different objects and they do different things, shouldn't this be standardized across classes that can have content dependencies in a TS? This makes the data coming out of Get-CMTaskSequenceStep difficult to work with, as you have to keep a rolling library of properties to check for Package ID's.3 votesNoted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We wouldn’t fix the backing WMI schema because that would introduce breaking changes to any SDK consumers.
We could consider a fix on the PowerShell side to allow for more consistent display of these objects (without changing the objects themselves) to make them easier to consume via automation.
If you play around with the possibility to send messages like inventory, ddr,... with the Microsoft.ConfigurationManagement.Messaging.dll it would be nice to write the message to a file on the lokal development system (for validation / verify purposes) instead of sending it over the wire to get the result.3 votesNoted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thank you for your feedback.
In the short term, can be worked around by implementing your own instance of IMessageSender and using this to send the message.. In this custom sender, you can handle the message any way you want.
We will consider adding this as built in functionality to the SDK in the future for advanced debugging scenarios.
ConfigMgr agents are able to fallback to an alternative SUP if the original SUP failed - agents do not fallback to the original SUP once it’s available again. In this case fallback needs to be triggered manually. This can be done from the console using „client notification“ – wouldn’t it be good to also be able to force SUP fallback on the client itself? Document a script method to switch to the next SUP that can be run on the client itself.5 votes
Please fix CCM_Client and CCM_DiscoveryData Discovery on Microsoft.ConfigurationManagement.Messaging.dll
We use Microsoft.ConfigurationManagement.Messaging.dll in Version 5.1706.1034.1000. The Discover() Method from "Microsoft.ConfigurationManagement.Messaging.Messages.ConfigMgrDataDiscoveryRecordMessage" return wrong results on CCMClient (InstanceDataXml : <CCMClient><ClientId>GUID:4D440652-FEC7-4709-B84C-1EC844F910FD</ClientId><ClientIdChangeDate>09/20/2017 14:50:30</ClientIdChangeDate><ClientVersion>5.00.8325.0000</ClientVersion><PreviousClientId>Unknown</PreviousClientId></CCMClient>, We use current Version SCCM1702) and on CCMDiscoveryData, the OS is Microsoft Windows NT Server 10.0 on a Windows 10 1703 Client (InstanceDataXml : <CCMDiscoveryData><PlatformID>Microsoft Windows NT Server 10.0</PlatformID></CCMDiscoveryData>)2 votesNoted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thank you for reporting this. We will look into fixing this in our next release.
The Messaging.dll only Support the old Boundary model for content requests and MP request. We need support for the new boundary model.6 votes
We will definitely look into adding support for the recent additions to location requests integrated into the messaging SDK for a future release.
Currently there is no way to use Secret Task Sequence Variables in third-party extension to SCCM. Please, add API for this or document how to achieve this.5 votes
Updated by bobmn for sangeev/OSD
- Don't see your idea?