Like the idea. Does it need to fail? What if it succeeded?
Do we just need a “patch Tuesday” concept, or is there any other named event that we also need to plug in?
Spent a lot of time talking about this w/ customers last week. Definitely a huge need:
I sum it up as these asks:
1) provide a offset for scheduling (2nd Tuesday + X days or hours)
2) improve filtering for architecture
3) improve filtering for language
4) possibly allow creating on deployments of updates not already deployed
We've partnered w/ Intel for their add on to integrate well with ConfigMgr. They will be able to keep it up to date w/ newer versions of VPro/AMT, as well as newer versions of ConfigMgr current branch.
This improvement is in #SCCM 1706 TP, and should be in the next production release.
18 votesNoted · 2 comments · Ideas » Setup and Server Infrastructure · Flag idea as inappropriate… · Admin →
This is already implemented in current branch. This is what the auto-upgrade feature of the client does. If you enable it on, you can set the timeframe for clients to check for updates and to upgrade themselves. There is no need to open any firewalls for server -> client communication; as the client is doing the checks on schedule and will pull down the needed content from DPs when it determines it needs to upgrade.
Have you looked into this feature?
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?
yes – we will address this. see my comment.
We know this limitation, and will address it. Rather than waiting until CloudProxy was perfect, we wanted to start shipping early previews of it... so we could start the conversation / feedback.
Currently, does not have user auth - so can't do things requiring user auth (like App Cat). We will fix this in the future.
Great idea. What should the default permissions be for this role? i.e. what actions does it need, and not need?
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.
do you have many objects under each of these? Is it just to deal with the large number of objects there? Or are you trying to solve another problem (like filters or automatic grouping?)
The intent is to move all of the application functionality into the new software center, which if I understand correctly should mitigate all of these issues. If we achieve that, what scenarios would still require a web based app catalog?
Where would you want to enter the email address to email?, and how many do you need? One per App? One for all approvals? (which I guess could be a DL)