Howdy!

A previous administrator at my job created an Office 2003 installer package using WinInstall LE, and distributed the package via an unknown method leaving no documentation. And now, the installation source has gone MIA and no one currently on board was here when the package was created - including yours truly - so finding the offender has proved

We are now in the midst of a full-on rollout of O2K3 w/patches via GPO distribution, but cannot update installations on client machines that were installed via the above method. The error produced is something along the lines of "WinInstall LE: Evaluation License Expired" (paraphrase). The only working fix that we'e found requires the Windows Installer Clean Up utility to remove the O2K3 installation, after which the GPO method works AOK - but, we'd have to visit 300+ desktops/laptops (either scriptically, or manually) to do so and the only way we know if a WinInstall error will occur is when the user tries to install/update O2K3 (via GPO or Microsoft update). Not very user friendly...

Does anyone know of a registry key, or other method by which we can detect and compile a list of WinInstall O2K3 installations? A registry search for 'wininstall' on an affected system turns up nada. I'd like to tailor a fix for just the WinInstall "infected" systems rather than than a mass uninstall/reinstall...

Thanks in advance for any help!

-C
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If you export and post the following keys from a "bad" machine, I'll take a quick look.

[HKEY_CLASSES_ROOT\Installer\Products\9040820900063D11C8EF00054038389C] (No subkeys)

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\9040820900063D11C8EF00054038389C\InstallProperties]

Edit: I'm guessing that it's been transformed or edited and the ProductCode is still the same.
Answered 08/18/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
Run a loginscript that control the GUID of the installed office 2003 version, if it's different from the original installation media of office 2003 then it's repackaged.
Answered 08/18/2005 by: AngelD
Red Belt

Please log in to comment
0
Hi Guys,

Thanks for the repsonse!

WiseUser: I was unable to find the specifc key you mentioned, but did find one in the same hive with some O2K3 info, included below.

AngelD: Not sure what you mean by control the GUID of the office install?

Thanks again!

-C

-------------------

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Installer\Products\9040110900063D11C8EF10054038389C]
"ProductName"="Microsoft Office Professional Edition 2003"
"PackageCode"="283E2016B5311624AB766F0FB9A64638"
"Language"=dword:00000409
"Version"=dword:0b0015ee
"Assignment"=dword:00000001
"AdvertiseFlags"=dword:00000184
"ProductIcon"="C:\\WINNT\\Installer\\{90110409-6000-11D3-8CFE-0150048383C9}\\misc.exe,6"
"InstanceType"=dword:00000000
"Clients"=hex(7):3a,00,00,00,00,00
Answered 08/18/2005 by: conrad.koch
Yellow Belt

Please log in to comment
0
Now go to HKEY_CLASSES_ROOT\Installer\Products\9040110900063D11C8EF10054038389C\SourceList
and find the value for LastUsedSource
OR
HKEY_CLASSES_ROOT\Installer\Products\9040110900063D11C8EF10054038389C\SourceList\Net
and find the value for 1.
Any of these entries should point to the location where you can find the installation.
Answered 08/19/2005 by: AngelD
Red Belt

Please log in to comment
0
WiseUser: I was unable to find the specifc key you mentioned, but did find one in the same hive with some O2K3 info, included below.

That's close enough... I just realised that the GUID I gave you was for Office XP.

It doesn't appear to have been transformed then. I guess it must have been edited with Wininstall LE?

Can't you find the other key though??

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\InstallProperties]

The following VBScript should allow you to differentiate between your install and the "old" one.

Set oInst = CreateObject("WindowsInstaller.Installer")

Msgbox oInst.ProductInfo("{90110409-6000-11D3-8CFE-0150048383C9}","InstallSource")

Set oInst = Nothing
Answered 08/19/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity