/build/static/layout/Breadcrumb_cap_w.png

Blackberry Repackage and User Rights

We are having a terrible time with the Blackberry Desktop Manager 3.6SP2 installation. We can get the silent install to work and customizations to come over when logged in as a local admin, but it seems that this software absolutely will not run with user rights.

setup.exe /s /f1"J:\setup.iss" /f2"J:\Install.log" <== this is the command line that works great logged on as local admin, but not when logged in with user rights.

When the .MSI is launched directly (even as admin), we get an error saying that setup.exe must be run, and not the MSI directly. We are trying to figure out a way to bypass the setup.exe, create a transform of the .msi, and run this transform with elevated privelages (Execute deferred) while logged on as the user. Has anyone gotten around this?

Thanks,
Steve

0 Comments   [ + ] Show comments

Answers (7)

Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
Blackberry have released a doco on repackaging their desktop app. I used it and got it working fine. The main point is setting up the custom action to install the USB driver correctly.

http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/8179/271477/Repackaging_the_BlackBerry_Desktop_Software_Installer.pdf?nodeid=348354&vernum=1

I might have some other info as well.....let me look aronud here and I'll post it if I find it.
Posted by: Skaye 20 years ago
Senior Yellow Belt
0
Thank you for the document, but is generally considered "Against best practice" when repackaging someone else's MSI file. I will use the document as a last resort.
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
I agree and I dont like repackaging vendor msi installations but in some cases you have to and considering some of the packages I have seen from vendors......its preferable in my opinion.

Vendors are happy to include just about any file in their installation and in lots of cases those files shouldnt be included.
Posted by: kaspianx 20 years ago
Senior Yellow Belt
0
Thanks for posting about this document. I've been struggling with trying to deploy BlackBerry via AD (computer side) for some time now.

I'm using WinInstall LE 2003 to repackage and ORCA to modify the tables. I've understood and done everything except the Binary Table part. Can you give a step-by-step for that piece? I've downloaded the files dllwrap.ini and dllwrap.dll but I can't seem to find the right way to add them to the MSI.

Thanks!
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
Well I use Wise Package Studio so I cant make a step by step for winstall for you....but you dont have to instert the binary data....just create the custom actions and point it to the dll's.

Make the custom properties as the doco requests and then make your custom actions. These custom actions will populate the binary tables for you.

CA1

Call DLL from Installation
Name it DLLWrapStartup or any name you choose
Browse to the dllwrap.dll in your installation
Function name is DLLWrapStartup

CA2

Call DLL from Installation
Name it RIM_SetupCopyOEMInf or any name you choose
Browse to the dllwrap.dll in your installation
Function name is DLL1

CA3

Call DLL from Installation
Name it DLLWrapCleanup or any name you choose
Browse to the dllwrap.dll in your installation
Function name is DLLWrapCleanup

There is a couple of sample msi files listed in the doco....I suggest you download them and have a look at them.
Posted by: kaspianx 20 years ago
Senior Yellow Belt
0
Thanks for the break down. I actually use ORCA to modify the tables and WILE2003 only to repackage so that helped.

Has anyone gotten this to work with 3.6 SP2? All I manage to get is a protocol error with my USB Blackberry. I've hit my frustration level and given up. [:'(]
Posted by: kaspianx 20 years ago
Senior Yellow Belt
0
OK, I went back to trying to repackage BlackBerry Desktop manager 3.6 SP2. This time I was mostly successful. (About all I can hope for [8|])

By following these instructions (thanks MSIMaker):
Repackaging BackBerry Desktop Software

And then the resolution here:
Protocol Error Data Transfer Aborted

My package works!

I hope this helps anyone else trying to do this frustrating task. Why, oh why, can't RIM release a straight .msi without the setup.exe???
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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