Blackberry Desktop Manager 6.x

Hi Team

I am ATTEMPTING repackaging BBDTM6.x .
My deployment mechanism is SymaNtec Deployment 7.x
I have extracted the MSI and associated files and have knocked out the use setup.exe launch condition.

I can get the App to install and uninstall using a CMD file that applies a transform against the MSI.
I have elected to use a CMD file rather than the internal logic as I want to prevent the program checking for updates, which I am trying to do with a REG argument

I am attempting to stop this behaviour by adding a line subsequent to the install section that is adding a false value to the following HKCU hive

"[HKEY_CURRENT_USER\Software\Research In Motion\DesktopAutoUpdate]

But It no work


Based on this (And bear in mind it is 11:22 pm my time so forgive any glaring omissions here)
Is my logic in achieving this change by adding a Reg key to the HKCU hive dodgy (If the install is applied when a user isnt logged on it wont be registered . That is if I can get it to work.)
Should it be GPO'd (VIA the Blackberry Users OU) or deployed in a better way. I am open to suggestions. Ideally I want it all deployed from a central point (Symantec) but will do whatever is best

I have a wee bit of experience as a desktop guy, I am in no way to be confused with someone who knows what they are doing packaging wise. So be gentle (VBScab, I'm looking at you!!)

YEs I am googling and yes I have scoured this site prior to posting

Many thanks for any suggestions that you see fit to propose.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 12 years ago
Red Belt
Adding the registry data is the correct way to do this but you need to trigger a repair in order to have it installed for the currently logged-in user.

To do that, you need to

- create a new feature and component containing your setting(s)
- find a feature with an advertised entry-point e.g. a shortcut
- make the feature above a child of the new feature

Now, when the entry-point is triggered, the app will "repair" the feature tree.

If there are no advertised entry-points, you could use Active Setup (thoroughly documented here and elsewhere). Remember, though, that AS is a one-off set-up and will not be repaired.
Posted by: Rheuvel 12 years ago
Brown Belt
So, if I get this right your only problem now is how to deliver the HKCU key to (every) user profile?

If that's the case and you have already eliminated the need for the setup.exe you can use Orca or Instedit to generate a transform file for the MSI. In this transform file you can add the registry key to the registry table (http://msdn.microsoft.com/en-us/library/aa371168(VS.85).aspx will show you what values it expects).

And if you need to do this on a regular basis, I'd demand a real tool like InstallShield that makes the above easier.
Posted by: invisibl 12 years ago
Senior Yellow Belt
Hi Guys

FIrst up thank you for your replies..
Sadly some (If not all) was completely beyond my understanding

I did boogle Active Setup searching here and on the web and elected to use that.
I imagine by the time I have to repackage the successor to this , EIther RIM will have changed the package style or I will hav learned enough to better understand the above instructions/suggestions.

I a not a repackagers @r53hole, BUt I am trying to learn!!!

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

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ