If you missed out on our webcast last week, never fear, our webcast recap is here. Last week was our PDQ & A...your opportunity to ask questions, and we answer them. Watch the webcast here or keep reading if that's more your thing.
I am new to PDQ and love it so far. We have a laptop that gets a DHCP reservation for both the Wi-Fi and LAN connections. PDQ seems to be looking for this Wi-Fi address, however, his laptop is docked which gives him the LAN address. If I removed the DNS record and flush DNS on the server I can get PDQ to talk to the laptop on the LAN address, but I don't want to have to do this every time. Any suggestions?
If a computer has been off for a while, or a laptop has been disconnected from the network, is there an easy/quick way to tell what packages need to be updated? Something other than checking individual packages, or waiting for triggers to happen?
How can I find out which deployments are targeting/linked to particular Collections? It would be great to see deployments that have targeted that Collection either in a Scheduled Deployment so that we know what deployments have used that in the recent past and also what deployments may be impacted before we modify a collection.
Trying to apply patches to Acrobat DC Reader, but in some cases, the package is showing failed. I assume some component is open and needs to be closed. Is there a simple command to close all open Adobe products?
We install several software titles not maintained by PDQ. Monthly we check for a downloaded updated versions, manually. Can you recommend a method that would automatically check or download from different websites new versions of software?
With Windows Defender ATP constantly wanting to rename files at reboot, the “Reboot Needed” flag isn’t meaningful anymore. Most computers want to reboot at least twice a day. Could we filter just on computers requesting a reboot for update purposes?
We have a PC that we setup at this location, and then moved to one of our other locations, and now cannot be seen in Inventory. I assume this is DNS related. Short of just removing the old entry in DNS, what would you recommend as the best DNS practice for this situation?
I have noticed that scans are not updating Inventory. No errors are reported with the scan, just that Inventory is not updating. The only resolution I have found is that if I delete the computer and then re-sync with AD it will update appropriately. Any idea what might be causing this?
Remember to check back next week for another recap and don't forget to tune in to the actual webcast every Thursday at 10 am MST. Thanks for reading, peace out folks!