Jump to content


Chongy

Application Creation Best Practice

Recommended Posts

Do you actually plan to uninstall every piece of software you deploy? If so, then maybe it is a good idea. I would be concerned about keeping track of group memberships.

 

In our case, I only create uninstall collections on an as-needed basis...sometimes I simply deploy the uninstall directly to an existing collection (such as a lab) when I know that we will not be deploying the software in the future and need to remove it from existing workstations.

  • Like 1

Share this post


Link to post
Share on other sites

I'd go about this on a organizational basis in regards to what's needed and not in your company. Normally organizations never deal with the uninstall dilemma. If you're not gonna provide some sort of option for the user to uninstall an application, don't bother. But if you're looking at licensing control for expensive software, you could setup Software Metering and based of that perhaps come up with some sort of automated uninstall for those software. As per your question, I'd not go with creating uninstall for all your applications, unless you have a Help Desk team that needs access to uninstall software on computers.

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.