Danny Nichols
Comments
-
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?
-
That would resolve the issue of not being able to install the package on new systems without the software, but then when running the weekly update schedule it would also install it on all systems e...
-
I was thinking of doing this, but this would also prevent these packages from being deployed to new systems as well, correct? If you limit the package to only be installed if they are a member of t...