🤘 40 reputation

chrisj

Administrator

Joined: 4/26/2018

Last seen: 1/11/2019

Activity
  • Thanks for sharing, sounds handy!

  • Hey Dan, a cleverly crafted SQL query against the deploy database should pull this information.

    Looks like that information lives in the PackageDefinitions table and the ScanAfterDeployment column. I think you'll need to join that table with the Packages table on the PackageDefinitionID column.

    Be very careful poking around in your database, I suggest making a backup and running the queries on a copy.

  • Hey there, are you looking to copy your packages or the deployment history?

    Packages can be exported and then imported from the File menu. Just select the packages you want to export File->Export or Right-Click Export. It is possible to export multiple packages at once this way. Then File->Import (Ctrl+I works as well) and pick the XML files created.

    To move deployment history you will need to make a copy of your database and move that to a new machine, you can find instructions on doing that for Deploy here: https://support.pdq.com/knowledge-base/1243

  • Hey there, I recommend contacting support: support@pdq.com

  • Hey Jim,

    Don't have access to the software to test here, but I found their documentation for network deployments here: https://fmhelp.filemaker.com/docs/17/en/fmpnisg/#install-filemaker-pro-windows_install-method-windows

    A lot of the time MSI installers will have fairly detailed output files, have you tried reviewing those as well?

  • We agree with Christian's suggestion to try an SSD. Having a single spinning disk attempting to read and write to a database will quickly become a bottleneck. While SQLite is highly optimized for read operations, lesser priority read operations get put to the back of the queue while the database is being used for other tasks. Writing at that scale does present some issues, but we believe it shouldn't be an issue in most cases on the suitable hardware. We have had other customers with environments as large or larger make use of Inventory successfully. It does take some time to tweak the settings and plan your scanning/deployments to not bog down your network and server.

  • Oh nice! I've been using PowerShell myself:

    $Processes = Get-Process
    if ( $Processes.ProcessName -contains "chrome" ) {
        Write-Output "Process Found - stopping"
        Exit 22
    } Else {
        Write-Output "Process Not Found"
        Exit 11
    }
    

    Stop Process if Found

  • I was hoping there would be an easy way to pull this information with the WMI scanner, but my initial research is proving to be quite futile 😦 Due to the nature of information WMI pulls in from AD it has the information of ALL computers in the local tables. Even if the scan worked you would not be able to add this information to the columns in Inventory.

    This would be query you could run to pull those fields into Inventory, but currently there is not a method for expanding variables in a WMI Scanner's query statement: SELECT DS_department FROM ds_computer WHERE ds_name="TARGETCOMPUTERNAME"

    Your best bet would be to gather the information with PowerShell and import that data into a Custom Field. I'm going to see if I can get some features considered for the future internally, but no promises.

  • We've seen some other customers experience similar behavior with network paths becoming unavailable intermittently. You could try enabling Debug logging in Preferences->Logging and see if Event Viewer provides any more insight when you see these files becoming unavailable again in the future.

  • I believe we may have tried some magic on this one in a customer build, please contact support@pdq.com

  • Office updates in particular are the more terrifying of the two. In the past you had to wait for Microsoft to release remediation patches for Office. Most everyday Windows hot fixes uninstall fairly easily, and when lucky Office KBs as well.

    In those lucky cases you can use wusa /uninstall KB#:

    woo SAH!

  • The background service should only require local admin permissions on your console machine and access to your repository location, if not local to your PDQ Deploy console installation.

    PDQ Credentials Explained

  • Hi Stuart, this typically is an issue with DNS or permission errors if the warning persists. Do you have a large amount of files in your repository that need to removed?

    What build are you currently running?

  • Hey there, did you receive a ticket number when you submitted this to support? If not, would you e-mail support@pdq.com and let us know the specific errors you're seeing in that ticket and we'll be happy to follow up there.

  • Hi Sheldon,

    We have a new customer build that might help you, please contact support@pdq.com to have that sent over to you.

  • Hey, thanks for the suggestion! We'll note that internally.

    In the mean time, you can accomplish this with a command or PowerShell step!

    This Example will stop a package from continuing if it finds the named process, chrome in this case. I have 11 as a success code, and if the script doesn't find the named process it exits with 11 and the package continues as successful.

    Stop if Process Found Running

    $Processes = Get-Process
    if ( $Processes.ProcessName -contains "chrome" ) {
        Write-Output "Process Found - stopping"
        Exit 22
    } Else {
        Write-Output "Process Not Found"
        Exit 11
    }
    
  • Hey guys, looks like you're running into a bug and we'd like it if you would submit a ticket to support@pdq.com and we'll take a look at it and handle the issues you're seeing there.

    Thanks!

  • Hey Jake, thanks for submitting this request. We've noted your request, but I wanted to take the opportunity to let you know of a couple of ways you could handle this right now, just not as a discrete feature you've described.

    The first way being target lists. I actually keep a target list of computers I routinely deploy tests to here internally. There's a shortcut here not everyone may be aware, if you drag and drop a Package to the Target List in the tree, or vice versa, it will open a deploy once window for that Package and those Targets.

    target lists!

    There is also the option to Remember these targets for next time, on the Deploy Once window.

    Deploy Once Remembers!

  • The files in the Install Files field copied over to the target machine, along with any additional files or entire directory if configured. The string in the command line box is ran on the target machine from the context of the directory those files were copied to on your target machine.

    I suggest trying to just put only TRANSFORMS=MCSAcroRead.mst in your parameters instead of the full UNC path to prevent the install from trying to grab those resources over the network since you are already copying those files on deployment.

    If that doesn't help, would you mind taking a screenshot of the install step you currently have configured to take a look at your settings to make sure I follow you explanation.