- #Found a shit ton of cab files in temp folder install#
- #Found a shit ton of cab files in temp folder software#
It also helps to prevent re-inventing the wheel each time a new application needs to be deployed. The PowerShell App Deployment Toolkit is a free toolkit that provides some answers to these challenges.
#Found a shit ton of cab files in temp folder software#
It seems pretty obvious that we’ll need the ability to make decisions specific to each applicion, but it also seems like we’ll need a single set of tools available to us for software installations.
#Found a shit ton of cab files in temp folder install#
If applications or updates need to be deployed while a workstation is in use, I need the ability to display an informative message to the user that they can easily understand, while preventing them from accidentally interrupting the install (or starting an application while it’s updating). I need a flexible logging framework so that when things go wrong (not if, but when), I know exactly where to look to find out more information on what happened. For example, I need the ability to disable Java’s automatic updates so our updates can be centrally managed. I often need the ability to perform post-install configuration. If I have to click a “Next” button once on an installation welcome, license agreement, or confirmation dialog, then someone will need to be able to click the “Next” button each time the software is installed on a new workstation or server. I need the ability to perform a fully automated, silent install. This means I’ve been responsible for integrating software installs in our workstation build process, but I’ve also had to deal with the issue of deploying and updating software on end-user workstations.Īdministering software deployments presents a unique set of challenges: 04/07/15 on PowerShell, PSADT Table of Contentsįor over a year now, I’ve been the primary software administrator for our organization’s SCCM infrastructure.
0 kommentar(er)
