BES Express was never sold- it's free, and still available. I have BES Express running at about 7 client sites, including my own company office (which yes- it's running on SBS). Guys- you have some real misconceptions about BES. For starters,yes- it's free, for the first device in your organization. After that, you need to buy CALs for each additional user/device, at a cost of about $100 each, up to the allowed max of 15 users. Beyond that number, you will need to purchase full-blown BES SBE, or BES for the enterprise. When orderingCALs for Express, you need to be sure to order the Small Bus Edition CALs, as the std. BES cals will not work.
BES can run on SBS, but IMO you should not. Too much interference and security issues between the BESAdmin account you must create, and local account permission requirements, which are not a good thing on SBS as it is your DC. You can do it, but it is a much more involved process than running it on a separate box.
But if you decide to, head over to blackberryforums.com and learn how to do it right, if you insist. I run it n my office, as I am the only BB user on the server, and my Exch. organization is small, as are my server requirements.
Not to fret though- BES Express can run on XP Pro- you do not need to purchase a server with a server OS. There really isn't a ton of overhead with it, and it will run happily on any decent P4 with a Gig of ram or better. Your problem with setting it up on anything when you use SBS is setting up the Exchange tools using the SBS media. You need stand-alone Exchange media to set this up, and your SBS media will not let you do this. There are ways around that too, as the biggest point in creating the Exch tools install is the creation of the MAPI profile, with Exch admin permissions carried over from your BESAdmin account settings. Not impossible, as you can accomplish this with install of Outlook 2003 from your SBS Client Apps, and setting the profile to the BESAdmin account.
You do not need to worry about setting up the MSDE instance from the command line- the install will create the instance for you- completely automated. No intervention necessary.
While it is true you should always manage the BES logged on as the BESAdmin account, you certainly can log onto it as any domain account you wish for other purposes. But when opening the BES Manager, or performing anything related to BES or BES setup, always only use the BESAdmin account. And these are services, not start-up items, so it is irrelevant whether you log onto it as BESAdmin after a reboot. If that's necessary on your setup- you did something wrong.
It's a great tool and brings a lot of simplification to the system admin for managing these devices, vs. having them run desktop redirectors, etc. Complete central control and administration- the users never need to plug the device into their desktops- ever. My only other suggestion is that it is much easier and quicker for you to set the devices up tethered to the BES server than over the air. OTA works, but takes a lot longer, and requires intervention from the user with the device. That can get a little flaky considering they've probably never touched one before, and you have to hand-hold them through the whole process. We always just make sure the device gets delivered to the client office instead of the end user, we provision it, and then ship the new toy out to the user all ready to go.
