 |
Software
Distribution |
NetSupport DNA provides a multi-delivery
option for Software Distribution.
Firstly, an Operator
will define a software package to be deployed, either
a collection of Files and Folders specified with appropriate
action parameters once successfully delivered to a target
system or by recording and scripting any user prompts
required during an application install so that the package
can be deployed onto a users' system without the need
for intervention.
|
Once created, the application package can be automatically
"Pushed" to the target PCs for deployment or
alternatively "Published" centrally on the DNA
server. Once published, a user can check to see which
applications are available for their PC and install these
on demand.
However, when initiating large scale deployments, the
need to minimize network traffic congestion becomes a
priority. In this case, NetSupport DNA allows a Client
PC, ideally local to the target machines, to be nominated
as a "Distribution Warehouse". When the package
is deployed, rather than distributing the package individually,
it is installs at the "Warehouse" Client which
then distributes it to the remaining target PCs.
 |
Software
Distribution - Schedule |
When operating across a range of locations and networks,
the timing of any major package deployment is critical
as this may result in a detrimental effect on other critical
applications and services, in terms of performance degradation.
To reduce this threat, NetSupport DNA offers a "Scheduling"
facility, whereby a specific date and time can be scheduled
by an Operator for initiating the package deployment -
usually out of core office hours when network traffic
is at its lowest.
To further simplify the package deployment process, NetSupport
DNA includes an "Application Packager", designed
for situations where the application to be rolled out
does not include its own silent install routine. The Packager
enables the operator to record and playback a 3rd party
installer, including all the necessary keystrokes and
movements. These are stored in a script which is then
replayed back at the Client PC without the need for user
intervention.
|
|
|
     |
Overview
