Stop users from starting an app when upgrading
Hi
Is it possible to stop the user from starting an app, when PDQ Deploy is updating that app?
We have an app, which gets regularly dll updates, but we can't put it in if the process is running.
I can force stop it, but what if the user starts the app before the update id finished?
It will then fail, as not all files is rolled out. Can I stop the user from starting that particularly application until the update is finished?
-
There are a few choices I can think of:
- Display a message to the user telling them to not open it. https://www.youtube.com/watch?v=5B-atetdEHY
- Edit the ACL for the executable (with something like Set-Acl) to deny the "Read & execute" permission. Make sure you don't block the Deploy User.
- Temporarily move/rename the executable so shortcuts don't work.
- Go full Lex on your users and kick them out with something like a Logoff or Reboot step :)
-
I like the first one the best.
I took out most of their script, so the popup just will inform users that the update is going on. I was thinking on letting it show for 30 sec, and then auto close it. The files copy should be done by that time.
But that gives me another issue. When I create a job i PDQ, where the first part i informing the user and the second part is the actual copy. The copy part will only start after the waiting periode at the popup. So now the user believes the update is done, which it isn't
Is it possible to have the copy process to start, just after the popup shows and not after is gone?
-
I recommend using a Message step instead. The PowerShell-based popup was used to provide interactivity. If you just want to display a warning, the Message step would probably be a better option.
Please sign in to leave a comment.
Comments
3 comments