Thanks. The other odd thing is I cannot get the report that shows failed distributions to match the number of failures in the console.
Everything else in CM12 has been FANTASTIC so far.... but the way you have to go from node to node to take actions on objects is a little irritating and makes me very inefficient. On Mon, Sep 9, 2013 at 1:31 PM, Ryan <[email protected]> wrote: > You could open a second console on your computer and use that to speed > things up. > > Shift + Right click on the console icon -> Run as different user -> Put in > your current user creds > > This will open a second console as yourself so you can switch between tabs > much easier. I've had a total of 6 consoles open at once when I was > importing large driver packs. For dual monitor setups, it's nice to have > two consoles open to different tabs... > > > I'll be doing right click tools for this also: > > Redistribute to all assigned DPs > Redistribute to all failures > Redistribute to specific DPs > Distribute to new DPs > > Those would be on the monitoring tab and have support for SP1. > > No ETA on them, probably a week or two. I have a long "to-do" list for new > tools, but I'll put those up towards the top and put them out in one of the > betas this month. > > > > > On Mon, Sep 9, 2013 at 1:16 PM, Jason Sandys <[email protected]> wrote: > >> R2 J**** >> >> ** ** >> >> I know that doesn’t help today, but they added the ability to retry or >> pause package distribution to specific DPs.**** >> >> ** ** >> >> J**** >> >> ** ** >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Todd Hemsell >> *Sent:* Monday, September 9, 2013 12:56 PM >> *To:* [email protected] >> *Subject:* [mssms] Distribution Point Maintenance**** >> >> ** ** >> >> Trying to find a good way to do this...**** >> >> **** >> >> I have 1 distribution point group and everything is assigned to it. I can >> go into monitoring and look at the "compliance" to see where the package >> might be missing from a DP, but in order to go do anything with that >> information I have to go figure out what DP it failed on. Then I have to go >> find the package and "redistribute content" then I have to go back to >> monitoring to find the next package in the list.**** >> >> **** >> >> This is incredibly inefficient and difficult to do. There MUST be a >> better way?**** >> >> **** >> >> /Todd**** >> >> ** ** >> >> > >
