[cisco-voip] Unity in a Windows 2008 R2 domain
Ed Leatherman
ealeatherman at gmail.com
Wed Mar 10 11:22:38 EST 2010
This came up on the list a bit ago, this was what I found out (copied
from previous post as it was buried a bit):
>
Unofficially, looks like this is what's causing the problem:
http://support.microsoft.com/default.aspx/kb/977180
Apparently applying the workaround in the KB article resolved the
problem, however the fix is still unsupported by TAC and there isn't a
likely official supported solution to this from Cisco until after
Unity 8 is released.
We're going to put our DC rollout on hold for a few weeks and possibly
build this scenario in a test environment ourselves and come to a
decision after that. Perhaps in the meantime Unity 8 will be out and
we will get a supported fix soon after.
>
I think basically if you call in for TAC support and the issue is
related in some way to running on an R2 domain, you're not getting any
sympathy from them. At least until some official fix comes out. There
have been a few people on the list that loaded R2 and didnt have any
particular problems.
On Wed, Mar 10, 2010 at 11:03 AM, Michael Thompson
<mthompson729 at gmail.com> wrote:
> A meeting with a customer led to a discussion about their AD structure.
> They have Unity 4.0.5 still in place and are going to move to Unity 7 or UC
> in the near future. The question on the AD structure brought out that they
> were in the midst of upgrading now. Even Unity 7 is not supported on a 2008
> R2 domain (only 2008 first release), though I can't get Cisco to tell me
> what specifically isn't supported.
>
> They've already upgraded their AD and the global catalog and most of the
> other servers in the cluster are already at 2008 R2. does anyone have any
> experience with what is 'broken' with 2008 R2, or what issues I can expect
> moving forward?
>
> any help is appreciated
> Mike
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
--
Ed Leatherman
More information about the cisco-voip
mailing list