🤘 6 reputation

Josh

Administrator

Joined: 4/29/2018

Last seen: 11/6/2018

Activity
  • Hey Geoff,

    A quick foreach loop in PowerShell should take care of this,

    $files = Get-ChildItem C:\Users\*\Desktop\your_shortcut.lnk
    
    foreach ($file in $files)
    {
        Remove-Item $file -Force -WhatIf
    }
    

    You can run that on a target machine manually first to verify its doing what you would like. if it is, go ahead and remove the -WhatIF and you can run it as a PDQ Inventory Tool, or a PowerShell step in PDQ Deploy.

    -Josh

  • Hi,

    This is really a matter of personal preference, just keep in mind what access your defined accounts in PDQ need access to

    Personally, I would suggest DFS servers and using pull mode as that will usually give you the best performance.

    -Josh

  • Hi,

    The run-as options are usually only needing to be modified for very specific installers, the Deploy User in most cases will be the best choice. Firefox for example, if ran under the context "Deploy User (Interactive)" will fail, whereas that run as option is sometimes needed for Office installations.

    It really depends under what context you need your commands to run, and weather the installer may not be quite as silent as it should (Office, sometimes throws a initialization splash screen but is otherwise silent).

    -Josh

  • Hi,

    Something like this should do the trick:

    enter image description here

    -Josh

  • Hi,

    Patrick is correct, there is not a way to do this directly within Deploy, but you could accomplish something similar with schedules, and some manual cleanup.

    Schedule 1: File-Copy all required files to the target machines (pre-stage)

    Schedule 2: Command step executing the installers with proper parameters

    Schedule 3: Command step removing the previously copied installers

    You could make sure that you are getting files on machines, and removing them with a file and directory scanner:

    https://support.pdq.com/knowledge-base/941

    -Josh

  • Hi,

    Its not possible to run a scan as the logged on user, but a files and directories scanner can still get that information, see this KB for more information:

    https://support.pdq.com/knowledge-base/941

    -Josh

  • Hi Gilbert,

    This link should get you going in the right direction:

    https://documentation.pdq.com/PDQInventory/16.4.0.0/index.html?dynamic_collection_editor.htm

    The collection library is also always an awesome cheat-sheet, you can duplicate collections from the library that are similar to what you are looking for then just change the values to reflect what you are looking for.

    -Josh

  • Hi,

    You'll likely want to structure your filters like this:

    All > Not Any > Application Name > Contains > (app_name)

    enter image description here

    This will also return machines in your console that have not been scanned, so to filter those machines out we'll want to add a scan comparison in the all filter, similar to this:

    enter image description here

  • Robert,

    Thank you for agreeing to work with Jason on this issue. We value feedback from admins like yourself who manage large numbers of machines.  We have been able to make tweaks to the applications based off of feedback like this and we will continue to do so. 

     

    There will likely need to be some hardware, and configuration changes on your end with 25,000+ machines, most likely the machine will need more RAM, and SSD based storage to keep up. 

  • Hey Alan,

    I have turned this into a support ticket, I'll be contacting you soon via email. 

  • Hi Greg,

    Our Windows update packages do defer a restart, and the OS is not patched until a reboot.  There are a couple of ways to make sure that those systems get rebooted. One way would be to create a "reboot" package that has a condition to only run if no user is logged in.  In that scenario before the reboot command is sent PDQ Deploy verifies that no user is logged in, if there is a user logged in the deployment will fail with the status "No steps able to run due to conditions."

    You can put this reboot package on a schedule to run at a time when most users will be logged out. 

    PDQ Inventory can also show you what patches are applied to a particular machine so you know if every machine in your network is patched.  The collection library has these built for you already so you have have a heads-up display of the machines in your environment that are, or are not patched. 

  • Hi Jeroen,

    I created a ticket from this post, it should be in your email. Since we are likely going to need some credential information its probably best this not be addressed on a public forum. 

     

    -Josh

  • Hi Joe,

    Kris wrote a blog post here that should get you going in the right direction.