Following my previous post regarding the Cloud Management Point gateway feature introduced with the fast channel current branch update (see http://blog.hametbenoit.info/2016/12/12/sccm-cloud-management-gateway/), another new “cloud” feature has been introduced called Cloud Distribution Point. As with the Cloud Management Gateway, this will help managing internet based client with SCCM.
This new feature will make your internal distribution point(s) available to the internet client based using Azure.
Enable the Cloud Distribution Point
NOTE if you already have enabled the Cloud Management Gateway as per my previous post, you can bypass this step
From the console, access the Update and Servicing section to download and install the update
When installing the update, ensure you enable the Cloud Management Gateway feature
Create the Cloud Distribution Point
Before starting you will need to request a new certificate to include the cloudapp.net namespace.
NOTE if you already have enabled and configured the Cloud Management Gateway, you need to define another cloudapp.net namespace which will need to be included in a certificate. Certificate which will be used as a management certificate (export to a .CER file) as well as to provision the Azure piece (export to a .PFX file)
Then from the SCCM console, go to the Administration\Cloud Services\Cloud Distribution Points to create the new gateway.
The process is pretty straight forward
Provide the Subscription ID and the management certificate (the new one with cloudapp.net in a .CER and .PFX format) – the CER file will be uploaded into the Azure subscription while the PFX will be imported into SCCM with the wizard.
You can get the Subscription ID from the Azure portal
Select the correct FQDN (*.cloudapp.net) to generate the service name as well as the Region where the VM will be provisioned and the SCCM site server to use as master
Once the cloud distribution point is provisioned (status Ready in the console) it will become an available distribution point
You can then associate it with a distribution group and/or select it as DP when deploying your packages.