Luke Nichols

Follow

Network Engineer at Kettering University

  • Total activity 1440
  • Last activity
  • Member since
  • Following 3 users
  • Followed by 0 users
  • Votes 939
  • Subscriptions 292

Activity overview

Latest activity by Luke Nichols

  • Luke Nichols commented,

    1. Community
    2. PDQ Inventory
    3. PDQ deploy or inventory auto run script to workstation

    Yes, you can make this automatic, depending on how you set it up. You will want to tweak your scan profile's triggers in order to catch these machines quickly. For example my "Standard" scan profil...

  • Luke Nichols commented,

    1. Community
    2. PDQ Inventory
    3. PDQ deploy or inventory auto run script to workstation

    Alan, Yes you can do this, it should be fairly simple. Wrap your script that deletes files into a PDQ Deploy package. Create a dynamic collection in PDQ Inventory that contains only computers with...

  • Luke Nichols commented,

    1. Community
    2. PDQ Deploy
    3. Siemens UGS NX12

    Frederic, The best way in my experience to find why an installation is timing out or hanging is to check the installer log file. I am not sure where the default location is because I manually chang...

  • Luke Nichols commented,

    1. Community
    2. PDQ Deploy
    3. Siemens UGS NX12

    Frederic, I have a couple of questions about your setup: Is there any reason you're not just doing a standard install step with the MSI file being in your PDQ Deploy repository? Why are you refere...

    • View comment
    • Luke Nichols
    • Edited
    • 1 vote

  • Luke Nichols commented,

    1. Community
    2. PDQ Deploy
    3. Trigger Install Upon New Collection Membership

    I can't say if it's unusual or not but it is how I would do it, personally. In my experience dynamic collections are the best tool for targeting deployments and if you just want a view of computers...

  • Luke Nichols commented,

    1. Community
    2. PDQ Deploy
    3. Trigger Install Upon New Collection Membership

    Adam, You could do a scheduled deployment on a heartbeat trigger and that should work. I usually recommend that if you're doing a heartbeat trigger you also add an interval trigger, e.g. 15 minutes...

    • View comment
    • Luke Nichols
    • 2 votes

  • Luke Nichols commented,

    1. Community
    2. PDQ Inventory
    3. Dynamic Collection of "old" last scan date

    Jonathan, I did basically the same as you described and did not see that in my environment. My report is correctly showing machines scanned on or before the 23rd of September. I'm guessing what hap...

  • Luke Nichols commented,

    1. Community
    2. PDQ Deploy
    3. Aws Domain Controller

    Shan, Did you install PDQ on your domain controller? I will say that is not exactly best practice but it might be ok for your environment if it's just a quick test. Does your AWS domain controller ...

    • View comment
    • Luke Nichols
    • 0 votes

  • Luke Nichols commented,

    1. Community
    2. PDQ Deploy
    3. Aws Domain Controller

    Shan, Do you have admin shares disabled on your laptop?

  • Luke Nichols commented,

    1. Community
    2. PDQ Deploy
    3. Bluebeam Install

    It looks like their installer command is basically just running two installers in sequence (using the && command). I would try doing this with two install steps in PDQ Deploy. The first step shoul...