Colby Bouma
Comments
-
My personal recommendation is to create 1 schedule per package. Setting up a large package with a bunch of Nested Package steps works, but you'll get a lot of failed deployments.
-
You can update pref.ini on the target with PowerShell. Where is "Server_IP" coming from? Is it the IP of the target?
-
Can you just copy pref.ini to your targets, or do you need to specify unique values for each target? Also, does your vendor have any documentation about silent installation?
-
If scans are getting stuck, that sounds like a bug to me. I recommend contacting support@pdq.com.
-
"Link to" was changed to "Choose Targets" a few versions back. https://link.pdq.com/docs-PDQDeploy?schedule.htm#part3targets
-
That filter looks right to me. Does "McAfee VirusScan Enterprise" show up on the Applications page (in Inventory) for the troublesome target? Also, what is the version number of Inventory that you ...
-
I did some more experimentation and found a potentially cleaner way to do it. Execute PS Core.ps1 param ( [Parameter(Mandatory = "True")] [String]$FileName)$Contents = Get-Content -Path $Fil...
-
Not directly. PDQ Deploy and Inventory are built with .NET Framework, which can't tie into .NET Core things like PowerShell Core. PDQ would have to do a lot of work to add a native PS Core option. ...
-
While it is possible to do this in Inventory, I personally recommend using a log management product like Graylog, Splunk, or ELK.
-
This is the closest I know how to get: https://www.youtube.com/watch?v=PUpf0oJeOYg&t=418s