23Jul W2K Terminal Services and MSI package install
I cant seem to figure out why when I go to install certain MSI packages on W2K via remote desktop I am not allowed. It is rather annoying.
Certain portions of our application are .NET components that are installed as part of an MSI package. The process is to uninstall the old package via remove programs, and then install the new package. Of course it is during the installation of the new package that this happens.
Is there a certain component that I am missing? Is there something that I am doing wrong? There could be something in the MSI itself that is the culprit.
Email me with suggestions.

