Unity 5.0 compatibility with Exchange 2010 SP2?

Has anyone out there tested Unity 5.0 (1) with Exchange 2010 SP2? Did you have any problems? I understand that Unity 5.x has gone end of maintenance, and it has not been officially been tested for compatibility with Exchange 2010 SP2 for unified messaging. I don't anticipate being able to upgrade Unity until next year, but the sytem admins want to upgrade from Exchange SP1 to SP2 sooner. Thanks.

Similar Messages

Cisco Unity Connection Single inbox with Exchange 2010

I have a new installation of Unity Connection 8.6.2 using single inbox with an Exchange 2010 cluster frontended by a Netscaler load balancer.Functionality that does not work is when a new message comes into outlook and the message is read or deleted it does not update the status on the phone- IE turn off the MWI or if the message is deleted it is still a new message in Unity. If you click reset in the user unified message account, the status gets updated.
TAC says its a blocked port on Exchange TCP 7080 but that is open.

I followed this document :
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg020.html
but when i try to integrate CUC with exchange 2010 , i didn't find is clear enough
do you have Step by Step more clear than that link becouse my lab very close to your case.
Regards

Unity 5.0(1) with Exchange 2010

According to the following link, Unity 5.0 supports Exchange 2010 as the partner Exchange server.
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html#wp47622
However, when I get to step 14 of this document (installing ExchangeMapiCdo.exe) I get an error saying it can't be installed with this version of Exchange.
I was just wondering if anyone elsel had tried to run Exchange 2010 with Unity 5.0 and if so, how you were able to get it to work. I followed all the steps in this document and everything seemed to be working until this step.

3 things:
1) You should get a TAC case going, if you haven't already.
2) For Unity 5x, ES83 was replaced by ES85 (which was yanked off the download site almost like a ghost in the night) and now there is ES86. You may want to read up on what is fixed here in this ES.
3) I think you may have your service account mailboxes homed in the wrong place. If you note there, is a section for where to put the mailbox for the UnityMsgStoreSvc. Excerpts I'm looking at are:
Adding One or More Exchange 2010 Servers to an Existing Cisco Unity 7.0 and/or 5.0 Installation
Step 14 On the Cisco Unity server, install ExchangeMapiCdo.exe, which you downloaded in Step 4.
Step 15 On the Cisco Unity server, install the version of the Permissions wizard that you downloaded in Step 2.
Step 16 Run the Permissions wizard, and select the Exchange 2010 message stores in which mailboxes for Cisco Unity subscribers will be homed.
Step 17 At the end of the Permissions wizard, on the You Have Completed the Cisco Unity Permissions Wizard page, click Granting Microsoft Exchange Administrator Rights, and do the procedure in the Help file to add the installation and directory services accounts to the Exchange 2010 Organization Management role group.
Step 18 Restart the Cisco Unity server.
Step 19 Move or create a mailbox for the Cisco Unity message store services account (typically UnityMsgStoreSvc), as applicable:
Exchange 2003 or Exchange 2007
mailbox already exists
Move the mailbox for the account to Exchange 2010.
No mailbox
Create a mailbox for the account in Exchange 2010.
Step 20 Remove the Exchange 2010 RPC limit for the message store services account by creating and applying a new mailbox policy to the message store services account:
a. Open an Exchange 2010 Management Shell window.
b. Create a new policy with unlimited RPC connections, for example:
new-throttlingpolicy -name "Unity Exchange 2010 Policy" -RCAMaxConcurrency $null
c. Apply the new policy to the message store services account, for example:
set-mailbox -identity "UnityMsgStoreSvc" -throttlingpolicy "Unity Exchange 2010 Policy"
d. Confirm that the mailbox is using the new policy, for example:
get-mailbox -identity "UnityMsgStoreSvc" | fl | findstr "Throttling Policy"
e. If you have more than one Cisco Unity server: Repeat Step c and Step d for every message store services account in the forest.
We recommend that you apply the policy to all message store service accounts, even the accounts for Cisco Unity servers for which you do not currently intend to home subscriber mailboxes in Exchange 2010 message stores. Applying the policy does not affect Cisco Unity performance, and it ensures that you will not encounter problems if you later move mailboxes to an Exchange 2010 server.
f. On each Exchange 2010 server with the CAS role, restart the Microsoft Exchange RPC Client Access service.
Personally, I would make sure you have all of these items down to a tee because, IMO, there is likely something that went astray in the install/backout/fix process.
Hailely

SBS2011 (Exchange 2010 SP2) - limiting cache size doesn't appear to work

Hi All,
Hoping for some clarification here, or extra input at least. I know there are other posts about this topic such as
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/5acb6e29-13b3-4e70-95d9-1a62fc9304ac but these have been
incorrectly marked as answer in my opinion.
To recap the issue. The Exchange 2010 store.exe process uses a lot of memory. So much in fact it has a negative performance impact on the server (sluggish access to the desktop etc). You can argue about this all day - it's by design
and shouldn't be messed with etc but the bottom line is that it does use too much memory and it does need tweaked. I know this because if you simply restart the Information Store process (or reboot the server) it frees up the memory and the performance
returns (until its cache is fully rebuilt that is). I have verified this on 4 different fresh builds of SBS2011 over the last 6 months. (all on servers with 16GB RAM)
I have scoured the internet for information on limiting how much memory exchange uses to cache the information store and most articles point back to the same two articles (http://eightwone.com/2011/04/06/limiting-exchange-2010-sp1-database-cache/
and
http://eightwone.com/2010/03/25/limiting-exchange-2010-database-cache) that deal with exchange 2010 and exchange 2010 SP1, notably not exchange 2010 SP2. Ergo most articles are out of date since exchange 2010 SP2 has been released since these articles
were posted.
When testing with our own in house SBS2011 server (with exchange 2010 SP2) I have found that specifying the min, max and cache sizes in ADSIEDIT has varying results that are not in line with the results documented in the articles I mentioned above.
I suspect the behaviour of these settings has changed with the release of exchange 2010 SP2 (as it did between the initial release and SP1).
Specifically here's what I have found using ADSIEDIT;
If you set the msExchESEParamCacheSize to a value - it doesn't have any effect.
If you set the msExchESEParamCacheSizeMax to a value - it doesn't have any effect.
If you set the msExchESEParamCacheSizeMin to a value - it always locks the store.exe process to using exactly this value.
I have also tested using combinations of these settings with the result that the size and max size values are always ignored (and the store.exe process uses the maximum available amount of memory - thus causing the performance degradation) but as soon as
you specify the min value it locks it to this value and it doesn't change.
As a temporary solution on our in-house SBS2011 I have set the min value to 4GB and it appears to be running fine (only 15 mailboxes though).
Anyone got some input on this ? thank you for your time.

I concur with Erin. I'm seeing the same behaviour across all SBS2011 boxes, whether running SP1, SP2 or SP3.
If a minimum value is set, the store cache size barely rises above the minumum. I have one server with 32GB RAM. Store.exe was using 20GB of RAM, plus all the other Exchange services which total 4GB+. That left virtually no free RAM and trying to do
anything else on the server was sluggish at best.
All the advise is that setting a maximum alone has no effect and a minimum must be set too. But when set, the store cache size barely rises above the minimum. I have set a 4GB minimum and 16GB max, but 5 days later it's still using only slightly more than
4GB and there's 8GB free. Now the server as a whole is responsive, but doing anything with Exchange is sluggish.
Just saying leave Exchange to manage itself is not an answer. The clue is in the name - Small Business Server. It's not Exchange Only Server - there are other tasks an SBS must handle so leaving Exchange to run rampant is not an option. Besides, there are
allegedly means to manage the Exchange cache size - they just don't apparently work!
I'm guessing nobody has an answer to this so the only solution is to effectively fix the cache size to a sensible value by setting min and max to the same value.
Adam@Regis IT

Exchange 2010 SP2: Different problems with E_ACCESSDENIED on exchange servers

Hello All,
I'm observing a strange problem in an AD 2008 R2 / Exchange 2010 SP2 environment:
When creating a DAG and adding 1 or more servers to the DAG, the following error occurs:
Summary: 2 item(s). 0 succeeded, 2 failed.
Elapsed time: 00:00:05
<MAILBOX SERVER 1> Failed
Error:
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer '<MAILBOX SERVER 1>' -Identity '<NAME DAG>'
Elapsed Time: 00:00:02
<MAILBOX SERVER 2> Failed
Error:
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer '<MAILBOX SERVER 2>' -Identity '<NAME DAG>'
Elapsed Time: 00:00:02
There are no logs created on the Mailservers, so I have no more detailed information. Where to start with troubleshooting this issue?
Edit: BTW I already checked the local admin membership of the "Exchange Trusted Subsystem" domain group.
Also commands like get-owavirtualdirectory give the Access Denied error (except on the CAS servers themselves).
You know you're an engineer when you have no life and can prove it mathematically

Hi Frank,
The DAG is not yet populated. When inserting the first server(s) in the freshly created DAG, the error appeared.
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Get-DatabaseAvailabilityGroup
Name             Member Servers
Operational Servers
IICT-DAG-002     {}
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Get-DatabaseAvailabilityGroup IICT-DAG-002 -Status | fl
RunspaceId                             : cc985264-fa89-48f8-8aba-c1b0c89eb097
Name                                   : IICT-DAG-002
Servers                                : {}
WitnessServer                          : iict-srvp00-011.insourceict.local
WitnessDirectory                       : C:\IICT-DAG-002
AlternateWitnessServer                 :
AlternateWitnessDirectory              :
NetworkCompression                     : InterSubnetOnly
NetworkEncryption                      : InterSubnetOnly
DatacenterActivationMode               : Off
StoppedMailboxServers                  : {}
StartedMailboxServers                  : {}
DatabaseAvailabilityGroupIpv4Addresses : {10.100.0.54}
DatabaseAvailabilityGroupIpAddresses   : {10.100.0.54}
AllowCrossSiteRpcClientAccess          : False
OperationalServers                     :
PrimaryActiveManager                   :
ServersInMaintenance                   :
ThirdPartyReplication                  : Disabled
ReplicationPort                        : 0
NetworkNames                           : {}
WitnessShareInUse                      :
AdminDisplayName                       :
ExchangeVersion                        : 0.10 (14.0.100.0)
DistinguishedName                      : CN=IICT-DAG-002,CN=Database Availability Groups,CN=Exchange Administrative Gro
                                         up (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=InsourceICT,CN=Microsoft Exch
                                         ange,CN=Services,CN=Configuration,DC=insourceict,DC=local
Identity                               : IICT-DAG-002
Guid                                   : 71d5d869-03ac-4f8a-8de7-fc15bc6a0ae1
ObjectCategory                         : insourceict.local/Configuration/Schema/ms-Exch-MDB-Availability-Group
ObjectClass                            : {top, msExchMDBAvailabilityGroup}
WhenChanged                            : 8-6-2012 14:35:59
WhenCreated                            : 8-6-2012 13:35:21
WhenChangedUTC                         : 8-6-2012 12:35:59
WhenCreatedUTC                         : 8-6-2012 11:35:21
OrganizationId                         :
OriginatingServer                      : IICT-SRV003.insourceict.local
IsValid                                : True
You know you're an engineer when you have no life and can prove it mathematically

Rollup 8 for Exchange 2010 SP2 causes EWS error with bad parameter for Exchange.MailboxReplicationService.ProxyService

When I installed Rollup 8 for Exchange 2010 SP2 it caused an error in EWS
EWS failed with the error:
exchange web service could not load file or assembly Exchange.MailboxReplicationService.ProxyService bad parameter
When I uninstalled the rollup all worked fine again.
Any ideas, Thanks in advance?

Hi,
To apply this update rollup, you must have Exchange Server 2010 SP2 installed. And remove all interim updates for Exchange Server 2010 SP2 before you apply this update rollup. Please check your installation deployment by the following article:
Install the Latest Update Rollup for Exchange 2010
http://technet.microsoft.com/en-us/library/ff637981.aspx
Description of Update Rollup 8 for Exchange Server 2010 Service Pack 2
http://support.microsoft.com/kb/2903903/en-us
If all requirements and preparations are configured properly, please collect your error logs to check your installation. It would be helpful to post some event logs here for further analysis.
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2010 Sp2 update rollup 7 fails with error code 80070643 on Sbs 2011

Hello Everyone,
When i trie to install rollup 7 voor exchange 2010 sp2 (sbs 2011) it gives me error code 80070643. I cannot find much to solve this problem. Update rollup 8 installs fine. I've read on internet that every rollup must be installed to succesfully install exchange
2010 sp3. Can anyone help me with this error?

I just installed exchange 2010 sp3, but it does not finish. It stops at 'client access role'
This is in the log;
[10-08-2014 21:55:24.0121] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'server.company.com', Preferred Global Catalog: 'server.company.com', Preferred Domain Controllers:
'{ server.company.com }'
[10-08-2014 21:55:24.0121] [2] Beginning processing Start-SetupProcess -Name:'iisreset' -Args:'/noforce /timeout:120'
[10-08-2014 21:55:24.0137] [2] Starting: iisreset with arguments: /noforce /timeout:120
[10-08-2014 21:55:31.0640] [2] Process standard output: Attempting stop...
Internet services successfully stopped
Attempting start...
Restart attempt failed.
The IIS Admin Service or the World Wide Web Publishing Service, or a service dependent on them failed to start. The service, or dependent services, may had an error during its startup or may be disabled.
Process standard error:
[10-08-2014 21:55:31.0640] [2] [ERROR] Unexpected Error
[10-08-2014 21:55:31.0640] [2] [ERROR] Process execution failed with exit code 1062.
[10-08-2014 21:55:31.0640] [2] Ending processing Start-SetupProcess
[10-08-2014 21:55:31.0640] [1] The following 1 error(s) occurred during task execution:
[10-08-2014 21:55:31.0640] [1] 0. ErrorRecord: Process execution failed with exit code 1062.
[10-08-2014 21:55:31.0640] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 1062.
[10-08-2014 21:55:31.0640] [1] [ERROR] The following error was generated when "$error.Clear();
Start-SetupProcess -Name "iisreset" -Args "/noforce /timeout:120"
" was run: "Process execution failed with exit code 1062.".
[10-08-2014 21:55:31.0640] [1] [ERROR] Process execution failed with exit code 1062.
[10-08-2014 21:55:31.0640] [1] [ERROR-REFERENCE] Id=ClientAccessServiceControl___ef7fa14362774cd9af8882d6287b640a Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[10-08-2014 21:55:31.0640] [1] Setup is stopping now because of one or more critical errors.
[10-08-2014 21:55:31.0640] [1] Finished executing component tasks.
[10-08-2014 21:55:31.0672] [1] Ending processing Install-ClientAccessRole
Anyone has any ideas?

Single Inbox on Unity Connection 8.5 and Exchange 2003 SP2

Hi,
We have Unity Connection 8.5 (with SU2) and Exchange 2003 SP2
We want to setup the Single Inbox feature that works well with Exchange 2007 and 2010, but my customer is running Exchange 2003 SP2.
We met all of the requirements outlined in: http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html#wp459928
I configure a new "Unified Messaging Services" profile for Exchange using Exchange 2003 and enabled for Single Inbox. When I run "Test" it displays the following errors (other validation is successfully)
The service port for IMAP is not functioning.
The system failed to connect to the server with a socket connection through port beatles.clubone.com:993. The error is error:0200206F:system library:connect:Connection refused. Refer to the tomcat log file for more details. If you are using secure connection, confirm that SSL is enabled on the server.
Why is it trying to connect using IMAP, that wasn't the case when I used for Exchange 2007 or 2010 when IMAP was not enabled.
Is there something else I'm missing for configuration with Unity Connection to support Single Inbox with Exchange 2003 SP2?
Thank you!
-rya

Hi Rya,
I just wanted to add my +5 vote for this great catch by Aaron (nice work "A")
If you are going to upgrade to Unity Connection 8.6
Check out this great doc from Saurabh for the refresh upgrade notes to 8.6.
https://supportforums.cisco.com/community/netpro/collaboration-voice-video/unified-comm-application/blog/2011/08/11/checklist-before-upgrading-to-unity-connection-86
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen

Exchange 2010 sp2 emc initialization error using "kerberos" authentication failed

We use exchange 2010 SP2.
We have 2 management stations, both w2k8 R2 SP1.
I have one mangement station on which the emc and ems works ok.
On the other management staiton (which is also in another ad site) the emc and ems don't work.
I get the following error message : The attempt to connect to
http://fqdnCasServer/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
I have checked the time on the management station and on the exchange server and this is ok.
It is not a permissions issue because the user functions ok on the other management station.
On the bad management station I can open the emc once and after a minute I get an error message and the message access denied. From then on I can't connect any more.
What am I doing wrong?
Anyone any tips?
Thanks,
JB

This is what I get in the eventlog of the bad management station.
Log Name:      MSExchange Management
Source:        MSExchange CmdletLogs
Date:          1/10/2012 11:39:27
Event ID:      6
Task Category: (1)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.domain.com
Description:
The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Get-ExchangeServer
{Identity=Servername}
Domain/ou/ou/ou/ou/username
Exchange Management Console-Local
3080
22
00:00:00.3593888
View Entire Forest: 'True', Configuration Domain Controller: 'FQDN DC', Preferred Global Catalog: 'FQDN DC', Preferred Domain Controllers: '{ FQDN DN }'
Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'FQDN MGMTSTATION' couldn't be found on 'FQDN DC'.
Context
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange CmdletLogs" />
    <EventID Qualifiers="49152">6</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-10-01T09:39:27.000000000Z" />
    <EventRecordID>11</EventRecordID>
    <Channel>MSExchange Management</Channel>
    <Computer>FQDN MGMT STATION</Computer>
    <Security />
</System>
<EventData>
    <Data>Get-ExchangeServer</Data>
    <Data>{Identity=MGMT STATION}</Data>
    <Data>domain/ou/ou/ou/ou/username</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>Exchange Management Console-Local</Data>
    <Data>3080</Data>
    <Data>
    </Data>
    <Data>22</Data>
    <Data>00:00:00.3593888</Data>
    <Data>View Entire Forest: 'True', Configuration Domain Controller: 'FQDN DC', Preferred Global Catalog: 'FQDN DC', Preferred Domain Controllers: '{ FQDN DC }'</Data>
    <Data>Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'FQDN MGMT STATION' couldn't be found on 'FQDN DC'.</Data>
    <Data>Context</Data>
    <Data>
    </Data>
</EventData>
</Event>

Exchange 2010 SP2 Upgradation in DR site

Hi All,
I am planning upgrade exchange 2010 SP2 from SP1in DR servers which is in different site of AD.
I have already run the prepare schema and prepare ad in schema master which is in production site and it got replicated in DR Domain controllers.
But, still i am not able to upgrade the server. The error says,
:\Exch SP2>Setup /m:upgrade /InstallWindowsComponents /Hosting
Welcome to Microsoft Exchange Server 2010 Unattended Setup
Preparing Exchange Setup
    Copying Setup Files                           COMPLETED
The following server roles will be upgraded
Languages
Hub Transport Role
Client Access Role
Management Tools
Performing Microsoft Exchange Server Prerequisite Check
    Configuring Prerequisites                                 COMPLETED
    Organization Checks
FAILED
     Setup needs to contact the Active Directory schema master but this computer
is not in the same Active Directory site as the schema master (Default-First-Si
te-Name).
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have been created but have not yet replicat
ed to the local domain. Wait for replication to complete and then run setup aga
in.
    Language Pack Checks
COMPLETED
    Hub Transport Role Checks                                 FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have been created but have not yet replicat
ed to the local domain. Wait for replication to complete and then run setup aga
in.
    Client Access Role Checks                                 FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have been created but have not yet replicat
ed to the local domain. Wait for replication to complete and then run setup aga
in.
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
Exchange Server setup encountered an error.
Please let me know if you have options

Hi All,
I am planning upgrade exchange 2010 SP2 from SP1in DR servers which is in different site of AD.
I have already run the prepare schema and prepare ad in schema master which is in production site and it got replicated in DR Domain controllers.
But, still i am not able to upgrade the server. The error says,
:\Exch SP2>Setup /m:upgrade /InstallWindowsComponents /Hosting
Hi,
If you run Get-OrganizationConfig | fl Name,objectversion in your DR-Site, what is the version number you see?
If its not 14247, the schema has not been upgraded.
/Hosting is not supported with SP2, so you need to leave that out.
It might be better if you post in the forum
Exchange 2010 for Hosters
Some additional reading:
Future of /Hosting Mode
Martina Miskovic

Applying Windows 2008 R2 SP1 on Exchange 2010 SP2 servers

Hi All,
Our current setup is Primary Site and DR site with a DAG.
Primary site is having 2 Mailbox servers, 2 hubcas servers with an NLB and one CAS server for OWA.
DR Site is having 1 mailbox server, one hubcas server and one CAS server. All these exchange servers are SP2 with update roll up5.
But the OS is Windows 2008 R2, need to apply Windows 2008 R2 SP1 on these servers, and what are things to be considered.
Does this affect CAS servers IIS?
Thanks,
Kanishka.

Agreed. One thing to mention - Win 2008 R2 needed SP1 a while back, no security updates have been released for a while.
Exchange 2010 SP2 goes out of support next month. please plan to update to SP3 for Exchange 2010.
http://blogs.technet.com/b/rmilne/archive/2013/10/08/save-the-date-end-of-exchange-2003-support-t-minus-6-months.aspx
The details for that, and a link to the lifecycle page are in the above post.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2

Hi,
We are planning cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2.
Requesting you to please help us out for below scenario.
Source Exchange 2010 SP2:- abc.com
2AD, 2CAS & 2 MBX servers
Database:- 4
Total Users :- 3500
Accepted Domains :- 8
Total Data:- 5TB +
Target Exchange 2010 SP2:- xyz.com
Resource allocated same as above.
Now we have to migrate users along with data to target forest xyz.com keeping both setup live, as moving 5TB + data will be a ongoing process and the same will take some time.
With the guidelines mentioned in
http://careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/#comment-14203 we are able to migrate test users along with data, but after migration the migrated user is not able to connect through MS Outlook even not able to login into
OWA. It gives error “The Outlook Web App address
https://mail.abc.com/owa is out of date.”
Kindly let us know how to solve this issue.
Kindly let me know if you want any more information from our end.
Thanks in advance.
Thanks and Regards, Shashank Kudi

Hi Shashank,
Do you have certificates properly installed and configured in the target Exchange?
If not, Please configure certificate and import the certificate to the trusted root CA if you are using internal CA cert.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Error 1603 when installing Rollup 4 for Exchange 2010 SP2

Hi There,
I have began upgrading our Exchange servers to Rollup 4 for Exchange 2010 SP2 last week and the first 3 servers all successfully installed it without any problems. However I have hit a problem with my 4th server.
I am receiving the 'common' error 1603 in my Application log and I have already ran through many potential fixes to this problem on various posts on this and other forums, but to no avail.
I have tried the following without success:
Turning off UAC
Running from elevated CMD prompt
Running from elevated Powershell command
Removing and re-adding "Exchange Trusted Subsystem" from the Administrators group
Re-downloading the RU4 install package to the local disk on the server
Adding more RAM and CPU resources
I have watched the installation process and it seems to update of the native assembly files and comes to the "Starting Services" process, with which it appears to do fine as I have watched the Services starting within Server Manager while this has been running,
but then all of a sudden just begins "Rolling back actions".
The only difference with this server to the others is the fact that a colleague of mine had to recover this server within the last 6 months and ran the Setup /m:RecoverServer command
to do so, could this have anything to do with it?
I have installed Exchange 2010 Service Pack 2 on this server since the recovery though.
I am running out of ideas so any help would be greatly appreciated.

skippy-85,
Any updates on this Issues?
In case if the issue stands
resolved, Please mark Solution for this Thread and close this.
In case if you still have
the issue with the RU4 installation do let us know!
Thanks
Exchangeexperts.in ~ ( Exchange | 2003/2007/2010/E15(2013)) ~Mark this if Helpful~ This Information is provided "AS IS" and confers no Rights!!

Exchange 2010 SP2 : Log Sequence Missing...

Hi Friends,
Recently we configure EMC Networker backup in our environment. but somehow it's not running incremental backup. when we send logs to EMC they reply some log sequence is missing. how i can fix this issue. can anyone help me.
I am using Exchange 2010 SP2
DAG Environment
Two Hubcas Server with two seprate Mailbox servers (Active and Passive)
Few logs are below...
18/05/2014 16:01:40
Mailbox.domain.local nsrsnap_vss_save NMM .. Possible loss of log data. For database DB-2GB-1, the current log file on disk is E01000D779E.log -- 882590. Previous log file backed up was E01000D6B22.log -- 879394.
Mailbox.domain.local nsrsnap_vss_save NMM .. Log file gap detected from previous backup to current for APPLICATIONS:\Microsoft Exchange 2010. Promoting this saveset to FULL.
Mailbox.domain.local nsrsnap_vss_save Save set name APPLICATIONS:\Microsoft Exchange 2010 is valid.
19/05/2014 16:01:18
Mailbox.domain.local nsrsnap_vss_save NMM .. Possible loss of log data. For database DB-2GB-1, the current log file on disk is E01000D8741.log -- 886593. Previous log file backed up was E01000D78AD.log -- 882861.
Mailbox.domain.local nsrsnap_vss_save NMM .. Log file gap detected from previous backup to current for APPLICATIONS:\Microsoft Exchange 2010. Promoting this saveset to FULL.
Mailbox.domain.local nsrsnap_vss_save Save set name APPLICATIONS:\Microsoft Exchange 2010 is valid.

Hi,
Please make sure the Microsoft Exchange Server Extension for Windows Server Backup service running fine.
Please also try to collect some App log for the further troubleshooting.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook 2013 cannot connect to Exchange 2010 SP2 server, Outlook 2010, OWA work fine. Ideas?

After upgrading a laptop from Outlook 2010 to 2013 it can no longer connect to our Exchange 2010 SP2 environment. OWA works, Outlook 2010 works, but Outlook 2013 will not create a profile via AutoDiscover. The first two checks go, the last check
Log On To server will not.
We can take the laptop to a different network and it works fine with Outlook 2013.
What is different with Outlook 2013 where it will not connect.
Jason Meyer

Does it work when we recreate a new Outlook profile?
At this point, We high recommand that we run Microsoft Connectivity Analyzer Tool from the folloing link to check what was happening
https://testconnectivity.microsoft.com/
Cheers,
Tony Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please contact
[email protected]

Unity 5.0 compatibility with Exchange 2010 SP2?

Similar Messages

Maybe you are looking for