EDIT: This post was edited on 11/28/2007 to mention KB944752.
The update is live at:
http://www.microsoft.com/downloads/details.aspx?FamilyId=41EC35E7-79A0-4ECB-A644-1ECE94178F9D&displaylang=en...
Updated Jul 01, 2019
Version 2.0
Blog Post
Similar problems to rcon, Alex, K, and David here...
Environment Details:
OS is Windows Server 2003 R2 Enterprise x64 Edition with SP2 for all Exchange Servers and AD
Problems caused by UR5 so far (in order of importance):-
1 (David's issue?) - Entourage clients see 'not connected' after the update was applied to the CAS machines. It appears to be a problem with the /exchange virtual directory used by the Entourage DAV service. When I use Internet Explorer to explore to the exchangecas.fqdn/exchange URL, I am prompted for my username and password and then get 'HTTP/1.1 503 Service Unavailable'. OWA, AutoDiscover, and Outlook Anywhere work fine.
2 (K's issue) - I ran the update separately on each node of my CCR cluster. Each time after setup completed, it noted that it was restarting services and then finished setup. When I look in the Services MMC I see all Exchange Services disabled. I know most should be automatic and some should be manual, but I don't know exactly what the config should be for a CCR cluster member machine. Like K, this update took well over an hour. On the CCR machines I think it was closer to 2.5h, but I wasn't closely watching the clock. Can someone give me a list of which services should be automatic vs. manual on a CCR machine?
3 (rcon's issue) - Various machines in my environment are affected by the service start-up issue. My CAS machines are having this problem as well but I manually started each of the services that the Service Control Manager reported as having failed to start.
4 (Alex's Issue) - Many machines show no updates to Exchange in the Add/Remove Control Panel after UR5 is installed (even though UR4 was installed before I started). Installing UR5 again will cause all of the applied updates to display (UR2, UR4, etc.).
If PSS has already identified these issues, why can't I find KB articles about these issues?
I'm not going to complain about the quality of the update because I know how unique my environment may be and I also know the kind of limited resources the testing teams work with.
The only think I'm going to push on here is the PSS to KB follow through. I don't know what happened. Back in the Windows 9x days the MS KB was the ultimate resource for finding up-to-date and timely articles from PSS on all kinds of issues, even if just to say 'hey, we've seen this problem but have no idea what's going on yet...'. These were the 'stay tuned' sorta things. These were great cause they were a clear signal that I don't have to call PSS and open a support case on these issues cause someone's already working on it. Today the KB has become less relevant and less helpful to us in getting access to real troubleshooting information.
I liked those good old KB days when I could make some more informed decisions about applying updates based on the types of issues that MS is addressing. Now I need to rely on these blogs for someone to say ‘yes, actually, we know of this, this, and this, but we don’t have the answers yet…’, which is fine, but it just doesn’t feel as formal as before.
Anyway, help on these issues is all I’m really excited about at the moment. It’s Sunday night at 1:40AM and most of my users are on MACs and Entourage and are likely tucked into bed right now, but in about 4h they’ll be calling and I’ll be directing them to OWA until I can get this problem (issue 1) solved.
Environment Details:
OS is Windows Server 2003 R2 Enterprise x64 Edition with SP2 for all Exchange Servers and AD
Problems caused by UR5 so far (in order of importance):-
1 (David's issue?) - Entourage clients see 'not connected' after the update was applied to the CAS machines. It appears to be a problem with the /exchange virtual directory used by the Entourage DAV service. When I use Internet Explorer to explore to the exchangecas.fqdn/exchange URL, I am prompted for my username and password and then get 'HTTP/1.1 503 Service Unavailable'. OWA, AutoDiscover, and Outlook Anywhere work fine.
2 (K's issue) - I ran the update separately on each node of my CCR cluster. Each time after setup completed, it noted that it was restarting services and then finished setup. When I look in the Services MMC I see all Exchange Services disabled. I know most should be automatic and some should be manual, but I don't know exactly what the config should be for a CCR cluster member machine. Like K, this update took well over an hour. On the CCR machines I think it was closer to 2.5h, but I wasn't closely watching the clock. Can someone give me a list of which services should be automatic vs. manual on a CCR machine?
3 (rcon's issue) - Various machines in my environment are affected by the service start-up issue. My CAS machines are having this problem as well but I manually started each of the services that the Service Control Manager reported as having failed to start.
4 (Alex's Issue) - Many machines show no updates to Exchange in the Add/Remove Control Panel after UR5 is installed (even though UR4 was installed before I started). Installing UR5 again will cause all of the applied updates to display (UR2, UR4, etc.).
If PSS has already identified these issues, why can't I find KB articles about these issues?
I'm not going to complain about the quality of the update because I know how unique my environment may be and I also know the kind of limited resources the testing teams work with.
The only think I'm going to push on here is the PSS to KB follow through. I don't know what happened. Back in the Windows 9x days the MS KB was the ultimate resource for finding up-to-date and timely articles from PSS on all kinds of issues, even if just to say 'hey, we've seen this problem but have no idea what's going on yet...'. These were the 'stay tuned' sorta things. These were great cause they were a clear signal that I don't have to call PSS and open a support case on these issues cause someone's already working on it. Today the KB has become less relevant and less helpful to us in getting access to real troubleshooting information.
I liked those good old KB days when I could make some more informed decisions about applying updates based on the types of issues that MS is addressing. Now I need to rely on these blogs for someone to say ‘yes, actually, we know of this, this, and this, but we don’t have the answers yet…’, which is fine, but it just doesn’t feel as formal as before.
Anyway, help on these issues is all I’m really excited about at the moment. It’s Sunday night at 1:40AM and most of my users are on MACs and Entourage and are likely tucked into bed right now, but in about 4h they’ll be calling and I’ll be directing them to OWA until I can get this problem (issue 1) solved.