[Webinar] Streamline your web hosting managementRegister Today


ESM 2003 on Server 2003 x64 Standard  - Required for BES 4.1.6 Installtion

Posted on 2010-03-29
Medium Priority
Last Modified: 2012-05-09

Wondering if this possible. I am trying to install/Move our BES 4.1.6 to a new server. BES requires ESM to be installed. Problem is the Exchange is 2003 which is not compatible on x64 so I have just found out. Is it possible to Install ESM 2007 management tools and for BES to work correctly?

I did find this link of someone trying to do the same thing but dont know the outcome:



Exchange Server: Exhchange 2003 SP2 (Windows 2003 x86)
BES Server: Windows 2003 x64, BES 4.1.6, SQL 2005 Express

Question by:ioko
  • 3
LVL 74

Expert Comment

by:Glen Knight
ID: 28977798
That's a very good question but I doubt anyone has tried it.

As the Exchange 2007 tools do not show any Exchange 2003 services/information I doubt it would work to be honest.

Author Comment

ID: 28979068
Its great that RIM have no problems saying BES 4.1.6 is supported on 2003 x64 but they dont say that ESM management tools for 2003 are not supported therefore BES wont run. Not much choice but to build and install on a new server.

Author Comment

ID: 28981321
If anyone else has any ideas how to get this to work if it possible please let me know
LVL 31

Expert Comment

ID: 28982787
How does it check? Have you looked in the install log file? maybe try add copy the exchsrvr and bin folder over to your BES server and put it in the PATH statement... maybe it is ony looking for the exchange dlls. CDO.dll normally lives in C:\windows\system32 though.

But to be honest, can BES address more than 4Gb of RAM? If I was you I'd rather be safe and re-install 32bit windows because your BES is going to be talking to 32bit Exchange anyway.

Later on when Exchange is upgraded to 2007/2010 then upgrade the BES to 64bit

Accepted Solution

ioko earned 0 total points
ID: 28984376
I think I may just have to move it to a new x86 bit VM. Also I could move back when the exchange is eventually upgraded. Reason I wanted on this x64 machine it runs core applications and is protected with Double take for windows and great for failing over when things go wrong.

I dont really want to mess the x64 bit machine up at the moment as its live and running core business applications.

Thanks all.

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You finally migrated Public Folders to Office 365, decommissioned the Public Folder mailbox database and since then, when you send an email from on-premise to mail-enabled Public Folders, you get the following error: "Misconfigured public folder mai…
Upgrading from older Exchange server to the latest Exchange server can be tiresome, error-prone and risky, without being a seasoned exchange server administrators. It can become even problematic if you're an organization that runs on tight timeline…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

590 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question