🤘 6 reputation



Joined: 4/12/2018

Last seen: 8/5/2019

  • Weird,

    After I shut down and restart Deploy no more errors are listed for this package.

  • Uninstall DropBox package broken.
  • You need to install an SQLite ODBC driver (look here: http://www.ch-werner.de/sqliteodbc) on your PDQ server. Then "Get Data" - "ODBC" and enter "database=Database-Location\Database.db" as connection string. This works at least for the PowerBI Desktop.

    All PDQ data is stored in the database's.

    C:\ProgramData\Admin Arsenal\PDQ Deploy\Database.db

    C:\ProgramData\Admin Arsenal\PDQ Inventory\Database.db

  • Powershell is your friend...

    function GetRemoteLogonStatus ($computer = 'localhost') { 
    if (Test-Connection $computer -Count 2 -Quiet) { 
        try { 
            $user = $null 
            $user = gwmi -Class win32_computersystem -ComputerName $computer | select -ExpandProperty username -ErrorAction Stop 
        catch { "Not logged on"; return } 
        try { 
            if ((Get-Process logonui -ComputerName $computer -ErrorAction Stop) -and ($user)) { 
                "Workstation locked by $user" 
        catch { if ($user) { "$user logged on" } } 
    else { "$computer Offline" } 
  • All PDQ data is stored in the SQLite database's.

    C:\ProgramData\Admin Arsenal\PDQ Deploy\Database.db

    C:\ProgramData\Admin Arsenal\PDQ Inventory\Database.db

  • I would open the .exe with something like 7-Zip and see if it has any msi's inside of it that you can run.

  • While the agent has become more stable over time I still don't feel it's ready for production use. If your clients are all internal I wouldn't use the agent at this time.

    I see great potential in the agent, but it has a way to go as far as stability.

  • https://support.pdq.com/knowledge-base/1248

    So try:

    C:\Windows\Temp\TopSolid\x64\TopSolid\setup.exe -s -f1answer.iss

  • We currently have just over 25,000 endpoints and add around 400 new endpoints a month. A mixture of both Workstations and Laptops over 52 different locations.

    If you want to discuss this further please email me at robertbasil@robertbasil.com as I rarely check this community any more, just happened to check in as it's a slow "Read Only" Friday afternoon. 😃


  • No, I do not have any virus protection running on any of the machines running PDQ Deploy or PDQ Inventory.

  • Going back to Manage Engine Desktop Central. Gonna miss you PDQ. :-(
  • You are welcome, sorry for the harsh posts on this subject, it's just been a very frustrating few months for me trying to get PDQ to work for us. I really, really, really would like to drop Manage Engine Desktop Central from our lineup.

  • Shane,

    That's exactly what I was looking for, thank you VERY much!

    Just an FYI, We would be more than happy to be an Alpha/Beta tester for MSSQL. I'm even willing to start with a fresh database, no conversion from SQLite needed.

    Thanks again.

  • Two downvotes with no comments?

    Am I on reddit?

    Look, I LOVE PDQ Inventory and Deploy, if I didn't I wouldn't be spending all this time trying to make it work for us. I just want a usable solution for large enterprises. (20,000+ endpoints). There needs to be an option to use something more robust than SQLite.

  • I think the question you are looking for is how to apply a feature update with PDQ Deploy.

    Look on a computer that has been updated to 1803 for the "1803" temp install files directory.

    Copy that directory to your repository.

    Create the following step (including copy the entire directory)

    $(Repository)\1803\setup.exe /auto upgrade /quiet

    Make sure you test this before widespread use. It's worked well for us but might not for everyone.

  • Please PDQ, for the love of God.., when are we going to have the option to use an ENTERPRISE database?
  • Report for endpoint counts of Windows updates by severity?
  • Go to one of the computers that has the software installed. Look in the applications area for the software, right click on the software in the list and create an uninstall package and then apply that package to a dynamic group that consists of the computers with that software installed.

  • Edit the following keys on your workstations:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ProgramFilesDir HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ProgramFilesDir (x86)

    Keep in mind I've heard this might cause problems with Windows updates though. I've not tried it so use at your own risk.

  • 2016: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Profiles

    2013: HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Profiles

    2010: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Profiles