Renaming domain with Exchange 2013 installed in AD

Hello, 
We installed Exchange 2013 into a Windows 2003 Domain (Forest and Domain are Native 2003).  The internal FQDN is for example internal.local  and the external FQDN is external.com. 
We created a certificate request in exchange that included both the internal and external FQDN’s for a 5 domain UCC certificate from godaddy.com.  When requesting the cert all
of the .local addresses were removed (was 10 domain names but who wants to pay more).  When we install the certificate on the exchange server and assign services to the certificate, OWA works externally without issue but internally OWA and outlook do
not work (certificate errors).
Is the following our only course of action or do we have another option?
Un-install Exchange (we’ll backup the user mailboxes via pst file as there are less than 10 mailboxes)
Rename the domain
Install Exchange 2013 again
Re-build the mailboxes

As others mentioned, it would not be a good idea here to rename your domain. It would be better to review the DNS names used internally to make sure that they are in the scope of the used certificate. You might consider using a split-DNS setup for internal
users if the certificate you use contains only external DNS domains.
For renaming an AD domain, you can refer to that: http://technet.microsoft.com/en-us/library/cc738208(v=ws.10).aspx
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password

Similar Messages

  • 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

  • How to setup Autodiscovery for .local internal domains with Exchange 2013

    Hi,
    I need to know about how i set autodiscovery in local domain.I have local domain eg
    abc.local and domin which i received the emails externally is  xyz.com.
    I have deployed Exchange2013 recently with same above scenario inbound and outbound mails are working fine using OWA.But outlook clients cannot connect to Exchange server with in the LAN. 
    Please help me out how set auto discovery in local domain and another help i need how i configure the self sign certificate in this scenario.   

    You cannot use a self signed cert for RPC/HTTP connections (which is how the Outlook client is connecting exchange2013). Please check this http://social.technet.microsoft.com/Forums/exchange/en-US/aed4ede9-57c3-44c3-90b4-bdfb3a7f017d/exchange-2013-self-signed-certs-and-outlook-client-access?forum=exchangesvrgeneral 
    But you can use a certificate from an internal CA which you can install in your network issue a certificate for exchange. Please check this it will help you manage internal certificates for a PC and for a domain.  http://technet.microsoft.com/en-us/library/cc754841.aspx
    You dont need to configure autodiscover for internal domain added clients. If you have clients on the network which are not members of the domain, using Exchange, this could be Windows, MACs or mobile devices, then you should ensure that autodiscover.example.com
    resolves internally to the Exchange server via a split DNS system. http://exchange.sembee.mobi/network/split-dns.asp
    Please configure your external and internal URLs as well
    http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
    I recommend to buy a 3rd party certificate as it may create issue for external clients e.g.Outlook anywhere
    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.

  • SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

    SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The virtual directory 'ecp' already exists under 'server/name'.
    Parameter name: VirtualDirectoryName".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    !! And now transport service won't start and mail is unavailable !!
    Any help would be appreciated.
    I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

    Hi,
    Thanks for your response.
    From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

    Hi guys (and girls)!
    Hear me up. The idea is like this:
    A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
    doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
    Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
    because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
    One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
    with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    bostjanc

    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    already answered by PS CL above
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    Just install the Edge Transport Server and make sure you install ADLDS services.
    as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
    Where Technology Meets Talent

  • Exchange 2010 install with Exchange 2013 present

    Good day,
    I have an Exchange 2010 SP3 instance, I then added a Exchange 2013 installation, the 2010 Exchange needs to be rebuilt due to space issues on the current host and moving the 2010 Exchange will require too much downtime.
    The issues that I am running into is when installing the new instance of 2010 on the new host with the Exchange 2010 x64 SP1 ISO, I am met with the following error:
    [08/22/2014 07:09:03.0912] [1] 0.  ErrorRecord: The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).
    [08/22/2014 07:09:03.0912] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.InvalidObjectOperationException: The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).
    After some reading I understand that Exchange 2010 must include SP3 to co-exist with Exchange 2013, all the roles have installed without any issues except the client access role, I get the above mentioned error, thus I cant upgrade to SP3.
    I came across a solution where the OAB needs to be removed and then re-created, but unfortunately this will cause too much issues as the OAB is always in use.
    So I am stranded where I need 2010 SP3 to install the server, but as far as I know there is no 2010 ISO with SP3 available.
    Any advice would be appreciated.
    Regards,
    Hendrik

    "So I am stranded where I need 2010 SP3 to install the server, but as far as I know there is no 2010 ISO with SP3 available."
    I'm not sure I understand this? If you download Exchange 2010...
    http://www.microsoft.com/en-us/download/details.aspx?id=36768
    That *is* the SP3 version.
    Otherwise, if you install Exchange 2013 (with no other Exchange 2010 servers present), you definitely cannot add 2010 servers after the fact.
    http://forums.petri.com/showthread.php?t=64056
    But if you started with 2010, then add 2013... I think you can add or replace 2010 servers provided they are at SP3.
    What if you had lots of Exchange servers (a hosting company for example) and had to replace a server member of a DAG? Let's assume some mailboxes have been migrated to DAGs on E2K13 and some are still on E2K10.
    Note: within a particular DAG you cannot have differents versions of Exchange but you could have some DAGs with E2K10 and others using E2K13.
    It would seem that you would have to be able to install a new/replacement E2K10 server in this case? You could not replace it with a E2K13 server.
    Please 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.

  • Can't get OWA to work on Essentials 2012 R2 with Exchange 2013 on second server 2012 R2 std.

    I have previously with success setup a working solution with server 2012 essentials, and a second server 2012 std. with exchange 2013, I did it following this guide: http://technet.microsoft.com/en-us/library/jj200172.aspx
    Unfortunately I lost the server due to a cooling error which led to an un-repairable essentials 2012, since this was a new setup and also a test setup I didn't have any working backup solution setup at the time...tsk.tsk.
    Since I had to make a complete do over I chose to try out the new R2 server editions, and set it up following the same guide, when it came to this part:
    Download KB2732764 for ARR 2.5, and then install the update on the server that is running Windows Server 2012 Essentials.
    Copy the SSL certificate file for Exchange Server to the server that is running Windows Server 2012 Essentials. The certificate file must contain the private key, and it must be in the PFX file format.
    Note
    If you are using a self-issued certificate, follow the instruction in the Exchange Server article Export an Exchange Certificate to export the certificate.
    Open a command window as an administrator, and then open the %ProgramFiles%\Windows Server\Bin directory.
    Based on you installation scenario, follow one of these steps to configure ARR:
    If you are performing a clean setup, run the following command:
    ARRConfig config –cert “path to the certificate file” –hostnames “host names for Exchange Server”
    I noticed that the version of "Application request routing" had changed to version 3, so obviously I didn't need to dl the 2.5 update.. When I came to the part where I wa instructed to run arrconfig config etc. I noticed
    that the ARRconfig file no longer where placed where the setup guide indicated, I then went ahead and tried som manual configuration regarding certificates and such. In the end I have a working solution where Exchange and OWA is working locally but OWA isn't
    working outside my local domain, the link get's placed in the RWA and is indicating the correct link for the exchange server www.remote.clinten.dk I have a certificate which include to separate domain names aforementioned and remote.clinten.dk and
    I get no errors indicating certificate errors, when I try to connect to www.remote.clinten.dk/owa from outside I get a 404 error, and when I connect to www.remote.clinten.dk I get the RWA login screen for the essentials RWA. Obviously I need to set up something
    in ISS probably in the url rewrite section, but I can't seem to find the right setting.. Can someone help with this?
    Btw. I have found the missing arrconfig file in c:\windows\system32\essentials" and tried to run the command as described in the guide "ARRConfig config –cert “path to the certificate file” –hostnames “host
    names for Exchange Server”" but it doesn't seem to work, it just prompts with a guide for using the arrconfig command and examples of correct use, I also tried removing the "" from the guide, like this "ARRConfig
    config –cert path to the certificate file –hostnames host names for Exchange Server",
    when I ran it without the "" It didn't prompt me with anything nor did It indicate any errors, it did not however make my OWA work either..
    I am aware that exchange 2013 atm. isn't officially supported on the R2 server, but the exchange works fine inside my domain, and the pop3/smtp also works from outside, since this Is a test environment, using only my own private domain and not a company
    domain I figured it would be ok to run the risk.. ;)

    Hi
    found this on
    https://social.technet.microsoft.com/Forums/en-US/1f099068-b3ed-44f3-a8c4-c22d760a8621/arr-broken-or-bad-syntax-exchange-2013-essentials-2012-r2?forum=winserveressentials
    "Ok just an update for anyone else how has this issue.
    The problem has been solved by Microsoft and I have included their findings below, but basically it comes down to a typo!
    I often use notepad to have all the commands I need on hand, and I must have copied the command direct from the TechNet article or other website and customised the required fields. The issue with this is one of the characters did not “convert” - for want
    of a better word. I should have retyped the whole command from scratch and it would have been right!
    Thanks for everyone’s input and for Microsoft for getting to the bottom of it.
    From Microsoft:
    We have tested on your environment and here is the investigation result from our senior engineer:
    ================================================================
    Basically the command fails due to invalid parameter, the invalid one is the ‘-‘. I think the one customer used is copied from the online document sample which translate to the unicode is 0x8211 means “en dash”, it
    can’t be input by normal keyboard, so I pretty sure it is from web (mostly HTML document).
    The one we check (compare) is ‘-‘ which has the code 0x45.
    So it always failed to compare the parameter and ARRconfig.exe thought it is invalid parameter.
    The solution is quite simple, just using keyboard to retype the command, using normal ‘-‘ and I have tried the password prompt shows
    Best Regards,
    Johnny Chen
    Microsoft Partner Support Community Technical Support Engineer
    Microsoft Global Partner Services"

  • SBS2008: Move email from Exchange 2007 to new server with Exchange 2013

    We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server. 
    Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one? 
    Old Server:
    SBS2008 running Exchange 2007
    New Server:
    Server 2012
    Exchange 2013
    Any help is appreciated!

    Hi Dave,
    It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
    you in the past).
    For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model.  In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
    up to 2 Virtual Machines on same host).
    There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration. 
    You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration.  But the high points are in here. If it looks
    like something you would be comfortable with then you should research more.
    http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
    Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
    http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
    If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
    and migrate your workstations out of old domain into new domain.  Whether this is more or less work at your workstation count is dependent upon a lot of variables.
    If you have more questions about the process, update the thread and we'll try to assist.
    Hopefully this info answered your original question.
    Cheers,
    -Jason
    Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

  • Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

    Here is the scenario:
    Legacy Host: Windows 2008 R2
    Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
    After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster).  (copy VM files to new 2012 R2host) Everything works fine.
    Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
    of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
    to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
    I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
    Services upgrade.
    Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
    upgrade.
    Thanks
    Gerhard Waterkamp ACSLA Inc.

    Hi,
    Could you try use the following method to fix this issue first?
    1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
     1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
     Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
     http://support.microsoft.com/kb/947821/en-us
    2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
    %SYSTEMROOT%\Logs\CBS\
    3. Please paste the checksur.log here for analysis.
    If there is no error found, please try the following step.
    ==================================
    2. Use Fix it tool to reset the Windows Update components.
     1. Open the following link.
     http://support.microsoft.com/kb/971058/en-nz
     2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
     3. Click “Run Now” to reset the Windows Update components.
    Note: We can reset the Windows Updates manually by following the steps in the KB above.
    3. Use the System File Checker tool to repair missing or corrupted system files
     1. Open the command promote with Administrators.
     2. At the command prompt, type the following command, and then press ENTER:
         sfc /scannow
    Any errors are found in the steps above, please let me know.
    Hope this helpful.
    Best Regards,
    Jason Zeng
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • 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

  • Cannot write email body in OWA with Exchange 2013 SP1 CU6

    Hi,
    I have a problem with Exchange 2013 SP1 with CU6.
    All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
    The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
    Have you an idea ?
    Thanks in advance!
    Sebastien

    Hi, 
    After contacting Microsoft support, we have found the solution.
    The problem appear after we have recently install the patch described in this KB 2997209:
    https://support.microsoft.com/kb/2997209?wa=wsignin1.0
    But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
    So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
    No need to reboot, or restart IIS, it's working after that!
    @+
    Sébastien

  • Can we connect Outlook with Exchange 2013 with the default Self-signed certificate?

    Hi,
    the question is very simple, but after several days searching in this forums and in the web I have not been able to find a definitive answer YES or NOT. I know that Self-signed certificates are not for a production enviroment and only for labs and we must
    purchase a third party certificate or get one from a internal CA.
    Anyone can answer this question with no doubt?
    Thanks in advance!
    jspt

    Hi Abhi,
    I wrote this question because in a recent migration to 2013 from 2007 we've found with this problem: you can view it in the post http://social.technet.microsoft.com/Forums/exchange/en-US/1ddd1e81-1061-4461-95dd-13de653ef8fe/outlook-cant-connect-with-exchange-2013-after-migration-from-exchange-2007?forum=exchangesvrdeploy.
    Also I have installed a new exchange 2013 in a lab enviroment and I also have unabled to connect from a Outlook 2013. The problem is the same Outlook is unable to detect the exchange server. Many people in this forums told me that have to be a certificate
    problem and for that I posted this question. Honestly, I don't know how to do for Outlook can be connect with Exchange 2013. I don't know what I'm doing wrong.
    Anyway thanks for your answer.
    jspt

  • Lync Server Integration with Exchange 2013

    Hello,
    I have Exchange 2013 standard edition server installed and running successfully on a Windows 2012 machine. Now, I would like to have a Lync 2013 server integrated with it. I came across some links telling that its not possible to integrate Unified Messaging
    in the Exchange standard edition and would need an Enterprise edition license. But, when I checked my ECP, I could see that UM is already there and its enabled. 
    So, Is it possible to integrate Lync 2013 with Exchange 2013 standard edition? What all things I need to take care of while Integrating? If someone could shed some light on this, that would be greatly appreciated.
    Thanks and Regards,
    Nash Burns

    Yes you can integrate Lync 2013 with Exchange 2013 Standard, the only big difference between Exchange 2013 Standard vs Enterprise is the number of mailbox databases (5 vs 50).
    Follow this link for information on integrating the two: http://technet.microsoft.com/en-us/library/jj688098.aspx (specifically integrating Lync with Exchange for Voicemail http://technet.microsoft.com/en-us/library/jj687983.aspx)
    Having said that, the confusion may be related to User CALs. You need Exchange Enterprise User CALs to use the Unified Messaging components. (I believe they still work regardless, but
    to be properly licensed and compliant you need to have the correct number of Enterprise CALs for the number of users that use UM)
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
    www.lynced.com.au | Twitter
    @imlynced

  • Exchange 2007 SP3 RU compatibility with Exchange 2013 lattest CU

    Hi Team,
    I have question, I want to migrate my exchange 2007 to 2013.
    right now exchange 2013 already provide CU7. 
    My question is, is exchange 2013 CU7 compatible with Exchange 2007 SP3 lattest RU (SP3 RU15) ?
    is there any limitation of version if i want to upgrade Exchange 2007 to 2013
    Thanks Before

    Hello,
    The first thing I would say, is that the MINIMUM supported update for Exchange 2007 is SP3 RU 10, so you should be ok with RU15 installed with Exchange 2013 Cu7.
    https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    The second thing I would say, and I am not sure how you're current environment is configured and how you plan on configuring your future environment, but if you are using Public Folders, Exchange 2013 CU7 changes the way public folders are handled during
    coexistence.  I would recommend taking a look at this blog post from The Exchange Team
    https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx 
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • Outlook 2013 with Exchange 2013 keeps giving read receipts

    Hello experts,
    We have an Exchange 2013 server. All users are joint to the domain, except one user (Windows 8.1) which is in a Workgroup, and using Outlook 2013 with IMAP protocol. 
    This particular user is having a problem. When he send's any email from Outlook and requests a read receipt, after that he keeps getting hundreds of read receipts in his inbox. I have tried disabling (for temporarily) the Windows server 2012 firewall,  but
    still having the same issue. 
    Is this a known bug in Outlook 2013 with Exchange 2013? Any help troubleshooting this?

    Hi,
    According to your description, I understand that IMPA account get hundreds of read receipts while he requests a read receipt.
    If I misunderstand you concern, please do not hesitate to let me know.
    Whether are all account or some special user experience this question? Please do a test in external with IMAP account to double confirm.
    How about the “Request a Delivery Receipt”?
    Also, please run message tracking log to get more details about message mail flow:
    Get-MessageTrackingLog –Server “mailbox server” –Sender “[email protected]” –Recipient “[email protected]” –MessageSubject “Read: message subject” | Select Timestamp, ClientHostname,ServerHostname,Source,EventID,Recipients,RecipientStatus,Sender | ConvertTo-Html > “C:\Test\Test.xml”
    Thanks
    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]
    Allen Wang
    TechNet Community Support

Maybe you are looking for