Table of Contents
Advertisement
194
Managing Windows Installer applications
Repairing Windows Installer applications
Repairing Windows Installer applications
Types of Windows Installer repairs
Table 15-1
Features
Type of scan
Scan time and resources
What it discovers
Method for performing
the repair
See
"Repairing Windows Installer applications"
You can proactively identify and repair broken Windows Installer applications
on managed computers even before the user encounters a problem. These repairs
can save time for both you and the user.
You can use a policy or a task to repair Windows Installer applications on managed
computers.
See
"About Windows Installer repair"
Windows Installer Quick
Repair
Runs a quick scan that
identifies Windows Installer
applications and verifies that
each component s key path is
installed correctly. If the
component s key path is not
installed correctly, the policy
tries to repair the component
and reports the results.
For example, if the Microsoft
Word key path file,
winword.exe, is not installed in
the correct path, the policy tries
to repair Word.
A Windows Installer Quick
Repair takes less time and fewer
resources than a Windows
Installer Full Repair.
A quick repair discovers only
broken or missing key paths. If
a component has other missing
or broken files, a quick repair
might not repair them.
Use a policy.
on page 193.
Windows Installer Full
Repair
Runs a quick scan, like the
quick repair, and then runs a
deep scan. The deep scan
identifies Windows Installer
applications and verifies that
all of the component s
resources are installed
correctly. If any element of a
component is not installed
correctly, the policy or the task
repairs that component and
reports the results.
A Windows Installer Full Repair
takes more time and resources
than a Windows Installer Quick
Repair.
A full repair discovers every
Windows Installer application
that needs repair while a quick
repair might not.
Use a policy or a task.
on page 194.
Advertisement
Table of Contents
