• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1028
  • Last Modified:

Blackberry Enterprise Server 4.0 won't install on Windows 2003 Server in Terminal Server Application Server Mode

I'm trying to upgrade my BES server to 4.0 on a Windows 2003 Server box.  When you run setup, it runs in two parts - the first part upgrades the database (no problem), then the second part launches the MSI file to install the BES application.

When we do the second part (or just run that MSI file) I get an error message:
BlackBerry Enterprise Server does not support execution on a Terminal Server in Application Server mode.  Please refer to the BlackBerry Enterprise Server documentation for instructions on how to install the software remotely using Terminal Server in Remote Administration mofe.  Setup cannot continue and will now exit.

In Windows Server 2000 you could easily change modes by going to Add/Remove Windows components, not touching the checkmarks, and clicking next.  It would then re-recognize Terminal Server and give you a choice of which mode to run in... no such luck on 2003.  I guess it relies more on Remote Desktop than on Remote Administration mode of TS.

How can I either:
a. Get the BES program to upgrade
b. Get out of Application Server mode completely

In my case, I really don't need the Application Server mode and am not sure how it got in that mode so it's OK with me if we just get back to regular old Windows mode.  I tried using Add/Remove Windows components and unchecked Terminal Server but got a scary message that:
"This option removes Terminal Server from your computer.  Programs that you have installed while Terminal Server was installed will no longer work and will have to be reinstalled."
This stopped me from uninstalling the Terminal Server component as I really don't want to have to reinstall my other programs!
1 Solution
Uninstalling TSAM...or moving BES to another box are your only two options....if you uninstall, you only loose programs installed after the TSAM was activated.....that may be your easist way to go, depending on how many apps you installed.

Note that, given the RAM requirements of the BES, and of the Attachment Service, it's not a very good idea to have the BES on a box that is running other apps anyway....the only other things on ours are exchange itself and ScanMail.
tolenmayAuthor Commented:
In talking to RIM, I found that removing Terminal Services was the only way to allow installation.  The only addition I would give to your answer is that only programs which you're actually serving up as managed applications to the terminal services clients are affected.  Regular programs on the machine (including ones which we installed after TS) worked fine.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now