Removing old exchange 2003 routing groups from Exchange 2010.

I have migrated over to Exchange 2010(server2008) from Exchange 2003(SBS2003). I've also already run the uninstall for exchange 2003 on the old SBS 2003 server. The old server itself is still running but exchange has been removed and once I get this fixed
I plan to fully remove the old SBS server.
I now get event ID 5020 and 5006 throughout the day on the new server. From what I've read, this happens because the old routing group connectors still exist.
If I run Get-ExchangeServer I get
Name                Site                 ServerRole  Edition     AdminDisplayVersion
SERVER                                   None       
Standard    Version 6.5 (Bui...
SERVER2008          hr.local/Configur... Mailbox,... Standard    Version 14.0 (Bu...
Am I correct in assuming that the way to fix this now is to go into ADSI edit and delete records under CN=First Administrative Groups? As in delete CN=Routing Groups and CN=Servers and everything under both of those? I'd try this myself but I'm not aware
of any way to restore those records easily if I'm wrong.
Event ID 5006
Cannot find route to Mailbox Server CN=SERVER,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=HR,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hr,DC=local for store CN=Public Folder Store (SERVER),CN=First Storage Group,CN=InformationStore,CN=SERVER,CN=Servers,CN=first
administrative group,CN=Administrative Groups,CN=HR,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hr,DC=local in routing tables with timestamp 27/09/2014 1:57:43 PM. Recipients will not be routed to this store.
Event ID 5020The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 server.hr.local in Routing Group CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative
Groups,CN=HR,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hr,DC=local in routing tables with the timestamp 27/09/2014 1:57:43 PM.

Get-RoutingGroupConnector shows nothing. As for the servers group. It has the old server under it as shown in the image I posted above. That's actually what stops me from just deleting it because other guides have said not to delete it if an old server
is listed.
Is the SBS2003 server listed because I haven't ran DCPROMO to remove it from the network yet? I am planning to do this but was waiting till I cleaned up all the errors before transferring the 5 FMSO roles and running DCPROMO on the old server.
DCPROMO isn't related to this, no.
So you removed Exchange already? How? With setup? It should have removed the Exchange Server object then.
It is supported to remove Exchange 2003 manually if required with adsiedit:
http://support2.microsoft.com/kb/833396
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

  • I cannot sync my contact groups from Outlook 2010 (Win 7) onto my iPad.  Can anyone help please ?

    I cannor sync my contact groups from Outlook 2010 (Win 7) onto my iPad.  Can anyone help please ?

    in Itunes, once you connect the iPad, do you see the 'info' tab? Tap that and scroll down and see if outlook is chosen as the place to sync contacts from. If not, check it and sync and see if your contacts move over.

  • Upgrading from Exchange 2003 Bridgehead servers to Exchange 2010 Transport Hub servers for routing SMTP only

    Our company moved from on-premises Exchange 2003 to Office365 and only have 4 Exchange 2003 servers on-prem that we use for Routing email from application servers to Office365. We need to migrate these servers to Exchange 2010 then to Exchange 2013 and
    only route email only. Is it possible to upgrade to Exchange 2010 by installing the transport Hub & Mailbox server options only? Our OAB and EWS services come from the CAS servers located on Office365 so we should not need a CAS server to set up Transport
    rules or route mail would we? Any assistance with this would be greatly appreciated! - Thanks, DWB
    Dave

    Since it is not internet facing we will not have to worry about configuring an Internet Domain Name when installing the first server, correct? in my planning I was going to
    install the Exchange 2010 CAS/Mailbox/Transport Hub roles on one server, then upgrade it to Exchange 2013. Once this is completed I'll then install the 2 mailbox role servers in one Datacenter, and 3 more in our DRP DC. If something happens to the
    primary Datacenter I would want it to fail over to the other site. For this I would have to install another CAS/mailbox server in the secondary DC. Would this plan sound about right? Since we moved to Office365 in 2010 I have not had a chance to deal with
    actual servers except for the Exchange 2003 servers we still have on-premises. Each of these are located in 4 Regional offices along with single Windows 2008 R2 servers using only the IIS SMTP service for routing mail from on-prem application servers
    and print/scanners which email back to the users. The plan is to move to a routing system which will provide both MTA and redundancy if one has an issue.
    Dave

  • Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

    Hi,
    I'm trying to resolve an issue.  We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010.  We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
    off this server and onto the Exchange 2010 environment.
    The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
    for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010).  The TO address is in the format of [email protected]  Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
    email, because one of our send connectors has, as address space, *.domain.corp.  However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
    also is an SMTP server.  I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
    the mail, processes it and then saves it to a file somewhere.
    We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server.  Any help troubleshooting this issue is appreciated.

    The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server.  You
    should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Routing email from exchange 2007 to 2010 .

    Although this is an
    hypothetical question but still would be a great help if anyone could answer this :  " How email routing takes place from exchange 2007 user
    to exchange 2010 user. I have exchange 2007 and 2010 ,provided i am using single forest with same domain name in both 2007 & 2010 environment "
    Aditya Mediratta

    Hi,
    Firstly,I'd like to explain, message routing from Exchange 2007 to Exchange 2010 is message delivery between responsed Hub Transport servers:
    When a Hub Transport server queries Active Directory to determine the Mailbox server hosting the destination mailbox, it also retrieves the version of the Mailbox server. If the Mailbox server is an Exchange 2007 server that's in the same site as the Hub Transport
    server, the Hub Transport server will relay the message to an Exchange 2007 Hub Transport server in the same Active Directory site.
    For more information about the emails routing process, you can refer to the following articles:
    http://technet.microsoft.com/en-us/library/bb232193(v=exchg.141).aspx#Old
    http://technet.microsoft.com/en-us/library/aa996349(v=exchg.141).aspx
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2007 setup, transitioning from Exchange 2003

    Hello Exchange Experts,
    I just setup a Exchange 2007 within our domain, transistioning from Exchange 2003, question: When I added the mailbox role on the setup of Exchange 2007, the mailboxes appeared instantly from our Exchange 2003..the connector I'm assuming automatically connected
    during the 07 setup. Is this normal? I was under the assumption to migrate mailboxes from 03 to 07 Exchange, the wizard must be ran. All active mailboxes from 03 appear. I attempted to migrate one mailbox using the wizard, error after the wizard completed,
    mailbox exists. Makes sense, just not understanding how the mailboxes flowed/migrated automatically without running the migration steps. Would someone explain? You could say, this migration is very new to me.
    Thanks in advance!
    James

    Ronny, our company had an existing license for 2007. Of courser 2010 or 2013 would have been a better transition, but 2007 is it. The server 2007 has met all the criteria for the transition, spent last moth prepping everything on 2003 and 2007. I'm just
    not understanding why the mailboxes appeared upon 2007 immediately after adding the mailbox role.  The management console on 07 shows the mailboxes reside on 03 exchange server. I did not go through the process/wizard to move to 07. Perhaps because
    during the installation of Exchange 07 created the connector from 2003? Maybe that's my question.
    Mail flow is very responsive now, just wondering for the reasons of decommissioning exchange 2003 at a later date. Exchange 2003 is functioning now as a bridgehead, working perfectly now.  
    Thanks for your input.
    James
    Thanks Ronnie for your input! Issue resolved

  • Migration from an exchange 2003 organisation A (Exchange 2003 sp2) to another Exchange 2010 organisation B

    Hello,
    We have two Exchange organisations:
    - A (Exchange 2003 SP2)
    - B (Exchange 2010)
    we want to migrate from A to B. the two organisations have to coexist during the migration (6 months). during this time the users have to share the same GAL and Calendar (Busy/Free informations).
    What are the steps to follow ?
    is there any docs/links treat this subject ?
    Regards

    Hi,
    You can use FIM for GALSYNC.
    REF:http://setspn.blogspot.in/2010/05/global-address-list-synchronization-gal.html
    For calendar sharing follow the below blog:
    REF:http://blogs.technet.com/b/exchange/archive/2011/03/28/iorepl-and-exchange-2010-sp1.aspx
    Regards
    Vickram

  • Changing the Default OAB from an Exchange 2003 server to an Exchange 2010

    I am in the process of decommissioning my old Exchange 2003 servers. All mailboxes have been moved over to Exchange 2010. I already have OABs and Public Folders created on the Exchange 2010 servers. Since I see the "Default Offline Address List",
    which is pointing to my old Exchange 2003 server and the Default OAB is set to "True", can I just make an existing Exchange 2010 OAB the "Default OAB"? I have read that I have to perform a move on the "Default Offline Address List"
    OAB. Is this required?
    thanks
    Noe

    Configure the Exchange 2010 mailbox databases to use the Exchange 2010 OAB, and leave the Exchange 2003 databases alone.  You can delete the old OAB just before taking the Exchange 2003 servers out of production.  The "Default" setting
    means the OAB is the one that's assigned by default when you create a new mailbox database, so yes, you should set that.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2003 will migrate to Exchange 2010 or Exchange 2013

    Hi,
    Exchange server is on exchange 2003 on windows 2003 R2. 
         I had an architecture of parent & child domain controllers, Where parent company is closed Down. But we have an additional Domain Controller
    of parent DC in our premise.
    Due to this fact exchange organization is also unavailable & cannot make modification on my exchange server configurations (Global Settings, such as changing recipients attachment restrictions, everything is grayed out).
    Is there any way where we can have staged migration. I mean can I keep old & new server running together & keep few users on new Exchange organization & rest of them be on an existing server itself. (I tried testing this too, but email delivers
    to mailbox store, so, it checks a name & say “Mailbox not available”)
    If I create a new domain environment, I have challenge of migrating users (This I can achieve with ADMT, but actual story starts with mailbox migration)
    Real pain is, I have more than 500 users, can I achieve direct migration over a weekend. (few are POP & OWA users, around 50)
    Can anyone help in this please.
    Imran

    So, you have exchange 2003 which is inaccessible! Database files .EDB and .STM is there, but Mailboxes are not available.
    And you are planning to create new environment (As you don't have any other option).
    This is a cross forest migration. Which exchange you are planning to install in new environment? I would suggest 2013.
    The only available option you have (As current environment is Inaccessible), Export the PST from EDB files.
    Create Mailbox on Exchange 2013 and Import the PST.
    Do you have Public Folder Database?
    If yes, apply the same process on it.
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • OUTLOOK 2013 permission shared calendar Free/Busy doesn't work for some the users Exchange 2010 and Exchange 2003 that use outlook 2007/2010

    Hello,
    We are in coexitence organisation (transition Migration) Exchange 2003 sp2 and Exchange 2010 sp1.
    Users in Exchange 2003 use outlook 2007 and outlook 2010
    Users in Exchange 2010 use outlook 2007, outlook 2010 and outlook 2013.
    Issue: users in Exchange 2003 can't open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
    User in Exchange 2010 with outlook 2007 can't also open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
    Is it normal ? or exist some configurations to do in order to coexist all thoses clients and servers ?
    Thanks in advance

    Hi,
    Does this issue occur on Outlook only or both Outlook and OWA?
    Since you have double checked the permissions via multiple methods, it seems there is nothing problem on permission. Please make sure the migration from Exchange 2003 server completed successfully.
    If in OWA everything goes well (cannot see details), it should be an issue on the Outlook client side.
    I suggest run Outlook under safe mode to avoid some AVs and add-ins.
    I suggest re-create profile to refresh the caches.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • How many system mailboxes should be in exchange 2013 after moving from exchange 2010?

    Hi, I am moving mailboxes from exchange 2010 to exchange 2013, I noticed that in exchange 2013, besides discovery search mailbox, there are other 5 system mailboxes.(especially, there are 2 x Microsoft Exchange system mailboxes) Please see the pic attached.
    Does this look right? thanks

    Looks perfectly fine - Why MS decided to name two of the five arbitration mailboxes the same (Microsoft Exchange) is unclear but it is what it is :)
    In EMS:
    Martina Miskovic

  • How to remove good for enterprise contacts group from iphone

    Hello Everyone,
    Could you pls help me with the Good for enterprise app contacts issue. I'm struggling to remove the Good for enterprise contacts group from iphone contacts group.

    Contest the makers of the app for support.

  • Removing "On My iPhone" Contacts group: Google (Exchange) Sync

    Hi guys,
    I've got all my contacts properly syncing with Google Sync.
    But as soon as I set it up on the iPhone, I get this empty folder in Contacts "On My iPhone"/"All on My iPhone", as well as Exchange Contacts and Exchange Global Address List.
    Then I have to change Settings/Mail, Contacts, Calendars/Contacts/Default Account to "Exchange" rather than "On My iPhone".
    Is there any way to just remove "All on my iPhone" empty directory, or is it impossible with Exchange syncing?
    Thanks.

    Hmmm, that would work, but in iOS you can't manage the groups and such, how would I do that exactly?

  • Move-mailbox from forest A exchange 2003 to Forest B exchange 2010

    i got this error after  any idea ?
    Get-MailUser "usertest" |New-MoveRequest -RemoteLegacy -TargetDatabase "test01" -baditemlimit 10 -RemoteGlobalCatalog $remoteGC -RemoteCredential $remoteCredentials -TargetDeliveryDomain $domainTarget
    MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
    Diagnostic context:
        Lid: 15000   dwParam: 0x6BA      Msg: EEInfo: prm[2]: Pointer val: 0x51C8A8C000000000
        Lid: 16280   dwParam: 0x6BA      Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x6BA      Msg: EEInfo: ProcessID: 19796
        Lid: 12696   dwParam: 0x6BA      Msg: EEInfo: Generation Time: 2015-01-14 20:21:54:210
        Lid: 10648   dwParam: 0x6BA      Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x6BA      Msg: EEInfo: Status: 10060
        Lid: 9624    dwParam: 0x6BA      Msg: EEInfo: Detection location: 318
        Lid: 13720   dwParam: 0x6BA      Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x6BA      Msg: EEInfo: NumberOfParameters: 0
        Lid: 45169   StoreEc: 0x977
        Lid: 52465   StoreEc: 0x977
        Lid: 60065
        Lid: 33777   StoreEc: 0x977
        Lid: 59805
        Lid: 52209   StoreEc: 0x977
        Lid: 56583
        Lid: 52487   StoreEc: 0x977
        Lid: 19778
        Lid: 27970   StoreEc: 0x977
        Lid: 17730
        Lid: 25922   StoreEc: 0x977
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
        + FullyQualifiedErrorId : FBB4FBA6,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

    See this error, sounds like some ports are blocked between tow forests...
    Check James Chong's blog post - http://msexchangetips.blogspot.com/2010/11/mapiexceptionnetworkerror-unable-to.html
    Amit Tank | Exchange - MVP | Blog:
    exchangeshare.wordpress.com 

  • Outlook can't connect with Exchange 2013 after migration from Exchange 2007

    <style type="text/css">P { margin-bottom: 0.21cm; }</style>
    Hello,
    recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
    But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
    To try to resolve it we've done:
    - Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
    - Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
    records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
    - In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
    Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
    - Check Outlook Anywhere block: we've cheked.
    Currently server state:
    - Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
    unless the mailbox. After a restart it can't start.
    -The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
    I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
    Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
    We continue to try to resolve the problem.
    Thanks to all in advance!
    Testing RPC / HTTP connectivity.
    Error in testing RPC / HTTP.
    additional Details
    Elapsed time: 24295 ms.
    Test steps
    Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
    Error in automatic detection test .
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Attempting each method of contacting the Autodiscover service .
    Failed to properly contact the Autodiscover service using all methods.
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 1509 ms.
    Test steps
    Attempting to resolve the host name in DNS empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 80.36.252.194
    Elapsed time: 507 ms.
    Testing TCP port 443 on the host to ensure empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 464 ms.
    Testing the SSL certificate to make sure it is valid.
    The SSL certificate is not exceeded one or more certificate validation checks .
    additional Details
    Elapsed time: 537 ms.
    Test steps
    Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
    Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
    additional Details
    Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
    Elapsed time: 454 ms.
    Validating the certificate name .
    The certificate name was validated successfully .
    additional Details
    Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
    Elapsed time: 1 ms.
    Is validating the trusted certificate .
    Validation Error trusted certificate.
    Test steps
    Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = ​​mail.empresa.com .
    Could not build a certificate chain for the certificate.
    Tell me more about this issue and how to resolve
    additional Details
    The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
    Elapsed time: 31 ms.
    Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 21723 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 498 ms.
    Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
    The specified port is blocked , not listening or does not generate the expected response .
    Tell me more about this issue and how to resolve
    additional Details
    Network Error communicating with the remote host.
    Elapsed time: 21224 ms.
    Attempting to contact the Autodiscover service with the HTTP redirect method .
    Error when trying to contact the Autodiscover HTTP redirect method .
    additional Details
    Elapsed time: 606 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 14 ms .
    Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 202 ms.
    Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
    Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
    additional Details
    Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
    lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
    Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
    Elapsed time: 388 ms.
    Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
    Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
    additional Details
    Elapsed time: 186 ms.
    Test steps
    Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
    Not the Autodiscover SRV record in DNS found .
    Tell me more about this issue and how to resolve
    additional Details
    Elapsed time: 186 ms.
    Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
    Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
    Tell me more about this issue and how to resolve
    additional Details
    No Autodiscover CNAME record for your domain ' empresa.com ' .
    Elapsed time: 268 ms.
    jspt

    Hello,
    We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
    below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
    Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
    $AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
    RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
    Name                                 : EXCHANGE13
    Fqdn                                 : EXCHANGE13.domain.local
    ClientAccessArray                    :
    OutlookAnywhereEnabled               : True
    AutoDiscoverServiceCN                : EXCHANGE13
    AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
    AlternateServiceAccountConfiguration :
    IsOutOfService                       : False
    WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
    Identity                             : EXCHANGE13
    IsValid                              : True
    ExchangeVersion                      : 0.1 (8.0.535.0)
    DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                           (FYDIBOHF23SPDLT),CN=Administrative
    Groups,CN=First Organization,CN=Microsoft
                                           Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
    ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                          : {top, server, msExchExchangeServer}
    WhenChanged                          : 09/03/2014 12:46:07
    WhenCreated                          : 08/03/2014 19:15:54
    WhenChangedUTC                       : 09/03/2014 11:46:07
    WhenCreatedUTC                       : 08/03/2014 18:15:54
    OrganizationId                       :
    OriginatingServer                    : severdc.domain.local
    ObjectState                          : Unchanged
    I hope this stuff can help you.
    Thanks!!
    jspt

Maybe you are looking for