I'm using bigdessert's script to update our remote XP workstations from 2.2 to 2.3 (server was done last week). I had a hiccup and RDP'd to the box and I noticed that a workstation had V2.1 and V2.2 installed on it in Add/Remove programs and also had 2 services listed as well.

I was able to tell Add/Remove to uninstall V2.2, but when trying to uninstall V2.1 it is looking for the original MSI package. After running the old trusty Office cleanup utility, I was able to manually install the V2.3 MSI.

However, the V2.1 service still shows up. I changed the startup type to Disabled, but would still like to remove the old 2.1 service and registry entries from the workstation.

I discovered another machine was showing V2.3 on the system tray, but the Add/Remove programs & Services both showed V2.2. Running the Add/Remove programs also called for a msi that was located in a temp directory. In this case, it appeared that it was there, but hard to say if it is the original MSI or one that is named the same.

Both above were used as an account that has local administrative credentials.

Thanks for your help.

Thanks for the help this morning.

I confirmed that the base URL was the same from the first script (V2.1 - V2.2) and the latest script you published. It appears that only a couple of machines, so the script works without issue.

I'm wondering about the original installation package that was used to install it on the old machines. I cannot say for certain if it was the test server or the production server. If the tech used the old one, it may "help" the issue.

I am leaning toward the original installation on certain machines was in a pseudo-funky state. It is the updates (from V2.1 - V2.2 - V2.3) that helped bring the issue to light.

The issue is that these workstations have specialized monitors and drivers. When issues happen, the specialized driver becomes corrupted (BSOD whenever try to SC to the machine). Typically, by reinstalling the driver, it takes care of the symptom.

I can live with driver corruption once in a while (prefer never), but I think I need to start from square 1 by ripping off SC totally (including the reg) and start fresh. Otherwise, our next step will be re-image the machine off hours.

Thanks again for the info on the reg key. I'll nuke that as soon as the machine is free.