Search the Community

Hi all, Background We’re running SCCM 2012 R2 CU1. It’s a single primary site with a physical Site Server, six virtual distribution points, and a physical SQL cluster. Our physical site server hosts, among other things, the distribution point role and has a 600GB drive for packages and the content library. It’s in a distribution point group with the six other DPs and customers distribute content to that group rather than to the DPs individually. Question Recently we started getting close to the hard 600GB limit on our primary site server, so we started thinking through our options. Buy more drives? Can’t, we’re maxed out. Buy bigger drives? We can, but how big should we get and is that the best option for us? It seems like the best option would be to remove the DP role from our physical site server and just let that role live on the virtual servers with drives that can be grown easily. Our thoughts were to Perform our maintenance in the off-hours and apply a maintenance window to keep people from doingthings. Pull the physical site server from the DP group Remove the DP role from the physical site server Lift the maintenance window so people can do things again Does that plan seem sufficient? Are there any gotchas to look out for? How does this affect any active or ongoing deployments that may be out there? If a computer is stuck waiting for content from our physical site server, how can we tell it to move on to the next available DP? All the documentation out there says how to remove the role, which isn't hard, but doesn't really go into any detail. So either it's very easy and we're over complicating things or you're just not supposed to do it. Thanks in advance for your help and thoughts!