Hello and welcome to this lansweeper
5.2 tutorial. Lansweeper 5.2 is the next major update of our network management
software and will officially be released in the very near future a beta is
available on our website at lansweeper.com/forum so feel free to update
now and follow along with this tutorial 5.2s important new feature is
mass deployment it allows you to manage the Windows computers in your network
and install and uninstall software make command line changes, kill processes and run
custom scripts this tutorial is meant to give you just a taste of what you can do
we’ll be creating a deployment package to silently install Adobe Reader on
multiple machines without user intervention creating a dynamic asset
group to deploy the package on deploying our package and reviewing the changes
that occur let’s get started okay so I’ve prepared this deployment by
researching cylon install procedures for Adobe Reader I’ve downloaded a reader 11
executable from the Adobe website and found the parameters I need to perform a
silent install with this executable different programs require different
installation procedures so it’s best to research these procedures online what
I’ve also done is added my executable to the Program Files lansweeper package
share folder on my lansweeper server this folder is automatically created and
shared when you install a lansweeper 5.2 and can be used to store
your deployment executables and scripts to keep things organized I’ve placed my
executable in an Adobe Reader folder which I manually created under package
share installers with the executable in place create your
package in the deployment packages section of the web console hit the new
package button and submit a name and description for this particular
deployment degree scan assets as well this will automatically rescan your
computers when the deployment has completed so you’ll see up-to-date
information on your computer webpages we won’t touch the other settings for now
just hit OK to start configuring your deployments a package consists of one or
more steps with each step leading to either another step or a success or
failure message our deployment will consist of two steps the first step is a
file condition that checks whether our Adobe executable is present in
landscapers package share folder you can easily reference this folder with a
package share parameter if the check is successful and the file exists the
package should proceed with the next step which will be the Adobe Reader
installation if the file does not exist the deployment should end in a failure
message basically if someone accidentally deletes our executable our
package will give us a warning this step looks ok so let’s create the next one
the second and final step is an installer step we’re going to launch our
executable with the parameters we’ve previously researched the successful
completion of the step should end the deployment in a success message a
failure should end in a failure message our package is ready now we’ll create a
dynamic asset group to deploy a package on dynamic asset groups our new in a
lansweeper 5.2 and let you group assets based on criteria this allows you to
quickly and easily target your deployments to specific machines create
a group by hitting the add dynamic root button under configuration asset groups
the first filter we want to add is one for installed software we of course only
want to deploy Adobe Reader on computers that don’t yet have the software
installed and just make things more interesting
let’s also specify that only 64-bit computers within the lansweeper
domains should be included hit the view assets button see a list of
computers that meet your criteria and then hit deploy package on the left
select your package and hit OK to start deploying again we won’t bother with the
other settings for now under deployment logs you can see the progress of your
deployment our package is initializing so let’s wait a few minutes for it to
complete okay I’ve refreshed a page and most
installations have successfully completed one machine generated an error
but is likely offline you’ll notice that we can ping this computer either if we
click through to machine whose installation did complete we can now see
Adobe Reader listed in the computer software tab the history tab also
indicates that the software was added in addition you’ll notice that the machine
is no longer part of the dynamic asset group we created earlier as it now has
Adobe Reader installed that’s all there is to it of course you can customize
your packages further and deploy based on a schedule or as your machines come
online but that’s beyond the scope of this video thank you for watching and
keep an eye out for more tutorials