AlwaysOn VPN-Settings with #ConfigMgr is great. However, I miss different setting: <AlwaysOn>, <RoutingPolicyType> to force tunneling, <CryptograpySuite>, <DeviceTunnel> and so on. Are there any plans to enhance this?
Since Windows 10 and this massive updates we rolled out 140 client distribution points. With 1806 network boot is also possible with these distribution points. Please add this missing feature. Then it's really perfect and really easy to support smaller remote locations. Thanks!
Version 1806 installed this week. While I love the possibility to define a custom web site we still miss categories deployed to machines. When do you think to implement this functionality? This worked well with the old Software center.
Historically we deploy apps to machines because it was the way to do so until ConfigMgr 2012 I think. We maintain 1300 Applications so it will take much more time to change to user targeted deployments. And we don't know how to prevent users to login to many machines to install licensed apps like AutoCAD or something else. Because of this we deploy to machines.
Historically we depoly Applications to machines. We have maintained the categories for the software catalog to make it easy for our users to find the software they need. However, the new Software Center do not show the categories in "Filter" for deployments targeted to machines.
Please enable filtering for machine targeted applications. Thanks!
We also deploy software to machines and we have really a problem if the catagories do not work. We deploy software on computer basis with AD Groups for years now and it's nearly impossible to change this system because of the amount of computers in combination with amount of software. That's history.
Updated by bobmn for sangeev/OSD
It would be great to have this feature. Please make it possible that the DPs are trusted locations. So it could be easy to "white list" a machine with applocker. :-)
Updating status to started, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of the values.
We released our 1905 Technical Preview today.
This release has the first round of changes to address this ask – see https://docs.microsoft.com/en-us/sccm/core/get-started/2019/technical-preview-1905#bkmk_osd
We do not use the built-in step. We use a custom command line to suspend bitlocker. This works like a charm.
Updating status to started:
SCCM 1904 Technical Preview is released.
For more info:
This Technical Preview has the new variable I mentioned – https://docs.microsoft.com/en-us/sccm/core/get-started/2019/technical-preview-1904#bkmk_osd
Set SMSTSRebootDelayNext to control the restart delay after SMSTSRebootDelay
With the new SAC this could be great!