Hi All,

I have loaded up WebDesktop Manager for Domino.
Its running and users can connect their devices and do what they need to do.

The next phase is to allow users to upgrade their firmware via the portal vs loading the software on their desktops - however I can't seem to get this feature working.

I've added in the line to the bas-config.properties file:

DefaultHandheldSoftwareSharePath="\\\\<full_comput er_name>\\<path>" (with our own settings.)

I've downloaded all the latest firmware packages for our devices and placed them in the share where they are defined in the line above.

If I click on application loader section and begin the process of adding/removing applicatons - I'm not prompted to upgrade firmware of the plugged in blackberry.

Do I need to alter the Blackberry Manager in anyway?

Many thanks.


-PF

You do not need to do it that complicated. There is an easier method: KB04537

Thanks acnst,

We can perform firmware upgrades via BB desktop already however when the company has 160+ devices and spread across 5 different states in Australia - we dont really want people to have the desktop software. That's why the Web Desktop is so appealing.

-Pf

Same boat here. Not to mention I'm lazy when it comes to dealing with the EU (end user). The EU generally has no clue and needs to have the hand held while working on their handheld :/

ANyways, <endrant>, we are looking at deploying the WebDesktop utility, still weighing the benefits vs. cons. Anything that you've run into?

A couple of things.
1. Backup/Restore.

You have to click on the ADVANCED to invoke the backup/restore application.
Simply clicking the BACKUP or RESTORE buttons don't do anything.
No big deal.

2. Signatures
Users can update their signatures for their blackberry. It works for some, others it doesn't.
Not really fussed.

But the firmware updates is what we really want since the Pearl 8100 need updating frequently.

pfarmer,

Did you ever figure this out?

I'm testing the Web Desktop Mgr and am running into the very issue you are. I've followed "Installation and Administration Guide to the letter, and yet my test devices are not finding the source files, in which to upgrade the Device Software.

I've Googled and searched here and RIM's knowledge base, till my fingers bled

Have you guys verified your base.config file that the share is noted properly? If needed I'll edit my specific settings out and post it.

I have been using WDM to update devices with no issues, heck of alot easier then visiting the users desk.

Well, I solved my issue!

I had checked and rechecked my bas-config.properties file, however I decided to take another look.

I tried changing what the RIM doc told me to create -

DefaultHandheldSoftwareSharePath="\\\\<computer name>\\Program Files\\Common Files\\Research In Motion"

to

DefaultHandheldSoftwareSharePath="\\\\<computer name>\\Research In Motion"

The Research In Motion folder is shared. Bingo!

I thought the former was a bit odd, as the path they gave was more of an absolute path. I should have known better. DOH!

I'm having difficulty sharing out the app folder. I do software configurations however they are not currently assigned. I am not sure if just having software configurations would stop this service from functioning.

My current line:

DefaultHandheldSoftwareSharePath="\\\\servername\\ Research In Motion"

Typed exactly as above except the server name. I can type the address in IE and or Windows Explorer and it does in fact resolve and I can see the folder shares. Any ideas?

Ok...after much trouble....I have the Apps working....and it does infact work across domains (tested and verified....called RIM and requested a KB be created). To have multiple domain functionality.....replace the server name with the actual FQDN.

Cheers!!

Chris