Last week we released Exchange Server 2010 Service Pack 1. It has received some great feedback and reviews from customers, experts, analysts, and the Exchange community.
The starting point for...
Updated Jul 01, 2019
Version 2.0
Blog Post
@Bharat; I completely understand, but you also need to understand what powerful medium you have here and that "you started this"; You (Exch-team) posted very important updates like SP1 is available, and you gave some updates to the initial post with 4-5 updates and corrections. Then what? I am left to be searching high and low in order to plan a migration onto the "unknown"?
In your table KB983440 is listed as required, in your footnote where you indicate changes, this one is not required (unless yes means no > See the table), then following the link to http://technet.microsoft.com/en-us/library/bb691354.aspx (pre reqs), this hotfix is still listed. This post was updated on 9/20, 5 days after this post tells us it’s not needed.
Another example of an upgrade issue is that OWA custom work gets lost unless you manually protect it. Sure, for those of us that has done this before, many times over, we learn and we take the extra steps to land the project solidly.
I want one single 10/6 “Exchange 2010 RTM Upgrade to SP1” step-by-step instructions like this one: http://technet.microsoft.com/en-us/library/bb629560.aspx but we need updates.
The environment at hand has a planned maintenance window very soon and with 6 hours at hand the plan is to upgrade the environment to Exchange 2010 sp1 from 2010 RTM. We have no fall back options as soon as we start touching the MBX servers and it is pretty scary to see the many issues listed with no or little guidance from the source.
I am on my way to bed now, probably dreaming about the empty GAL’s for the Outlook 2007 users I hear about, then I will wake up pondering about how to explain the to the Executive team that no-one is to be found in the GAL anymore and that the 120k users that was there yesterday just got scrubbed by SP1.
Before “I go”, I will commend the Exchange team from the bottom of my heart; Exchange 2010 is the best communication product I have ever seen, and the way it behaves when configured properly is simply amazing. Performance totally rocks and the various features we are growing fond of include both CAS Arrays and DAG groups. What used to be heavy loads on Exchange servers now is handled with such ease I find myself logging on to the CAS array (any protocol) to see if it is really responsive with 20k active connections on a single box.
In your table KB983440 is listed as required, in your footnote where you indicate changes, this one is not required (unless yes means no > See the table), then following the link to http://technet.microsoft.com/en-us/library/bb691354.aspx (pre reqs), this hotfix is still listed. This post was updated on 9/20, 5 days after this post tells us it’s not needed.
Another example of an upgrade issue is that OWA custom work gets lost unless you manually protect it. Sure, for those of us that has done this before, many times over, we learn and we take the extra steps to land the project solidly.
I want one single 10/6 “Exchange 2010 RTM Upgrade to SP1” step-by-step instructions like this one: http://technet.microsoft.com/en-us/library/bb629560.aspx but we need updates.
The environment at hand has a planned maintenance window very soon and with 6 hours at hand the plan is to upgrade the environment to Exchange 2010 sp1 from 2010 RTM. We have no fall back options as soon as we start touching the MBX servers and it is pretty scary to see the many issues listed with no or little guidance from the source.
I am on my way to bed now, probably dreaming about the empty GAL’s for the Outlook 2007 users I hear about, then I will wake up pondering about how to explain the to the Executive team that no-one is to be found in the GAL anymore and that the 120k users that was there yesterday just got scrubbed by SP1.
Before “I go”, I will commend the Exchange team from the bottom of my heart; Exchange 2010 is the best communication product I have ever seen, and the way it behaves when configured properly is simply amazing. Performance totally rocks and the various features we are growing fond of include both CAS Arrays and DAG groups. What used to be heavy loads on Exchange servers now is handled with such ease I find myself logging on to the CAS array (any protocol) to see if it is really responsive with 20k active connections on a single box.