[cisco-voip] Windows 2k3 sp1

[Ryan Ratliff]

Ok did a little digging into the bug and the basic operation that broke 
in SP1 is a function called OpenSCManager.  This is what Unity uses to 
see if we have connectivity to the Exchange server and to verify that 
the Exchange services are indeed running.   SP1 denies this query 
because we are trying to get service status.   The quick and easy fix 
is to change it so Unity only checks to see if the server is alive.  
But what happens if the server is running but all Exchange services 
stopped (hint, nothing good)?

Fixing this will involve completely rewriting the way Unity polls 
Exchange and is very code intensive  So rather write some half-baked 
fix for 4.0(4) and slap it into an ES they decided to put it into 
4.0(5).  This gave them time (I assume) to heavily test this new 
mechanism for reliability and scalability (Unity polls Exchange a LOT).

The bug notes indicate that an ES for 4.0(4) may well be in the works, 
but with 4.0(5) out they may just want folks to upgrade.
Even with 4.0(5) there is a registry entry that allows you to go back 
to the "old" method of polling Exchange if necessary.   Please open a 
TAC case if you run into odd Mailstore issues with 4.0(5) and are not 
running Win2k3 SP1 on your Exchange server(s).

-Ryan
On Jun 1, 2005, at 1:20 PM, Voll, Scott wrote:

According to the bug.  4.0.5 still does NOT fix the problem it just gets
me one step closer. So when they do come out with a SR for 4.0.5 I can
load it.

But if I just put the UnityMsgStoreSvc account (the account the
AvMsgStoreMonitor service logs on as) in the local Administrators group
this should fix it( in either 4.0.4 or .5)?  Is this what the SR is
going to do?

Thanks

Scott

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Wednesday, June 01, 2005 4:57 AM
To: Voll, Scott
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Windows 2k3 sp1

The bug notes on CCO indicate the workaround if you are running 4.0(4)
as well as a detailed explanation of exactly what in SP1 breaks things.
   There won't be a fix in 4.0(4).

The short of it is that your UnityMsgStoreSvc in the local Admin group
on your Exchange server.

-Ryan
On May 31, 2005, at 5:26 PM, Voll, Scott wrote:


Is Cisco going to come up with a solution for 4.0.4 or is 4.0.5 the
solution?

If so, has anyone done the upgrade to 4.0.5?  was it painful?  Any
gotchas?

TIA

Scott

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Tuesday, May 31, 2005 2:03 PM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net; Voll, Scott
Subject: Re: [cisco-voip] Windows 2k3 sp1

CSCsa80702 is the bug ID.  Took me a min to find.

-Ryan
On May 31, 2005, at 5:00 PM, Ryan Ratliff wrote:

My bad, misread your email.

I actually hit a bug the other day with Win2k3 sp1.  Right now it
breaks things if installed on your Exchange servers.  I believe 4.0(5)
works fine but don't quote me on it :)

-Ryan
On May 31, 2005, at 4:55 PM, Voll, Scott wrote:

That seems to fix the issues with Exchange SP1.

I was referring to Windows 2003 sp1.

https://puck.nether.net/pipermail/cisco-voip/2005-April/004223.html

Is Exchange and windows 2003 SP1 the same issue?

I'm confused (doesn't take much).

Scott

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Tuesday, May 31, 2005 1:42 PM
To: Voll, Scott
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Windows 2k3 sp1

There's a new version of PW out on ciscounitytools.com to fix all the
issues that were found previously.  It should be working fine now.

-Ryan
On May 31, 2005, at 4:35 PM, Voll, Scott wrote:

What is the final word on SP1 for Windows 2003 servers running Exchange
2003 or Unity 4.0.4?

My Server guy would like to get it loaded on the exchange servers.

Thanks

Scott


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip