Exchange server 2007 Service Pack problems SBS 2008

I am Running Exchange server 2007 on Small Business server 2008 (SBS 2008). I tried to install SP2 but it fails both windows update and manually. Can anyone first advise me what version I'm currently running?
Help / about form Exchange Management Console displays:
Version 08.01.0436.000
And running repair on Exchange server from programs and features displays 2007 SP1 setup. So I believe SP2 to be next I have also ran SP3 but this fails.
Here is the end lines from a log:
[03/05/2014 08:54:13] [0] Setup will run the task 'uninstall-msipackage'
[03/05/2014 08:54:13] [1] Setup launched task 'uninstall-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode '24b2c164-de66-44fe-b468-a46d9d5e6b31' -PropertyValues 'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU''
[03/05/2014 08:54:13] [1] Beginning processing.
[03/05/2014 08:54:13] [1] Property 'PackageName' is 'EXCHANGESERVER.msi'.
[03/05/2014 08:54:13] [1] Removing MSI package with code '24b2c164-de66-44fe-b468-a46d9d5e6b31'.
[03/05/2014 09:09:01] [1] [ERROR] Unexpected Error
[03/05/2014 09:09:01] [1] [ERROR] Unable to remove product with code 24b2c164-de66-44fe-b468-a46d9d5e6b31. Fatal error during installation. Error code is 1603. Last error reported by the .msi package is 'Could not open key: UNKNOWN\Components\7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613.
Verify that you have sufficient access to that key, or contact your support personnel. '.
[03/05/2014 09:09:01] [1] [ERROR] Fatal error during installation
[03/05/2014 09:09:01] [1] Ending processing.
[07/05/2014 19:45:17] [0] End of Setup
There is a registry key to match this and The administrator account used for setup has access to it i believe??? What does this log mean?

Hi,
This error indicated that your account missed registry permissions on: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\ 7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613
Please check whether you have permission. You can also check whether the key have permissions inherited from the Parent Key or not.
After changing the permission, please run the setup again.
Best Regards.

Similar Messages

Is there a way to sync Pre-MS Exchange Server 2007 (Service Pack 1) Calendar?

Hello all,
I think my company must be using Pre-Microsoft Exchange Server 2007 with Service Pack 1 for our exchange server, because
I can only set up company Exchange account on MS Entourage, not the new Outlook
I can only set up the same exchange account only on iPad and iPhone (able to view in Mail, Calendar, Contacts & Reminders)
But
I am unable to use Lion's Mail, iCal and Address Book to see my Exchange account
For the moment, I am not really concern about mail and addresses,
but can I see my Exchange calendar on my desktop iCal? How do I set it up?
I guess the most obvious and straight forward way, for now, is to view on my iPad :-) But it is really funny that the iDevices are backward compatible but yet Lion OS cannot...
Thanks and cheers.

Hi,
Yes it will work, it says enterprise because it works there as well.
Thanks
Bifocals
Click Accept as Solution for posts that have solved your issue(s)!
Be sure to click Like! for those who have helped you.
Install BlackBerry Protect it's a free application designed to help find your lost BlackBerry smartphone, and keep the information on it secure.

Any known issue reported for "Rollup 8 for Exchange Server 2010 Service Pack 2"

Hello,
Currently our servers are running with "Exchange 2010 SP2 RU7", we are planning to update the Rollup version to RU8 for SP2.
Is there any knows issues reported for "Rollup 8 for Exchange Server 2010 Service Pack 2" till now ? is it safe to update the RU8 ?
http://www.microsoft.com/en-us/download/details.aspx?id=41394

(1) I had to roll it back:
The rollup released Tuesday the 9th caused random problems with systems ranging from general slow down to operation failed errors. It didn’t impact everyone at once and seemed to take 48hrs for everyone to have a problem. Rolling
back the update and rebooting the server seemed to resolve the issue.
Issues reported before the general mailflow stopping for everyone:
Nothing major … an occasional operation failed when I hit send but, it will go thru after I hit the send button a couple of times.
A MICROSOFT OUTLOOK BOX APPEARS WITH A TRIANGLE WITH A ! INSIDE IT. THE MESSAGE SAYS THE OPERATION FAILED.
(2)
ANOTHER CODE APPEARED WHEN I TRIED TO SEND THIS E-MAIL SO I CLOSED OUTLOOK AND RE-STARTED OUTLOOK. THE MESSAGE READ, CANNOT CREATE THE E-MAIL MESSAGE BECAUSE A DATA FILE TO SEND AND RECEIVE MESSAGE CANNOT BE FOUND. CHECK YOUR SETTINGS IN THIS MICROSOFT
OUTLOOK PROFILE. IN MICROSOFT WINDOWS, CLICK CONTROL PANEL.CLICK USER ACCOUNTS AND THEN CLICK MAIL. CLICK SHOW PROFILE, AND THEN CLICK PROPERTIES.
When he tries to open an e-mail, he gets an error message.
If he tries to mark an e-mail unread, he gets a different message.
Thanks Ben

Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

Hi,
After upgrading to Exchange Server 2013 service pack 1, we are unable to connect via Outlook 2010 or Outlook 2013. Outlook Web Access is working fine though. We have followed all the instructions, and have applied Outlook upgrades, but the issue remain the
same. Outlook was working fine before the upgrade.
Have we missed out something. I would highly appreciate if someone can help out? I'm not sure if this is the known issue as I can't seem to find anything on the internet.
Already applied the transport fix.
Thanks in advance!

Hi,
According to your description, your Outlook 2010 and Outlook 2013 come across the connectivity issue.
To narrow down the issue, I’d like to recommend the following troubleshooting:
1. Check if the issue happens on all Outlook users
2. Check the Outlook Anywhere connectivity by using ExRCA:
https://testconnectivity.microsoft.com/
Additionally, MAPI over HTTP is only supported when you use Outlook 2013 sp1 and Exchange 2013 sp1 at the same time. Since the issue also happens on Outlook 2010 client, we can firstly try the above troubleshooting.
If you have any question , please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Performing Exchange Server patching & service pack for mailbox server without losing some data during the rollback ?

People,
I'd like to know how can I safely apply the Exchange Server service pack or cumulative update to the Mailbox Server role (no DAG) without losing some email during the downtime and rolling back the snapshot ?
Can I do the following:
1. Stop all of the Exchange Server services.
2. Disconnect the vNIC in Mailbox server
3. Take VM snapshot
4. Apply the Exchange Server service Pack / Cumulative Update or Windows Update
5. Reboot
6. Reconnect the vNIC, if the server back online again with no issue, commit / delete the snapshot, if not, then disconnect the vNIC followed by roll back.
would that be make sense or supported from both Vmware and Microsoft http://www.vmware.com/files/pdf/exchange-2010-on-vmware-support-and-licensing-guide.pdf ?
If yu have any other suggestion, please let me know here.
Thanks in advance.

Hey AlbertWT,
I'll start off by saying that I wouldn't do it. Microsoft is explicit that snapshots are not supported with Exchange when virtualized. See below (from Exchange 2013 virtualization: Exchange 2013 Help):
Some hypervisors include features for taking snapshots of virtual machines. Virtual machine snapshots capture the state of a virtual machine while it's running. This feature enables you to take multiple snapshots of a virtual machine and then revert the virtual machine to any of the previous states by applying a snapshot to the virtual machine. However, virtual machine snapshots aren't application aware, and using them can have unintended and unexpected consequences for a server application that maintains state data, such as Exchange. As a result, making virtual machine snapshots of an Exchange guest virtual machine isn't supported.
Even if we ignore the support statement on snapshots this is still not a good idea. Here are some things to consider.
1) Cumulative updates for Exchange make changes to the Active Directory Schema. Rolling back the snapshot on the Mailbox server will not roll back the changes to AD, which could cause functional and supportability issues. See this link to give you an idea of how there are AD schema updates in every Exchange CU and service pack: Exchange 2013 Active Directory schema changes: Exchange 2013 Help
2) It is possible for email to come in during the time that you're testing the update, and if you need to roll back you would need a plan to get that email back. Third party services could work, or you could prevent email from coming into your environment completely during that time, but those are not ideal solutions.
A far better solution would be to create a lab environment that is isolated from production. You could either take clones of your Exchange and AD VMs and put them into a network fenced environment, or create a lab and import your AD structure so it matches production. I think this is a far better way to test than trying to rely on snapshots in production.
Hope that helps!
Matt

Exchange Server 2007 : Attachment Size Problem

Dear Support Team,
My company has used Exchange Server 2007, Our Attachment policy is limit 10 MB. Our user send the attachment size 7 MB to Company B that it's the same policy.
But user in company B cannot received attachment, it's exceed.
I check EventID in my site.
- Received is 7 MB
- Transfer is more than 10 MB
Why? Please help to clarify and suggest how do I set the new policy.
Thanks in advance.

Hi MasterBird,
It is hard to say how ??% per attachment increased, it's according to the encapsulation.
I have tested on my real Outlook, (47KB->51KB), (535KB->539KB), (575KB->579KB).
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

SBS 2011 - Update Rollup 6 for Exchange Server 2010 Service Pack 2

I wonder if I have to install this rollup, since the server is already up-to-date using Windows Update? The KB article (http://support.microsoft.com/kb/2746164/en-us) doesn't mention that.
In this article, under 'Prerequisites' it says you have to "remove all interim updates". What updates are they?
Simon

Firstly, I will do an introduction of interim update.
An interim update is a fix that resolves a problem that is considered critical to the functioning of Exchange. It is built specially for a particular service pack and Rollup. This means internally there could be loads of interim updates for a particular fix.
If you have multiple problems on a server that requires interim builds, you cannot just add a second interim build. You can only install one interim update per server. You have to get a combined interim build that included both fixes. Currently MS supports
up to 3 fixes in a combined IU. The good news is that interim builds can be seen in Add/Remove in the control panel so you do not end up checking file versions.
See more details in the following link: http://blogs.technet.com/b/mlines/archive/2008/12/30/interim-updates.aspx
That is to say, the interim update is different from Exchange Rollups
You don't have to unstall anything to apply this Roll Up. Rollup Updates are always important and should be applied. If you are running SP2 for exchange 2010 and if their a rollup available to install for exchange , my suggestion woiuld be to install as it
will keep your exchange server upto date.

Update Rollup 7 for Exchange Server 2010 Service Pack 3 (KB2961522)

This rollups will not install and has caused multiple issues on the Windows SBS 2011.
The issues are as follows:
All Exchange and related services were stopped and had to be manually restarted.
The update fails for multiple reasons, changes every time.
I am no longer able to perform ANY updates without some sort of error code.
All Domain client computers now report Security Status as Critical, Servers as not available.
DNS does not appear to be properly, many internet requests from domain PC's stop with "Fix connection problems" error page.
Running BPA shows no major issues
I can no longer run the WSUS server cleanup. I get a Connection Error and have to reset the node, but it soon fails again.
Shared folders may take quite a bit of time to open.
Any help would be greatly appreciated. I do have an open ticket with Microsoft and although this is rated critical I am not getting any resolution. The only thing that MS support managed to do was bring the server down for an additional day and corrupt my
EDB files so that they had to be rebuilt.

Hi,
à
All Exchange and related services were stopped and had to be manually restarted.
While the update was installed, it will automatically stop Exchange and IIS services. You may need to restart
manually.
àThe update fails
for multiple reasons, changes every time.
à
I am no longer able to perform ANY updates without some sort of error code.
Would you please let me know any of those
update-failed reasons? Meanwhile, please let me know some error code that you can get when can’t perform updates. Meanwhile, please refer to installation suggestions and tips in following article when install this update rollup.
Exchange
2010 SP3 Update Rollup 7 released and installation tips
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
àAll Domain client
computers now report Security Status as Critical, Servers as not available.
àDNS does not
appear to be properly, many internet requests from domain PC's stop with "Fix connection problems" error page.
Please check if ping the SBS server successfully from the problematic client computer via server name and ip
address. In the SBS 2011, can you access
internet successfully? In addition, please select a client computer as a test machine, re-join it to the SBS network, then check if Security Status still report as Critical. Please also run Fix my network wizard in SBS console. Any find?
Meanwhile, please refer to following article and check if can help you to
repair Windows Server Update Services.
Repair Windows Server Update Services
By the way, did you have a good backup for the server?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

A list of files changed for Update Rollup 4 for Exchange Server 2010 Service Pack 3

Hi.
Is there a list of files changed for Rollup 4?
After our RollUp installation, some files in the BIN directory still has the date of 2/5/2013 (SP3, no RollUp4), some has the date of 6/13/2013 (RollUp4)
Despite RollUp4 looks like to have been installed, Exchange Server still reports it's running "Version 14.3 (Build 123.4)"
Thanks...

Hi,
After you install an update rollup for Exchange 2010, the version of Exchange Server isn't updated to show that the update rollup is installed. This issue occurs because the version number that is displayed by the Exchange Management Console or by other
administrative mechanisms is obtained from the Exchange Server Object in Active Directory.
If you want to get the latest version of Exchange server, the article Andy provided is a good way.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange Server 2007 shows email as "Receive" but not "Deliver"

Hi Guys
We have Exchange Server 2007 inside of a SBS 2008 set up.
One specific email from a regular sender wasn't received by the recipient. The recipient is used to receiving messages from this sender and the email is not hiding within Outlook.
Exchange 2007 mail tracker shows the email was received, but that's it. Nothing has happened to the email after that. Normally we'd see a "Deliver" report, or possibly a "Fail", but always something to show the email has been actioned
in some way.
The queues are all empty.
So, this one email has disappeared into the ether of Exchange! So far as I can see, this is the only email with only a "Receive" notification. All others have something else immediately following the Receive.
The Server has GFI anti-spam installed, but that hasn't seen the email either, because emails are collected by Exchange before being passed to GFI. In this instance it hasn't been passed, or returned to the sender as undeliverable. It just seems
to have been eaten.
Would anyone have any sensible suggestions on where to start kicking this email back into life?

Hi Simon
Apologies for the late response, but I only get to this client once a month.
1. Did the sender get NDR? ~ No
2. Let the receiver check the email via OWA and see
whether the email is available. ~ Still not available
3. Use MFCMAPI to check the user mailbox, can you
find the missing email? ~ I haven't yet worked out what is MFCMAPI or how to use it to check, but I suspect that as the Exchange email tracker doesn't have any actions after "Receive" that it cannot have sent the email on to the user's mailbox or rejected
the email as non-deliverable.
The client isn't too willing to expend too much effort
/ cost on this issue which does appear to be a one-off glitch, but I am interested in resolving it for myself as I haven't heard of this problem before.
Thanks for the interest,
Michael D

Hidden Contact Subfolders are visible on iPhone after sync with Exchange Server 2007

Hello,
We have encountered an issue where synchronizing the iPhone with Contacts from an Exchange Server 2007 mailbox, causes hidden contact subfolders (from Outlook) to be visible and appear in the Groups list in the Contacts App on the iPhone. This does not occur with Exchange Server 2010 mailboxes.
We have a 3rd party application that creates hidden subfolders in the default Contacts folder on Exchange Server 2007 mailboxes. The hidden folders do not display in the Outlook client, Blackberry or on an Android phone. We did see that they were showing up in Outlook Web Access until we applied this Microsoft Exchange Server 2007 Service Pack 3 Rollup 2 patch unto the Exchange server:
http://support.microsoft.com/kb/2210042 - A sub contact folder is still visible after you set the "PR_ATTR_HIDDEN" attribute to "True" in an Exchange Server 2007 environment.
After the patch was applied, the hidden contacts do not show up anywhere else. However, when we synced the mailbox to an iPhone and synced existing contacts, all of the hidden folders appear in the Contact Groups list. Is there a way to hide the hidden sub contact folders on the iPhone and prevent them from appearing in the Contact Group lists?
Any help provided would be most appreciated.
Thanks and Best Regards

Hi SBuchan,
I have an open case with Microsoft about it. It is an issue with ActiveSync in Exchange 2007 that sends the hidden objects. Microsoft tried to resolve this in Exchange 2010 by sending a delete message after sending the hidden objects to remove them from the device. Am awaiting to see if they will approve a design change to Exchange 2007 ActiveSync to prevent the synching of hidden objects.

Exchange server 2007 still on version 8.1 even after applying sp3

hello,
I have exchange 2007 version 8.1 and I want to migrate to exchange 2013, so in order to to that I need to upgrade the exchange 2007 to sp3.
I install the sp3 without any issue but the version of the exchange 2007 still 8.1, I try to re install but it show that the sp3 already installed.
any idea about this issue?
thank you

Hi
As is well known, you
must patch Exchange 2007 to the very latest Service Pack and Update Rollup before you attempt to do anything with Exchange 2013.
According to your description, I suggest you should check the rangeUpper value by using ADSI Edit . If the value was 14625. This indicates
your schema is at Exchange 2007 SP3.
Here is the article for your reference: https://supertekboy.com/2014/05/01/check-exchange-schema-objects-adsi-edit/
Also you could re-install the patches in the following links .
Please download and install these patches from here:
Exchange Server 2007 Service Pack 3: https://www.microsoft.com/en-gb/download/details.aspx?id=24111
Exchange Server 2007 SP3 Update Rollup 10 : https://www.microsoft.com/en-us/download/details.aspx?id=36708
Hope it’s helpful to you .
Best Regards,
David

Exchange server 2007 SP3

Dear all,
Presently we are using exchange server 2007 Sp3 along with windows 2008 x64 Domain controller it's working fine . But we have some issue related with
Message Size restriction when I changed maximum msg size sent and receive this option will applied to the mail box user taking long time how can i update this option immediately to the end users ?
Best Regards
Subash

Hi,
After you configure the mailbox size restriction for a mailbox, the configured limits are enforced after a period of time, but do not take effect immediately. Restarting the Microsoft Exchange Information Store service causes the configured limits to take
effect immediately.
Please restart the Microsoft Exchange Information Store service to check result.
Here is a related article about this issue for your reference.
http://technet.microsoft.com/en-us/library/bb684892(v=exchg.80).aspx
Best regards,
Belinda Ma
TechNet Community Support

Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
failure. I have always felt nervous with SBS because it only runs on a single server.
My plan is:
Install Windows Server 2012 Standard on a new server machine
Join that new server to the existing SBS domain and sync the users, etc.
Install Exchange Server 2013 on the new 2012 Server
Migrate the existing Exchange data and account info to the new server
Demote the SBS Server and promote the new server to primary DC
Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
services)
Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
Thanks,
Colin
Colin

Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
Constraints/objectives:
None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
maintenance.
Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
want to keep all IT tasks as simple as possible.
We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
New Plan:
Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
(or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
it there. In any case, do NOT install Exchange directly on either DC.
Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
Thanks so much for all your help,
Colin

Compatibility between Exchange 2007 service packs

Hi all, I have 5 servers Exchange:
- 3 Servers CAS and HUB
- 2 Servers Mailbox server in Microsoft Failover Cluster (MSCS)
Domain Controllers are all
Windows Server 2003 SP2
The versions of Exchange 2007 SP1 servers are all:
8.1 Build 240.6
I have thought about installing SP3 and RU13 in all 5 servers for Exchange, but I'm going to install SP3 and RU13 on 2 servers CAS / HUB and the following week at the other CAS / HUB server.
Finally, the following week in the two Mailbox Servers.
Is there any problem if I miss 2 servers CAS / HUB with SP3 RU13 and the other CAS / HUB in SP1, this will only be for a few days?
Is there any problem if I leave the servidors Mailbox Servers in SP1 while CAS / HUB are in SP3 RU13, this will only be for a few days?
regards
Microsoft Certified IT Professional Server Administrator

Hi Yupikaiey.
Only thing you should be concerned is if you have CAS-CAS proxy or the Mailbox Cluster part.
Your current plan looks good. Just stay alert for any uncommon issues popping up, which would normally mean due to the difference.
If you upgrade your servers in this order, you may avoid potential service interruptions.
Details below:
Version Constrains are more of between roles of 2007-2010-2013 and not between same version SPs or RUs.
Exchange 2013 Server Role Architecture
The Past: Exchange 2007 and Exchange 2010
Our goal was to make these server roles autonomous units. Unfortunately, that goal did not materialize in either Exchange 2007 or Exchange 2010. The server roles were tightly coupled along four key dimensions:
2.This also necessitated a tight versioning alignment – a down-level Hub Transport or Client Access shouldn’t communicate with a higher version Mailbox server; in some cases this was enforced (e.g., Exchange 2007 Hub Transport servers cannot deliver messages
to Exchange 2010 Mailbox servers), but in other cases they were not (e.g., an Exchange 2010 SP1 Client Access server can render data from an Exchange 2010 SP2 Mailbox server).
The versioning restriction also meant that you could not simply upgrade a single server role to take advantage of new functionality – you had to upgrade all of them.
The Present: Exchange Server 2013
If I upgrade the Mailbox server with a service pack or cumulative update, then for a given mailbox hosted on that server, all data rendering and content conversions for that mailbox will be local, thus removing version constraints and functionality issues
that arose in previous releases.
Exchange 2007 Servicing
http://technet.microsoft.com/en-in/library/dd421853(v=exchg.80).aspx
Deployment Order
Our test infrastructure guarantees that Exchange hotfixes work across multiple server roles. The order in which you apply the update rollup to the servers is not important except if you are deploying CAS-CAS proxying. Because the update rollups are not segmented
for different Exchange server roles or for specific file configurations, apply each update rollup package to all Exchange 2007 servers in your environment.
If you have multiple Active Directory sites, and if you deploy a Client Access server in the proxy sites that do not face the Internet, you must
apply the update rollup to the Internet-facing Client Access servers
and to the non-Internet-facing Client Access servers in the proxy site simultaneously. For other Exchange 2007 configurations, we recommend that you
apply the update rollup package to the Client Access servers before
you apply it to servers that are running other Exchange 2007 server roles, such as the Mailbox server role, the Hub Transport server role, and the Edge Transport server role.
Note:
Applying service packs and update rollups to clustered Mailbox servers requires specific planning and application steps. For more information about how to apply service packs to Exchange 2007 clustered Mailbox servers, see
Upgrading Clustered Mailbox Servers to Exchange 2007 SP1 or later. For more information about how to apply update rollups to Exchange 2007 clustered Mailbox servers, see
Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers.
For Patching and compatibility between versions:
Determine the service pack level of Exchange.
Update rollups are service pack dependent. For example, an Update Rollup 5 package is available for Exchange 2007 and for Exchange 2007 Service Pack 1. To determine the service pack level of Exchange, examine the
ExchangeVersion property. For more information about how to view the
ExchangeVersion property and about the build number that is associated with each Exchange version, see
Exchange Server 2007: Platforms, Editions, and Versions.
References:
How to Install the Latest Service Pack or Update Rollup for Exchange 2007
Exchange Server Updates: build numbers and release dates
We are looking at doing the roll-up to SP3
Coexistence of Exchange2007 SP1 and Exchange 2007 SP3
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange server 2007 Service Pack problems SBS 2008

Similar Messages

Maybe you are looking for