Hello, When we try to configure the PullDP to use CDP as Source, the pullDP only uses the proxy configured on Winhttp service, neither the proxy configured in site system property or the Configmgr control panel applet are used. Seems at moment the admin has to configure Winhttp proxy manually to allow the pullDP to get the content from CDP, whereas this should be handled by sccm, whenever the Pulldp is being enabled in the console, the proxy configured on the Site system props has to be applied in the winhttp service on the system context as well.

Got to know that this piece is missing as proxy configured on site system applicable only for Site system (server config) and pullDP is not a server component as it uses CCM_framework of the client, also on the other-hand the proxy on the configmgr client applet also not get applied as PullDP runs independent of the client though it shares the same framework.

Thanks in advance.

Improve the SQL AlwaysOn Pre-Requisite detection so that "Set Trustworthy" and "Enable CLR" are flagged; if that's not possible prior to DB creation, could a note be added to the pre-req page with a warning stating these pre-reqs for SQL AlwaysOn? Today using 1606 baseline media, the installation nearly completes and then logs this error when those pre-reqs are not installed:

INFO: SQL Connection succeeded. Connection: <myserver> CMXXX, Type: Secure Configuration Manager Setup 1/26/2017 4:11:30 PM 5276 (0x149C)
SELECT dbo.fnConvertBinaryToBase64String(thumbprint) FROM master.sys.certificates WHERE name='ConfigMgrEndpointCert' Configuration Manager Setup 1/26/2017 4:11:37 PM 5276 (0x149C)
[42000][6263][Microsoft][SQL Server Native Client 11.0][SQL Server]Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option. Configuration Manager Setup 1/26/2017 4:11:37 PM 5276 (0x149C)
CSiteControlSetup::CreateBackupSQLCert : Failed to get SSB certificate thumbprint. Configuration Manager Setup 1/26/2017 4:11:37 PM 5276 (0x149C)
CSiteControlSetup::SetupCertificateForSSB : Failed to create/backup SQL SSB certificate. Configuration Manager Setup 1/26/2017 4:11:37 PM 5276 (0x149C)
ERROR: Failed to set up SQL Server certificate for service broker on replica node "<myserver>" . Configuration Manager Setup 1/26/2017 4:11:37 PM 5276 (0x149C)
ERROR: Failed to initialize the site control data. Configuration Manager Setup 1/26/2017 4:11:37 PM 5276 (0x149C)
Not recovery mode or not top level site. Skip restoring client piloting packages. Configuration Manager Setup 1/26/2017 4:11:37 PM 5276 (0x149C)

Some replications groups are big like 'Configuration Data' and for big enterprises could go up to 30-50 Gigs. The issue is that is the BCPIn fails for some reason, the retry count is only 3 and until we realize we are in failed state. So if we fix the issue after sometime we have to again reinit the big group and that is again waste of time and bandwidth.
Currently we expose these settings in the SiteControlFile.
//
select * from SCComponentProperty where name like '%bcp%'

BCPOutRetryCount
BCPInRetryCount
BCPInBatch
//
We want to modify these settings say BCPInRetryCount to be more so that we can fix the issues that we incur and avoid the Reinit.

When deploying the new Cloud Proxy Service role in SCCM 1606, the user is asked to provide a Cloud Service Name. However, the UX does not explain that this is needs to be globally unique in all of Azure. I chose the name of 'SCCMCloud' turns out someone else already got that one though, and so the wizard completes and then fails in provisioning.

This is sloppy. The UX should include instructions for the end-user to validate their name first (which can be done in Azure -> Cloud Service -> New, you're able to test various names until you find one which is unique to all of Azure), OR the UX should integrate the same logic found in Azure and validate the name before we proceed.

The introduction of preferred management points in SP2/R2 SP1 is GREAT! But I'd like to see the following added to the console to improve usability.

When viewing the properties of a boundary group in the console, you can add/remove site system servers on the 'References' tab. Pre SP2/R2 SP1, all you were adding here were DPs... now, those site systems can be DP's, MP's, and SMP's.

By simply looking at the list of site system servers, you cannot tell whether the server is a DP, MP, SMP, or any combination.

Please add 3 more columns or similar (one for each possible role) to display with check marks/dots indicating what roles are installed on each of the selected servers.

My customers would find this very useful, especially in environments with 100's of DP/MP/SMP's.