[cisco-voip] Unity/Exchange User Question
Turpin, Mark
mark.turpin at bryancave.com
Tue Aug 15 11:33:19 EDT 2006
You must have a SID on an account to get mail. The problem is when you
disable them - that SID goes away and mail bounces.
Easiest way to associate SELF as the external associated account and
give them mailbox access on the disabled account.
Here are some related articles...
http://www.msexchange.org/tutorials/Understanding-External-Associated-Ac
count-Windows-Server-2003-Exchange-2003.html
http://www.msexchange.org/articles/NoMAS-Tool.html
http://support.microsoft.com/default.aspx?scid=kb;en-us;319047
Once it has a SID, you can use the disabled account, hide it, and have
voicemail only accounts with no security risk.
Works like a champ...
-Mark
________________________________
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ed Leatherman
Sent: Tuesday, August 15, 2006 10:16 AM
To: Israel Lang
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unity/Exchange User Question
Israel,
We also have a large number of users who only have AD accounts for the
purposes of a Unity Voicemail-Only account. We ran into a lot of
problems at first with this, what we found we needed to do was set a
specific attribute on the accounts so that they would still function
correctly with Unity while disabled. I'm no AD expert but I can see if
our windows server admins have the relevant KB docs that they used to
figure it all out - it may be something specific to our particular
install though.
The exchange admin recently told me there was an exchange hotfix that he
installed that fixed this so we wouldnt have to change attributes on
accounts anymore, he's testing it now to see if it does work. That one
particularly was KB903158
Hope that helps, sorry i couldnt be more specific
Ed
On 8/15/06, Israel Lang <zephy316 at gmail.com > wrote:
We have a number of departments that use CM and Unity VM-Only for their
telephony needs. However, they are on their own domains and for all
intents and purposes networks sans their phones. We recently got audited
and one of the concerns was these departments that had accounts that
either had passwords that didn't expire, passwords that hadn't been
changed in a long time, and/or accounts that hadn't logged into the
system in months.
My question is how do others handle users that only need
exchange/network accounts only for the purpose of VM?
I have disabled some accounts in the past and have had mixed results at
best with the Unity Accounts working after doing so. Perhaps, I am just
not following the right procedure at all times to do this.
Any help would be greatly appreciated.
--
Have a great day!!!!!!!!!!
zephy316_gmail.com
Replace the _ with an @ symbol
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
Senior Voice Engineer
West Virginia University
Telecommunications and Network Operations
This electronic message is from a law firm. It may contain confidential or privileged information. If you received this transmission in error, please reply to the sender to advise of the error and delete this transmission and any attachments.
IRS Circular 230 Disclosure: To ensure compliance with requirements imposed by the IRS, we inform you that any U.S. federal tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties under the Internal Revenue Code or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060815/c335dd42/attachment.html
More information about the cisco-voip
mailing list