Elliot Jordan

One solution: - Configure the Auto Update policies to run once per computer. - When promoting a successfully-tested app to production, manually flush the associated Auto Update policy log. This...

@opragel suggested another alternative: keeping an extension attribute for each auto-updated app, and the value of the EA would determine whether the Auto Update policy is scoped. - **Advantages**: It...

Hi @bandoned. I have two initial thoughts: - Have you tried omitting the site ID from the template entirely? I don't use sites, but it seems logical to me that...

Well, you're beyond my wheelhouse. I've never found the added complexity of Sites has been worth it.

Hi @sparkymac, You may want to run one of your autoupdate recipes in isolation, using Terminal to see what errors occur, if any. For example: `autopkg run -v AdobeFlashPlayer-autoupdate.jss` The...

Hi Mark, Here are a few steps for troubleshooting: - Rather than running the recipes individually at the Terminal, try running them from the recipe list using this command: ```...

> One more point: when some people on this thread were maintaining both ".recipe" (plist) and ".recipe.yaml" versions of the same recipes, did you use different RecipeIdentifiers for each variant?...

I'm not working on json support, nor am I interested in doing so. My reaction was a bit of a "more the merrier" joke, poorly executed.

@grahampugh AutoPkgr parses plists in order to provide additional functionality like this without having to shell out to `autopkg info` for every right-click or table refresh. 

@jgstew If there is, I haven't found it yet. You can experiment with the search URLs on the web to try alternatives: `https://github.com/autopkg/hansen-m-recipes/search?q=%22com\.github\.hansen-m\.download\.zoomus%22`