<div>
Thanks for the comments, however that doesn't answer my question. The original question was this: <br />
<br />
Is it best to just perform a System State backup and attempt to uninstall the Windows Installer and reinstall again? &nbsp;- This being and DC and Exch box. The Windows Installer is corrupted - when attempting to install an app such as (BE 10d SP3 remote agent) and it doesn't install (due to the fact that windows installer is corrupted - verified by BE support). <br />
<br />
What I'm trying to get @ is the fact that if u think Windows Server 2000 would hold up an uninstall of Windows Installer 3.1 and a reinstall of it - as question of stability. THanks...<br />

</div>


Thanks for the comments, however that doesn't answer my question. The original question was this:

Is it best to just perform a System State backup and attempt to uninstall the Windows Installer and reinstall again?  - This being and DC and Exch box. The Windows Installer is corrupted - when attempting to install an app such as (BE 10d SP3 remote agent) and it doesn't install (due to the fact that windows installer is corrupted - verified by BE support).

What I'm trying to get @ is the fact that if u think Windows Server 2000 would hold up an uninstall of Windows Installer 3.1 and a reinstall of it - as question of stability. THanks...


<div>
<div class="content wysiwyg-content">
I have an Windows 2000 Server w/ SP4. Server functions as a DC, Exchange and quickbooks. Unable to install applications due to a possile corrupt Windows Installer 3.1. All files that I see that are .msi, .mst are now unidentifiable. Is it best to just perform a System State backup and attempt to uninstall the Windows Installer and reinstall again? <br />
<br />
Any suggestions anyone?<br />
<br />
Thanks...
</div>
</div>


I have an Windows 2000 Server w/ SP4. Server functions as a DC, Exchange and quickbooks. Unable to install applications due to a possile corrupt Windows Installer 3.1. All files that I see that are .msi, .mst are now unidentifiable. Is it best to just perform a System State backup and attempt to uninstall the Windows Installer and reinstall again? 

Any suggestions anyone?

Thanks...

Windows Installer Corrupted

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

The term "Backup" means the methods and processes involved to copy computer data (system data as well as application data) to media other than the ones where the data originally live (disk, tape, optical, cloud). "Restore" in turn means the methods and processes involved in data recovery, i. e., bringing back copied computer data to their original location. Backup/Restore primarily serves as a means of protection against data loss, be it due to disaster, corruption or sabotage. It can also be used for recovering data from an earlier point in time and even for cloning machines or applications. There is a wide variety of backup/restore software available, from expensive commercial products to free or open source tools.

Storage Software

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.