Hi All,
I am Working on Vendor MSI IP Communicator. I Created MST with a few custom actions.
When I uninstall , the log file says uninstall is successful. And there are no folders in c drive.
But there are a few registry keys related to cisco communicator that remains, and also CDP Packet driver.

A few are

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{39B06043-A189-4F35-92DD-693F6DB870FF}\1.0\0\win32]
@="C:\\Program Files\\Cisco Systems\\Cisco IP Communicator\\GNNetcomHandset.dll"

[HKEY_CLASSES_ROOT\TypeLib\{1F4DC43C-02A8-4E0D-A5A8-9F92241C0697}\1.0\0\win32]
@="C:\\Program Files\\Cisco Systems\\Cisco IP Communicator\\ClarisysHandset.dll"

Even though these dll 's are not there in the c drive.
Similary there are a few more registry keys, showing dll 's in c drive, when there is no folders.

Has anyone come across the same situation.
Any help is appreciated

Thanks.
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
Have you checked the behaviour of your Vendor MSI, If your Vendor MSI is behaving as the same then you can take this as an exception and proceed with the next steps.
Answered 11/03/2011 by: sanath_sunny
Orange Belt

Please log in to comment
0
Thanks for the reply. The Vendor MSI also does the same. It does not remove the registries.
How about the driver, is there a way I can get rid of CDP driver. Wont it be a problem, if it exists?
Answered 11/03/2011 by: shamu99
Fifth Degree Brown Belt

Please log in to comment
0
I tried writing a script to remove the registries from the HKCR, HKLM, HKCU. But the registry keys are not deleted.
for example
=========================
const HKEY_LOCAL_MACHINE = &H80000002
strComputer = "."

Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_
strComputer & "\root\default:StdRegProv")

strKeyPath = "SYSTEM\ControlSet001\Enum\Root\LEGACY_CDPPACKET"

oReg.DeleteKey HKEY_LOCAL_MACHINE, strKeyPath
===============
Tried to create a vbscript to delete the CDP Packet. but the registry does not delete.
These are other registries that does not get deleted after uninstall.

[HKEY_CLASSES_ROOT\TypeLib\{1F4DC43C-02A8-4E0D-A5A8-9F92241C0697}]
[HKEY_CLASSES_ROOT\TypeLib\{39B06043-A189-4F35-92DD-693F6DB870FF}\1.0]
@="GNNetcomHandset 1.0 Type Library"

[HKEY_CLASSES_ROOT\TypeLib\{1F4DC43C-02A8-4E0D-A5A8-9F92241C0697}]
"C:\\Program Files\\Cisco Systems\\Cisco IP Communicator\\CdpTester.exe"="CdpTester"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{39B06043-A189-4F35-92DD-693F6DB870FF}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{C72CE17C-93FA-400C-9228-2A5419FBB8D7}\1.0]
@="DeviceManager 1.0 Type Library"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{C8100E01-E7B5-475F-99EF-818EFEF80FC5}]

How else can I work with this? Is there a way I can get rid of these registries

Thanks
Answered 11/03/2011 by: shamu99
Fifth Degree Brown Belt

Please log in to comment
0
Is there a way I can get rid of these registriesFirst, look up the relationship and interaction between 'CurrentControlSet' and 'ControlSet000x' and you'll discover why.

Forget script. These deletions belong in your MST.
Answered 11/04/2011 by: VBScab
Red Belt

Please log in to comment
0
It is a Vendor MSI, I Just had to add a merge module to it, so not much custom actions.. Just the MSI uninstall also has the same issue.

I did delete them from the MST HKLM\system. But still it is created and does not delete after uninstallation. And the components created in HKCR\TypeLib and HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\,
dont get deleted. Is it by any chance because those components GNNetcomHandset , DeviceManager 1.0 Type Library are set as key or because they are related to handset, or something they are not deleted?

Please advice,
Thanks
Answered 11/04/2011 by: shamu99
Fifth Degree Brown Belt

Please log in to comment
0
HI All,
I am having another issue with this application, When I try to do the admin install , the installation happens in a different language not english.
I checked the 1033 in the MSI and MST i created, and also tried using the 1033.mst by
msiexec -i <Name.msi> TRANSFORMS=<transform1.mst>;TRANSFORMS=<1033.mst>
It still does not work.
Any Ideas as to how I need to go ahead, any one faced the same issue

Thanks
Answered 11/07/2011 by: shamu99
Fifth Degree Brown Belt

Please log in to comment
0
msiexec -i TRANSFORMS=;TRANSFORMS=<1033.mst> That should bemsiexec -i <Name.msi> TRANSFORMS="<transform1.mst>;<1033.mst"
Answered 11/08/2011 by: VBScab
Red Belt

Please log in to comment
0
I tried msiexec -a <Name.msi> TRANSFORMS="<transform1.mst>;<1033.mst"
For admin install, it does not work, the windows installer options open. I typed the right way. And the previous command line i used was for admin install
msiexec -a <Name.msi> TRANSFORMS=<transform1.mst>;TRANSFORMS=<1033.mst>
Answered 11/08/2011 by: shamu99
Fifth Degree Brown Belt

Please log in to comment
0
Oh wait, by "admin install", you mean "creating an Administrative Installation Point". Transforms are ignored when creating an AIP. If you think about what an AIP is, you'll realise why.

You really need to get some training.
Answered 11/08/2011 by: VBScab
Red Belt

Please log in to comment
0
Thanks a lot for your fast reply. I'm new, learning things. Thanks a lot to forums, happy to learn.
Either way it will ignore the MST right.
I did try just with the msi too, still the files installed are in a different lang, for admin install, whereas the msi install,
msiexec /i <msi>
This is proper.
I dont know why only as admin install, the language changes, and everytime I do it, the language is different, like once german, then italian.
Answered 11/08/2011 by: shamu99
Fifth Degree Brown Belt

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