Software Deployment

This is not removing the CA, just removing the call to it.. don't see how that's any different to setting an impossible to meet condition.

I'd prefer removing from InstallExecuteSequence it as it's more obvious to anyone looking at the package later - although good documentation should always cover this stuff of course!

Cheers,
Rob.

Hi,

I haven't seen the msi for this but I'm guessing a custom action is resetting all the registration information. Not sure if it's kept in a file or registry key. You might try putting a condition on the CA if this is the case.

Hey thanks for the reply.

Right I did find the component that is resetting the registry to NULL. I put the condition to TSC_WRITEREGKEY AND NOT PATCH that didn't work then TSC_WRITEREGKEY AND NOT Installed OR REMOVE~="ALL" but is still patching.

Why can't you just stop the custom action from being executed at all be removing it from the InstallExecuteSequence table?

Cheers,
Rob.

I don't like removing CAs from vendor MSIs. I generally advise using an impossible-to-meet condition instead, something like 'If 0=1' is about as impossible-to-meet as I can think of.

Finally figured it out Monday afternoon. I don’t like deleting CA’s from the vendor either.

A property called CURRENTUSER had a value of XxxXxxXxxXxx. So I changed the value to my company name. Created a CA called CURRENTUSER gave it a, type 51, source CURRENTUSER and target my company name.

Then added a entry in InstallExecuteSeq behind the WriteRegistryValues, then added the condition for WriteIniValues NOT Installed and it worked.

The app runs “registered” from looking at the REGINFO.INI for a company name. When selfheal runs it blanks the registry and writes a blake or deletes the company name from a line called CURRENTUSER in a file called REGINFO.INI in AllUsers%\AppData\app folder.

Thank you everyone that replied and for the ideas!