New Exchange 2013 server, reusing name of 2010 servers

Hi,
I've uninstalled my Windows 2008 R2, 2010 Exchange server from the control panel and removed it from the domain.
The computer object still remains in AD though disabled.
I want to re-use the same computer name on a new server build with Windows 2012 R2, 2013 Exchange. 
Do I just delete the disabled object? Do I need to wait sometime before deleting it to allow AD to replicate? Or whats best practise?
Thanks!

A computer object in AD is just an object. You can do anything with it. You can delete it (and it will be recreated when you add a new computer with the same name) or keep it intact (and then a new computer with the same name will attach itself to that object).
Unless your old server was a DC, you needn't any special procedures to follow when deleting its computer object.
Evgeniy Lotosh
MCSE: Server infractructire, MCSE: Messaging

Similar Messages

  • Built-in domain Administrator account not given full access to new Exchange 2013 server

    I migrated from Exchange 2010 to 2013 over the weekend.  I cannot log into the EAC with my domain administrator account I use to log into all my other servers.  I also cannot run the clean-mailboxdatabase cmdlet logged in as this user.  I
    had no trouble moving mailboxes from the old server to the new server with this account though.
    This account is a member of: Domain Admins, Enterprise Admins, Exchange Full Admin, Exchange Organization Admin, Organization Management, Schema Admins, Server Management.
    I can log into the EAC with another admin account that has the same memberships as the Administrator account.
    I tried giving the account the role of "Databases" as suggested by others to fix the clean-mailboxdatabase issue but that did not work for me either.
    The Administrator mailbox has been moved to the new database on the Exchange 2013 server.  The Exchange 2010 has been decommissioned and is turned off.

    Hi,
    Based on my research, to retrieves the mailbox statistics for the disconnected mailboxes for all mailbox databases in the organization, we can try the following command:
    Get-MailboxDatabase | Get-MailboxStatistics -Filter 'DisconnectDate -ne $null'
    http://technet.microsoft.com/en-us/library/bb124612(v=exchg.150).aspx
    Additionally, The Identity parameter specifies the disconnected mailbox in the Exchange database and it can be display name instead of mailbox GUID.
    http://technet.microsoft.com/en-us/library/jj863439(v=exchg.150).aspx
    Hope it can help you.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2013 server to new Exchange 2013 server

    Hello,
    We have a Exchange 2013 server that is hosted outside the company and would like to move the server in house.
    To do this we plan on standing up our own Exchange 2013 server and move the mailboxes and such over to the new server. My question is there any kind of documentation with steps to take to make sure nothing is left behind\missed?
    THank you.
    Tom

    Hi Tom,
    Its two different organization and you need to follow cross forest migration to migrate mailbox from one organization to another. Below links has the details steps to perform cross forest migration for exchange 2010 and you could follow the same step for
    Exchange 2013 as well.
    http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
    http://blogs.technet.com/b/meamcs/archive/2011/10/25/exchange-2010-cross-forest-migration-step-by-step-guide-part-ii.aspx
    http://blogs.technet.com/b/meamcs/archive/2011/10/25/exchange-2010-cross-forest-migration-step-by-step-guide-part-iii.aspx
    Alternatively, you could also use some third party tool like  Exchange Server Manager to perform this task much easier
    http://www.lepide.com/exchange-manager/
    Regards,
    Krishna
    http://smtpport25.wordpress.com

  • First Exchange 2013 server in 2010 Deployment - 2010 edge is routing SOME inbound mail to new server where it fails.

    I have a Barracuda filter receiving all inbound internet mail which delivers to the edge server (both in DMZ).  I have one 2010 edge server and one 2010 ht,cas,mailbox server.   I have added a 2013 server and started working
    on configuring virtual directories.  This is a far as I have gotten. Goal is once new box is working to move all mailboxes to 2013 server and remove 2010 mail box server and keep Barracuda and 2010 edge server to pass mail to the 2013 box.
    My issue is the edge server is already passing inbound internet mail to the new 2013 server.  I see the mail being accepted by the Barracuda and message tracking on the edge shows it as delivered to the new 2013 server, but mailbox
    users never receive.
    Is my solution to simply create a new send connector from the 2013 server to the 2010 box or could this be something else?
    And why is it delivering to a server with now mailboxes on it yet?
    Thank you for any help
    dean

    Hello Dean,
    I understand that the message tracking log indicates the email delivered to Exchange 2013 server. Please check the message tracking log on both Exchange 2013 server and Exchange 2010 server.
    How about the result? Have you created new 2013 mailbox and tested if it works?
    As for the send connector, actually an intra-org send connector will be involved for internal mail flow within an organization. So there is no need to create another send connector.
    In addition, I’d like to share you an article about Edge Subscriptions:
    Title:
    Understanding Edge Subscriptions
    Link:
    http://technet.microsoft.com/en-us/library/aa997438(v=exchg.141).aspx
    Regards,

  • Addition of Exchange 2013 server to Exchange 2010 organization broke Exchange

    This is somewhat of an emergency, since Exchange is down completely for us right now.
    I just migrated from SBS2003 to Exchange 2010 on Windows 2012 over last weekend. Everything is now stable, and SBS2003 is shut down. Now I am attempting to migrate from Exchange 2010 to Exchange 2013.
    The plan was this:
    Install Exchange 2013 on another server (Windows 2008R2)
    Wait until everything is replicated
    Remove the Exchange 2010  server from the organization
    Uninstall Exchange 2010
    Install Exchange 2013 on the Windows 2012 server
    Wait until everything is replicated
    Remove Exchange 2013 from the Windows 2008R2 server
    But here is what actually happened:
    Installed all Exchange 2013 prerequisites on the Windows 2008R2 server
    Began Exchange 2013 server setup on the Windows 2008R2 server. Included both Mailbox & CAS roles
    At step 11 of 15 (not sure what that was, though), received this error message:
    Error: The following error was generated when "$error.Clear();
            netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes   
            " was run: "The term 'netsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
    and try again.".
    And setup halted. I ran the netsh command via the command prompt, and it correctly said something about four rules being created or updated (not sure of exact verbiage). Now, when I try to restart setup, it says it is in the middle and will try to complete
    but stays at 0%. But here is the most immediate issue:
    Now I cannot access e-mail from any workstations (says Exchange server is unavailable)
    Opening EMC on the Exchange 2010 server: I get as far as Microsoft Exchange -> Microsoft Exchange On-Premises and get this error:
    The attempt to connect to http://[Exchange 2010 FQDN]/PowerShell using "Kerberos authentication failed: Processing data from remote server [Exchange 2010 FQDN] failed with the following error message:
    Couldn't find Enterprise Organizaiton container. (Note that it refers to the local server as remote server)
    I get an event 7031 on the Exchange 2010 server: The Microsoft Exchange Service Host service terminated unexpectedly
    Opening the Exchange Management Shell on the Exchange 2010 server yields the same message regarding "Couldn't find the Enterprise Organization container..."
    It also says, "Connecting to [Exchange 2013 server FQDN], then says connected to that server. Opening EMS on the Exchange 2013 server seems to connect correctly to the Exchange 2013 server, but there is no EM Console available there.
    At this point, I am lost. I will continue to research this online but may have to call Microsoft soon, since we are entirely down at the moment. Any help is much appreciated!

    All of the above, I believe. And E2003 is on the DC (and functioning just fine); E2012 on a member server (this is a very small environment--they have only the DC, a DB2 database server, and a lightly-used and old terminal server). I just spent 12 hours
    on the phone with MS support on this issue, and it has now come down to this: the Exchange 2013 installation will not run to completion. It has failed repeatedly at a few points today, all related to the shell being unable to access Windows EXEs or environment
    variables with variations on this error:
    "...not recognized as the name of a cmdlet, function, script file, or operable program..." for each of these:
    netsh (windows exe)
    sc.exe (windows exe)
    hostname (windows command that returns workstation name)
    These all work from the command prompt. I am currently stuck on sc.exe failing on each attempt to install Exchange 2013 or Exchange 2013 SP1. Nor can I just remove it--it insists on attempting to proceed with installation even with the manual command-line
    argument to remove it instead.
    At this point, I am awaiting a night call back from Microsoft support, since the technician that worked on it with me for 12 hours today had to go home.

  • Outlook 2011 for Mac users must click send/receive to get new mail from exchange 2013 server

    I recently switched our primary CAS servers over from a single exchange 2010 cas/mailbox/hub server to a couple new exchange 2013 CAS/Mailbox servers.  Exchange 2013 has cu3, and is hosted on windows server 2012.  Anyone who has their mailbox hosted
    on one of these exchange 2013 servers has an issue where they must click the send/receive button to get new messages downloaded to their client. This is only the case for outlook 2011 for mac client.  Activesync clients, mac mail, OWA, and Outlook 2010/13
    all behave normally.
    Where can I look or what can I check to troubleshoot this issue?

    Hi,
    Any good news from the Mac Forum?
    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

  • ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!

    Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
    users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
    I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
    As you can see from the error above  ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
    virtual folders?!
    What I’m missing here?! Please help.

    Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
    To check whether inheritance is disabled on the user:
    1.Open Active Directory Users and Computers.
    2.On the menu at the top of the console, click View > Advanced Features.
    3.Locate and right-click the mailbox account in the console, and then click Properties.
    4.Click the Security tab.
    5.Click Advanced.
    6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
    Ref:
    http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
    Also check the Virtual directory authentication
    Microsoft-Server-ActiveSync
     •Basic authentication
     •SSL required
     •Requires 128-bit encryption
    Ref:
    http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
    Check the IIS log if you are able to find any error message on it
    Exchange Queries

  • New Exchange 2013 CAS server in existing Exchange 2007 Organization

    Dear Friends,
    We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
    R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
    Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
    https://servername/ecp/?ExchClientVer=15
    Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
    Thanks in advance!!

    Dear Friends,
    We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
    R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
    Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
    https://servername/ecp/?ExchClientVer=15
    Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
    Thanks in advance!!
    If you have only the 2013 CAS installed and not the mailbox role, then nothing will really work. Remember, in 2013, the mailbox role does all the work, the CAS is simply a proxy for the most part.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • First Exchange 2013 server in an Exchange 2010 SP3 organization

    I've read the documentation that states to install Exchange 2013 with CU2 as the first Exchange 2013 server in an organization running Exchange 2010 SP3. Maybe I over-read this to mean "Exchange 2013 with at least CU2" (meaning to start with Exchange2013-x64-cu3.exe),
    but when I installed the CU3 version I ended up with Standard rather than Enterprise. I need to run 2013 with Enterprise. I've looked around for an Enterprise version of Exchange2013-x64-cu3.exe but cannot find one.
    How do I install Exchange 2013 Enterprise into my Exchange 2010 SP3 organization? Thank you.

    Please review
    http://technet.microsoft.com/en-us/library/bb232170(v=exchg.150).aspx
    These (Exchange 2013 Standard Edition and Enterprise Edition)
    licensing editions are defined by a product key. When you enter a valid license product key, the supported edition for the server is established. Product keys can be used for the same edition key swaps and upgrades only; they can't be used
    for downgrades. You can use a valid product key to move from the evaluation version (Trial Edition) of Exchange 2013 to either Standard Edition or Enterprise Edition.
    You can also use a valid product key to move from Standard Edition to Enterprise Edition.

  • Unable to access ECP on a new Exchange 2013 Install

    I have a standalone exchange 2010 server (setup with all roles) and yesterday went ahead to setup an Exchange 2013 Server. Installed both CAS and mailbox roles for Exchange 2013 but after the install, I am unable to access the Exchange Admin Center. 
    If i try to access to https://EXCHANGE 2013 FQDN\ecp , after inserting my login information, it asks for the login information again and redirects to webmail. I have read all posts of users experiencing similar issues and tried all possible measures. 
    As the 2013 coexists with Exchange 2010 and mailboxes still reside on 2010, I have tried the URL
    https://EXCHANGE 2013 FQDN/ecp?ExchClientVer=15 but got the same result.
    Also, the CAS is installed on the server and i see the ECP virtual directory and URL.
    please see below the output for Get-ExchangeServer | FL and Get-EcpVirtualDirectory | FL
    [PS] C:\Windows\system32>Get-ExchangeServer | FL
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    Name                            : NYC-HQXCH-02
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V14\Mailbox
    Domain                          : company.loc
    Edition                         : Enterprise
    ExchangeLegacyDN                : /o=company/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=NYC-HQXCH-02
    ExchangeLegacyServerRole        : 0
    Fqdn                            : NYC-HQXCH-02.company.loc
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : True
    IsClientAccessServer            : True
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : False
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : False
    IsFrontendTransportServer       : False
    NetworkAddress                  : {ncacn_vns_spp:NYC-HQXCH-02, netbios:NYC-HQXCH-02, ncacn_np:NYC-HQXCH-02,
                                      ncacn_spx:NYC-HQXCH-02, ncacn_ip_tcp:NYC-HQXCH-02.company.loc, ncalrpc:NYC-HQXCH-02}
    OrganizationalUnit              : company.loc/NYC-HQXCH-02
    AdminDisplayVersion             : Version 14.3 (Build 123.4)
    Site                            : company.loc/Configuration/Sites/NewYorkHQ
    ServerRole                      : Mailbox, ClientAccess, HubTransport
    ErrorReportingEnabled           :
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        :
    CurrentDomainControllers        : {}
    CurrentGlobalCatalogs           : {}
    CurrentConfigDomainController   :
    ProductID                       : 02064-110-8022196-75756
    IsExchangeTrialEdition          : False
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 00:00:00
    Identity                        : NYC-HQXCH-02
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=NYC-HQXCH-02,CN=Servers,CN=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Guid                            : 1745c93f-419d-402c-b832-708958fc502c
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 4/2/2014 1:50:56 PM
    WhenCreated                     : 8/25/2013 11:12:43 AM
    WhenChangedUTC                  : 4/2/2014 6:50:56 PM
    WhenCreatedUTC                  : 8/25/2013 4:12:43 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    ObjectState                     : Unchanged
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    Name                            : NYC-HQARC-02
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V14\Mailbox
    Domain                          : company.loc
    Edition                         : Enterprise
    ExchangeLegacyDN                : /o=company/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=NYC-HQARC-02
    ExchangeLegacyServerRole        : 0
    Fqdn                            : NYC-HQARC-02.company.loc
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : False
    IsClientAccessServer            : False
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : False
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : False
    IsFrontendTransportServer       : False
    NetworkAddress                  : {ncacn_vns_spp:NYC-HQARC-02, netbios:NYC-HQARC-02, ncacn_np:NYC-HQARC-02,
                                      ncacn_spx:NYC-HQARC-02, ncacn_ip_tcp:NYC-HQARC-02.company.loc, ncalrpc:NYC-HQARC-02}
    OrganizationalUnit              : company.loc/NYC-HQARC-02
    AdminDisplayVersion             : Version 14.3 (Build 123.4)
    Site                            : company.loc/Configuration/Sites/NewYorkHQ
    ServerRole                      : Mailbox
    ErrorReportingEnabled           :
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        :
    CurrentDomainControllers        : {}
    CurrentGlobalCatalogs           : {}
    CurrentConfigDomainController   :
    ProductID                       : 02064-110-8022196-75187
    IsExchangeTrialEdition          : False
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 00:00:00
    Identity                        : NYC-HQARC-02
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=NYC-HQARC-02,CN=Servers,CN=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Guid                            : c07f34f4-92f1-49f0-a412-d7094eaaba3b
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 4/2/2014 1:50:57 PM
    WhenCreated                     : 9/9/2013 3:27:16 PM
    WhenChangedUTC                  : 4/2/2014 6:50:57 PM
    WhenCreatedUTC                  : 9/9/2013 8:27:16 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    ObjectState                     : Unchanged
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    Name                            : SVR-EXCH-01
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox
    Domain                          : company.loc
    Edition                         : StandardEvaluation
    ExchangeLegacyDN                : /o=company/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SVR-EXCH-01
    ExchangeLegacyServerRole        : 0
    Fqdn                            : SVR-EXCH-01.company.loc
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : True
    IsClientAccessServer            : True
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : True
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : True
    IsFrontendTransportServer       : True
    NetworkAddress                  : {ncacn_vns_spp:SVR-EXCH-01, netbios:SVR-EXCH-01, ncacn_np:SVR-EXCH-01,
                                      ncacn_spx:SVR-EXCH-01, ncacn_ip_tcp:SVR-EXCH-01.company.loc, ncalrpc:SVR-EXCH-01}
    OrganizationalUnit              : company.loc/SVR-EXCH-01
    AdminDisplayVersion             : Version 15.0 (Build 847.32)
    Site                            : company.loc/Configuration/Sites/Chicago-COLO1
    ServerRole                      : Mailbox, ClientAccess
    ErrorReportingEnabled           :
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        : DefaultWorkloadManagementPolicy_15.0.825.0
    CurrentDomainControllers        : {}
    CurrentGlobalCatalogs           : {}
    CurrentConfigDomainController   :
    ProductID                       :
    IsExchangeTrialEdition          : True
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 179.06:13:25.2449639
    Identity                        : SVR-EXCH-01
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=SVR-EXCH-01,CN=Servers,CN=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Guid                            : 91eb6d6b-bfd0-4ce0-80ce-67585e7cbeae
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 5/13/2014 6:54:13 PM
    WhenCreated                     : 5/13/2014 6:41:08 PM
    WhenChangedUTC                  : 5/13/2014 11:54:13 PM
    WhenCreatedUTC                  : 5/13/2014 11:41:08 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    ObjectState                     : Unchanged
    [PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    AdminEnabled                    : True
    OwaOptionsEnabled               : True
    Name                            : ecp (Default Web Site)
    InternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated}
    MetabasePath                    : IIS://NYC-HQXCH-02.company.loc/W3SVC/1/ROOT/ecp
    BasicAuthentication             : True
    WindowsAuthentication           : True
    DigestAuthentication            : False
    FormsAuthentication             : False
    LiveIdAuthentication            : False
    AdfsAuthentication              : False
    OAuthAuthentication             : False
    DefaultDomain                   : company.loc
    GzipLevel                       : High
    WebSite                         : Default Web Site
    DisplayName                     : ecp
    Path                            : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp
    ExtendedProtectionTokenChecking : None
    ExtendedProtectionFlags         : {}
    ExtendedProtectionSPNList       : {}
    AdminDisplayVersion             : Version 14.3 (Build 123.4)
    Server                          : NYC-HQXCH-02
    InternalUrl                     : https://webmail.companytravel.com/ecp
    ExternalUrl                     :
    ExternalAuthenticationMethods   : {Fba}
    AdminDisplayName                :
    ExchangeVersion                 : 0.10 (14.0.100.0)
    DistinguishedName               : CN=ecp (Default Web
                                      Site),CN=HTTP,CN=Protocols,CN=NYC-HQXCH-02,CN=Servers,CN=Exchange Administrative
                                      Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Identity                        : NYC-HQXCH-02\ecp (Default Web Site)
    Guid                            : 0963f097-ff86-4d8f-a98a-8be409068eae
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-ECP-Virtual-Directory
    ObjectClass                     : {top, msExchVirtualDirectory, msExchECPVirtualDirectory}
    WhenChanged                     : 4/2/2014 1:50:57 PM
    WhenCreated                     : 8/30/2013 1:06:50 PM
    WhenChangedUTC                  : 4/2/2014 6:50:57 PM
    WhenCreatedUTC                  : 8/30/2013 6:06:50 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    IsValid                         : True
    ObjectState                     : Changed
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    AdminEnabled                    : True
    OwaOptionsEnabled               : True
    Name                            : ecp (Default Web Site)
    InternalAuthenticationMethods   : {Basic, Fba}
    MetabasePath                    : IIS://SVR-EXCH-01.company.loc/W3SVC/1/ROOT/ecp
    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)
    Server                          : SVR-EXCH-01
    InternalUrl                     : https://svr-exch-01.company.loc/ecp
    ExternalUrl                     :
    ExternalAuthenticationMethods   : {Fba}
    AdminDisplayName                :
    ExchangeVersion                 : 0.10 (14.0.100.0)
    DistinguishedName               : CN=ecp (Default Web Site),CN=HTTP,CN=Protocols,CN=SVR-EXCH-01,CN=Servers,CN=Exchange
                                      Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                      Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Identity                        : SVR-EXCH-01\ecp (Default Web Site)
    Guid                            : 052fdd05-42f4-471b-8759-525e93d6b97d
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-ECP-Virtual-Directory
    ObjectClass                     : {top, msExchVirtualDirectory, msExchECPVirtualDirectory}
    WhenChanged                     : 5/13/2014 6:52:11 PM
    WhenCreated                     : 5/13/2014 6:52:11 PM
    WhenChangedUTC                  : 5/13/2014 11:52:11 PM
    WhenCreatedUTC                  : 5/13/2014 11:52:11 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    IsValid                         : True
    ObjectState                     : Changed

    Ok. Went ahead and tried https://<EX2013_FQDN/ecp/?ExchClientVer=15
    Still took me to the webmail.
    I also tried creating a user on 2013 mailbox database. gave all permissions. Still no luck.

  • Second Exchange 2013 server in remote site

    Just finished migrating from 2007 to 2013 and decommissioned 2007.  Exchange 2013 is running in site A with 350 mailboxes on it.  However, almost half of those users reside in site B so the plan is to introduce a second Exchange 2013 server to
    this site and migrating mailboxes to it.  There already exists a DC & GC in both sites.
    My question is, immediately after I introduce Exchange 2013 into site B with CAS & MBX role, client computers from that site will start to receive certificate errors.  Will updating the SCP on the new exchange server to point to the SCP on the exchange
    server in site A be enough to mitigate that problem?  What other precautions will I need to take?  Has anybody been down this road?

    Hi
    You can introduce the second exchange server in the remote site and also setup a DAG. If you are using the same name on your certificate like mail.domain.com then you can use the cert for your second server as well. You need to make sure you have autodiscover
    records setup correctly.
    Hope this helps. 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.

  • Can't recover exchange 2013 server using recoverserver switch

    CU5 crashed while installing on one of our 4 DAG members.  I was able to coax it back to life with some manual steps and doing a repair of sp1, but was unable to get cu5 to install or to cleanly uninstall sp1 despite repeated tries.
    Finally I decided to rebuild it and use recoverserver (after removing database copies and removing it from the DAG).  I built a new server with the same name, reset the AD account, domain joined it, and then ran the /recoverserver switch.  But
    I get this error every time:
    "Can't specify installation mode because no Exchange Server is installed on this machine. Install Exchange Server."

    Hi,
    As far as I know,  to remove Exchange 2013 server, here are the additional steps except with removing objects through ADSIEdit:
    1. Delete the Exchange Server installation folder: C:\Program Files\Microsoft\Exchange Server
    2. Delete the Exchange Back End and Front End websites with the IIS-Manager.
    3. Delete the container in AD Users and Computers:
    DiscoverySearch Mailbox{GUID}
     Exchange Online-ApplicationAccount
    FederatedEmail.GUID
    Migration.GUID
     *SystemMailbox{GUID}
     *HealthMailboxGUID
    4. Delete the following registries:
    the key “ExchangeServer” under: HKLM\Software\Microsoft
    the keys “MSExchange*” under: HKLM\CurrentControlSet\Services
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

  • Update from Exchange 2013 Cu2 to SP1 - Outlook 2010 with SP2 clients disconnected

    Hi,
    we recently upgraded a standalone Exchange 2013 Server to SP1. Owa works fine, but all internal Outlook 2010 Clients (with SP2) get disconnected. Creating a new Profile, and testing the internal autodiscovery leeds to an Error 12030 (Connection reset) during
    the discovery process.
    I already checked the Service Point, the discovery URLs, even recreated the autodiscover virtual Directory in iis. But nothing changed.
    The self signed certificate, that was used before the update is further used, and well known to all Clients. As I tested, OWA is working well everywhere.
    Anyone some new ideas?
    Best regards
    Bernhard

    Hi,
    How did you recreate outlook profile? Manually or Automatic?
    If automatic failed, please try to recreate manually and check the result.
    If manual failed, please refer to the following methods to troubleshoot the issue:
    1>Try to open the following link and check the result:
     https://CASName/autodiscover/autodiscover.xml
    2>Try to use RCA to test outlook autodiscover and check the result.
    https://testconnectivity.microsoft.com/
    Thansk.
    Niko Cheng
    TechNet Community Support

  • New Exchange 2013 SP1 install, can't get ECP to display

    Hi all,
    I stood up a new exchange 2013 environment in my lab running on Server 2012.  Everything looks like it should be working.  All services running, no errors in the event log, I'm able to get into ECS.  When I try and launch the ECP, it spins
    for a little bit then I get a page can't be displayed.  I've checked that exchange sees it: 
    I'm stumped.  I've been scouring forums and can't pinpoint the issue.  I know I could just blow my lab away and try to re-install from scratch but I'm so close to getting this stood up and don't want to just give up.  Plus, I'm curious as
    to what the cause is and how it's tied into Exchange functionality.
    Also, when I try to browse to OWA, the page can't be displayed as well.  I've tried to disable Enhanced IE security to no avail.
    Any suggestions are appreciated.
    Thanks.

    Hi,
    Please use the https://localhost/ecp URL to logon from the local CAS server and check if you can access EAC.
    What's more, I have a test in my environment using Exchange 2013, when I use
    https://exc2013cas.contoso.com/ecp to logon EAC, the same error occurs. But when I use
    https://exc2013cas/ecp to logon, EAC works well. In your case, I recommend you use the
    https://skunkms1/ecp URL to logon EAC and check the result.
    Hope this can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

    Objective:
    We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
    to download and upload mail from the old tennant to the new tennant.
    Background: 
    We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
    the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan.  As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
    vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
    After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
    migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
    Environment:
    1 MS AD domain:
    - Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
    - UPN has been changed to [email protected] to allow for ADFS
    - ADFS has been deployed and SSO works for all users with UPN [email protected]
    - An "On-Prem exchange server" does not yet exist
    1 O365 Account where main tennant FQDN is @corp.com
    - There are 5 registered domains
    -contoso.ca
    -corp.com
    - contoso.legacy.ca
    -deprecated/will be deleted
    -deprecated/will be deleted
    - There are 40 E3 licenses, all using a @corp.com UPN
    - There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
    - No accounts currently use contoso.ca for email
    - O365 was upgraded to 'the latest version' sometime in summer 2013.
    Migration Plan (High Level):
    Setup a local windows server (trial license)  
      Deploy an exchange 2013 server (trial license) on the aforementioned windows server  http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
      Prepare and deploy Dirsync Deployment
    of Dirsync
      Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
    More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
    http://help.outlook.com/en-us/140/ff633682.aspx
      Evaluate total time it took to sync data. 
    Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
      Open a new office365 account under the M plan.
      Plan a 1 hour mail & contoso.ca domain login outage
      temporarily change all user UPN's to match the new tennant
      perform a dirsync to the new tennant
      disable dirsync after all accounts have been auto-created/provisioned
      re-establish UPN + mail access.
      Plan a date and time for the cut over.
      remove the exchange hybrid server from the old tennant. 
      Point MX records directly to the exchange server.
      Cut office 365 service.
      After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
    the new tennant
      fix all user UPN's in the cloud to match their real UPN's.
    This can be done with powershell.
      attach exchange hybrid server to new tennant
      Point MX records to the new tennant 
      Migrate all data from the local exchange server to the cloud under the new plan.
    Current progress (Lab):
    I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
    1x Domain Controller (DC) running windows server 2012 (named DC02)
    1x DC running windows server 2008 R2 (named DC01)
    1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
    Where I am stuck / Problem:
    I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected]. 
    After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
    the problem. 
    In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
    1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
    2) If I must add them to exchange, I am provided with three choices: 
    - Authoritative Domain
    - Internal Relay Domain
    - External Relay Domain
    Given that the domain is currently in office365 and is authoritative there, which of these applies?
    3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
    process? Would love it if it took into consideration multiple UPN/email addresses.

    Hi,
    Here are my answers you can refer to:
    1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
    http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
    2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
    To determine it, you can firstly check the function of the three types in the following article:
    http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
    3. Here are some reference about the migration from on-premise Exchange server to Office 365:
    http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
    Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
    http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
    If you have any question, please feel free to let me know.
    thanks,
    Angela Shi
    TechNet Community Support

Maybe you are looking for