/build/static/layout/Breadcrumb_cap_w.png

Don't be a Stranger!

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

Sign up! or login
Views: 6.5k  |  Created: 01/24/2007

Average Rating: 0
BlackBerry Desktop Software has 28 inventory records, 0 Questions, 0 Blogs and 3 links. Please help add to this by sharing more!

Deployment Tips (14)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 3 / 5 (Average) based on 1 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (answer file driven)
122
Command Line
I was able to deploy Blackberry Desktop Manager 4.2 via SMS by editing setup.ini to include the following at the end of the file:

[INSTALL_OPTIONS]
COUNTRY = United States
SETUPTYPE = Enterprise
MAILSERVER = Exchange
REDIRECTOR = Enterprise
USERS = AllUsers
SHORTCUTSTARTUP = True
SHORTCUTDESKTOP = True
UNINSTALLEXISTINGHANDHELDS = False
SUPPRESSREBOOT = True

The full context of these options is:

[INSTALL_OPTIONS]
COUNTRY = Algeria | Anguilla | Aruba | Australia | Austria | Bahamas | Bahrain | Barbados | Belgium Dutch | Belgium French | Bermuda | Brazil | Bulgaria | Canada | Canada French | Cayman Islands | Chile | China | Colombia | Croatia | Cyprus | Czech | Denmark | Dominican Republic | Ecuador | Egypt | El Salvador | Fiji | Finland | France | Germany | Greece | Grenada | Guatemala | Guernsey | Honduras | Hong Kong | Hungary | Iceland | India | Indonesia | Ireland | Israel | Italy | Jamaica | Japan | Kuwait | Latvia | Lithuania | Luxembourg | Macau | Malaysia | Mexico | Montserrat | Netherlands | Netherlands Antilles and Curacao | New Zealand | Nicaragua | Nigeria | Pakistan | Panama | Paraguay | Peru | Poland | Portugal | Philippines | Puerto Rico | Romania | Russia | Saudi Arabia | Singapore | Slovakia | Slovenia | South Africa | South Korea | Spain | Sri Lanka | St Lucia | St Vincent and Grenadines | Sweden | Switzerland French | Switzerland German | Taiwan | Thailand | Trinidad Tobago | Turks and Caicos Islands | UK | United Arab Emirates | United States | Uruguay | Venezuela
SETUPTYPE = Enterprise | Internet
MAILSERVER = Exchange | Lotus | GroupWise | None
REDIRECTOR = Desktop | Enterprise
USERS = AllUsers | CurrentUser
SHORTCUTSTARTUP = True | False
SHORTCUTDESKTOP = True | False
HANDHELDINSTALLERDIR = <path to optional handheld installers. Default is 'Device' dir on CD image>
UNINSTALLEXISTINGHANDHELDS = True | False
SUPPRESSREBOOT = True | False
URL = <path to optional URL to be launched at the end of a 'Blackberry Internet Service' installation>

I removed the settings that didn't apply to my install and left the appropriate option for those that did.

If you don't know how to get the raw setup files:
Run the zipped exe that you can download from blackberry.com and wait until the installer comes up and you can click "Next". Ignore that and open your temp directory (probably C:\documents and settings\%username%\local settings\temp). Copy everything from the WZSE0.TMP folder to another folder, then you can cancel the install. These are the install files.

I deployed the package with this command line: setup.exe /S /v/qn

I'm not sure if case matters, but that's what worked for me (capital s, lower case v and qn. Spacing seems to be the key factor for making this install work silently.

Package settings: Require drive letter, run whether a user is logged in or not.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

120
Command Line
Uninstall Blackberry Desktop Manager 3.6.0.43, 4.0.0.30, 4.1.0.8, 4.2, 4.2.2, 4.3 and Roxio Media Manager 9

'DM
MsiExec.Exe /x {5CDC6050-20F8-4D4D-8764-886ED7A05B03} /qn /norestart
'DM
MsiExec.Exe /x {556144BE-61D6-4B04-8776-B09454897E87} /qn /norestart
'DM
MsiExec.Exe /x {7F29BE4F-1651-4CFE-AF63-68825B90EE3B} /qn /norestart
'DM
MsiExec.Exe /x {D6D4F23F-75F9-4F3D-8D0F-2CD426B1B69D} /qn /norestart
'DM
MsiExec.Exe /x {0725C68F-FD3A-4476-BDA0-C002C7FE307C} /qn /norestart
'DM
MsiExec.Exe /x {DE7A46A8-D4DA-4EE0-AD6C-326049517BF2} /qn /norestart
'MM 9
MsiExec.Exe /x {66D171AA-670F-4309-9C74-5BA7F7DBA0B3} /qn /norestart
MsiExec.Exe /x {303379C9-8610-4CCF-AF37-C4BF8998C591} /qn /norestart
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • wond696
  • 11/21/2007  
  • Show Comments   ( 0 )

119
Note
A note to anyone looking to install this app silently~

Unlike in the past, rather than running setup.exe /r to create an answer file, add the following to the bottom of the setup.ini:

[INSTALL_OPTIONS]

COUNTRY = Canada

SETUPTYPE = Enterprise

REDIRECTOR = Enterprise

MAILSERVER = Exchange

USERS = AllUsers

SHORTCUTSTARTUP = True

SHORTCUTDESKTOP = True

And alter the values accordingly. Note that the kb article regarding this is WRONG in its syntax. Check the install.txt in the folder to see the correct options for each value.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Bladerun
  • 03/07/2005  
  • Show Comments   ( 0 )

119
Note

I've been having a lot of trouble with getting this silent install to work. I finally got a working batch with the following script: "setup.exe /s/v USEINI=setup.ini /qn" All the other options failed on me (MSI, ISS capture, etc). If you're having a problem with the installation, try this out.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • fozzi58
  • 05/07/2005  
  • Show Comments   ( 0 )

119
Note
HOWTO Perform a Full Silent Install of Blackberry Desktop Manager 4.x without any reboots

Edit setup.ini to add the following. (Customise to your needs based on readme.txt)

[INSTALL_OPTIONS]
COUNTRY=UNITED STATES
SETUPTYPE=Enterprise
MAILSERVER=Exchange
REDIRECTOR=Enterprise
USERS=AllUsers
SHORTCUTSTARTUP=False
SHORTCUTDESKTOP=True
SUPPRESSREBOOT=True

Edit BlackBerry Desktop Software.msi with Orca
Properties Table
INSTALLLEVEL=125
RIMSUPPRESSREBOOT=1

SR_MM\Roxio Media Manager.msi with Orca
CustomAction Table
Delete ForceSetupReboot Row

Run "BlackBerrySetup.exe /s" to install silently.

If you want to Install the Cert Sync feature but not Media Manager then edit BlackBerry Desktop Software.msi using Orca
Features Table
CertSync=110
Media_Manager=125
Properties Table
NSTALLLEVEL=110

This is the only method that successfully suppresses reboots.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • wond696
  • 11/21/2007  
  • Show Comments   ( 0 )

118
Note

I tired the above methods with little or no success. The application would install but not take in account the setup.ini parameters. I finally got the silent unattended installation working by using AdminStudio to edit the extracted msi and then creating a transform with the differences. Works like a dream.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • south9
  • 06/27/2005  
  • Show Comments   ( 0 )

118
Note
Deploying via Altiris, the installation works using "setup.exe /s/v USEINI=setup.ini /qn" as recommended by fozzi58, but the app won't launch for me. I've configured the setup.ini as recommended, yet it still no workie.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • jmoore
  • 08/24/2005  
  • Show Comments   ( 0 )

118
Note
Hi all,

I have been able to create an MST for BlackBerry Desktop Manager 4.1 with Wise and it installed fine on a comp where user is a Local Admin. But when tried to install on a restricted PC (where user just has user rights not Admin) i got all sorts of 1720 Install Errors...
After opening the MST up and poking around in Tables I found that two Actions in CustomActions tables where trying to write somewhere they didn't have rights for (As indicated by Install log). Those actions are RIM_InstallUserGuides and RIM_InstallOptionalITAdminFiles.

Also Installation was trying to reference a Documentation directory that was not there. If you go to Directory Table, you will find DOCUMENTATION directory entry that was also causing problems.
After getting rid of those, I was able to install the software on restricted PC but then got some other issues about not being able to register couple of DLL files upon completion of installation.

Did anybody have similar problems? Any comments are appreciated
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Hubasan
  • 10/20/2005  
  • Show Comments   ( 0 )

118
Note
I finally managed to get it working by doing the following:-

Putting all the above detailed parameters into the setup.ini file, but also amending the following line as shown.

[Startup]
CmdLine=/qn /l*v %TEMP%\BB_DM.log

Then running setup.exe /s works - note it has to be a lower case 's'!

This works when you use the 'INSTALLLEVEL' parameter to deploy the Handheld Manager only option as well, which is what I was trying to do - but subsequently discovered that Handheld Manager doesn't actually seem to do what it claims it should.... if anyone has any experience of that I wouldn't mind hearing from them!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • DRMcBean
  • 11/03/2005  
  • Show Comments   ( 0 )

117
Security
Hi,
I would add something to the Hubasan note about the deployment on a locked down environment. I was able to deploy BB 4.0 only creating a script to run the two MSI (ISScript9.Msi - BlackBerry Desktop Software.msi) instead of the Setup.exe. The main point is that running ISScript9.Msi you will install a DCOM component (see it with dcomcnfg.exe): InstallShield InstallDriver (GUID={9338AA50-B293-4CE9-B284-8A5E9E8FF901}) with the Identity set to "The Interactive user". In this case the component will not work if the logged in User has not administrator rights. As result the next BlackBerry Desktop Software.msi installation fails. To workaround that I used dcomperm.exe to change the DCOM setting from "The Interactive user" to "Launching User" before the BlackBerry Desktop Software.msi installation. Be careful: the BlackBerry Desktop Software.msi contains a merge module called InstallShieldScriptingEngine that installs the same DCOM component. You have to remove this module from the msi and run the installation via a transform. This resolves the Hubasan issue.
Auro
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • AR
  • 02/09/2006  
  • Show Comments   ( 0 )

117
Note

1. Change your setup.ini

The options for all settings you'll find in the install.txt file.

Put this section to the end.

[INSTALL_OPTIONS]

COUNTRY = Germany

SETUPTYPE = Enterprise

MAILSERVER = Exchange

REDIRECTOR = Enterprise

USERS = AllUsers

SHORTCUTSTARTUP = False

SHORTCUTDESKTOP = False

Change to the folder where the install files are stored and execute the following line.

setup.exe /s /l1031 /vINSTALLLEVEL=100

The options are:

/l<language ID>

US is default.

1031 German

1034 Spanish

1036 French

1040 Italian

/vINSTALLLEVEL=<X>

100 is default

1 BlackBerry Handheld Manager 1

100 BlackBerry Handheld Manager and BlackBerry Desktop Manager

125 BlackBerry Handheld Manager, BlackBerry Desktop Manager, and Certificate Synchronization

Further Option are in the KB Article:

http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/8021/728075/728944/728556/How_To_-_Perform_a_silent_installation_of_BlackBerry_Desktop_Manager_4.0?nodeid=788170&vernum=0

3. Logs

In the file %Temp%\BB_DM_WR.log you'll see if the options are working in the right way.

4. My environment

User has only "USER" rights.

Scrip was executed as Computer related Service with Netinstall.

It works fine!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • bwjudge
  • 09/08/2006  
  • Show Comments   ( 0 )

4
Note
Something that I have always found to work when wanting to automate MSIs wrapped in an executable is the following:
Start the setup process, but don't press Next when prompted at the first dialog.
If the install has a splash screen, hit the Windows key to bring up the start menu, otherwise, open explorer and navigate to your temp folder.
In the temp folder (ussually your profile) there will be a folder the the setup program uncompresses to that will contain the MSI and install files.
Copy those files off to another location for offline editing and then exit your install.

You can usually run the install from the files that you copied off. You can use that as your source and run normal windows installer command lines from there. This is what I did with the install for Blackberry 4.x without any problems. I was even able to create an MST for it.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • CondoPC
  • 08/26/2005  
  • Show Comments   ( 0 )

1
Command Line
If using the INSTALLLEVEL=<x> switch

1 = Blackberry Device Manager
100 = Blackberry Device Manager and Blackberry Desktop Manager
110 = Blackberry Device Manager, Blackberry Desktop Manager and Media Manager
125 = Blackberry Device Manager, Blackberry Desktop Manager, Media Manager and certificate Synchronization
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • jtsm
  • 03/30/2009  
  • Show Comments   ( 0 )

0
Note
I had quite a bit of difficulty getting the SETUP.INI to process STARTUPSHORTCUT=False. I looked in the installation log and the MSI processed the .ini, but was changing the value from 0 to 1 after it processed it.

I looked through the Custom Actions and found setSHORTCUT_Startup with a value of 1. I edited that CA and changed the value to 0 and saved the MSI. That fixed the problem without an entry in SETUP.INI. There were also other CAs for the rest of the usual entries in the .ini file.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • JMelton
  • 06/18/2009  
  • Show Comments   ( 0 )

Inventory Records (28)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

BlackBerry Desktop Software

Version

4.2.2.14

Uninstall String

MsiExec.exe /i{0725C68F-FD3A-4476-BDA0-C002C7FE307C} MsiExec.exe /i{CEAC229C-5264-4E63-BB52-95B7D1CC2C5A} MsiExec.exe /i{8B3D9881-8D0F-4E0A-884D-D7F8B1E1EE63} MsiExec.exe /i{9B449C1A-4F64-4ED4-8C96-31B222E8377F} MsiExec.exe /i{98605CAA-5F52-44EC-8AF7-2EC1

Questions & Answers (0)

Questions & Answers related to Research In Motion BlackBerry Desktop Software

Blogs (0)

Blog posts related to Research In Motion BlackBerry Desktop Software

Reviews (0)

Reviews related to Research In Motion BlackBerry Desktop Software

 
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