🤘 11 reputation



Joined: 1/10/2018

Last seen: 5/28/2019

  • Look into creating a DFS replication of your file store and switching to pull mode. https://www.pdq.com/blog/setting-up-dfs-in-your-environment/

  • Heads up on Firefox ESR 60.6.1
  • Deploy isn't set to not communicate out, it checks in for list of updated packages / Daily notifications of webcasts / Software updates (These minus package updates can be disabled in Alerts under Preferences). My guess would be that it's a simple AWS connection hosting these resources. Block it and see if any of those stop working.

    Only other guess I can think of is Agent to PDQ server to local PDQ inv/deploy communication described in https://www.pdq.com/optional-agent/

  • Use the German Exe from https://www.mozilla.org/en-US/firefox/all/

    The PDQ auto update package just uses the EXE with an ini file for configuration, you can further customize by copying over the cfg file for Firefox or through the admin pack file for group policy

  • we have been fighting the same thing here, We recently went through and named our schedules per application and deleted everything blank. A few QOL changes with schedules would be a handy change down the line.

    I was thinking that being able to batch edit triggers of schedules would be handy.

    Our schedules use to be only tied to PDQ Inv old software Dynamic Collections and triggered with a heartbeat. In the past heartbeat had been quite unreliable with any quick booting system. SSDs and all. (not sure if it's tied to the agent coming online yet) We decided to set up timed deployments as a catch all. I then learned that you can't select multiple schedules and add a common trigger time.

    Or (and I know I've beat this to death) the option to right click a machine and trigger the heartbeat pending deployments. I know you can check for heartbeat but have this actually kick off the check in with PDQ Deploy for pending deployments. right now we do some weird restart-netadapter * then trigger the heartbeat twice thing.

  • Does this fit what you are looking for ? https://www.pdq.com/blog/initiating-deployments-using-powershell-2/

    Invoke-Command -ComputerName "PDQSERVERHERE" -ScriptBlock {
        pdqdeploy Deploy -Package "Example Package" -Targets "targetname or IP"

    So the remote client just jumps into PDQ and executes the deploy through CLI. You could probably just do $hostnamepass = hostname and pass that in for the target, I just don't remember how to pass the variable to a remote session.

  • net use "M:" \\server\share /p:yes

    I just did this in PDQ deploy and it worked for me

    1 2

  • Yes that's seems like the normal trial restriction. I believe it also restricts the amount of steps you can create and some other stuff. When we did our trial we received an email with the following. I think I remember everything either being grayed out but a few or everything greying out after we selected three, can't remember.

    "Thanks for trying PDQ Deploy Enterprise! If you haven't downloaded PDQ Deploy yet, you can do so with this direct link. Your trial key will be sent to you in a separate email. The Package Library

    During your 14 day trial you will have access to your choice of any three applications to deploy from the package library. You may also create your own deployment packages. "

    Side note, it's worth it, you should pick it up. We have never looked back.

  • Sounds like your DNS and DHCP servers are super out of sync. Have you set up dynamic DNS? Having your DHCP server/s be the owner of the client DNS entry is game changing for PDQ. We had a similar problem and after setting up dynamic DNS and forcing a scavenge we were 100%.

  • I'm not sure if it helps in your situation but have you looked into Microsoft VAMT, it's a free utility from MS to manage Windows/Office licensing for networked systems. Supports right click activate and will return available uses of MAK / store KMS keys etc.

  • Update on this, it's definitely something with GPU acceleration. Task manager shows GPU 2 -3D permanently when Deploy is up and only occasionally when Inventory is up. Something must be different between Inventory 16/5 and Deploy 17 for HW acceleration. I wish there was an off button for it.

  • Odd CPU load with PDQ Deploy console
  • Weird happenings with cloned systems
  • I believe you are describing a native Windows Server roll called Distributed File System (DFS)


  • the notification from above would only be relevant to users already logged on. For anyone after that it would not happen until the next notification window.

    I'm having trouble understanding your specific requirement, it might help if I understood a bit more of what your attempting to achieve.

    A few questions to help better understand

    1. Do you have a prohibiting factor for off hour updates?
    2. Could you instead opt for something like a desktop background? I have a BGINFO script that throws up system information over a default background that could be used to update the background to a "Under construction" background or whatever for all system users.

    for part 2 you just download BGINFO and add a startup script to group policy to run the BGINFO template file against bginfo after copying it local with the background of your choice. Something like C:\generalstuff\bginfo

    Then just change step one to copy a replacement jpg or whatever to bginfo new step 2 execute the same script as logged on user and tada the background changes to "stuff is happening" untill whatever step where you put it back to normal or to a finished background until log off and on gpolicy reapply normal.

  • I thought it just stored the value returned from the computer information scan

    More or less Get-CimInstance -ClassName win32_operatingsystem | select csname, lastbootuptime stored as a value and iterated on against current date.

    Look at one of your systems where this is wrong and check the last time it successfully scanned computer information or did the standard scan. If you don't currently have a scan set to when heartbeat is detected, I would highly recomend setting that. Options > Scan Profiles > standard (edit) > triggers | modify when scan aget is * days old to your preferred value and add heartbeat

    Check your minimum time between standard scans and make sure it's set to what you would consider reasonable, If I remember default was like 7 days. We prefer to have it set to 24h in our environment.

  • This might work for you. It doesn't ask for permission but it will let the user know what's up per step.

    Step 1 (powershell - make sure to select run as logged on user under options)

    $wshell = New-Object -ComObject Wscript.Shell
    $wshell.Popup("A message to your user that the program will update",0,"Box Name",0x0)

    Step 2 (powershell) get-service -name "whatever" | stop-service

    Step 3 (do your thing)

    Step 45678 (inject any other messages between steps for update or task completed) (again make sure to select Run as Logged on User under Options for the task)

    ref https://mcpmag.com/articles/2016/06/09/display-gui-message-boxes-in-powershell.aspx https://powershell.org/2013/04/29/powershell-popup/

  • $oldComputerName = '$(COMPUTER:TARGET)' pass it with ' '
    For the pop up box you may need to select close shell on completion (or leave it open) in the tool editor under Shell

    If you use the tool window I think it suppresses input like that.

  • We use SW Web Helpdesk here but a common feature is a CSV asset import. You can usually download a template CSV from web help desks asset tab and copy paste the appropriate columns from PDQ then import.


    But this is my low level knowledge of DB workaround solution. I'm sure there is a more fluid way.

  • I did some digging. best way I could find to create the popup and return it as a value is below. Running this local now instead of remote.

    $NewHname = [Microsoft.VisualBasic.Interaction]::InputBox("Enter New Hostname", "Get New Name Box", '$(Computer:TARGET)')
    Rename-Computer -computername '$(Computer:TARGET)' -NewName $NewHname -force -restart

    my reference for this https://stackoverflow.com/questions/30534273/simple-inputbox-function https://stackoverflow.com/questions/16208013/make-input-box-with-predefined-value

    Edit revised and cleaned up some Worked on my end up to getting access denied on rename, I think I remember this being some quirk that I didn't want to research. This is why I ran our other script local. Perhaps I'm missing something but your box popup is in this one. It references the computer name from PDQs variable, to test just the popup in PS without PDQ first run. I'm sure you can edit it to get what you need out of it.

    $CurHname = "test"
    $Value = [Microsoft.VisualBasic.Interaction]::InputBox("Enter New Hostname", "Get New Name Box", $CurHname)