Software Deployment

Hi,

Delete Cisco Systems enter at HKLM\Software\Cisco. Then you can uninstall the VPN

Check the LaunchCondition table and see if there's an entry 'Privileged' or possibly 'IsAdmin'. If there is, remove it. It's probably being used to condition execution of actions in th einstall sequence.

Hi,

Thanks for your answer... You are right there was a entry named Privileged that I deleted.
But it did not solve my problem [:(]

check below link:
http://winprogger.com/?p=14

I presume you have stopped the VPN services and closed all client apps, including the System Tray applet?

More importantly, ANY installation is going to require local administrative privileges so it's a pre-requisite that the installing user account be a member of the 'Administrators' group.

Its not the installation that is the problem. The problem is when it is installed and a user that is not local admin wants to use it. Then he/she get this message.

And sorry but the Link wasent to any help.

Its not the installation that is the problem. The problem is when it is installed and a user that is not local admin wants to use it. Then he/she get this message.

Do a capture of the first startup under admin account and see if anything interesting pops up.
Another option is to ProcMon the startups and look for differences between Admin/User and other possible blocking issues

PJ

Start off by assigning write permissions for INSTALLDIR and any HKLM registry keys which the package creates. If that fixes the problem, you should add to the package a Custom Action that assigns those permissions. Alternatively, it could be that the app is trying to write *new* files and/or registry entries, in which case, you need to add those to your package.

As Pieter allludes, it's always instructive to create a separate snapshot of an application's start-up: that highlights this kind of activity.

Hi Eric,
this version of Cisco VPN was released more than 18 months ago, is buggy as hell and has severe security issues! Please use the latest version (5.0.5, i think).
Uninstall it and then make sure, the beloved DNE (Deterministic Network Enhancer) is gone.
Use this tool to remove the beast: http://www.citrix.com/lang/English/lp/lp_1680845.asp
Afterward install the actual version and copy the profile to its directory by hand.
Test it. If this works, go a step further and analyze your transform. Load the MSI into ORCA and apply the transform. See if there are green marked entries, which are not used to do your changes.
Which tool did you use to create it?
Hope, this gives you some ideas to attack the problem.
Regards, Nick

Hi,

unfortunately I am not allowed to use another version because it has to be tested and approved on a corporate level [:@]

Hi Eric,
this does not change the general approach to solve your problem, as i outlined above.
However: A Testcrew, which needs more than a year to release a cruical piece of software in terms of security is just plain useless. No its more than that, its a danger to the hole company!
Regards, Nick

unfortunately I am not allowed to use another version because it has to be tested and approved on a corporate level [:@]BTDT. Just say to the head of the test/approval team that you are happy to release the version they have tested right after he sends you an email signing off the release into Production of a product with known issues. Your email will include bug reports/advice from vendor, etc., etc. You will never receive that email.