<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1515" name=GENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=095275104-11112005><FONT face=Arial
color=#0000ff size=2>I'd say a domain group policy caused this issue. I've
seen this sort of thing happen numerous times.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=095275104-11112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=095275104-11112005><FONT face=Arial
color=#0000ff size=2>My general recommendation is to put the Unity server and
it's accounts in an OU that does not inherit anything from the domain (gets left
alone essentially). This prevents various things from shutting the server
down, or causing other related account problems.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Schuett, Court
(MBNAP it)<BR><B>Sent:</B> Thursday, November 10, 2005 11:09 AM<BR><B>To:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> [cisco-voip] Unity
Integration<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005>Hello all,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005>Some set up. We have a centralized call manager
set up. All calls are handled in one primary location. We have a
distributed voice mail set up. At a remote office, we have a small unity
server connected to the site's primary exchange server. The Unity
users have a seperate login, but share a mailbox with their primary
login. (There was a reason for this, but it predates
me)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005>We've run into a problem where the AD and Exchange
guys are making changes to the network that are seriously affecting our
voicemail servers. The other day, there was a permissions problem on the
Exchange server and company-wide we couldn't send outbound email. To fix
this, the Exchange team rolled back security settings to a few days
prior. That fixed their problem, but it completely shut down our
voicemail. We're not entirely sure what happened, but the result was
that the Unity server could not communicate with the Exchange server. To
solve the problem, we took the Unity users out of their OU and put them in a
seperate OU then copied them back. I stopped and started the Unity
service and everything worked. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005>We would like to find a solution where the
Exchange/AD guys can't cause us problems, but we are still able to use Unified
Messaging. Is there a solution? The problem is that I'm not that
good with Windows or Exchange so I have a hard time understanding and
communicating my desires to the AD/Exchange guys. Anyone out there with
some more experience that could possibly help? We love UM, but are not
big fans of the headaches caused by depending on others for
security.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Verdana size=2><SPAN
class=488010217-10112005>Thanks!</SPAN></FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV>
<DIV align=left><FONT face="Comic Sans MS" size=4><STRONG><EM>Court
Schuett</EM></STRONG></FONT></DIV>
<DIV align=left><FONT face=Verdana size=2></FONT> </DIV>
<DIV align=left><FONT face=Verdana size=2>Millward Brown</FONT></DIV>
<DIV align=left><FONT face=Verdana size=2>Network Systems
Engineer</FONT></DIV>
<DIV align=left><FONT face=Verdana size=2>630-955-8983</FONT></DIV>
<DIV align=left><FONT face=Verdana size=2><A
href="mailto:court.schuett@us.millwardbrown.com">court.schuett@us.millwardbrown.com</A></FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT> </DIV><BR><BR>
<TABLE style="COLOR: black" bgColor=white>
<TBODY>
<TR>
<TD><BR><BR>==================================================== <BR>This email is confidential and intended solely for the use of the <BR>individual or organization to whom it is addressed. Any opinions or <BR>advice presented are solely those of the author and do not necessarily <BR>represent those of the Millward Brown Group of Companies. If you are <BR>not the intended recipient of this email, you should not copy, modify, <BR>distribute or take any action in reliance on it. If you have received <BR>this email in error please notify the sender and delete this email <BR>from your system. Although this email has been checked for viruses <BR> and other defects, no responsibility can be accepted for any loss or <BR>damage arising from its receipt or use. <BR>==================================================== <BR></TD></TR></TBODY></TABLE></BLOCKQUOTE></BODY></HTML>