Code: Select all
ommodu -o besadmin/<scalixnode> -c +mboxadmin
BaldBoy wrote:Webdesktop - AD Integration yet to fix
Managing and binding of devices to users is beyond the scope of this writing. Nevertheless you should know that binding can be performed by an Administrator (using webconsole) or by users' themselves using Webdesktop (they have to be previously imported into BES using Webconsole).
However if your users authenticate using AD (which is by default in BES for Exchange) you'll find that they can not log in. The reason is this: BES AD connector looks for legacyExchangeDN attribute to be valued in AD for the authenticating user but if you do not have Exchange installed ... you do not have this attribute valued. Most likely, if you're reading this, you have Scalix, not Exchange.
I am working on it ... maybe a script populating proper attributes from Scalix's schema will do the trick.
nlindq wrote:As it turns out there was some wacky software conflict on the device, and after a factory wipe a wireless activation worked fine.
sbroeer wrote:Hi to all,
I followed step by step the post from BaldBoy and now I'm at the point where I have to enter the license information for BES. After i do that there comes up a window where I can see the sername and the mailboxname. But when I click on "Test Name" I get a message "Setup can't connect to the Microsoft Exchange Server".
Instead of the name I also tried the ip-adress of our scalix-server, but it's the same. The ip-adress and name of our scalix can be resolved via ping.
Has anybody an idea where our problem is ???
Users browsing this forum: No registered users and 1 guest