Preventing all PDQ updates until ready to work with them
This might seem a bit odd but here is my dilemma - PDQ is updating too frequently! :)
Here is my routine:
- on the last friday of the month I :
- manually update my WSUS server and push updates to a test group
- push out any app updates via PDQ to a test group
- on the first friday of the month I:
- push updates from WSUS to the rest of the network
- push out any app updates via PDQ to the rest of the network
- run reports in WSUS and PDQ to make sure everything is up to date
Sometimes though I won't get around to running those reports for a few days. Sometimes it will take me a few days to get through all the deployments. And in the mean time PDQ is checking for updates - heck it has been checking for updates every day even since the first test round of updates. i'm not complaining about this in itself. I think it's awesome.
But today on the 9th a new update came out for Thunderbird. And while I've already pushed out the previous version of Thunderbird that was new at the time - PDQ is now showing that Thunderbird is out of date - I assume this is because the variable for Thunderbird's version has updated? i do love that it does this - I just don't want it to be automatic. :)
I figure I can create a rule in my firewall to block my PDQ server from the internet and just turn it on for a bit before I start on my end of month routine - but I wanted to ask if there was a way to do this in PDQ itself? Plus i don't necessarily want to block the entire server from the internet. Just PDQ itself.
Maybe i could put a fake host in the proxy server? Would that prevent PDQ from grabbing variable updates? Then when I'm ready to check for updates on the last friday of the month I just temporarily switch back to using the host setting?
Basically this is all because i want my reports to come out as clean as possible. I hope this all makes sense?
thanks
Please sign in to leave a comment.
Comments
1 comment