Activating Enable distribution-point sharing for this source site in the Source Site properties will allows previous version Distribution Point to show up in SCCM 1511 and to be used by client as content source when packages are migrated.
You can see the status of Shared Distribution Point in the console under Administration / Migration / Source Hierarchy and by selecting the Shared Distribution Point tab at the bottom.
In case you are not familiar with it, WSUS is Microsoft's free patch management tool. If you don't know the difference then you don't do Windows support.
OK, here's the main difference: In addition to OS patches, Microsoft Update takes care of your MS Applications like Office, SQL Server and Exchange. WSUS has a good monitoring and reporting feature that allows me to see at a glance which machines are struggling with the stuff Microsoft is trying to send to it.
The disadvantage is that it requires a bit more operational tasks and planning.
The remaining steps only apply if your client computers use SSL to connect to WSUS. I started the Remote Desktop Gateway service and was again able to log on using Remote Desktop.This upgrades WSUS to supply Windows 10 upgrades (not in use at this location) but the more obvious effect is that it kills WSUS: while connected via Remote Desktop.I was immediately disconnected and could not reconnect: “50331661 Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable.” Fortunately, I have another way to access this server.Someone on his blog actually asked if the extension was necessary. After nuking the old folder, run the update again and all is well but it takes a long time to go through that long download and update process. I have found that the easiest way to fix a Microsoft Update problem is to switch back to Windows Update from the "Change Setting" option on the left-side menu. After deploying WSUS on a Server 2012 R2 Essentials machine, I allowed WSUS to update itself with KB3159706.