Danny Nichols
Comments
-
Thank you! That's exactly what I was looking for and hadn't found. I was able to create a collection with a custom variable. I'll have to manually update the variable but I don't know of any other ...
-
I agree, this would be useful when running commands that are specific to a user and would be great to not have to edit the package every time. Any change in this after 3 years?
-
Thank you Colby Bouma, that works great...exactly what was needed. Seems like there should be a function for that rather then needing the for loop but the first one worked perfect. I appreciate you...
-
Thank you Colby Bouma. Unfortunately, that is still producing the same output in PDQi (and Powershell) as before.
-
I've been using this script. It allows an in-place upgrade and is much better suited for what you are looking for without any uninstall. I use the CDN option, but there is a way to download the ins...
-
Has this issue been resolved yet? I believe I'm having the same issue still with version 19.
-
Bumping this again. This would be a great feature. I currently have to set a generic command line step to allow it to run successfully.
-
Okay, I think I figured out how to do this. I was looking in the schedule but instead you want to create a nested package with all of the packages you want to run in one schedule. This way, each pa...
-
So that would be manually added to a system whenever I want the software installed on it? I feel like that's more work than just creating a second package that doesn't have the limiting collection ...
-
I don't know much about custom fields. Can you elaborate? Where would the field be placed, on the collection, package, or system?