|
|
|
|
|
|
Functionality
Focus |
|
Starter
Edition |
Professional
Edition |
Enterprise
Edition |
|
Produce
MSI
Package
for
Silent
Remote
Deployment
|
|
|
|
|
|
Generated
MSI
packages
can
be
installed
silently,
i.e.
without
interaction
with
end-user,
and
are
ready
for
remote
deployment
through
Group
Policy
or
Remote
Installer.
|
|
|
|
|
|
Create
New
MSI
Installation
|
|
|
|
|
|
New
MSI
packages
can
be
created
from
scratch
using
easy
visual
editor
that
helps
to
define
installation
resources
and
configure
installation
actions.
|
|
|
|
|
|
Repackage
Existing
Installation
into
MSI
Format
|
|
|
|
|
|
EXE
and
other
types
of
installations,
including
installations
that
require
user
input,
can
be
automatically
transformed
into
MSI
format,
ready
for
silent
execution
and
remote
deployment
through
Group
Policy
or
Remote
Installer.
|
|
|
|
|
|
Customize
MSI
Package
|
|
|
|
|
|
Existing
MSI
packages
can
be
decompiled
to
apply
required
changes
and
produce
new,
customized
MSI
package
based
on
it.
|
|
|
|
|
|
Convert
Any
Activity
into
Installation
|
|
|
|
|
|
Any
actions
on
file
system
and
registry
can
be
monitored
and
used
as
input
for
creation
of
MSI
package
that
will
perform
same
actions
in
scope
of
the
installation.
|
|
|
|
|
|
|
|
|
|
|
|
|
MSI
Creation
Approach |
|
Starter
Edition |
Professional
Edition |
Enterprise
Edition |
|
Manual
Creation
Using
Visual
Editor
|
|
|
|
|
|
MSI
package
can
be
generated
from
manually
created
installation
project.
In
this
case
all
installation
resources
together
with
their
installation
actions
are
manually
defined
using
a
special
visual
editor.
|
|
|
|
|
|
Automatic
Creation
Based
on
Monitoring
Results
|
|
|
|
|
|
Unique
'Live
Monitoring'
technology
can
be
used
to
track
all
changes
on
file
system
and
registry.
These
changes
are
transformed
to
installation
project
and
used
for
automatic
MSI
package
generation.
|
|
|
|
|
|
Automatic
Creation
Based
on
MSI
Decompilation
|
|
|
|
|
|
Existing
MSI
package
can
be
decompiled
and
changed
to
produce
new
customized
installation.
|
|
|
|
|
|
|
|
|
|
|
|
|
Supported
Installation
Resources |
|
Starter
Edition |
Professional
Edition |
Enterprise
Edition |
|
Files
and
Folders
|
|
|
|
|
|
Create
or
delete
folder.
Create,
delete
or
modify
file.
Update
file
content.
|
|
|
|
|
|
System
Folders
|
|
|
|
|
|
Installation
paths
to
file
system
resources
can
be
defined
using
special
system
folders
that
are
converted
to
OS-specific
values
during
installation.
It
guarantees
resources
installation
to
right
system
directories,
for
example
to
the
Program
Files,
regardless
of
their
different
locations
or
names
on
different
platforms.
|
|
|
|
|
|
Registry
Keys
and
Values
|
|
|
|
|
|
Create
or
delete
registry
key.
Create,
delete
or
modify
String,
Binary,
DWORD,
Multi-String
and
Expandable
String
registry
value.
|
|
|
|
|
|
Environment
Variables
|
|
|
|
|
|
Create
or
delete
user
or
system
environment
variable.
|
|
|
|
|
|
Shortcuts
|
|
|
|
|
|
Create
shortcut.
Configure
shortcut
name,
target,
start
folder,
run
parameters,
start
arguments
and
comment.
|
|
|
|
|
|
Services
|
|
|
|
|
|
Create,
delete
or
manage
service.
Set
or
change
service
state,
start
options,
arguments,
execution
account
and
dependencies.
|
|
|
|
|
|
|
|
|
|
|
|
|
Resource
Management
Options |
|
Starter
Edition |
Professional
Edition |
Enterprise
Edition |
|
File
Attributes
Management
|
|
|
|
|
|
Set
or
modify
Read
Only,
Hidden,
System
and
Compressed
file
attributes.
|
|
|
|
|
|
Permanence
Option
for
Files
|
|
|
|
|
|
Set
a
special
option
to
prevent
file
deletion
on
uninstall.
|
|
|
|
|
|
Update
Options
for
Registry
Values
|
|
|
|
|
|
Update
existing
String,
Multi-String
and
Expandable
String
registry
values
to
replace
existing
content
or
append/prepend
new
content
to
existing.
|
|
|
|
|
|
Permanence
Option
for
Registry
Keys
and
Values
|
|
|
|
|
|
Set
a
special
option
to
prevent
registry
key
or
value
deletion
on
uninstall.
|
|
|
|
|
|
Conditional
Creation
and
Deletion
of
Environment
Variables
|
|
|
|
|
|
Create
environment
variable
only
if
it
doesn't
exist.
Delete
environment
variable
if
its
value
is
equal
to
configured
parameter.
|
|
|
|
|
|
Update
Options
for
Environment
Variables
|
|
|
|
|
|
Update
existing
environment
variable
to
replace
existing
content
or
append/prepend
new
content
to
existing.
|
|
|
|
|
|
|
|
|
|
|
|
|
MSI
Generation
Options |
|
Starter
Edition |
Professional
Edition |
Enterprise
Edition |
|
Basic
MSI
Options
|
|
|
|
|
|
Every
generated
MSI
package
includes
product
name,
information
about
manufacturer,
package
version
and
installation
language.
This
information
is
used
by
Windows
Installer
infrastructure
and
displayed
in
the
list
of
installed
applications.
|
|
|
|
|
|
Include
Installation
into
Add/Remove
Programs
List
|
|
|
|
|
|
Correspondent
option
allows
showing
or
hiding
installed
MSI
package
in
the
list
of
application
displayed
by
Windows
Add/Remove
Programs.
|
|
|
|
|
|
Reboot
After
Installation
Option
|
|
|
|
|
|
If
MSI
installation
process
requires
a
reboot,
it
can
be
enabled
automatically
by
defining
a
special
option
in
MSI
properties.
|
|
|
|
|
|
File
Versions
Handling
|
|
|
|
|
|
Various
file
version
handling
options
allows
controlling
installation
behavior
in
case
of
files
overwriting.
Available
options
include
force
overwriting,
install
if
file
is
missing
or
if
file
is
previous
or
equal
version.
|
|
|
|
|
|
Installation
Summary
Information
|
|
|
|
|
|
Summary
information
about
author,
subject,
keywords,
comment
can
be
included
into
generated
MSI
package.
|
|
|
|
|
|
Installation
Support
Information
|
|
|
|
|
|
Produced
MSI
file
can
provide
full
support
information
including:
contact,
phone,
online
support,
update
info
URL,
help
URL,
manufacturer
URL
and
comments.
|
|
|
|
|
|
|
|
|
|
|
|
|
Projects
and
Installations |
|
Starter
Edition |
Professional
Edition |
Enterprise
Edition |
|
Persistent
Installation
Projects
|
|
|
|
|
|
Information
about
one
or
multiple
installations,
including
installation
resources
and
actions,
is
grouped
into
the
installation
project.
Projects
are
stored
as
XML
files
and
can
be
saved
and
loaded
when
required.
|
|
|
|
|
|
Import
Installation
Resources
|
|
|
|
|
|
The
entire
folder
with
a
list
of
subfolders
and
files
can
be
imported
into
the
installation
to
save
a
time
for
installation
model
creation.
Set
of
registry
values
and
keys
can
be
imported
also
in
one
step
from
the
*.reg
file.
|
|
|
|
|
|
Rolling/Unrolling
System
Folders
|
|
|
|
|
|
Paths
to
file
system
resources
in
the
installation
model
can
be
automatically
transformed
to/from
special
system
folder
variables
that
represent
system
OS
locations,
such
as
Program
Files
folder,
by
the
OS-independent
way.
It
guarantees
installation
resources
to
the
right
system
locations
even
if
these
locations
have
different
paths
on
different
platforms.
|
|
|
|
|
|
Merge
Installations
|
|
|
|
|
|
Few
installations
can
be
automatically
merged
to
produce
a
new
one
that
combines
all
installation
resources
and
actions.
|
|
|
|
|
|
|
|
|
|
|
|
|
Filters |
|
Starter
Edition |
Professional
Edition |
Enterprise
Edition |
|
Resource
Filter
|
|
|
|
|
|
Resource
filter
helps
to
exclude
operations
with
particular
file
system
and
registry
resources
from
monitoring
results.
Application
comes
with
a
set
of
predefined
filters
to
exclude
monitoring
of
specific
OS
resources
that
should
not
be
changed
by
generated
MSI.
If
required,
this
list
can
be
extended
by
any
custom
filters.
|
|
|
|
|
|
Process
Filter
|
|
|
|
|
|
Process
filter
helps
to
exclude
all
actions
of
particular
service
from
monitoring
results.
Application
comes
with
a
set
of
predefined
filters
to
exclude
monitoring
of
changes
generated
by
specific
OS
processes.
If
required,
this
list
can
be
extended
by
any
custom
filters.
|
|
|
|
|
|
Permanence
Filter
|
|
|
|
|
|
Permanence
filter
helps
to
mark
particular
file
system
and
registry
resources
in
MSI
as
permanent
and
protect
them
from
deletion
during
MSI
uninstallation.
Application
comes
with
a
set
of
predefined
filters
that
can
be
enlarged
by
any
custom
filters
if
required.
|
|
|
|
|
|
|
|