How to Deploy Blackberry Drivers and Desktop Mgr
Not sure if this is posted(cause I can't find it) but I have figured out how to deploy bb device drivers for charging the blackberry and the desktop manager. In my case, this worked for 8210's I had to deploy along with the desktop manager v4.2.0. It might work with other versions.
8210 Drivers
- Download the drivers from your vendor's support site
- open your run command line
- drag the exe file to the command line or type in it's path followed by a space then "/a"
- follow the prompts and specify the path for extraction
- you now have a working and deployable msi for use with a GPO!
Desktop Manager
- Download the drivers from your vendor's support site
- Clean out your %username%\local settings\temp folder
- the self extracting zip file and stop when the language selector window appears
- browse to your temp folder
- locate a directory named wzse0.tmp and open it
- open your run command line and type the following:
"C:\documents and settings\%username%\Local Settings\Temp\WZSE0.TMP\_setup.exe" /a
- press enter
- ONLY FOLLOW THE STEPS OF THE SECOND SETUP WINDOW
- DO NOT CLOSE THE FIRST SETUP WINDOW UNTIL THE SETUP PROCESS FROM THE SECOND SETUP WINDOW IS COMPLETED
DONE!! You now have a package that is deployable via GPO!
8210 Drivers
- Download the drivers from your vendor's support site
- open your run command line
- drag the exe file to the command line or type in it's path followed by a space then "/a"
- follow the prompts and specify the path for extraction
- you now have a working and deployable msi for use with a GPO!
Desktop Manager
- Download the drivers from your vendor's support site
- Clean out your %username%\local settings\temp folder
- the self extracting zip file and stop when the language selector window appears
- browse to your temp folder
- locate a directory named wzse0.tmp and open it
- open your run command line and type the following:
"C:\documents and settings\%username%\Local Settings\Temp\WZSE0.TMP\_setup.exe" /a
- press enter
- ONLY FOLLOW THE STEPS OF THE SECOND SETUP WINDOW
- DO NOT CLOSE THE FIRST SETUP WINDOW UNTIL THE SETUP PROCESS FROM THE SECOND SETUP WINDOW IS COMPLETED
DONE!! You now have a package that is deployable via GPO!
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.