Webcast Recap: Automating packages that aren't in our library

Never fear your webcast recap is here! Last week Lex and Jordan ran us through how to automate a package that isn't in our Package Library. There were some caveats and things that you need to follow, so make sure you pay attention...don't even blink because you might miss something good. And ironically Lex and Jordan joke that the secret to our success here at PDQ.com is laziness. We are willing to put in the time and effort upfront so that we can sit back and drink coffee later. The idea of this post is to promote automation and allow you to sit back and enjoy a drink while your job does itself for you. So, with that let's review the webcast!

Automate a package

Variables Deploy and Inventory. :47

Discussion of repository paths with variables. 2:12

Create a package with Variable path. 6:19

Question: We have a package that only wants to install when logged into a user and then installed as Admin. How might we automate it in Deploy? 7:59

Create a schedule. 10:24

Question: Whenever I change a custom package, I need to delete the schedule and create a new one for it to deploy again. Is there a better way? 15:23

Using Powershell to make it run. 16:30

Q&A : Speed Round

Question: Does the new Chrome package exclude Server 2019? 22:24

Question: SketchUp Plugins are scripts (text files). To track deployment of new/updated plugins I drop a text file 20190919.txt. The next time I deploy SketchUp Plugins I check for the previous text file. Is there a better way? 27:02

Question: We have a ps1 file with a large number of custom functions. Is there a way to include functions in the deploy powershell environment? 29:02

Stay Tuned!

If you don't want to miss out next week tune in live on Thursdays at 9:30 am MST. We have a good time and share some helpful tips too! See you next time!