This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 99%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFS%3C/text%3E%3C/svg%3E)
The newest SCCM Version shows the following feature:
Can anyone explain what we can do with the new "VPN for Windows 10" feature?
Franz
Hi, @Franz Schenk
I'm afraid we do not have other way to deploy VPN profile to clients with SCCM.
As the documentation states, it's recommended to use Microsoft Intune to deploy it.
You may try to send a frown about this:
https://learn.microsoft.com/en-us/mem/configmgr/core/understand/product-feedback#send-a-frown
Thank you. Can't understand Microsoft anymore.
Publishing such misleading information (listing "VPN for Windows 10" as a new feature for 2107)
This is not a correct statement as has been called out.
Remove SCCM features without providing a replacement. Customers using SCCM use SCCM and normally not Intune. Customers using Intune do not use SCCM.
This is also not a correct statement. Co-management is the path forward and we've been saying that for many years and we have a large percentage of customers doing just this.
So poor SW quality for their onpremise products.
I'm sorry you feel that way although that's not what this thread is about. Thus, have you opened support cases or at least started additional threads about what you perceive as poor quality?
I see why that's confusing, but that list is not for new features in the release; it's for features you can optionally enable with most having been around for a while now. See https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/whats-new-in-version-2107 for what's new in 2107.
Hi, @Franz Schenk
Thank you for posting in Microsoft Q&A forum.
First, the feature "VPN for Windows 10" is not a new feature in SCCM 2107 like Jason said, it's the feature you can choose to enable if you haven't enable it yet, it also listed in SCCM 2103 feature list. And the feature is for create and deploy VPN profiles.
Then, starting in Configuration Manager version 2103, this company resource access feature is deprecated. We can use Microsoft Intune to deploy resource access profiles. It is first announced on March 2021, but we can still use it, it will be removed in the first release after March 1, 2022.
For your reference:
https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures#deprecated-features
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hello Jason and AllenLiu
Thank you for your feedback. But can anyone explain about the SCCM "VPN for Windows 10" feature that is not a sub-category of company resource access? I can't find anything else about VPN in SCCM.
I have seen the Microsoft statement rhat company resource access is depreciated in 2103. You are right that the feature is still visible in 2103, but it has stopped working already with this version. Have a VPN profile with EAP Authentication, and it's deployed with MS-Chapv2 Password authentication to the clients. In SCCM 2010, a VPN profile with EAP Authentication was deployed correctly.
Franz
"VPN for Windows 10" feature is VPN Profiles in your screenshot, is a sub-category of company resource access.
What do you mean when you say "it has stopped working already with this version"?
I hope that the printscreen below explains the situation. Have configured a VPN profile in SCCM with EAP authentication. And since SCCM 2103, the profile is still created on the client, but unusable due to the wrong authentication method.
