Dismission of Exchange 2007 after a succesfull transition to 2013

I have this issue decommisioning an Exchange 2007 server.
As is:
All user maibox are migrated to Exc 2013
There is a Public Folder Database on the Exch 2007 containing only system mailbox
[PS] C:\Program Files\Microsoft\Exchange Server\scripts>Get-PublicFolderStatisti
cs
Name                                     ItemCount               LastAccessTime
Default                                  0                6/11/2014 12:42:31 PM
EX:/o=Organization/ou=Exchange Administrative  169               6/11/2014 2:00:00 AM
Group (FYDIBOHF23SPDLT)
EX:/o=Organization/ou=Exchange Administrative  0                 6/11/2014 2:15:00 AM
Group (FYDIBOHF23SPDLT)
exchangeV1                               401              6/11/2014 12:42:31 PM
globalevents                             0                6/11/2014 12:42:31 PM
internal                                 0                6/11/2014 12:42:31 PM
microsoft                                0                6/11/2014 12:42:31 PM
OAB Version 2                            0                 6/11/2014 5:13:04 AM
OAB Version 3a                           32                6/11/2014 5:13:04 AM
OAB Version 4                            13                6/11/2014 5:13:04 AM
OWAScratchPad{3FFF7BEF-E55C-4CCF-A27C-CD 0                6/11/2014 12:42:31 PM
F1F89C84FF}
schema-root                              0                6/11/2014 12:42:31 PM
StoreEvents{3FFF7BEF-E55C-4CCF-A27C-CDF1 0                6/11/2014 12:42:31 PM
F89C84FF}
/o=Organization/cn=addrlists/cn=oabs/cn=Defaul 0                 6/11/2014 2:15:00 AM
t Offline Address Book
If I try to launch get-publifolder I get this error
[PS] C:\Program Files\Microsoft\Exchange Server\scripts>Get-PublicFolder
Get-PublicFolder : There is no existing PublicFolder that matches the following
 Identity: '\'. Please make sure that you specified the correct PublicFolder Id
entity and that you have the necessary permissions to view PublicFolder.
At line:1 char:17
+ Get-PublicFolder <<<<
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-PublicFolder], Mapi
   OperationException
    + FullyQualifiedErrorId : A7F40D58,Microsoft.Exchange.Management.MapiTasks
   .GetPublicFolder
The Exchange 2007 server has cas,hub,mbx roles.
I need to delete the public folder database before uninstalling the Exchange 2007. There are no need to use the public folder database and the Exchange 2013 will become the single Exchange Server of the organization.
I thank you so much for your help and remain.
Regards,
Enrico

Hello Belinda,
The two commands return error:
[PS] C:\Documents and Settings\resulta>Get-PublicFolder -Identity \ -Recurse
Get-PublicFolder : There is no existing PublicFolder that matches the following
 Identity: '\'. Please make sure that you specified the correct PublicFolder Id
entity and that you have the necessary permissions to view PublicFolder.
At line:1 char:17
+ Get-PublicFolder <<<<  -Identity \ -Recurse
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-PublicFolder], Mapi
   OperationException
    + FullyQualifiedErrorId : 20AE3673,Microsoft.Exchange.Management.MapiTasks
   .GetPublicFolder
[PS] C:\Documents and Settings\resulta>Get-PublicFolder -Identity \NON_IPM_SUBTR
EE -Recurse
Get-PublicFolder : There is no existing PublicFolder that matches the following
 Identity: '\NON_IPM_SUBTREE'. Please make sure that you specified the correct
PublicFolder Identity and that you have the necessary permissions to view Publi
cFolder.
At line:1 char:17
+ Get-PublicFolder <<<<  -Identity \NON_IPM_SUBTREE -Recurse
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-PublicFolder], Mapi
   OperationException
    + FullyQualifiedErrorId : 71DB2DD1,Microsoft.Exchange.Management.MapiTasks
   .GetPublicFolder
The homeMDB attribution for System Attendant Mailbox in Exchange 2007 has been added before opening the thread. It was empty, but now it is the DN of a mailbox database as described (http://technet.microsoft.com/en-us/library/dd535374(v=exchg.80).aspx)
As I am transitioning to a single Exchange server 2013 Migration I immagine I can dismiss the public folder database without migrating the system public folder to Exchange 2013. AM I right?
Of course in this situation the migration scripts will fail, so I cannot
I can delete the public folder database using adsiedit.msc, but this will be the last option as I do not want to cause any side effect. Do you agree?
I run the command
StorageLimitStatus      : BelowLimit
TotalDeletedItemSize    : 0B
TotalItemSize           : 369231B
Database                : EXCHANGE\Ancon\DB
ServerName              : EXCHANGE
StorageGroupName        : Ancon
DatabaseName            : DB
Identity                : caadff47-57e5-4941-a9f3-7f8f7c27868d
IsValid                 : True
OriginatingServer       : exchange.Client.lan
AssociatedItemCount     : 0
DeletedItemCount        : 0
DisconnectDate          :
DisplayName             : Microsoft System Attendant
ItemCount               : 0
LastLoggedOnUserAccount : NT AUTHORITY\SYSTEM
LastLogoffTime          : 6/12/2014 10:41:18 AM
LastLogonTime           : 6/12/2014 10:41:18 AM
LegacyDN                : /O=Client/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF2
                          3SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE/CN=MI
                          CROSOFT SYSTEM ATTENDANT
MailboxGuid             : 36c7d6db-76b1-4de2-855a-ee63b2597220
ObjectClass             : Mailbox, SystemAttendantMailbox
StorageLimitStatus      : BelowLimit
TotalDeletedItemSize    : 0B
TotalItemSize           : 0B
Database                : EXCHANGE\Ancon\DB
ServerName              : EXCHANGE
StorageGroupName        : Ancon
DatabaseName            : DB
Identity                : 36c7d6db-76b1-4de2-855a-ee63b2597220
IsValid                 : True
OriginatingServer       : exchange.Client.lan
To confirm system attendand mailbox exists.
I thank you for your assistance and please tell me it adsiedit may solve the issue easily.
Kind regards,
Enrico

Similar Messages

  • Can Exchange 2007 to be integrated with SharePoint 2013

    Can Exchange 2007 to be integrated with SharePoint 2013?

    In the sense of using Incoming and Outgoing email, absolutely. But not for other things, like Site Mailboxes, which require Exchange 2013.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Issue removing Exchange 2007 after migration to 2013

    After migrating relatively successfully from Exchange 2007 to 2013, I am in the process of trying to decommission and uninstall 2007 from the servers. Through this process I have been following a guide found
    here. Our old 2007 servers have been off for over two weeks and it seems like a good time to remove them and reclaim some space. I removed the old OAB and Mailbox DB, however when I attempted to remove the Public Folders so I could take the PF DB out the
    following error appeared.
    Get-PublicFolder : There is no existing PublicFolder that matches the following Identity: '\'.
    I know that there are Public Folders existing as I can see them when I run Get-PublicFolderStatistics:
    I've been back and forth across the forums and web and haven't been able to find a solution to this. Ultimately we never have and are not interested in using public folders but they were originally configured when we had a contractor move us from 2003 >
    2007 several years ago. What I would like is to remove all traces of this garbage and just be able to uninstall/delete the old servers and move on with life.
    Any help is greatly appreciated. Thank you in advance.
    Jon Howard

    Hi,
    Have you tried to use Exfolders tool to remove PF?
    More details about exfolders tool refer to the following article:
    http://gallery.technet.microsoft.com/office/Exchange-2010-SP1-ExFolders-e6bfd405
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Address list service failed to respond error on Exchange 2007 (after adding first 2013 server)

    Hi,
    We just installed an Exchange 2013 server within an Exchange 2007 environment.
    The Exchange 2013 (CU6) server will be used to setup a hybrid connection with O365, and move mailboxes to O365.
    After installing the Exchange 2013 server it isn't possible anymore to create/enable mailboxes on the Exchange 2007 server.
    We end up with an error :
    Mig1 TestAccount
    Failed
    Error:
    The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.
    Exchange Management Shell command attempted:
    Enable-Mailbox -Identity 'domain.be/customer/TEMP/Mig1 TestAccount' -Alias 'mig1' -Database 'Exchange2007\SG01\DB02'
    When executed via EMS we receive this error :
    The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error

    Hi Lyncer
    This error can be caused if the default Public Folder Database not being pointed to the exchange 2007 database which you are trying to create a new mailbox.
    Also it can happen if System Attendant service is not running.
    Troubleshooting steps:
    1) Restart the System Attendant Service 
    2) Point the affected database to the default public folder
    Follow the below steps to do that 
    Open EMC
    Go to Organization Configuration > Mailbox.
    Select the mailbox database that you want to change the default public folder database.
    Right click the database and select properties
    In <Mailbox Database Name> Properties, click the Client Settings tab.
    Next to the Default public folder database box, click Browse.
    In Select Public Folder Database, select the public folder database from the list of public folder databases, and then click OK.
    Cheers!!!
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
    (MVP)

  • Provisioning to Exchange 2007 failing

    Hi All,
    I have installed the Exchange 2007 connector to create the mailbox of the users in the Exchange 2007. This requires Remote manager as well so did the configuration of the remote manager as per the guide.
    Now when i try to provision the user to Exchange 2007 after it is successfully provisioned into AD.
    The users mailbox is not created.
    The Exchange provisioning task performs the following tasks.
    1. first it check if the mailbox is already present in the Exchange.
    2. If it is not present then it execute the scripts createmailboxexchange2007.vbs script using the remote manager.
    3. It then again checks if the mailbox is created.
    At this check it is giving the basically the information:
    "DEBUG,09 Nov 2009 14:01:19,977,[OIMCP.MEXC],com.thortech.xl.integration.Exchange.tcExchangeTasks : checkMailboxCreation : No value for homeMDB fetched
    INFO,09 Nov 2009 14:01:19,978,[OIMCP.MEXC],com.thortech.xl.integration.Exchange.tcExchangeTasks : checkMailboxCreation : Unable to execute the Power Shell command"
    So basically it is not able to fetch the homeMDB as it was unable to execute the Power shell command.
    I am not getting any logs on the Remote manager side but i guess the remote manager is not able to execute the power shell command.
    Any ideas??

    I would also check if you can call the .vbs script from a stand-alone Java program and if you really want to troubleshoot, from an RMI server that you build yourself (takes 15 mins). OIM remote manager is an RMI server. One issue could be JDK permissions (http://java.sun.com/javase/6/docs/technotes/guides/security/permissions.html), the default in the JDK you're using may not allow execution of scripts.
    If the permissions are ok, I can't think of anything else. Maybe the same JDK on OIM and remote manager? It shouldn't matter but it could.

  • 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

  • ActiveSync stops working after migrating from Exchange 2007 to Exchange 2013

    We have started the migration from Exchange 2007 to Exchange 2013. We've followed best practices and everything is working great except ActiveSync. I've performed Exchange migrations in the past so this is nothing new for me. I've also been referring to
    a great guide which has been a big help,
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html.
    Once a user is migrated from Exchange 2007 to 2013, ActiveSync stops working properly. Email can be pulled to the device (Nokia Lumia 625 running Windows Phone 8) by performing a manual sync. But DirectPush is not working. The strange part is it's not affecting
    everyone who's been migrated. Anyone who is still on Exchange 2007 is not affected.
    At first I thought it was our wildcard certificate. 99% of our users are running Outlook 2013 on Windows 7 or higher but we do have a few terminal servers still running Outlook 2010. Outlook 2010 was giving us certificate errors. I realized it was the wildcard
    certificate. Rather than making changes to the OutlookProvider I simply obtained a new SAN certificate. Although that resolved the issues for Outlook 2010 users, ActiveSync was still a problem.
    Rebooting the phones and removing the email account from the user's device and re-adding it didn't resolve the issue either.
    Then I performed an iisreset on the CAS server. This didn't help either. I didn't know it at the time, but I was getting closer...
    I tried using the cmdlet Test-ActiveSyncConnectivity but it gave me the following error:
    WARNING: Test user 'extest_0d9a45b025374' isn't accessible, so this cmdlet won't be able to test Client Access server
    connectivity.
    Could not find or sign in with user DOMAIN.com\extest_0d9a45b025374. If this task is being run without
    credentials, sign in as a Domain Administrator, and then run Scripts\new-TestCasConnectivityUser.ps1 to verify that
    the user exists on Mailbox server EX02.DOMAIN.COM
    I started reviewing how Exchange 2013 proxied information from the CAS to the mailbox server and realized the issue may in fact be on the mailbox server.
    I performed an iisreset on the mailbox server and all of a sudden ActiveSync started working again. Awesome!
    I can't explain why. The only thing I can assume is when some users were migrated from 2007 to 2013 something wasn't being triggered on the Exchange 2013 side. Resetting IIS resolved the issue. I guess I'll have to do an IIS reset after I perform a batch
    of migrations. Disabling ActiveSync and re-enabling it for the affected users didn't help - only the IISRESET resolved the issue.
    If anyone has any information as to why this happens, please chime in. Also, if anyone knows why I can't run the Test-ActiveSyncConnectivity cmdlet, I'd appreciate the help.
    Thanks.

    Hi,
    In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
    Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
    public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
    there’s no coexistence between versions.
    For this reason, it’s recommended that prior to migrating your public folders, you should
    first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    (Please note the What do you need to know before you begin part in this link)
    Regards,
    Winnie Liang
    TechNet Community Support

  • Can only access emails through OWA after migration from exchange 2007 to 2013

    can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
    needed RCA ... plz help..

    Hi,
    From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
    In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

    Hello, everyone, my name is rafl
    I have a problem with exchange 2013 active sync.
    I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
    but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
    (legacy.domain.com)
    the process of moving mailboxes successfully without error.
    Access OWA for exchange 2007 and exchange 2013 is running normally
    access mail from Outlook running normally
    Certificate request has been installed and has no problem with it
    The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
    The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
    ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
    user mailboxes are still on exchange 2007 is not problematic.
    only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
    but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
    only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
    any ideas for this problem, and what should I check on the exchange server ..?

    i have run the activesync test connectivity and get some error :
    Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 3091 ms.
    Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21072 ms.
    Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21049 ms.
    I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
    for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

  • 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

  • Exchange 2007 - unable to connect to smtp after severall hours

    Hi,
    We have a Windows SBS 2008 server with Exchange 2007 SP3. After severall hours we are unable to connect to the server with telnet on port 25 from outside. Sometimes a local telnet on the server still works but not always.
    The only solution is to restart the server. The transport service can not be stopped.
    Even after a fresh reboot the telnet session does not alway show the smtp banner.

    Hi Joost,
    Is there any related error message left on Exchange server?
    I have found a similar thread for your reference:
    https://social.technet.microsoft.com/Forums/en-US/5e2b3320-7c97-4b33-bd8e-e27768f51ec0/hub-transport-service-wont-start-and-keep-running-sbs-2008-exchange-2007
    More detailed error message without sensitive informaiton is helpful for the further troubleshooting.
    Also, SBS 2008 is different from Exchange 2007 on Windows Server, I suggest ask SBS Forum to double confirm this issue.
    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]
    Mavis Huang
    TechNet Community Support

  • Exchange 2007/2010 Console doesn't show up Exchange 2007 Databases after RBAC Implementation

    I have implemented a RBAC model after which Exchange 2010/2007 Console won't show up Exchange 2007 Mailbox Databases.
    Everything was working fine up until the Users were members of "Exchange Recipient Administrators" Group.
    I have created Custom Roles based on PArent Roles, Mail Recipients, Mail Recipient Creation, Distribution Groups & Public Folders and assigned that to a universal security group "Helpdesk operations". I removed membership for Helpdesk operations
    from "Exchange Recipient Administrators" Group and assigned the Custom Roles to "Helpdesk Operations" using the cmdlet below:
    New-ManagementRoleAssignment "Custom Role" -SecurityGroup "HelpDesk Operations"
    Exchange 2010 console shows Exchange 2010 Databases but not Exchange 2007 DAtabases. Exchange 2007 console doesn't show up any databases on New-Mailbox and simply displays a message "No Objects Found".
    Even Get-MailboxDatabase REturns blank output on Exchange 2007 SHell. Please help me with this and let me know in case if there is something that i need to be looking at!
    any help on this is much appreciated.
    M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
    Information is provided is "AS IS" and confers NO Rights!!

    Hi,
    I recommend you use the following cmdlet and check the result.
    Get-MailboxDatabase -Server "Exchange 2007 server name"
    In my environment, if I don't specify the Server parameter on Exchange 2010 Management Shell, Exchange 2007 mailbox database can't be displayed. If I specify the Server parameter, Exchange 2007 mailbox database will be displayed.
    What's more, please check if the account you use has been delegated the Exchange View-Only Administrator role.
    Here is a thread for your reference.
    Get-MailboxDatabase
    http://technet.microsoft.com/en-us/library/bb676367(v=exchg.80).aspx
    Hope it helps.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Receive Connector stopped working after Update Rollout 2 for Exchange 2007 SP2

    One of the Exchange 2007 servers receive connector has stopped working since installing the latest rollout update for Exchange 2007 SP2 - for some reason the following error is received (when troubleshooting on the adjacent server) :
    "Remote server server.domain.co.uk failed the mail acceptance test. MAIL FROM command: Respond = 530 5.7.1 Client was not authenticated."
    Most admins will know you usually get this when first setting up Exchange and the receive connector not allowing anonymous connections. But our setup has been working for well over a year with no problems. Even enabling anonymous connections still doesn't fix the problem.
    Our setup is 2 exchange servers across 2 sites, with the problematic server never receiving email from the internet, only from the other Exchange server (which is internet facing). The above error is received when the internet facing server is relaying email over to the problematic server. Though in the message queue the following error is received:
    "SMTPSEND.DNS.NonExistantDomain; nonecistant domain"
    After testing DNS that all seems fine, so I don't believe it's a DNS problem.
    Any ideas why this would happen?
    Thanks,
    Matt

    Hi Matt....
    To receive e-mails from the external servers or domains or clients, you can setup a new receive connector on Hub Transport Server. To do this task, you can go through the steps mentioned in this blog....
    https://mailsolutions.wordpress.com/2015/02/06/resolving-error-530-5-7-1-client-was-not-authenticated-with-receiver-connector/
    Hope this will work
    Thanks

  • Exchange 2007 to Exchange 2010 Transition

    I am in the process of transitioning a client from Exchange 2007 to 2010(clients are XP/Win 7 with Outlook 2007/Outlook 2010). I know if have to extend the schema for Exchange 2010 and there will be co-existence throughout the process. At this point, Outlook
    profile on users are point to either IP or netbios name of the server and their credentials. When I move their mailbox(in Exchange 2010 migration wizard), do I have to go to each Outlook and repoint their profile to the new netbios name of the Exchange 2010? 

    Outlook 2007 and newer will use a combination of AutoDiscover and redirection to update the client profile from the existing settings to the new server supporting their mailbox.  Just make sure you have DNS resolution for autodiscover and the new
    server names.
    Gary A. Cooper | Senior Systems Architect | MCA:Exchange 2003/2007/2010 | MCM:Exchange 2003/2007/2010 | Horizons Consulting, Inc. If you have found my answer helpful, please vote as such.

  • Exchange 2007 SP1 don't send or receive emails after main DC shutdown

    I have two DC (DC1 and DC2), both of them GC and DNS.
    After shutting down DC1 (with all the roles instaled), Exchange 2007 stops to sending and receive emails, but Outlook clients can process the request of sending emails (like it has been sent) and "Connected To Exchange" is showed correctly.
    If I switch on again DC1, the pending messages are sent and received (internal or external).
    I thought that making GC also the DC2, Exchange could work in the same manner in a DC1 failover scenario.
    Maybe any kind of info in Exchange for main DC is cached and needs to be updated or so?
    Thanks in advance

    Hi,
    DC and GC hard failures are generally handled seamlessly by DSAccess if other servers are available. However, GC failures can impact Outlook clients harshly depending on the version of Outlook being used. Worst case scenario is that Outlook ‘hangs’ and the
    user must restart. The exception is Outlook XP (Outlook 2002) which can automatically reconnect to a new GC without a restart.
    More details about Exchange 2007 Disaster Recovery:
    https://technet.microsoft.com/en-us/library/aa998848(v=exchg.80).aspx
    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

  • 802.1X Athentication Successful but can't ping Default Router. PSK works fine

    Got an interesting scenario. I am labbing out 802.1X authentication for wireless with a Cisco 2504 WLC along with a Windows Server 2012 r2 with AD, DHCP Server, DNS Server, Certificate Services, and NPS. I was able to make the different parts communi

  • List of users and their licence allocation

    I am aware of accessing Admin>> License>> License allocation, one by on - but would like to have access to be able to llist users and their licence allocation.

  • Inbuilt protection from viruses, etc.

    I'm going to refer to a discussion that appeared in Apple Support Communities > Desktop Computers > iMac (Intel) > Discussions entitled "slow start up on my macbook pro (gray screen)" (https://discussions.apple.com/message/19137371#19137371), in whic

  • Change of e-mail

    I changed my e-mail address and now I can't update any apps purchased with the old e-mail address. What do I do?

  • E-Recruitment Scope update

    Hi Guru's, Please guide me whether all the below details are possible to map in standard E-Recruitment, 1. Accepting resumes in auto format 2. Generating Comparison charts for the applicants 3. Short listing Probables 4. Confirming Probables post int