Hi all,
I'm packaging MindManager 6 Pro via transform, I've deactivated the ISScriptEngine so it's not needed for this package.
The only thing that remain to solve is a CU key to avoid seeing the TipsScreen on the first use of each user.

Please does anybody can help without adding ActiveSetup Key?

Thanks in Advance

Kris
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
Kris,
Did the general method of creating CurrentUser Component and making the MSI repair for each user also didnot work in your case??
Answered 08/16/2006 by: slb
Purple Belt

Please log in to comment
0
Hi Slb,
I've tried this option too but it doesn't work in this case. Self-repair seems to not initialize correctly in this transform because the registry key that I include is a KeyPath and it should work...
Answered 08/16/2006 by: KrisBcn
Purple Belt

Please log in to comment
0
Hope you have tried by having the currentuser component in a seperate feature and having this new feature as your parent feature too..

If nothing works and you get no answers from our other friends in this forum then..
there is a way but which is not efficient in MSI concepts..

You can create an executable to do the following jobs
set your current user registry value
and start the mindmanger main exe


Make your shortcuts to launch the above created exe(which should be a part of your installation).

Hope this helps...[:D]
Answered 08/16/2006 by: slb
Purple Belt

Please log in to comment
0
yes, I've tried this way, and that was the result, I'm not allowed to use this kind of packaging, I must give a clean (as clean as possible) msi/mst...
So I'll wait for a while, to if anybody else wakes up with any idea..

Thanks for all [:)]

Kris
Answered 08/16/2006 by: KrisBcn
Purple Belt

Please log in to comment
0
write a vbs script...

Have it record what keys are open under HKEY_USERS before starting

have it attempt to load each NTUSER.dat for each profile using reg.exe (comes with windows xp)-- IT WILL FAIL ON THE KEYS ALREADY OPEN

Load the keys as the foldername it's coming from -- the name doesn't matter but it makes it easy.

Once loaded enumerate the HKEY_USER Hive and write the value to each key..

At the end unload the keys if they weren't open at the beginning - if you leave users CU Hives loaded it will cause problems when they try to login..

Done ... put this in your MSI as a Custom Action or have it run seperately depending on what your deployment method is...

I wrote a script that would take a Regedit export as my parameter and then complete those imports - it's a little easier then writing your own each time.

and no i can not share it... wish i could.

Good Luck ...

fyi - this is probably the only method you have left ... Windows doesn't make Current User very easy to manipulate...
Answered 08/16/2006 by: gmorgan618
Blue Belt

Please log in to comment
2
Hi KrisBcn,

To be able to disable the TipsScreen that is, self-healing the HKCU registry setting just:
Create a component, lets call it "CurrentUser" and set the KeyPath to "HKCU_DisableTipsScreen"(will create this later)
(Enter values in the Component, ComponentId, Directory_, Attributes and KeyPath columns)
CurrentUser <GUID for the component> TARGETDIR 4 HKCU_DisableTipsScreen

Add the registry for the "ShowWelcomeScreen" to the component (ex. DisableTipsScreen).
The entry under Registry table should look like:
(Enter values in the Registry, Root, Key, Name, Value and Component_ columns)
HKCU_DisableTipsScreen 1 Software\Mindjet\MindManager\6\Settings ShowWelcomeScreen #0 CurrentUser

Add the "CurrentUser" component to the "Program_Pro" feature as this feature contains the "N_MindManager6.exe" component which in turn holds the file resource "MindManager.exe" that is launched with the shortcut (this will make the self-healing be triggered when the shortcut is launched.)
Values for Feature and Component column in the FeatureComponents table:
Program_Pro CurrentUser

If you do this correct the self-healing will take care of the WelcomeScreen (aka TipsScreen).
Tips: capture the application launch and include the files created in the userprofile and HKCU registry entries and include that in the package. In that way the user don't have to wait for the files to be created which seemed to take a little bit of time.

Cheers!
Answered 08/21/2006 by: AngelD
Red Belt

Please log in to comment
0
Hi AngelD!
It sounds good, I'm gonna try it right now and let you all know the result!
Thanks for all. KrisBcn [:D]
Answered 08/21/2006 by: KrisBcn
Purple Belt

Please log in to comment
0
Hi again AngelD,
Now it works OK, thanks a lot !!! and thanks to gmorgan and slb for their contribution too :)
KrisBcn
Answered 08/22/2006 by: KrisBcn
Purple Belt

Please log in to comment
0
Yeah I know it would [8D]
Answered 08/22/2006 by: AngelD
Red Belt

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