ArchieDean
MIS
How anyone done this in their environment? If so, I’m looking for the software so do this. I have what I think is the correct documentation.
Thanks
AD
Thanks
AD
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Deploying Blackberry Silent installs
- Thread starter ArchieDean
- Start date
- Status
I created the silent install pkg for DM and pushed it out with a script to all users in the "Blackberry" group.
I used a scripting engine called kixtart which is free. In the script I checked each desktop for a certain file which was particular to v3.6, if the file did not exist, the software was installed.
The technical advisory from RIM states that you can create a directory for all the different handheld software that's deployed in your enterprise and the install program will find the right s/w and install it. However, in testing I found this process to be far too slow.
I pushed out the standardized DM install, but unfortunately had to touch all users to install Handheld s/w.
I would like to find a better method for the next major upgrade to 4.0.
Maybe my company will invest in SMS or something similar.
I used a scripting engine called kixtart which is free. In the script I checked each desktop for a certain file which was particular to v3.6, if the file did not exist, the software was installed.
The technical advisory from RIM states that you can create a directory for all the different handheld software that's deployed in your enterprise and the install program will find the right s/w and install it. However, in testing I found this process to be far too slow.
I pushed out the standardized DM install, but unfortunately had to touch all users to install Handheld s/w.
I would like to find a better method for the next major upgrade to 4.0.
Maybe my company will invest in SMS or something similar.
- Thread starter
- #4
ArchieDean
MIS
Yes I do have SMS. With SMS is it possible to push out the handheld software too?
StevePruitt
IS-IT--Management
We haven't succeeded in creating an MSI package of the BB software, so I created the iss and xml files plus a batch file that runs the silent install. Packaged it all as a self-extracting zip exe file and made it available through our intranet. That has worked well.
NT4 systems need to run one other batch file first that fixes a DLL registration problem. It copies and registers a file based on a MSKB fix.
Steve
NT4 systems need to run one other batch file first that fixes a DLL registration problem. It copies and registers a file based on a MSKB fix.
Steve
ArchieDean, with SMS you can even go one step further - define specific user groups according to OS, need or even departmental policies. You get to pick a specific "collections" which will receive the Desktop Manager "packages" as you define them.
SMS can push any package out to its site clients, as long as you prepare the package using the SMS Installer or the MSI packager in SMS 2003. You can even let the last option record the installation process of an application to "learn" how to make its own package.
I'm simplifying the process greatly here, but SMS 2003 is the way I will deploy, maintain and update the Desktop Manager across our WAN.
SMS can push any package out to its site clients, as long as you prepare the package using the SMS Installer or the MSI packager in SMS 2003. You can even let the last option record the installation process of an application to "learn" how to make its own package.
I'm simplifying the process greatly here, but SMS 2003 is the way I will deploy, maintain and update the Desktop Manager across our WAN.
- Status
Similar threads