Exchange 2013 Schema/AD/Domain Prep/Install & Outlook 2003

Hi
I am in the process of preparing for a migration from Exchange 2010 to Exchange 2013.
75% of our users are on Outlook 2007 Sp3 / 2010
25% of our users are on Outlook 2003.
I understand that Outlook 2003 is not supported for mailboxes on 2013.
However, can I perform the schema/AD/Domain prep and Exchange 2013 install without disrupting Outlook 2003 users?
I can then work on migrating them at a later point.
Many Thanks
Steven

Hi Steven
You can safely run all the schema extensions in preparation to Exchange 2013 setup in your environment.
But when you install the first Exchange 2013 server with the CAS role things will change fast, because you are then in a mixed coexistence scenario, where Exchange 2013 will start running the
show.
The reason why Exchange 2013 does not support Outlook 2003 is documented here:
technet.microsoft.com/en-us/library/jj619283(v=exchg.150).aspx
Outlook 2003 is not supported
To connect Microsoft Outlook to Exchange 2013, the use of the Autodiscover service is required. However, Microsoft Outlook 2003 doesn’t support the use of the Autodiscover
service.
As workaround you can always have you Outlook 2003 connect over IMAP until you get Outlook upgraded.
Even so I would really recommend starting by upgrading your clients and only then consider adding the new Exchange 2013 servers to your infrastructure.
You can confirm the Exchange Server Supportability Matrix here:
technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
A very nice entry on the Exchange team blog about exchange 2013 mixed coexistence and client connectivity:
blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
And here are a couple of articles that might help you prevent some minor bumps on your project:
technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx
msexchangeguru.com/2014/03/02/e2013sp1-installationupgrade/
Hope all of this helps you make the best decision for your environment.
Best regards.

Similar Messages

Exchange 2013 - schema prep (net assambly error)

Setup.exe /prepareschema /IAcceptExchangeserverlicenseterms
gives error: [ERROR] An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default,
so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See
http://go.microsoft.com/fwlink/?LinkId=155569 for more information. ; Any hints how to solve this?
bostjanc

Hello,
According to the above error, exchange setup file is copied from a network location. So please try to unblock "
this file came from another computer and might be blocked to help protect this computer" on properties of exchange setup file.
Please follow the Ed's suggestion to check the exchange 2013 prerequisites.
Here is an article for your reference.
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2013 fails Active Directory Prep

This is a new, new, installation of Windows Server 2012 R2 Essentials followed by Exchange 2013, all on a single server that is also the DC, in a lab environment.   This is to replace an existing SBS2000 installation in a small business.
Server 2012 setup without any significant issues. The first pass at Exchange 2013 resulted in "access denied" when attempting to access the Exchange Management PS and login credentials failure for Exchange EAC (ECP).   After manually
adding the installation Administrator to a number of the Exchange security groups, I was able to access Exchange Manager. I checked that there was a mailbox associated with the Installation Admin ID, attempted to reset passwords and a number of other
things to no avail. I uninstalled Exchange (what a pain).
I reinstalled Exchange. As with the first time, no prerequisite errors and no installation failure alerts.   Again, I could not access Exchange Manager (access denied) or the EAC (login credentials failure).   This time, I was not
able change the security group permissions to gain access to Exchange Manager. Again, checked about everything there was to check on the web and found a reference to Exchange possibly not installing correctly due to lingering entries from the first install.
As I could not access Exchange Manager to perform the uninstall prerequisites, I attempted to manually delete it (nothing to loose at this point), but made the anticipated mess.
Wiped the RAID and started over with a clean sheet install of Server 2012 Essentials-OK. Progressed in the Exchange install prep to "Prepare Active Directory and Domains" (http://technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx)
and stopped when I could not detect the confirming ADSI entries of AD prep set forth at the close of the TechNet document.
I methodically stepped through the install procedure and again received no prerequisite failures or installation failure alerts. I examined the install logs and found no errors, either.
Any words of wisdom?

Hi,
From your description, Windows Server 2012 R2 Essentials and Exchange 2013 are installed on a single server that is also the DC.
Microsoft does not support installing Exchange Server on a server that is running Windows Server Essentials. You need to install Exchange Server on a second server and then join the second server to the Windows Server Essentials domain.
And it is not recommended to install Exchange server on DC.
Here is a related article for your reference.
Integrate an On-Premises Exchange Server with Windows Server Essentials
http://technet.microsoft.com/en-us/library/jj200172.aspx
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 Two different Domains

hi guys
i am having Exchange 2013 on a production, our domain is domain1.com
i need to know if it possible to have two domains assign to the users over the exchange 2013
like user A will be able to have domain1.com and domain2.com
Domain1 and domain2 are a pop accounts wich will copy the emails from a external pop server.
domain1.com is working fine for users
much appreciate it

ok julian lets take one by one...
you mean i can configure user 1 to send with [email protected] and user2 with [email protected] ? on the same domain controller ?
Jatin: yes you can do this, but both the domains will have shared calender, address book and other resources. this kind of thing is basically done in case of group company environments where you have multiple sister companies and all need their seperate
email address. on single exchange server. so this is possible
and create Domain user with different name just to log in to the AD but send emails with different email adres ?
Jatin: AD login will always be with the primary domain create when installing AD.
can i create two adress policies on one exchange and specify each one to each user?
yes, and then apply to a OU with one OU having users from company1 and others form company 2. you can also apply two policies to one user. just in case
can i create two accepterd domain ? or just one with two different format ?
Jatin: you can create two accepted domains, so your mail server will then start receiving email from other domains also. for email address login on OWA/ECP you can add one more UPN suffix under AD domain and trust. once this is done and logon changed in
AD users and computers then users can log in to owa with their OWN company domian ID and they dont have to use primary domain to log in to OWA or outlook
Mark as useful or answered if my replies helped you solving your query.
Thanks, Happiness Always
Jatin
Skype: jatider2jatin, Email: [email protected]

530 5.7.1 Client was not authenticated - Exchange 2013 to external domains

Hi all,
I have an Exchange server 2013 on windows 2012 R2 and do all the configuration for sending and receiving the mail according to the document provided by Microsoft.
But whenever I am trying to send mails from external domains to my exchange server domain I got the following error:
530 5.7.1 Client was not authenticated
Same thing I am getting If I am sending mail through outlook from my Exchange domains to external domain.
But if I am selecting the
<label for="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers" id="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers_label">Anonymous
users in the security option of Default Frontend XXXX, I am able to send the mails through outlook.</label>
<label for="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers" id="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers_label">But I don't
want to use this option as it will enable to send the mails without validating the Exchange server user name and password.</label>
SO can anyone please suggest some solutions to resolve this as using Anonymous users fro sending and receiving mails is not secure.
Regards
Pankaj Raman.
<label for="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers" id="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers_label">
</label>

I have a java code for sending mails using the SMTP address of the servers. For sending a mail it required a valid user name and password. For all other SMTP servers if I have used invalid user name and password then I am getting the 530
5.7.1 Client was not authenticated error, but
if I am using my SMTP address and invalid user name and password then also I am able to send the mails.
So I just want to know what I have to configure in the exchange 2013 server so that it will validate the user name and password.
Regards
Pankaj Raman.
Hi Pankaj,
Thank you for your question.
Was invalid user name and password included in Java code?
Did outlook send emails?
If this issue happen on Java code instead of outlook?
In fact, Exchange server didn’t validate user account and password, user account and password will be validated on domain controller,
I suggest we create a new dedicated receive connector and enable “anonymous” permission for java code
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

I wasn't prepared for this task, and it was thrown at me to do... Eyes are bleeding from planning reading and planning, would LOVE any input from you guys. First time posting, here and have heard great things about these forums. The Company
I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
Scenario:
Old Domain/Server: (To be decommissioned)
Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
Exchange 2003 SP2 (6.5.7638.1)
Server is a domain controller and exchange server.
Migrating to:
Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality
VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
These are probably not ideal conditions, but I have to work with what I'm given.
Host server (2012 R2) is in work group mode. Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2. I had intended starting at a lower functionality level and raising
it later, but.... ya I forgot to change it. If needed I can spool up a new DC with a lower functional level.
DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain. The concern is migrating the mailboxes from Exchange 2003 on the old domain to
Exchange 2013 on the new domain. The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
I had some ideas, but I'm not sure if they will work. This is something I have never done before (Senior Engineer Quit).
My thoughts:
- Establish a two way trust relationship between the two domains.
- Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
- Create the users on the new domain
- Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013
- Link Exchange accounts to the correct user accounts on the new DC.
Can this be done cleanly? Am I going about this the correct way? Any feedback would be GREATLY appreciated.
Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

Hi,
Base on my experience, your idea is feasible.
However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link:
http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
Best regards,
Niko Cheng
TechNet Community Support

Can I run Exchange 2013 Schema more than once

I have started in installing Exchange 2013. I ran schema update using the Exchange 2013 RTM. Should I go ahead and install Exch2013 RTm and just run the updates afterwards or should I run schema update again using the Exch2013 SP1 setup.exe?

Exchange 2013 CU5 is the latest one so if you haven't installed Exchange yet, I would suggest you to run the schema update again for
CU5 and then install instead of installing RTM first...
But if something is blocking you to run Schema upgrade again currently then you can go for Exchange 2013 RTM install too, only thing is you would end up spending double time installing and upgrading and fighting with known bugs between RTM and CU5...
Blog |
Get Your Exchange Powershell Tip of the Day from here

Deploy Exchange 2013 in multiple domain scenario

I currently have an AD forest abc.com under which there are 2 domains def.abc.com and ghi.abc.com. Exchange 2013 is deployed in domain ghi.abc.com. Now I want to add a third domain jkl.abc.com and use exchange 2013 for it. I want to use the same exchange
which is currently deployed in ghi.abc.com by adding new servers and use the same namespace etc. Do I need to do anything special for it or just add servers and start creating mailboxes.

Hi Gaurav,
You need to prepare the domain to accept the exchange organization into it. (Note you can't have a seperate exchange org, it will be conencted to the existing org, but with different user scope)
Make sure to follow the full preparation steps as in for the first exchange deployment.
Prepare Active Directory domains
The final step to get Active Directory ready for Exchange is to prepare each of the Active Directory domains where Exchange will be installed or where mail-enabled users will be located. This step creates additional containers and security groups, and sets
permissions so that Exchange can access them.
The account you use needs permissions depending on when the domain was created:
Domain created after PrepareAD was run If the domain was created
after you ran the PrepareAD command in step 2 above, then the account you use needs to 1) be a member of the Organization Management role group and 2) be a member of the Domain Admins group in the domain you want to prepare.
Wait until Active Directory has replicated the changes made in step 2 to all of your domain controllers. If you don't, you might get an error when you try to prepare the domain.
When you're ready, do the following to prepare an individual domain in your Active Directory forest for Exchange.
Open a Windows Command Prompt window and go to where you downloaded the Exchange installation files.
Run the following command. Include the FQDN of the domain you want to prepare. If you want to prepare the domain you're running the command in, you don't have to include the FQDN.
Setup.exe /PrepareDomain:<FQDN of the domain you want to prepare> /IAcceptExchangeServerLicenseTerms
Repeat the steps for each Active Directory domain where you'll install an Exchange server or where mail-enabled users will be located.
Below info is bit old, but should still hold true:
To install Exchange on a server in a child domain:
Log on to the server in the child domain using the account that has been granted the Exchange Full Administrator role for the organization.
Run Setup from your Exchange CD-ROM. The Setup.exe file is located in the Setup\i386 folder on the Exchange CD-ROM.
Note If you are joining an existing Exchange site, the account that you use to log on must have the following permissions to access the Exchange Server directory:
Exchange must recognize the site services account name and password.
The Exchange Server site naming context for the Exchange Server site you want to join.
Admin role on the Exchange Server configuration naming context for the Exchange Server site that you want to join.
A two-way trust is required between the domain where you are installing Exchange and the domain where the Exchange Server computer exists.
https://social.technet.microsoft.com/Forums/exchange/en-US/c9c11765-0d2c-4dd2-9258-5fc8c5015570/installing-exchange-2010-for-the-child-domain-only
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 2013 Mailbox Replication Service not installed

I have two Exchange 2013 Exchange CA servers running in a HA/Load Balance environment. Both are missing the Mailbox Replication Service. I didn't have any errors at any point during my installation. I look at the list of services on the
server and they're simply not there.
If I go to c:\program files\Microsoft\Exchange Server\v15\Bin the exe and config files are there. I tried just clicking the exe, but nothing changed. I need to be able to import mailboxes, so this is critical. I'm sure it is critical for
other reasons too.
Anything I can do here?

Hey,
It's a default behavior in Exchange 2013. Mailbox Replication service runs on MBX server role. You can review architecture of Exchange 2013 on below mentioned link.
http://blogs.technet.com/b/marwahasamir/archive/2012/08/28/what-s-new-in-exchange-2013.aspx
Pls mark this as answer if it resolves your issue. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Exchange 2013 / 2010 coexistence with different public domains

Currently in my organization
1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
1x Exchange 2010 Standard w/SP3 - Mailbox
In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
miles away. We have no IT staff in any of our field locations.
We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
domain.local - Our internal Active Directory domain.
We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
severely underutilized.
Goals for the Exchange migration
My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
final topology is:
2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
1x VM with Exchange 2013 Standard w/SP1 - Client Access
1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
until Exchange 2013 SP3 is released.
Deployment Plan
Install Exchange 2013 on new VMs.
Create CAS Array object.
Configure Exchange 2013 to publish under the new namespace.
Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
Unknowns
My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
since we'll be using the new domain for each mailbox we move.
My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

Hi,
From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013.
About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
Checklist: Upgrade from Exchange 2010
Install Exchange 2013 in an Existing Exchange 2010 Organization
Upgrade from Exchange 2010 to Exchange 2013
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Apps for Outlook on Exchange 2013 only work in Safari on Mac OS X (not anywhere else)

With Exchange 2013 SP1, a few "Apps for Outlook" are installed by default. I have not been able to get any of them to actually work... UNLESS I log into OWA from Apple's Safari web browser on Mac OS X. Safari on Windows loads the "lite"
Outlook Web App which doesn't load "Apps for Outlook" at all.
OWA on Internet Explorer 11 lists the apps within the emails, but they don't work (see screenshot). The full Outlook 2013 desktop program lists the apps as well, but again they don't work at all.
Am I missing some sort of configuration on Exchange 2013 that gets these to work on Microsoft's web browser and email client products? It's kind of strange that they work on Apple's products so easily. I've tried Chrome and Firefox on Windows
as well, but those don't work either.

Ah, okay. From the Exchange Management Shell, I did "Get-ECPVirtualDirectory | FL"
AdminEnabled                    : True
OwaOptionsEnabled               : True
Name                            : ecp (Default Web Site)
InternalAuthenticationMethods   : {Basic, Fba}
BasicAuthentication             : True
WindowsAuthentication           : False
DigestAuthentication            : False
FormsAuthentication             : True
LiveIdAuthentication            : False
AdfsAuthentication              : False
OAuthAuthentication             : False
DefaultDomain                   :
GzipLevel                       : Low
WebSite                         : Default Web Site
DisplayName                     : ecp
Path                            : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ecp
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags         : {}
ExtendedProtectionSPNList       : {}
AdminDisplayVersion             : Version 15.0 (Build 847.32)
ExternalAuthenticationMethods   : {Fba}
AdminDisplayName                :
ExchangeVersion                 : 0.10 (14.0.100.0)
All seems to be configured as you say. I didn't change anything, but realized the ExternalURL was pointing to DOMAIN.com/ecp which had a DNS issue, where-as
www.DOMAIN.com and mail.DOMAIN.com were all working. So,
www.DOMAIN.com/owa was working fine on everything (except the Outlook Apps on Windows PCs), but DOMAIN.com/owa was not. Now that DOMAIN.com/owa is working correctly, it seems that Outlook Apps are working correctly
too. I guess even though we are accessing everything via
www.DOMAIN.com or mail.DOMAIN.com, the Outlook/Exchange Apps are still accessing stuff via
http://DOMAIN.com instead (unless the client is using Mac OS X Safari). That sounds like that should be a bug in the way the Outlook Apps are loaded, no?

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Outlook 2010/2013 not able to connect to Exchange 2013

Hi, I'm the midst of co-exist between Exchange 2010/2013. I have issues where none of internal users that migrated to Exchange 2013 not able to connect via Outlook 2010/2013. OWA is running fine without issue. Using MCA, the issue due to port is blocked
but I have verified that firewall on Exchange 2013 server is turn off all.
    1. Exchange 2010/2013 cert is using public CA cert.
    2. Both outlook anywhere external URL for Exchange2010/2013 is set to outlook.domain.com. internal pointing to server.domain.com. while autodiscover is set to autodiscover.domain.com.
   3. user mailbox in exchange 2010 do not have any issue
while if I try to logon, the error look like below:
Cannot open your default e-mail forlders. You must connect to microsoft exchange with the current profile before you can synchronuze your folder with your outlook data file (.ost).
what else should I check ?
many thanks.

Hello,
What server does “outlook.domain.com” and “autodiscover.domain.com” point to, Exchange 2013 FE or 2010 CAS?
You can also do a Outlook Test Email AutoConfiguration by the following steps:
a. While Outlook is running, click the CTRL key and then right-click the Outlook icon in the system tray and then select “Test Email Autoconfiguration”.
b. Confirm that your email address is in the address field, uncheck “Use Guessmart” and “secure Guessmart authentication” boxes. Then click the “Test” button.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

How do i connect manually to Exchange 2013 from Outlook 2007/2010 in another forest?

Hello All,
I have a source organization: Windows 2003 domain + Exchange 2010 SP3 + smtp domain acme.com
Target organization: Winows 2012 R2 domain + Exchange 2013 CU3 + smtp domain acme.com
We are migrating to target organization.
I want to connect Outlook 2007/2010 to their target mailbox (Exchange 2013) from a machine which is joined to Source DOmain.
I couldn't use autodiscover, because as the machine is joined to source domain, autodiscover it's mapping to Exchange 2010.
It only works when I machine is joined to target domain.
Any idea how to connect manually to eXCHANGE 2013 mailbox from a machine which is joined to source domain?
Regards
José Osorio

Hi,
Firstly, I’d like to explain, Autodiscover service can be used cross forest:
1. the two forests must be trusted.
2. configure a mail contact in the original forest.
For more information, please refer to the partition named how to configure the Autodiscover service for cross-forest moves in the following article:
http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx#BKMK_ConfigureForCrossForestMoves
Thanks,
Angela Shi
TechNet Community Support

Creating a New Email address policy for users in another Domain with Exchange 2013 powershell?

Hi
Everyone
Is it possible to create a new-emailaddress policy with Exchange
2013 Powershell, for users within OU´s located on another different
domain/forest than where Exchange 2013 is installed?
There
is a Transitive, two way trust between the domain/forest where the users are
located - and the Exchange 2013, multi tenant domain.
Further
more, and if possible, I need to create linked mailboxes to all these users as
well.
Í have been struckling with this issue for weeks, so please anyone -
advice - and comment.
Best
Regards
Peter
A-ONE Solutions

Hi Siddharth
I want to create a new e-mailaaddress policy - and after that create linked mailboxes/users in my account domain with powershell.
Can you help me achieve that ?
I have a powershell CMDlet, but i doesn´t work. (Cannot fint user OU in my account domain)
CMDlet is as follows:
New-EmailAddressPolicy -Name $CustomerName -RecipientContainer "OU=$CustomerName, OU=kunder, DC=Domain, DC=local" -IncludedRecipients 'AllRecipients' -ConditionalCustomAttribute1 $CustomerName -Priority '1' -EnabledEmailAddressTemplates SMTP:%2g%1s@$AcceptedEmailDomain
Where $Customername = test.dk
and Account domain is = OU=kunder, DC=Domain, DC=local
But the command fails with:
New-EmailAddressPolicy : Couldn't find organizational unit "OU=Test.dk, OU=kunder, DC=Domain, DC=local". Make sure you have typed the name correctly.
At line:52 char:1
+ New-EmailAddressPolicy -Name $CustomerName -RecipientContainer "OU=$CustomerNa
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-EmailAddressPolicy], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : [Server=HE-MBX03,RequestId=2cbe1b51-4af2-4c04-9f7e-e440000975e6,TimeStamp=24-03-2014 12:58:19] 2D00FD2A,Mi
crosoft.Exchange.Management.SystemConfigurationTasks.NewEmailAddressPolicy
So, I cannot find the OU on the Account forest/Domain, even though the OU do exists in the Account domain.
Verifying with this:
Get-ADOrganizationalUnit -Identity "OU=$CustomerName,OU=kunder,DC=Domain,DC=local" –Server ‘DC01.domain.local’| FL
This works fine, Can you please help/assist?
Peter

Exchange 2013 Schema/AD/Domain Prep/Install & Outlook 2003

Similar Messages

Maybe you are looking for