I have an SBS 2011 domain consisting of the main SBS server and a second Windows 2008 R2 server hosting BES Express. To this second server I have just added two roles: Active directory Domain Services and DNS. As a result a number of Blackberry services will now not start (Dispatcher, MDS Connection being two of them) which is not something I had expected. What's the best way of fixing this please?
Well, I *think* I have resolved this. Mea culpa, I made three changes at once so I'm not sure whether they are all necessary or only one (or two) of them is:
1) Added the BESAdmin user account to the Server Operators group. I did this because the Blackberry docs require a pre-installation task of allowing BESAdmin to log on locally. Prior to DCPROMO that was the case but when I looked at that setting after DCPROMO a) BESAdmin was missing and b) the Add button was greyed out. Consequently I added BESAdmin to one of the groups shown
2) As there is no such thing as a local administrator's group on a DC, I was unable to add BESAdmin to it (another of the pre-installation requirements). So, somewhat reluctantly, I added it to the built-in admin group
3) I changed the log-on credentials for SQL Server (BLACKBERRY) from NetworkService (which was not allowing the service to start) to the Local System account
Now, I am quite happy to accept that none of these changes is actually the right way of going about fixing the problem but at least I now having working Blackberrys again. Any elucidation gratefully received
Well, I *think* I have resolved this. Mea culpa, I made three changes at once so I'm not sure whether they are all necessary or only one (or two) of them is:
1) Added the BESAdmin user account to the Server Operators group. I did this because the Blackberry docs require a pre-installation task of allowing BESAdmin to log on locally. Prior to DCPROMO that was the case but when I looked at that setting after DCPROMO a) BESAdmin was missing and b) the Add button was greyed out. Consequently I added BESAdmin to one of the groups shown
the besadmin should be a normal domain user account.
2) As there is no such thing as a local administrator's group on a DC, I was unable to add BESAdmin to it (another of the pre-installation requirements). So, somewhat reluctantly, I added it to the built-in admin group
correct, the besadmin must be the member of the "administrators" group if it runs on a DC
3) I changed the log-on credentials for SQL Server (BLACKBERRY) from NetworkService (which was not allowing the service to start) to the Local System account
Now, I am quite happy to accept that none of these changes is actually the right way of going about fixing the problem but at least I now having working Blackberrys again. Any elucidation gratefully received
[QUOTE=nobody7290;1719731][COLOR="Navy"]Maybe, just rerun the installer again (under the besadmin account) if you still have problems.
also read this document: