Exchange 2013 autodiscover question about PublicFolders pointing to old server.

I had Exchange 2007, and migrated everything to Exchange 2013,
One users is having "conflict problems in Outlook", the errors I found seems to be that the Outlook y trying to look for the old server (Exchange 2007), I have uninstalled the server passing every roll to the new server...

Doing an autodiscover query, I can see my old server in only one part; maybe this is the problem, maybe not.

Part of the autodiscover:
<MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=8e4c6389-e877-.....@avilaxxxxx.com/cn=Microsoft Private MDB</MdbDN>
        <PublicFolderServer>ama.avilaxxxx.com</PublicFolderServer>
        <AD>SERVxxxx.avila.local</AD>

SERVxxxx.avila.local it´s my old server and it still exists on my network, but I have uninstalled completely Exchange...

How can I fix the autodiscover??  Also, on Outlook 2013 I am not seeing any Public Folders I created on Exchange 2013 when I am outside the organization.

Best regards,
LVL 2
marpanetAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeff GloverSr. Systems AdministratorCommented:
A few things. What version of Outlook are you using? When you run the following command in the EMS, what do you get?
Get-ClientAccessServer | Select Name,AutodiscoverServiceInternalURI
0
marpanetAuthor Commented:
Outlook 2013.

When running the command:
On name, I get the name of my new server
AutodiscoverServiceInternalUri: I get the external autodiscover url (working one) (https://external.officeurl.com/autodiscover/auto....)

You can configure without problem a new account using autodiscover.
0
Jeff GloverSr. Systems AdministratorCommented:
OK, if you can configure a new account then Autodiscover should be fine. For the Public folders, I assume you have migrated all your old Public Folders to Exchange 2013 and Completed the Migration using the Powershell cmdlet.
When you run
Get-OrganizationConfig | fl
What do you see for PublicFolderMigrationComplete and PublicFodlersEnabled ?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

marpanetAuthor Commented:
True and Local.....

Actually, because we don´t use public folders.... Once migrated the root folder from Exchange 2007 to 2013....  and after trying many things.. I deleted the publicmailbox and recreated it again, without migration, and still cant see it from Outlook....   Also, I can see the "originatingServer" I see the old server, is this normal?
0
Jeff GloverSr. Systems AdministratorCommented:
THe originating server is where you ran Forest and Domain prep from.
0
marpanetAuthor Commented:
Ok, so that´s no problem..
The problem I have is that in the autodiscover
 <PublicFolderServer>ama.avilaxxxx.com</PublicFolderServer>
         <AD>SERVxxxx.avila.local</AD>

The old server appeards....
Also, I have read that the SMTP from the public Mailbox now it´s @domain.local , and I have to change it to @externaldomain.com , but I haven´t been able to.
0
Jeff GloverSr. Systems AdministratorCommented:
Never is easy. Autodiscover.xml is generated on the fly. There is no way that I know of to edit it manually on the server. Can you see what the default Public Folder Mailbox is set to on a user account
Get-mailbox "name" | select name, defaultpublicfoldermailbox

And maybe do a Get-Database -Identity "dbname" | fl and make sure the PublicFolderDatabase attribute is empty

Otherwise, I suspect this has to do with the failed Public Folder migration but where autodiscover.xml gets the PublicFolderServer  from is beyond me.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
marpanetAuthor Commented:
In the Get-mailbox "name", the user does point to the Public Mailbox...

The Get-Database command does not work, I think you meant Get-MailboxDatabase... but when trying using the name of the Public Mailbox, it says it dosent exist.
0
Jeff GloverSr. Systems AdministratorCommented:
There are no Public folder mailbox databases in 2013. I meant to do (and you are right, I meant Get-mailboxDatabase) that command against your mailbox database. Do you have at least one Public Folder mailbox created besides the Primary Hierarchy one?
0
marpanetAuthor Commented:
I am still trying to investigate the problema... post right back this week
0
marpanetAuthor Commented:
I haven´t found a solution to the problem...
I will try to unistall the old Exchange server to see if the problem goes away.
0
marpanetAuthor Commented:
As I uninstalled Exchange 2007 and demoted the old server, the problema went away.

Thank you!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.