It does seem that I have to connect to the primary sites to remove the update package targetted to the DPs for that region, so that question is answered.
What I don't understand is why this is needed. On Mon, Mar 24, 2014 at 10:36 AM, Stephen Owen <[email protected]> wrote: > Hi guys, > > In my environment I have one central site, four primaries and 170+ DPs. > > I accidentally pushed out a massive Software Update package to my whole > environment last week and due to its size, I'm having trouble transmitting > other packages out to these sites until it finishes. However when I > attempt to select this update deployment package from the Central Site and > click 'Manage Distribution Points', then Remove this Package from DPs, I > don't see any of the child sites listed, just the primaries. However, I do > see all of these sites listed as Targeted under Package Status for the same > Package. > > Is this a situation in which I need to connect to each primary site to > remove the updates for each DP? If so, why is this behavior present? > > Thanks, > >
