After both myself and a business college (another company) spending hours trying to get BES wireless activation to work, I've found the solution


1. Make sure you have installed the hotfix 1 for service pack 3

If you're running small business server (SBS) 2000 or 2003, make the following registry change:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NetBT\Parameters\
Set the SMBDeviceEnabled registry entry to 1 (the default is 0).

http://www.blackberry.com/knowledgec...876&ve rnum=3

Just thought I'd post it for any other poor system admins who're given the task of installing it with no support from their provider.

Cheers!

-- DJ

Wireless activation has worked fine for me and I haven't touched the registry. What exactly does this do?

see the Microsoft Help and Support site and search for articles 318332 and 326927.


That is typically with problems with Agents starting, which if they don't - then yes wireless activations will never start... and no messsage flow. So probably a new BES I would imagine and no users could activate.

To elablorate, it is not a problem with the agents failing to spawn, the Agent(s) will start and run, but communication will fail between the different BES services thus creating the appearance of no message flow. When in fact the Agent is likely processing new mail, calendar events, etc (provided you have active users on the BES). from Exchange, the Agent has no way or forwarding the data to the dispatcher hence the appearance of no message flow.

DJ did you see an MAGT log created before implementing this key? I would tend to agree with T-Roy, as the BlackBerry KB also supports, so I think it would be helpful to know which answer is right.

Never had problems with activation...Lotus Domino Environment.