Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user IT Stonebranch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Macro name changed from html to html-bobswift during server to cloud migration processing.

...

To repair a UEC Client Applications installation from the command line, without using the Windows Installer graphical interface, issue the following command:

Panel

Html bobswift

<pre>
msiexec.exe /fom SetupPath\UEClient.msi /q
</pre>

 

Interactive Repair, with Log File

To repair a UEC Client Applications installation using the Windows Installer graphical interface, and instruct Windows Installer to write a log file to C:\Temp\repair.log while running the repair, issue the following command:

Panel

Html bobswift

<pre>
msiexec.exe /fom SetupPath\UEClient.msi /L C:\Temp\repair.log
</pre>

Removing UEC Client Applications from the Command Line

...

To uninstall the UEC Client Applications without using a graphical interface, issue the following command:

Panel

Html bobswift

<pre>
msiexec.exe /x SetupPath\UEClient.msi /q
</pre>

 

Silent Removal, Per-User Installation

To remove a per-user installation that was installed using an Administrator account, issue the following command:

Panel

Html bobswift

<pre>
msiexec.exe /x SetupPath\UEClient.msi PERUSER=1 /q
</pre>


Tip
titleA Stonebranch Tip

If you know that the UEC Client Applications were installed using an account that is a member of the Administrators group, but are not sure if a per-user or per-machine installation was done, it might be best to uninstall the Client Applications using the graphical interface (see Removing a UEC Client Applications Installation).

This will ensure complete removal of the UEC Client Applications.

If you are removing a UEC Client Applications installation that was installed using a non-administrative account, the PERUSER parameter is not necessary.