Messages

1

MiVoice Office 250/Mitel 5000 / Re: Mitel 5000 Email Sync - Enhanced Integration User Accounts & Passwords

« on: April 10, 2014, 03:02:38 PM »

Ok, I tested it and unfortunately it doesn't work.

I setup an AD account named "miteladmin" with a very strong password and granted it full rights to my mailbox in exchange. I then changed my mailbox in the 5000 to enhanced integration, entered the miteladmin username and password, but left my email.

I received the 'welcome to email synchronization' email from the controller which was promising, but the voicemails don't forward.

In hindsight, the controller is obviously using the username to open the mailbox like one would when logging into OWA and so this idea would never work. It's a shame that this is the case, as it means we will be leaving our org on forward & copy instead.

Way back when I was running an Exchange 2000 environment we ran BES (Blackberry Enterprise Server) against it, and it used the scheme I proposed in my original post. You would create a BESAdmin account, grant it rights across the exchange org, and then it would handle message administration across all the users. I believe it still works that way (although I've been lucky enough to not have to touch a blackberry in years.)  I was hoping for a similar scheme within the Mitel environment, but it looks like today isn't my day for it.


Thanks for everyone's input regardless, it is appreciated.

2

MiVoice Office 250/Mitel 5000 / Mitel 5000 Email Sync - Enhanced Integration User Accounts & Passwords

« on: April 10, 2014, 01:25:10 PM »

We currently have our 5000 email sync set to "forward & copy" but would like to change this to enhanced integration to take advantage of removing messages from the phone when we delete them from email and vice-versa. We are running Exchange 2010.

My question:
Can I setup an active directory account named say "MitelAdmin" and grant it full mailbox permissions in exchange, and use that username and password in each user's mailbox (but their email of course)?

It seems the default method is entering the user's username and password manually into the db programmer for each user. We enforce a strong password policy here and our users change their passwords frequently.

I would prefer to #1 - not know the user's passwords, and #2- to not have to manually change user's passwords in the db programmer everytime they change passwords.

What's the best practice on this? How are you guys doing it? I can't imagine an organization with hundreds of users entering and maintaining these passwords manually.

Thanks