1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Changes to shortcuts (deployed via .lnk File Copy)

Avatar
Terence Hoad

Hi all,

We deploy .lnk shortcuts to the Public desktop on all company workstations + laptops.

These are deployed automatically via a Heartbeat schedule linked to a Sync of computers in an Active Directory OU (i.e. a PDQ Inventory target).

If we make changes to the .lnk shortcut (i.e. the target file), starting the Heartbeat schedule - or invoking it by turning the workstation/laptop off and on again - does not automatically run a deployment to overwrite the shortcut file.

Instead, we have to manually force this via the 'Redeploy' function.

Is there any way that the heartbeat schedule can initiate an overwrite of a shortcut file if this has already been deployed in the past?

 

 

 

 

0

Comments

1 comment
Date Votes
  • Avatar
    Stephen Valdinger

    Sounds like you have "Stop deploying to this target once it succeeds" turned on. You could negate this by incrementing the Version of the package each time you make a change.

    You'd need to setup a collection to kind of match the built-in collections for (Latest Version), (Old Version), and (Not Installed), and set the heartbeat schedule to deploy to Older Version. 

    0