Hi,
I setup cloud distribution point using certificates exported from my main primary site server, cer and pfx.

I followed this blog article:

http://blogs.technet.com/b/kevinremde/archive/2013/05/22/cloud-based-sccm-distribution-point-why-yes-20-key-scenarios-with-windows-azure-infrastructure-services.aspx

I added them into azure portal then into sccm console to setup cloud dp.

It seems to confuse my primary site server running as distribution point and the cloud one.

I deleted the cloud distribution and distribution point role disappeared from primary site server, also adding new role option by right clic is grayed out.

Any update on this?  I have the same issue.

Hi, We noted these values in RCResUse table, where primary site FQDN is mmarked as Windows Azure in NalResType column instead of Windows NT. This is a change not supported by Microsoft unless under incident ticket CSS. Once that value change you'll have primary site server and site system roles disappeared. We added them manually back and all of needed rols especially distribution point one. Then we noted in distributionpoints table, for primary site row these two values: Column isPullDP -> NULL (like cloud dp values); we changed that to 0 (zero) Column isProtected -> 0 (like dp values); we changed to 1; We did then restart the server and then everything is back to normal.

This solution worked for me, although the table I used was  SC_SysResUse.

I have ran into this exact issue, i used a powershell script to re-add my DP, but fails to upload packages because the logs think it is still an Azure DP.

Can someone elaborate where this SC_SysResUse table is?  I cannot find anything like it in the registry.

Thank you!

FYI this was my exact fix.

"Open SQL Server Management Studio on the server>Logon>Expand Databases>Expand CM_***(your site code)>Expand Tables>Find dbo.SC_SysResUse>Right-Click on this table and choose edit top 200 row (this will pull back all the rows in this table)

 

From there I adjusted the NALResType fields for your Local DP. They were set to Azure DP for the NALPath that matches your local DP. I changed them to Windows NT Server.  Then we removed the distribution point role and added it back."