Dakota Clark
Comments
-
Official comment
Try using /l=.\output.log as some installer technologies will interpret . as the current directory. If that doesn't work try setting just the file name like so /l=output.log as that can also be ta...
-
Official comment
To my knowledge, that method of setting a proxy only works for interactive sessions which is why is works when you sign in to perform that action but fails when you run it using PDQ Deploy. You mig...
-
For this I recommend substituting $(Get-Location) with $pwd. $pwd = present working directory and should be the exact same as Get-Location.
-
I recommend reaching out to support@pdq.com for help.
-
Sadly that is all Microsoft indicates it to mean. You can look at the LicenseStatus property on the WMI class from the documentation link, it's how Colby determined the meaning too. https://docs.mi...
-
This sounds like a DNS or firewall issue. You mention the firewall ports are open but you cannot ping it, did you follow this guide? https://support.pdq.com/knowledge-base/1023 How did you confirm ...
-
You can automate optimizing the database by using the command line tools to do so. The syntax and options: C:\> PDQDeploy Help OptimizeDatabase NAME OptimizeDatabase SYNTAX Optimize...
-
Hi RPS-Joel, This sounds like it could be an issue with an antivirus software scanning the files. There is a list of recommended antivirus exclusions below. https://support.pdq.com/knowledge-base/8...
-
You'd have to use OR Applications.Name LIKE '%APP2%' for the wildcard to be evaluated.
-
Hi Stuart, The PDQ products have no reliance on SMB v1. The error you are receiving is a DNS / NetBIOS issue outside of the products themselves. You may find the same error occurs if you attempt to...