In the second part of this series, we walked through the initial considerations, installation, and configuration of the AGPM Server and the AGPM Client (which if I didn’t make it clear before - the client is ONLY required on the machines that will be managing controlled group policies) - in this post we’ll actually put all of that work to “good” use and create some policies. We’re going to do this two separate ways:
After taking over a year long hiatus on this series (can I even call it a series if there was only one post?), I got a gentle reminder that I should finish what I started (thanksĀ for the reminder @markraldridge). So when we last talked about this we had a brief top-level overview of how AGPM functions and a promise that the next post would cover installation of AGPM and creating/deploying your first controlled policy. First off - I attempted to make all of that into one post but it got…!-->!-->
We took the opportunity during our SCCM migration (2012r2 to 1610) to clean up a lot of the “junk” that had accumulated in our environment. Instead of using the migration wizard the goal was to use the export/import features selectively to get us to a “clean” environment going forward. This for the most part worked really well - application deployment types obviously had to have new content locations set, packages had to have updated content locations, and the task…