Dealing with Shortcomings of Current Software Deployment Solutions

Education IT environments are heterogeneous. Different software versions are deployed on a multitude of hardware platforms across a campus environment. Each one is likely managed by a different remote systems management tool. This wide diversity of systems can add many steps to deploying, monitoring and updating software.

Education IT departments often don’t know what software is installed on distributed systems in a campus environment, making a simple patch update more complex than it needs to be. Before software deployment, remote systems need to be detected and audited to find out what version is currently installed and what needs to be done to make the computer ready for its update. After deployment, the system needs to be tested, monitored and flagged for remediation if necessary. Without easy access of pertinent inventory information, and without the ability to conduct remote operations seamlessly on each machine, simple updates become multi-step complex operations.

remote software deployment

Current remote software deployment solutions are typically point products that cause complexity rather than create efficiencies. They often lack visibility that’s necessary for planning and testing of software deployments. IT departments often don’t know the current state of systems or if they’re ready for an update. Most education IT departments push software patches out without knowing if the systems can handle the upgrade. This results in system down time and unhappy users.

If it takes ten minutes to manually check readiness, conduct pre-deployment routines, install the software and then wrap up the operation, that’s 10,000 minutes or 167 hours per 1,000 devices. Add to that the fact that most software deployment tools aren’t integrated with the service desk, preventing your staff from combining remote sessions with the remediation of unsuccessful installs. If a process fails, the administrator has to log out of the software deployment tool, boot up a remote control application, worm in and remediate the issue. Once done, he would have to back out again and repeat the deployment process.

There has to be a better way!

Complete Visibility with Integrated Software Deployment

Imagine this scenario: a new research application needs to be deployed on 25 desktops in a science lab. An administrator triggers a series of automated commands that install the software on the machines. This script causes all of the following to happen automatically:

  • All systems are audited and checked for readiness for installation
  • Desktops that need additional components are flagged and a ticket request created for each machine
  • Pre-deployment and automated scripts are processed on the systems, including uninstalling the old software and wiping the temporary files folder
  • Application is pushed out to the waiting systems and installed
  • Desktops are rebooted and the software is tested
  • Additional alerts are set for the systems and reports are routed to an administrator

Routing software deployment and IT systems management functions through a single management console can help education IT professionals tie IT operations to the school’s operational processes. Software deployments don’t have to be stressful, time consuming chores. They can be simple, efficient and almost effortless.

Learn more about Kaseya remote software deployment. Download our free white paper “School IT Systems Management Complete and Integrated Remote Control ” now!

Trackbacks/Pingbacks:

  1. Patch Management Best Practices for Education IT Environments | Kaseya - June 16, 2011

    […] Management Best Practice #3 – Evaluate and Plan Develop the patch software deployment policy and schedule and a corresponding exception […]

  2. K-12 Education Bundle for IT Systems Management | Kaseya - October 24, 2011

    […] Software deployment & agent scripting […]

Leave a Reply:

Gravatar Image

-->