Exchange 2010 Service Pack 3 question

Forum,
We currently have a small Exchange organization consisting of one Exchange 2010 SP1 server at the corporate office and a 2nd server (mailbox) at another location. The other location also has a CAS server. We need to apply SP3 to Exchange and
have already performed the schema update for SP3.
My question is: are we able to install SP3 on the corporate Exchange server
now and apply SP3 to the remote CAS and mailbox servers later without causing any Exchange Organization issues? Server downtime at the corporate office is easier to schedule than the remote location which needs change
control notification and planning well in advance as they operate 24/7.
I just don't want to upgrade one server then cause problems throughout the Organization as Exchange is heavily used. We need to upgrade to SP3 not only because it is the latest SP that resolves a host of issues but also to prepare for
a hybrid deployment of Office 365.
Thank you in advance,
Joe

You would want to update CAS servers first, prior to any mailbox servers.
Is the single Exchange server in the corporate office multi-role?
Do you have a DAG between the two mailbox servers going over the WAN connection?
http://supertekboy.com/2014/05/01/exchange-2010-installing-service-pack-3/
Check out my latest blog posts on www.supertekboy.com A tech blog for I.T. Superheroes.

Similar Messages

Questions about upgrading from Exchange 2010 RTM to Exchange 2010 Service Pack 3

I am preparing to perform an maintenance upgrade on our current Exchange 2010 Server, to Service Pack 3 (and any post-SP3 roll ups), but I have a couple questions about the process.
Current Exchange Server details:
Exchange 2010 Standard
Version: 14.0 (Build 639.21) - from Exchange Management Console
Version: 14.0.702.4000 - from Outook client
Active Directory forest and domain levels: Windows 2008 R2 native
The questions I have are:
1. Can I assume that because it's version 10.0.702.4000 I am on Exchange Server 2010 RTM Update Rollup 4?
2. Can Exchange 2010 Standard RTM be patched directly to Service Pack 3, or would I need to perform incremental patches (i.e. SP1, SP2, etc.) before going to SP3?
3. Do I need to manually perform the AD domain schema prep before applying Service Pack 3, or will the Service Pack 3 update process automatically handle the modifications of the AD schema?

Hi,
Here are my answers you can refer to:
1. Firstly, I’d like to explain , we can use connection status to check our Exchange server version from Outlook client:
http://office.microsoft.com/en-in/outlook-help/determine-the-version-of-microsoft-exchange-server-my-account-connects-to-HA010117038.aspx
And I check my version from both EMC and Outlook client. It’s same.
2. We can directly update RTM version to SP3 , and the update will take an additional 30 minutes or longer per database.
3. Since Exchange 2010 SP3 makes updates to the Active Directory schema, we need prepare AD domain schema. However, it will automatically prepare AD and the domain when you install the update.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/jj965774(v=exchg.141).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

Exchange 2010 Service Pack 1 and Unity 7.0(2)

We are in the process of migrating from Exchange 2003 to Exchange 2010. We had everything working with 2010, but wanted to install SP1 prior to migrating users over to the new Exchange server.
After installing SP1, messages are no longer being transfered to the Exchange server. We've re-run the permissions wizard, thinking that the update may have undone some permission setting. This succeeded, but we still get nothing.
Has anyone else installed SP1 for Exchange 2010? If so, any issues?

For those with Unity 7.0(2) integration with Exchange 2010, please refer to this defect CSCti70702 and you may find your answer to the multiple issues you are experienced. It has to do with MS/CDO library.
https://supportforums.cisco.com/docs/DOC-12848
http://support.microsoft.com/kb/2405611

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

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 2010 Management Pack Data Warehouse Synchronization Fails

Hi Everyone!
Has anyone had success with importing the Exchange 2010 management pack into Service Manager 2012?
When we try to import it, it fails.
Upon further investigation, the 'System Center Core Monitoring' management pack (which is not included with Service Manager 2012) is a dependency of the Exchange 2010 management pack but
after we import it from the OpsMgr 2012 media, we still get the following warning when we import the Exchange 2010 management into Service Manager 2012...
"The management pack was imported successfully.
Warnings (1):
Override verification failed, cannot find Management Pack Element : : Cannot find ManagementPackElement [Type=ManagementPackRule, ID=Microsoft.SystemCenter.Agent.MonitoringHost.PrivateBytesThreshold] in management pack ManagementPack:[Name=Microsoft.SystemCenter.2007,
KeyToken=31bf3856ad364e35, Version=6.0.6246.0]."
...and, the Exchange 2010 management pack status in the Service Manager 2012 Data Warehouse 'Management Pack' view indicates 'failed' after the MPSyncJob completes.
We have a few 'Business Services' which depend on the Exchange 2010 management pack that we are trying to synchronize from OpsMgr 2012 and we are stuck until we can get the Exchange 2010 management
successfully imported into Service Manager 2012 and have it show a status of 'Completed' the Service Manager 2012 Data Warehouse 'Management Pack' view.
Nothing useful in the
Service Manager 2012 Data Warehouse and Management servers events logs that we could see.
Any help or guidance would be GREATLY appreciated!
Regards,
JJ

Update: I Just tested with CU2 installed for SrvMgr 2012 and OpsMgr 2012 and version 14.3.38.2 of the Exchange 2010 management, but the management pack still fails to deploy to the SrvMgr 2012 data warehouse (the management pack status shows
up as 'failed' and the MPSyncJob shows the management pack as 'pending association'). The only clue I have for this problem is the folllowing warning which occurs when I import the management pack into SrvMgr 2012...
I also get the following 33519 Event ID warning in the Operations Manager event log on the data warehouse server...
~~~~~
Management pack association ignored. This does not require any action. If you continue to frequently see this warning, contact your administrator. This process will continue to retry.
Management pack ID: e2296ed5-ddbc-ebc7-3881-c5288adaa7cf
Management pack name: Microsoft.Exchange.2010
Management pack version: 14.3.38.2
Data source name: SRV
Message: Either the MP has failed deployment Or any of its references has failed deployment
~~~~~
Has anyone had success with getting the Exchange 2010 management pack imported and successfully deployed to the SrvMgr 2012 data warehouse?
The good news is that even though the Exchange 2010 management pack has a status of failed, the distributed applications in OpsMgr 2012 that depend on the Exchange management pack now show up under Configuration Items/Business Services including
all related service component objects which was what I was trying to accomplish in the first place, so for now I'll just leave the Exchange 2010 management pack in the data warehouse with a failed status.
Regards,
JJ

Office 2010 Service Pack 2 (SP2) installation failing with error code 0x80070643 and B56

I've been trying to install Office 2010 service pack 2 (32 bit) multiple ways without success. I've tried getting it directly from Microsoft Update, downloading the full file from Microsoft and installing it, using WSUS to deploy to clients, and I've tried
using LANDesk to deploy it. All methods are failing.
I need a solution that doesn't involve touching each PC manually, as I have a feeling this error is going to occur on several hundred PC's in my organization. So far on a group of 15-20 test PC's, every one has failed. We have not had problems with any other
Microsoft Updates before this one.
When I try Microsoft Update, I receive the following error:
Code B56 Windows Update encountered an unknown error.
Below is the WindowsUpdate.log excerpt:
2013-08-06 12:45:33:313 3952 dc4 Handler :::::::::::::
2013-08-06 12:45:33:328 3952 dc4 Handler :: START :: Handler: MSI Install
2013-08-06 12:45:33:328 3952 dc4 Handler :::::::::
2013-08-06 12:45:33:328 3952 dc4 Handler   : Updates to install = 7
2013-08-06 12:45:33:328 3952 dc4 Handler Extracting MSP file stored in CAB officesuiteww-x-none.cab
2013-08-06 12:45:43:671 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:43:671 3952 dc4 Handler Extracting MSP file stored in CAB proofing-en-us.cab
2013-08-06 12:45:43:702 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:43:702 3952 dc4 Handler Extracting MSP file stored in CAB proof-fr-fr.cab
2013-08-06 12:45:43:983 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:43:983 3952 dc4 Handler Extracting MSP file stored in CAB clientshared64ww-x-none.cab
2013-08-06 12:45:44:217 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:44:217 3952 dc4 Handler Extracting MSP file stored in CAB officesuitemui-en-us.cab
2013-08-06 12:45:44:482 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:44:482 3952 dc4 Handler Extracting MSP file stored in CAB clientshared64mui-en-us.cab
2013-08-06 12:45:44:529 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:44:529 3952 dc4 Handler Extracting MSP file stored in CAB proof-en-us.cab
2013-08-06 12:45:44:716 3952 dc4 Handler MSP update {00000000-0000-0000-0000-000000000000}.0 using full-file patch
2013-08-06 12:45:44:716 3952 dc4 Handler   : Batch installing 7 updates
2013-08-06 12:45:46:417 3952 dc4 Handler List of MSPs in transaction:
2013-08-06 12:45:46:417 3952 dc4 Handler   C:\Windows\SoftwareDistribution\Download\29f5035d168bf9e9d0369f84037ff787\img\officesuiteww-x-none.MSP
2013-08-06 12:45:46:417 3952 dc4 Handler MSP final command line: DISABLESRCPROMPT=1 LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS MSIRESTARTMANAGERCONTROL=Disable
2013-08-06 12:46:42:265 112 600 Report Uploading 2 events using cached cookie, reporting URL =
http://wsus:8530/ReportingWebService/ReportingWebService.asmx
2013-08-06 12:46:42:358 112 600 Report Reporter successfully uploaded 2 events.
2013-08-06 12:47:52:012 3952 dc4 Handler MSP Error List:
2013-08-06 12:47:52:012 3952 dc4 Handler 1: 2902 2: ixfAssemblyCopy
2013-08-06 12:47:52:012 3952 dc4 Handler   : MSI transaction completed. MSI: 0x80070643, Handler: 0x8024200b, Source: No, Reboot: 0
2013-08-06 12:47:52:012 3952 dc4 Handler   : WARNING: First failure for update {365F23BF-5D31-4811-A197-29C2C0751961}, transaction error = 0x8024200b, MSI result = 0x80070643, MSI action = InstallFiles
2013-08-06 12:47:52:012 112 938 AU >>## RESUMED ## AU: Installing update [UpdateId = {9C5E43A3-3AE9-434D-B105-A9D7902D5F9F}]
2013-08-06 12:47:52:012 112 938 AU   # WARNING: Install failed, error = 0x80070643 / 0x00000B56
2013-08-06 12:47:52:012 3952 dc4 Handler   : WARNING: Operation failed at update 0, Exit code = 0x8024200B
2013-08-06 12:47:52:012 3952 dc4 Handler :::::::::
2013-08-06 12:47:52:012 3952 dc4 Handler :: END :: Handler: MSI Install
2013-08-06 12:47:52:012 3952 dc4 Handler :::::::::::::
2013-08-06 12:47:52:168 112 5c4 Agent *********
2013-08-06 12:47:52:168 112 5c4 Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
2013-08-06 12:47:52:168 112 5c4 Agent *************
2013-08-06 12:47:52:168 112 938 AU Install call completed.
2013-08-06 12:47:52:168 112 938 AU   # WARNING: Install call completed, reboot required = No, error = 0x00000000
2013-08-06 12:47:52:168 112 938 AU #########
2013-08-06 12:47:52:168 112 938 AU ## END ## AU: Installing updates [CallId = {87C0C0A5-18CE-45A0-9376-989DCA9CACCA}]
2013-08-06 12:47:52:168 112 938 AU #############

I too have been unable to install the Office 2010 SP2 update on either a Win7 or a Win 8 system. Researching the errors I got led me to discover the following:
1. Many people are encountering errors during the SP2 installation. Some were able to get around it by downloading the self-installing package and bypassing Windows Update. Some were able to get it installed by first doing a Repair on Office 210 itself
first, and then installing SP2. But many others have not been able to install it at all.
2. Apparently a common and insurmountable issue that prevents SP2 from installing is the lack of the MSOCACHE directory. This directory normally gets installed on a machine during the original install of Office, and contains all the install files used
during the installation. Apparently the idea behind creating MSOCACHE was to allow subsequent updates without requiring the user to have the original source CD available.
The problem is that if MSOCACHE is deleted, which is an option many people choose, you can then no longer do any updates to Office.
I am one of those people.
I found a posting that described a way to recreate MSOCACHE from the source CD. I did that, and the SP2 update actually got farther - it started to install stuff but then stopped and asked for a particular file. I found the file on the CD and
pointed the installer to it, but it said the file was not found and quit. So my install still failed.
The last response I got at the Microsoft Answers site was to wait until SP2 is debugged. It's not clear to me this will ever happen, but we'll see.
Birk Binnard http://www.birkbinnard.com

Detection Office 2010 Service Pack 2 - Slipstreamed Install and WSUS rebuild

Hi,
at a customer of us the WSUS infrastructure had some problems and after some investigation the WSUS infrastructure was built up from scratch. We do have one WSUS Server which syncs with Microsoft and two downstream servers. After rebuild the WSUS infrastructure
we do see one issue:
Many clients were deployed with Office 2010 SP2 slipstreamed. Now the WSUS tells us for the Office 2010 Service Pack 2 Update (KB2687455) that it is missing on the clients.
Is this a normal behaviour or is there an issue with the WSUS detection of the Service Pack? How can I see which updates a client reports to WSUS as installed while connecting with the new WSUS Server? I've tried to figure that out within the WindowsUpdateLog.log
file but without success.
Any ideas are very appreciated.
Peter Forster | MVP Virtual Machine 2002-2011 | Austria |

but wouldn't that cause SP2 to install again (or even downloaded to the client?)
Maybe.
Probably.
If the "SP2 slipstream" was incomplete, or additional Office modules were added post-image, then the service pack needs to be reapplied. The key here is understanding how Office 2010 SP2 is different from other Office service packs in history.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

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

OfficeJet 4315 no longer works after Win 7 and Office 2010 service packs applied

I've used OfficeJet 4315 on a Toshiba Satellite with WinXP (SP3) and Office 2003 and been delighted with the printer. I recently migrated to a brand-new Acer Aspire with Win 7 and Office 2010 (home & student ed.) At first, the 4315 worked well--in fact, all I had to do was plug in the USB connection and the in-OS drivers installed automatically. However, something has now caused the printer too be essentially useless! I think it happened after I applied SP1 to Win 7 and/or the service pack to Office 2010. I can no longer print Word files (.doc or .docx), Excel spread sheets (.xls or .xlsx), PDFs, Web pages, or even e-mails, The only things I can print are .txt files or equivalent and .jpg files or equivalent. I've tried deleting and reinstalling the printer (including deleting the drivers and reloading them from Windows Update). I don't believe I should have to replace a perfectly good printer just to support Windows 7 and Office 2010. I NEED HELP URGENTLY with this problem! If anyone has any knowledge or ideas, I'd be forever in your debt. (HP, I'd even pay to get the help I need on this one!!) TIA.

Hi,
Based on your description, my understanding is that the PDF files cannot be checked out to local drafts folder after Office 2013 is installed.
Did this issue occur with Office files?
I recommend to check if the Office files can be checked out to local drafts folder with Office 2013.
And it is recommended to use Office 2010 with SharePoint 2010 for best practice.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Outlook web login screen not displaying correctly on Exchange 2007 service pack install

Hello everyone,
I believe our exchange server installed a service pack 3 update and after rebooting the server, we noticed that the Outlook web access login screen is not displaying correctly. The page looks white with some black X's (I think that's where the
pictures/background images used to be). We tried to restart the ISS service with no luck. I would appreciate any help you guys can provide.
Thanks,
Brian Kourdou

Hi,
I have seen this issue in another similar thread, that issue was solved by re-creating the OWA virtual directory.
Please try the following steps to solve this issue.
Open EMC, navigate to Server Configuration -> Client Access, under Outlook Web App tab, double-click owa (default web site) properties.
Then check InternalURL, ExternalURL, Forms-Based Authentication settings ect
Open EMS, use Get-OwaVirtualDirectory get the list of virtual directories and identify the directory which is giving the problem.
Remove it with this command
Remove-OwaVirtualDirectory “owa (Default Web Site)”
Now create it again with the following command
New-OwaVirtualDirectory -OwaVersion “Exchange2007″ -Name “owa (Default Web Site)”
Then configure the “owa” virtual directory settings like InternalURL, ExternalURL, Forms-Based Authentications etc… & check the OWA by logging with some test users.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Crystal Report Service Pack Question

Hi,
I have some question regarding Crystal Report Service Pack for different version respectively :-
Crystal Report 9
1. I have SP5 and SP7. Can I just install SP7 without installing SP5 ?
Crystal Report XI R2
1. I have install a distribution of Crystal Report X1 R2 in a non-development server.
Can I install the latest SP6 into that non-development server ? Which SP6 I should install, preferably a link to that SP would be great.
NOTE: I am a VS.NET 2003 and 2005 developer.
Best regards
Joseph

Crystal Report 9
1. I have SP5 and SP7. Can I just install SP7 without installing SP5 ?
- Yes
Crystal Report XI R2
1. I have install a distribution of Crystal Report X1 R2 in a non-development server.
Can I install the latest SP6 into that non-development server ?
- no. From CR XI on, SPs are only meant to be used on development computers. E.g.; a computer that has the CR designer installed. To update your runtime computer, you will have to uninstall the current runtime and install the SP6 runtime:
MSM
https://smpdl.sap-ag.de/~sapidp/012002523100000634042010E/crxir2sp6_net_mm.zip
MSI
https://smpdl.sap-ag.de/~sapidp/012002523100000633302010E/crxir2sp6_net_si.zip
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup

Exchange 2010 RPC Encyption question

Quick question. We are running Exchange 2010 SP3 RU 5 (latest and greatest). All of our CAS servers have RPC Encryption disabled. If clients are enabled for Encyrption will this encrypt traffic to the CAS servers? Question is we're
seeing issues with some of our Cisco Wan Optimizers. I just want a better understanding if only the client side (Outlook 2007/2010) is enabled does that encrypt.

Hi,
Agree with above opinion, if all cas servers have disabled RPC Encryption, Clients will not be encrypted traffic to the server regardless of whether the client encryption is enabled.
More details refer to the following articles:
RPC Encryption Required
Outlook connection issues with Exchange 2010 mailboxes because of the RPC encryption requirement
In addition,Microsoft strongly recommends you leave the encryption requirement enabled on your server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2010 Service Pack 3 question

Similar Messages

Maybe you are looking for