Exchange 2013 Co-existence Post Installation Tasks

Hello,
I recently installed Exchange 2013 binaries on 2 new 2012 r2 servers for a migration. Our existing environment is 2010 sp3 and Outlook 2010/2013. After extending the schema, preparing the forest/domain and installing binaries on the new servers (cas and
mailbox), some Outlook clients received certificate warnings. I am assuming the new servers are using a default self signed certificate and will require our 3rd party public certificate installed. Is this normal after installing binaries even without configuring
2013? What would be the next steps? Right now the servers are powered off to avoid end user disruption.

Hi,
Please have a look in to the below mentioned points and the blogs .
Checklist :
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
http://msexchangeguru.com/2013/12/17/exchange-2013-migrationchecklist/
1.You can use the same exchange 2010 SAN certificate in exchange 2013.But the condition is you should have to use the same namespaces available on the SAN certificate during exchange 2013 namespace and URL'S configuration.
Export the SAN certificate with key in exchange via mmc and import it on exchange 2013 cas servers .Then you need to enable the certificate for the exchange services like iis,pop,imap and smtp.
Note :If you have LB you need to install the SAN certificate on LB with intermediate certificate also.
2.Then you need to configure the virtual directory URL'S name as same as exchange 2010 .
3.Then you can redirect all the connections to exchange 2013 by re pointing the autodiscover record to exchange 2013 cas servers or else to LB if you have .
4.Then move one test mailbox from exchange 2010 to exchange 2013.
If anyone of the user who is having an mailbox in exchange 2010 tries to connect the mailbox ,automatically those connections will be proxied from exchange 2013 to exchange 2010 cas server .
So finally all the connections to mailboxes will happen via exchange 2013 cas server or else via LB if you have .
Please reply if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Similar Messages

WSUS reinstall on 2012 SCCM server post-installation task fails to run/finish

I had to re-install WSUS on a 2012 R2 SCCM server (Windows 2012), and am running into several issues re-installing. It may help to point out that the SCCM SQL server is remote, so this isn't a WSUS / SQL 2012 issue.
The sticky post at the top of the WSUS forum has helpful troubleshooting information, and I have tried going through this as well as many other threads on this very topic of re-installing WSUS.
1. Roles for WSUS and WID were removed successfully. The WSUS Website was manually deleted from IIS. As this is a SCCM server, removing the IIS role is not an option.
2. I removed the existing WID database files for SUSDB
3. After rebooting, I verified registry keys were gone, system files were cleaned up, and deleted the program files\update services directory
4. This isn't a permission issue, as I have clearly installed this before on this server.
5. Registry keys, system files, and susdb files no longer exist, and the server has rebooted cleanly.
6. I am able to add the WSUS role selecting WID, and this installs WID without any errors. At this point, simply clicking the post installation task fails, generates an empty .tmp file in my %appdata%\temp folder, and exits the MMC.
7. This file is blank. Absolutely empty, so I couldn't really troubleshoot any post installation tasks.
8. Further investigation shows that the 'C:\Program Files\Update Services\Tools\' directory is gone, and isn't being
generated.
9. Ok... DISM /online /Cleanup-Image /Scanhealth didn't return any issues, so I copied the wsusutil out of the windows\WinSxS directory.
10. Yey! wsusutil postinstall runs, but bombs out on the IIS portion. It generated the DB without an issue, but results
in an IIS generation error. So, I installed WSUS on a clean 2012 install, then copied over the program files\updateServices directory to reclaim the missing files.
The log files show --
2013-12-06 10:30:34 Configuring IIS...
2013-12-06 10:30:35 Start: ConfigureWebsite
2013-12-06 10:30:36 Configuring website on port 8530
2013-12-06 10:30:39 System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Microsoft.UpdateServices.Administration.UseCustomWebSite.ExecuteIisCustomAction(String arguments)
at Microsoft.UpdateServices.Administration.UseCustomWebSite.Install(Int32 portNumber)
at Microsoft.UpdateServices.Administration.UseCustomWebSite.InstallAndConfigure(IisConfiguration& iisConfiguration, Int32 newPortNumber)
at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)
at Microsoft.UpdateServices.Administration.PostInstall.Run()
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
... ok - tripple checked that network service has permissions to .net and windows\temp folders.
netstat -a doesn't show anything running on port 8530 ( in case this was some weird port check in use)
Which goes back to the missing directory problem -- further net searches show that this is a reoccurring issue for some OOBE... sfc /verifyonly shows ... nothing.
What is left to be done at this point? The missing folders from the program directory seems to be a problem for some with some users right out of the box. I have read many other threads where users just formatted and started over. Not exactly a solution
- any help out there on this issue? Any suggestions to determine what file is missing, or generating the IIS issues?

Part of the post install tasks wanted to download some items including the tools folder.
Can you expand on this please. The WSUS post-install tasks do not download anything, except what is acquired during the initial synchronization with Microsoft.
Because of my group policy the WSUS server was trying to download the updates from itself even though it was not setup yet.
What update(s) was the WSUS server trying to "download"?
In fact, if the WSUS Server was not setup yet (but you already had a GPO in place), then the first issue here was performing deployment steps out of order.
But still.... except for the actual installation binaries for the WSUS Server Role on a WS2008SP2/WS2008R2 system, there's nothing the WSUS server needs to get from either Windows Update or a WSUS server. This scenario is actually discussed hundreds of times
in this forum, but complicating matters, this thread isn't about installing WSUS V3.2 on a WS2008SP2/WS2008R2 system, it's about installing WSUS v65 on a WS2012 system, so I'm a bit confused as to what the actual installation environment is that we're discussing.
I changed the WSUS server to get it's windows updates from Microsoft and then the post install task succeeded.
I'd really like to get some more details about what exactly in the "post-install task" was dependent upon content from WU/WSUS.
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.

Task sequence fails to resume after first reboot - Post Installation Task Sequence

Hi everyone,
I am unable to deploy a Post Installation Task Sequence whenever I add an application to the "custom tasks" folder in the task sequence. If I create a blank Post Installation Task Sequence w/o making any changes, it deploys fine and gives
me a summary page w/ no errors. Just to be clear, Litetouch runs fine when I kick off "cscript litetouch.vbs" from an elevated cmd prompt when logged in as administrator, but after reboot it boots to windows and does nothing.
I know it's not deploying because it's leaving around a mapped drive to the share, a SMSTaskSequence folder and MININT folder on the target machine. My understanding is that those are supposed to get cleaned up by LTIcleanup.wsf at the end of the
task sequence.
The BDD.log doesn't seem to be of much use. The last line of the log says "sms task sequencer already found on c:\minint\tools\x64" and then it does nothing.
FWIW, I'm able to deploy using the standard task sequence and also able to sysprep and capture. The application that I am trying to install is just a batch file that adds the reg key to hide the start menu, then reboot. I am not rebooting in the script,
I'm telling the application to do the reboot in MDT.
I know to a certainty that the target machine (a VM) has been sysprepped and am able to establish a connection to the deployment share so I'm kind of at a loss. Also looked over Keith's FAQ on the subject and couldn't find any similarities to my issue.
Any help is appreciated. I can provide logs if necessary. Thanks!

Well, I created a fresh deploymentshare on a fresh windows server 2012 VM and am still having the same problem. If I create a blank Post OS Installation Task and make no changes, it deploys fine to the target vm (win8.1). If I have an app (chrome)
that I have set to reboot after installation, it always (tested this 30+times) fails to resume the task sequence. I get no final confirmation page and a big mess that I clean up with LTIcleanup.wsf.
The deployment share has full (everyone) permissions to the share and I have full perms set to domain admin group for ntfs. It seems like something goes wrong with the reboot cycle, but autologin seems to work fine with the admin pw so I'm really confused.
Like I said, the bdd.log in c:\windows\temp\deploymentshare doesn't have any errors. I've tested this both on joined and unjoined (workgroup) machines and it makes no difference.
I should note that I can deploy Chrome and other apps sequentially as long as reboots are not involved. So far, I've only had this problem if the reboot occurs with the first application. Haven't yet tested on reboots w/ other apps in the sequence.
FWIW, this is starting to look like this:
https://social.technet.microsoft.com/Forums/en-US/2db5f184-8332-4f63-b1ad-385a6d893f8c/mdt-2013-windows-81-application-install-with-reboot-problem?forum=mdt
Can someone tell me why this might be happening? Is this a bug with this task sequence? Would someone mind testing this to see if there's just something wrong in my environment?
I'd appreciate it. Thanks.

Post Installation task of Enterprise Portal

Subject : During the Post Installation task of Enterprise Portal such as Run Configuration Wizard u201CNWA_01u2026..u201D to u201CNWA_07u2026..u201D for portal system. Run u201CInitial setup of functional unit Development Infrastructure (DI all-in-one)u201D in development portal.
Problem : Can anyone guide me how we are doing ( executing ) task i.e.Run u201CInitial setup of functional unit Development Infrastructure (DI all-in-one)u201D in development portal.What this is step is doing as well as what all the prerequisites for this step.
Work Area : Dev portal with Java stack only.( SP Level is 17)
Please guide me on this step as well as all Configuration Wizard steps( NWA_01 to NWA_07) so that I can finish with the post installation of portal.
Regards
Nilesh

Hi my question has been resolved.

SQL 2005 Upgrade complete! - Post installation tasks questions!

Hi All
I have managed to upgrade our DEV and TST ECC6 systems to SQL2005 (from SQL2000) and so far all seems ok however I have a a few questions and checks I would like some help with. I have included my post installation tasks at the bottom of this post, so you know what I have done.
I have noticed that when I run SGEN I get a short dump LOAD_VERSION_LOST which I am not sure what this means.
If there is anything else I need to do or should do please let me know.
Thanks
Phil
Post Installation Tasks
SQL Queries
exec sp_configure 'show advanced options', 1
reconfigure with override
exec sp_configure 'max degree of parallelism', 1
reconfigure with override
exec sp_configure 'xp_cmdshell', 1
reconfigure with override
alter database <SID> set page_verify checksum
go
alter database <SID> set auto_create_statistics on
go
alter database <SID> set auto_update_statistics on
go
alter database <SID> set auto_update_statistics_async on
go
dbcc updateusage ('<SID>')
go
exec sp_updatestats
go
SAP Tasks
Check SM21/SM50/DB02/ST04/ST22/SICK for any unusual error messages.

Hello,
I want run the below script on SQL 2005, can anyone tell me how I run it in SQL 2005?
exec sp_configure 'xp_cmdshell', 1
reconfigure with override
I need to enable xp_cmdshell in sql 2005
Reg,
SAT

OBIEE 11g post installation tasks in Linux?

Hi,
Do I need to write any script for high availability of OBIEE and web logic servers in Linux? what are the processes to start/stop manually using command? Please give me post installation tasks I need to taken care of.
Thanks
Jay.

Becky,
You need not do any thing additional to have EM running in the OBI 11g instance. Although it is a deployed JEE application, if your Weblogic Server (WLS) is started and up and running then your EM Console should also be up and running.
You say that you are doing everything from the command line. So, start the Weblogic Server then navigate to http://< your server name> : 7001/console
If that comes up then go to
http://<your server name>:7001/em
That is your EM Fusion Console and it should come up as well.
Don't mess with the XML file directly.

Post-Installation task client

Hi
I´ve a doubt with the post-installation tasks of the installation of the sap system. The default clients are 000,001 and 666.
In with client I´ve to realize this tasks?In the client 001 and after that I realize the client copy of the client 000. The changes are cross-client?
More thanks

Hi Ruben,
Please let us know which SAP Product and version you have installed. Because there are seperate set of post installation activities for each Product such as ECC, PI, EP, CRM,SRM etc.
For Ex: If you have installed a ECC system, most of the initial post installation activities such as STMS configuration, SGEN etc need to be done on client 000. This information is very well available in Post installation guides.
If you have installed a PI system, you need to carry most of the PI specific post installation activities in the java UME client i.e by default it is 001. But you can also perform the activities in any custom client by having a client copy and come configuration changes.
Cheers....,
Raghu

Installing Update Rollup 4 for R2. Question of post installation task

I will be installing Update Rollup 4 for Service Manager 2012 R2 on our Orchestrator, Data Warehouse, Service Manager and Portal Server as well as updating the client Consoles.
Following MS article
http://support2.microsoft.com/kb/2989601/en-us?sd=rss#install.
A bit confused about the Post installation tasks. Particularly the following:
Resynchronize System Center Operations Manager mount point data
To resynchronize Operations Manager mount point data after you apply this update, follow these steps:
Disable all the Operations Manager configuration item (CI) connectors in the Service Manager console.
In Windows PowerShell, check the current execution policy by running the following cmdlet:
Get-ExecutionPolicy
If the current execution policy is Restricted, set it to
Remotesigned by running the following command:
Set-ExecutionPolicy –force RemoteSigned
Find the following PowerShell script in your System Center 2012 R2 installation directory:
OMCIConnector_SyncMetadata_UpdateTimestamp.ps1
By default, you should find this file in the following location:
C:\Program Files\Microsoft System Center 2012 R2\Service Manager\PowerShell
Run the following command from the Primary Management server:
PowerShell .\OMCIConnector_SyncMetadata_UpdateTimestamp.ps1
Revert the execution policy to the original value that it had in step 2.
Enable and synchronize the relevant Operations Manager CI connectors.
Make sure that all the mount point data is populated in Service Manager.
I am guessing they are talking about the System Center Configuration Manager Connector but not sure. We don't have a Connector for SCOM. If by OMCIConnector they mean SCOM, then I don't need to worry about this. If would be nice if they would tell
you why you are doing this. I don't even know what "Mount Point Data" is.
Does anyone know if it would cause any problems if I skipped this step? I hate doing stuff when I don't know why I am doing it. For example, step 8 "Make sure that all the mount point data is populated in Service Manager."
What does that even mean?
Also, I cannot even find the PowerShell script they are talking about in the C:\Program Files\Microsoft System Center 2012\Service Manager\Powershell folder so are they talking about SCOM or SCCM?

All of the steps listed refer to the Operations Manager connections. none of these steps relate to the Config Manager connector. If you are not using SCOM, or don't have a SCOM connector, then you can safely ignore these steps.

APEX POST INSTALLATION TASKS

i have upgraded from 1.6 To 2.2 .... the installation was successfully now ...
now i am doing the post installation tasks .. i ahve arrived here and i got this problem
E:\oracle\HTML_DB\dcm\bin>dcmctl updateConfig -ct ohs
ADMN-202045
An exception occurred while constructing the OracleAS Repository API, a DCM depe
ndent component.
Resolution:
This exception may be occurring because the ias.properties file is misconfigured
Check the exception thrown by the OracleAS Repository API for any additional res
olution information.
Base Exception:
oracle.ias.repository.schema.SchemaException
iAS Property could not be found Property Name OIDhost in E:\oracle\HTML_DB\confi
g\ias.properties
oracle.ias.repository.schema.SchemaException: iAS Property could not be found Pr
operty Name OIDhost in E:\oracle\HTML_DB\config\ias.properties
at oracle.ias.repository.local.IASPropertyCache.readValue(IASPropertyCac
he.java:62)
at oracle.ias.repository.IASSchema.init(IASSchema.java:234)
at oracle.ias.repository.IASSchema.<init>(IASSchema.java:200)
at oracle.ias.repository.SchemaManager.<init>(SchemaManager.java:145)
at oracle.ias.sysmgmt.persistence.SeedDbAccess.<init>(Unknown Source)
at oracle.ias.sysmgmt.persistence.SeedDbAccess.getDbAccess(Unknown Sourc
e)
at oracle.ias.sysmgmt.persistence.SeedDbAccess.getDbAccess(Unknown Sourc
e)
at oracle.ias.sysmgmt.clustermanagement.ComponentTypeFactory.init(Unknow
n Source)
at oracle.ias.sysmgmt.task.InstanceManager.sysInit(Unknown Source)
at oracle.ias.sysmgmt.task.InstanceManager.init(Unknown Source)
at oracle.ias.sysmgmt.cmdline.DcmCmdLine.checkInit(Unknown Source)
at oracle.ias.sysmgmt.cmdline.DcmCmdLine.execute(Unknown Source)
at oracle.ias.sysmgmt.cmdline.DcmCmdLine.main(Unknown Source)
E:\oracle\HTML_DB\dcm\bin>

Bounced,
I am having the same issue.
Ant.

Exchange 2013 co-existence with Exchange 2010 proxying issue.

Hello,
I am testing Exchange 2010 and Exchange 2013 co-existence in my test lab at the moment, with
a view to migrating our production environment to 2013 later in the year.
The lab is setup, and the problem I'm having is that internal Outlook clients cannot open
their respective mailboxes once the 2013 CAS server is introduced into the mix.
The
setup is listed below:
EXCHANGE 2010 Servers
TESTLABEXCH01 - CAS,HT,MBX - Exchange 2010 SP3
TESTLABEXCH02 - CAS,HT,MBX - Exchange 2010 SP3
Both servers are part of a CAS Array - casarray01.testlab.local
Both servers are part of a DAG - DAG01.testlab.local
RpcClientAccessServer on all 2010 databases set to casarray01.testlab.local
The A record for casarray01.testlab.local points to the IP of the VIP of a load balancer.
The loadbalancer serves
the following ports: 25,80,443,143,993,110,995,135,60200,60201
OutlookAnywhere is enabled on both servers:
ClientAuthenticationMethod : Ntlm
IISAuthenticationMethods   : {Basic, Ntlm}
Internal and external mail flow works without issue before the 2013 server is introduced.
Internal and external client access works without issue before the 2013 server is introduced.
Part Two to follow.....
Matt

EXCHANGE 2013 Servers :
TESTLABEXCH03 - CAS,MBX - Exchange 2013 SP1
OutlookAnywhere is enabled on the server:
ClientAuthenticationMethod : Ntlm
IISAuthenticationMethods   : {Basic, Ntlm}
RpcClientAccessServer on all 2013 databases set to casarray01.testlab.local
(This an inherited setting I assume from the pre-existing 2010 organization)
Split DNS is in place and all internal/external URL's point to either:
autidiscover.external.com
mail.external.com
The A record for the mail.external.com points to the IP of the load balancer VIP
The CNAME record for autodiscover.external.com points to mail.external.com
When the TESTLABEXCH03 is added to the load balancer config,
and given highest priority this is when the Outlook clients stop working.
Any existing profiles in Outlook 2010/Outlook 2013 can no be opened as there is a persistent
credentials prompt.
Upon trying to create a new profile, the process errors when reaching the "Log onto server"
stage and again prompts for credentials.
Running the test-outlookconnectivity cmdlet from
either of the 2010 servers produces the following results.
[PS] C:\Windows\system32>Test-OutlookConnectivity -Protocol:http
ClientAccessServer   ServiceEndpoint
Scenario                            Result Latency
TESTLABEXCH02 autodiscover.external.com    Autodiscover:
Web service request. Success 343.20
TESTLABEXCH02 casarray01.testlab.local       RpcProxy::VerifyRpcProxy.
Success    0.00
TESTLABEXCH02 casarray01.testlab.local         RFRI::GetReferral.
Failure   -1.00
TESTLABEXCH02 casarray01.testlab.local        NSPI::GetProfileDetails.
Failure   -1.00
TESTLABEXCH02 casarray01.testlab.local
Mailbox::Connect.                   Failure   -1.00
TESTLABEXCH02 casarray01.testlab.local
Mailbox::Logon.                     Skipped   -1.00
If remove the 2013 CAS server from the loadbalancer config and
all connections go directly to the 2010 servers again, all of the above tests pass and Outlook connectivity is also restored.
IIS has been reset on all 3 servers incidentally, following any changes made whilst troubleshooting.
I'm struggling to see what I'm missing here, if anyone can assist in troubleshooting this
matter further, or point out any errors in my setup it would be greatly appreciated.
Regards
Matt
Matt

Wsus server 2012 r2 fails to launch post-installation task

wsus server 2012 r2 faild to launch post-installation task
please help i attach a photo with log , this is a brend new domain contoroller of a brand new domain.
i installed th wsus from server manager .
this is the log :
2014-05-01 13:17:51 Postinstall started
2014-05-01 13:17:51 Detected role services: UI, WidDatabase, Services
2014-05-01 13:17:51 Start: LoadSettingsFromXml
2014-05-01 13:17:51 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2014-05-01 13:17:51 System.TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.Internal.UtilConstants' threw an exception. ---> System.IO.InvalidDataException: Invalid installation directory
at Microsoft.UpdateServices.Internal.SetupInfo.GetInstallDirectory()
at Microsoft.UpdateServices.Internal.UtilConstants..cctor()
--- End of inner exception stack trace ---
at Microsoft.UpdateServices.Administration.PostInstall.GetConfigValue(String filename, String item)
at Microsoft.UpdateServices.Administration.PostInstall.LoadSettingsFromXml()
at Microsoft.UpdateServices.Administration.PostInstall.Initalize(Parameters parameters)
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: The type initializer for 'Microsoft.UpdateServices.Internal.UtilConstants' threw an exception.

the installion location is the default installion path - C:\Program Files\Update Services
the content folder was directed to a diffrent volume - e:\wsus\
i tried to delete everything that connected to iis and wsus and re install and now i am getting:
2014-05-05 12:05:33 Postinstall started
2014-05-05 12:05:33 Detected role services: UI, WidDatabase, Services
2014-05-05 12:05:33 Start: LoadSettingsFromXml
2014-05-05 12:05:33 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2014-05-05 12:05:33 System.TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.Internal.UtilConstants' threw an exception. ---> System.IO.InvalidDataException: Invalid installation directory
at Microsoft.UpdateServices.Internal.SetupInfo.GetInstallDirectory()
at Microsoft.UpdateServices.Internal.UtilConstants..cctor()
--- End of inner exception stack trace ---
at Microsoft.UpdateServices.Administration.PostInstall.GetConfigValue(String filename, String item)
at Microsoft.UpdateServices.Administration.PostInstall.LoadSettingsFromXml()
at Microsoft.UpdateServices.Administration.PostInstall.Initalize(Parameters parameters)
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: The type initializer for 'Microsoft.UpdateServices.Internal.UtilConstants' threw an exception.

Exchange 2013 (co-existence 2007) - 2013 mailbox can not connect with Outlook 2010

This was working but after some problems with third party pop3 its been broken. Grrrrrrr
OWA internally works fine for my 2013 test mailboxes. It doesn't work externally yet because I have yet to cutover to co-existence. (Still pointing to the 07 CAS externally)
Internally Outlook 2010 is working for 2007 users. But for my three test 2013 mailboxes it is not. Outlook 2010 is patched to the correct level (even tried sp2)
It finds the user name - finds the server but refuses to authenticate. I have checked the outlook anywhere url on the 2013 server and I get the correct urls- internal and external set the same. I have set the service control point for autodiscover
on 2013.
Now I haven't yet cut over externally to 2013 - and my internal urls for OWA are still set to webmail. But the legacy name exists and is set internally for all others. Authentication? basic externally NTLM internally
Where do I start looking. .

Hi
Did you try running ExRCA test ?
If you have tried whats the result for EXRCA?
Do you have a valid Certificate assigned for Exchange 2013 ?
Do you have a valid cert principal Name for Exchange 2013 ?
Do you get any errors while trying to open outlook for test migrated users ?
If so can you paste the errors
You can also use test-outlookconnectivity cmdlet to test connectivity and see the results for any errors
Note :The outlook that you are using should patched with latest patch at-least with Nov 2013 patch.
Since Exchange 2013 has minimum requirement on the outlook version. Also check the authentication for Outlook Anywhere should be NTLM in co-existence mode of Exchange 2007 and 2013.
you can verify them using ps Get-OutlookAnywhere | fl and check the Authentication method for external and internal.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on www.exchangequery.com

Post installation tasks after rapidwiz

what are the post instllation taskes needs to perform after installation.
On Windows XP machine all services related to E Business Suite not started automatically.
We are getting error http 404 not found every time.
After instllation we were able to login in apps only one time, after that we are unable to login page.

I checked the log Only two lines are written in the log.
Following text written in both lines
process manager initialized.
OracleVIS_localhost_ToolsTNSListenerAPPS_IVS not started, when I tried to start it manually by the help of services it gives errors Service on localcomputer started then stopped.
And when I tried to start listener from command prompt it says __"*procedure entry point snlinAddrLocalhost could not be located in dynamic link libaray oranl10.dll."_*_

Update Exchange 2013 CU5 to CU7 - Installation Order

Hi,
I have a multi-site, multi-DAG, Exchange 2010 and Exchange 2013 CU5 installation. All servers are multi-role. We are about to commence a server update to CU7 for all of the Exchange 2013 Servers.
What is the Microsoft supported order in which to upgrade the servers?
Can I do the upgrades over a number of nights, does everything need upgrading together, should I do it site at a time or a DAG at a time?
Are there any TechNet articles which explain the supported method? It is important that during the update to CU7 the installation stays in a supported configuration.
Thanks in advance.

Hi,
As Andy suggested, you need to upgrade Mailbox servers and then upgrade Client Access servers. What's more, if your DAG have more nodes, at first, you need upgrade all non-PAM nodes and then upgrade PAM node.
Here is a helpful blog for your reference.
How to Apply Exchange Server 2013 RTM to Cumulative Update 1 (Note: Though it is upgrading from Exchange RTM to CU1, it also applies to upgrading from Exchange 2013 CU5 to CU7 about the required order issue.)
http://blogs.technet.com/b/justin_gao/archive/2013/04/09/you-need-to-know-how-to-apply-exchange-server-2013-rtm-to-cumulative-update-1.aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 co-existence with 2007 can not send from 2013 - receives OK

2013 SP1 -separate servers for MBX and CAS - 4 of each. Exchange 2007 configured as a CCR
I am in co-existence mode but have not yet switched on the legacy.domainname.com. I have a new certificate installed on all servers - 2007 and 2013 with the legacy namespace included
I can receive on the exchange 2013 servers and can send to exchange 2013 users but cannot send to 2007 users or externally. I have enabled protocol logging and I'm seeing:
2014-04-02T00:57:31.476Z,Outbound Primary,08D1120CF8FEEDBA,0,,10.0.9.1:25,*,,attempting to connect
2014-04-02T00:57:52.521Z,Outbound Primary,08D1120CF8FEEDBA,1,,10.0.9.1:25,*,,"Failed to connect. Winsock error code: 10060, Win32 error code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host has failed to respond 10.0.9.1:25"
The client has a pair of Axway mailgateway appliances (Tumbleweed). We can Telnet between the exchange 2013 servers and the Axways. There is a firewall between these mail gateways and the exchange servers and the following ports were opened - 25,443,465,995,110
I used the existing send connectors from 2007 and just added the mailbox servers to them. I created 2 new receive connectors to match 2 specialist 2007 connectors.
But I still can't send mail. Any suggestions where next to check?

Hi Tony
Based on the protocol logs error looks like there is connectivity problem between Ex2007 and Ex2013
First you can try dropping an email through Telnet from Exchange 2013 to Exchange 2007 to see the message failure happens at which transit.
You can add the IP address of Exchange 2013 in Exchange 2007 default receive connector and vice versa.
Restart the transport service and try sending an email from exchange 2013 to Exchange 2007 and see the results
Also you can try creating a dedicated receive connector for Exchange 2007 in Exchange 2013 and vice versa if the above step does not work
Also try disabling the firewall and see if it helps.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

Exchange 2013 Co-existence Post Installation Tasks

Similar Messages

Maybe you are looking for