So here's the plan, I got a BlackBerry Curve 8310 from work, which is hooked up to our corporate Exchange email. I want to hook it up to my personal Exchange 2007 Server running on a Server 2008 Hyper-V virtual machine at home. One super-easy way to do it is via POP3 or IMAP4. But this post covers how to do it like your company would, through the BlackBerry Enterprise Server. Please note, your BlackBerry can only be connected to one BES account at a time (as of July 2008), regardless of what you may have read elsewhere. I had to contact my company's helpdesk to re-connect my company email.
I've followed some good tutorials on how to do this, a BlackBerry Guide and a CrackBerry Guide, but I'm going to write down my exact steps anyway.
Change Your Corporate Email Message Service Display Name
Install the BlackBerry Desktop Software on your work machine with all the default installation choices. Run the manager, connect your BlackBerry, then choose:
Email Settings -> Advanced Tab -> Message Service Display Name -> "YourCompany".
Synchronize -> Synchronize Now.
Disconnect your BlackBerry, goto your mail, compose and new message and scroll to the top. In "Send Using" you should see your new display name.
Download BlackBerry Professional Software, aka, BlackBerry Enterprise Server Express
You can obtain a fully-functional copy of BES with a single Client Access License (CAL) for free. http://www.blackberry.com/select/professional/express.shtml
Create your BES Server
-
Create new BES Virtual Machine - I've configured a Windows Server 2003 R2 Standard x86 machine for the job. Updated and ready to go. I tried on a Server 2008 x64 virtual, and the software would install but at the very end of the installation, only the last two processes would start.
-
Add BES Server to Domain - This isn't necessary, but I like to manage my machines using my domain administrator account.
-
Create BESAdmin Mailbox and User Account
-
Open the Exchange Management Console on your Exchange server.
-
Recipient Configuration -> New Mailbox... -> New User named BESAdmin.
Add BESAdmin Domain Rights
-
Open the Exchange PowerShell on your Exchange server.
-
Enter this command:
add-exchangeadministrator "BESAdmin" –role ViewOnlyAdmin
-
Enter this command (replace MAIL_SERVER_NAME with your servers machine name and DOMAIN with your domain name if you're using one):
get-mailboxserver MAIL_SERVER_NAME | add-adpermission -user DOMAIN\BESAdmin -accessrights GenericRead, GenericWrite -extendedrights Send-As, Receive-As, ms-Exch-Store-Admin
Configure BESAdmin Domain Security Settings
-
On your Exchange Server, Start -> Administrative Tools -> Active Directory Users and Computers.
-
View -> Advanced Features.
-
Global Setting - To configure for all users, right-click your domain -> Properties.
Security Tab -> Advanced -> Add... -> BESAdmin
Apply to: Descendant User objects -> Allow Send as.
Individual Setting - Instead of configuring globally you can just choose the user who's mailbox will be connected to your BlackBerry:
User -> Properties -> Security Tab -> Add BESAdmin -> Allow Send as.
Temporarily Whitelist "blackberry.net" for Activation
-
On your Exchange Server, open PowerShell.
-
Execute this command:
Set-ContentFilterConfig –BypassedSenderDomains blackberry.net
-
Verify with:
get-ContentFilterConfig
-
Force a sync with Edge to be sure:
Start-EdgeSynchronization
Add BESAdmin as Local Administrator on BES Server Machine
-
On your BES Server, Right-click -> My Computer -> Manage.
-
Local Users and Groups -> Groups -> Administrators.
Add BESAdmin to Local Security Policy on BES Server Machine
-
On your BES Server, Start -> Administrative Tools -> Local Security Policy.
-
Security Settings -> Local Policies -> User Rights Assignment -> Allow log on locally.
-
Security Settings -> Local Policies -> User Rights Assignment -> Log on as a service.
Login as BESAdmin and Install BlackBerry Professional Software
-
On the 3rd or 4th installation screen you'll see a warning:
"The setup application could not verify the Microsoft Exchange permissions for the Microsoft Windows account. Before you continue, verify that the permissions are correct." That's fine, don't worry about it.
-
Install SQL Express locally.
-
Press Continue to reboot.
-
Leave the default database settings, click yes to create the database.
-
Enter your CAL and SRP information, you will have received this from BlackBerry with the link to download the software.
-
Enter your Exchange server name and click Check Name. It will validate it, then click OK.
-
Click Start Service. All services should start successfully. Click Finish.
Open BlackBerry Manager and Configure your User
-
Open BlackBerry Manager and you will receive a warning that "The MAPI Profile 'BlackBerryManager' does not exist." Click OK.
-
Enter your server name, again, Check Name, and click OK.
-
Your service status should be "Running" and your SRP Status should be "Connected".
-
Add New Users Wizard -> Select your user.
-
Choose the Default IT Policy. Next.
-
Deploy Devices Wirelessly. Done. An email will be sent to that user's mailbox.
Active BlackBerry Handheld Device
-
Obtain your password from the email in your user's mailbox.
-
On your BlackBerry choose Enterprise Activation or Options -> Advanced Options -> Enterprise Activation.
-
Enter your user's email address and password.
Troubleshooting
-
Activation times out, after about 30 minutes, with "Server is not responding".
Verify the BESAdmin Domain Rights were properly set by going to your BES Server:
Run -> cmd -> cd c:\program files\research in motion\blackberry enterprise server\utility\
IEMSTest.exe
Run the test for both choices against your user. If you see a failure, which I did in my case, then the domain rights weren't properly set. Revisit that step.
-
Policy Error, try wiping your BlackBerry. I also received this error, so the next time I tried activation I said Yes to wiping the BlackBerry. Activation was then successful, but now I've lost my work email account. I made a backup before doing all this, so I'll have to see if that restores things, otherwise I'll be sending it off to get it fixed. *** I just tried the restore, it did not restore my enterprise activation settings, I'll have to ask infrastructure to re-activate my phone.