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

Similar Messages

Exchange 2003 service packs and Unity 4.04

My client wants to move to Exchange 2003 SP2 and his current Unity version is 4.04 Sr1. Are there any incompatibility between the two ?
Thanks

From what I hear SP2 is TAC supported only with 4.0.5 and above. So, upgrade them and enjoy the billing part.
Regards,
Dragi

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 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.

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

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.

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.

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

Exchange 2010, UCC SSL, and the "new" CA/BROWSER Forum not issuing for .local

I don't know how many people have run into this yet, but the CA/BROSWER Forum, the "standards" authority for SSL issuing, has mandated that CA's can no longer issue a certificate using a FQDN "intranet" name for new or renewal SSL certificates effective
Nov 1, 2012. i.e. the Microsoft standard of mydomain.local will no longer be accepted as a SAN on a UCC for Exchange 2010. I've looked thru the KBs and Social forums, but haven't really found any guidance on how to solve this. I'm presuming
that the certs will have to be split and the "external" domain name of server.mydomain.net will just become a single server SSL, and the internal name of server.mydomain.local will become a Self-Signed certificate. With the increasing prevalence of OA
and ActiveSync devices, is there any baseline guidance yet on how to make this happen without completely fouling up production servers and killing access to the user community?

On the same topic, though likely different environment...
Against recommended deployment, I have a number of clients running all their services on one box. Windows Server 2008, Active Directoy, DNS, Exchange 2010 ...and so on. These servers all have .local addresses, which means of course that the SAN
certificates have .local addresses as one of the SANs.
I've read alot online about this issue, and am trying to find the most cost effective solution to switch numerous production servers running this configuration.
The best solution I've come up with so far is...
1. Virtual AD with new external domain, 2. Migrate Exchange CAS to this domain, 3. Reconfigure network through the box.
Obviously these steps will contain alot more details, but this is just the outline atm. At best, I see me having to take a second box with me to each location to perform these steps, and I can't see it happening without disruption to the work flow
of employees.
Thankfully, all of these businesses are relatively smal...under 25 employees. Still, I'd like to find the smoothest transition solution possible.
Any suggestions would be greatly appreciated!
Regards

How to find out the IPS and DS Service Pack and patch levels in windows server.

Hi,
I have installed the Information Platform Services 4.0 and Data services 4.0 in windows QA system, now we need to install the same version of IPS & DS in windows PRD system for this how could we find out the exact version of IPS & DS ( Service pack and patch levels ) and where we can find the same.
Many Thanks,
Sudheer

Hi Sudheer,
On a Windows Operating Systems you can check the “Programs and Features” in control panel.You can see a list of both the Name and Version number of SAP BusinessObjects that is installed.
option 2:
Open CMC go to Settings. In the properties, you will find the Product Version.
Please check below SAP notes for more information.
http://service.sap.com/sap/support/notes/1602088
Regards,
Pavan

Service packs and hot fixes for BusinessObjects Enterprise XI 3.1

Hello Experts.
Which is the cronology or order of the service packs and hot fixes for BusinessObjects Enterprise XI 3.1, or which are tha latest?
thanks

For BO XI 3.1, SP 5 is the latest, released in August 2011. You can directly install SP5 if you already have SP3 installed.
Previous Service Pack is 4.0 and Fix Pack 4.1.

2008 Engage Server Service packs and Fix Packs

I have Engage Server. I tried to load SP 3 and it didn't let me open old files. SAP told me SP3 was not compatible with Server product. I had to roll back to base version 5.0.0.99 build 12,0,0,121. Does anybody know if I can at least load SP1 or SP2 (and/or Fix packs) so I can have some of the basic features?

Your first question was answered many time int his forums, please use search functionality before posting a question.
There is no publicly available Version matrix + fixed issues list.
However, you can do to Service Market Place > Downloads locate XIR2 section and see how many Service Packs and Fix Packs are available.
Latest Service Pack for XIR2 is 6
latest Fix Pack for XIR2 is FP6.4 (needs to be installed on top of SP6)
To the right of each SP/FP in the download section of SMP is a link called "Info" , it leads to Knowledge articles which contain list of fixed issues.
As all SP/FP's are cumulative, you can view Sp6 readme and Fp6.4readme to get overall picture of fixed issues.

Install the latest Service Pack and Cumulative Update

Hi Expert,
I am installing SAP on SQL SERVER 2008 R2. The database software installation is done,but as per
installation guide it is recommending to install "Service Pack and Cumulative Update" as SAP Notes 62988
Please suggest me if i donot install service pack then will it impact our installation?
Please relply ASAP.

Its always recommanded to have your database at patch level and cummulative update supported by SAP.
If you don't perform now then you have to take again downtime to perform this activity.
Regards,
Nikunj Thaker

Exchange 2010 Service Pack 1 and Unity 7.0(2)

Similar Messages

Maybe you are looking for