Exchange Autodiscover
Have just moved 10 test mailboxes from Ex2003 to Ex2010. As a test before the move I logged into Outlook 2007 on 5 of the users, the others had never been logged in before.
I have turned off the Ex2003 server. The 5 users who hadn't ever logged on before work fine when opening Outlook, but the 5 other users outlook are still looking for the Ex2003 server.
I thought Autodiscover would fix this so I have set up DNS entry for 'autodiscover' and ran the command:
> Set-OutlookProvider –id exch –server:ex2010
but the XP client is still looking for Ex2003.
Tried to "Test Email AutoConfiguration" in outlook but it seems you need to login to start the test...which I cant do!
(I know that leaving the Ex2003 server on will make outlook change its settings but I want autodiscover to do this and turn off Ex2003)
I have turned off the Ex2003 server. The 5 users who hadn't ever logged on before work fine when opening Outlook, but the 5 other users outlook are still looking for the Ex2003 server.
I thought Autodiscover would fix this so I have set up DNS entry for 'autodiscover' and ran the command:
> Set-OutlookProvider –id exch –server:ex2010
but the XP client is still looking for Ex2003.
Tried to "Test Email AutoConfiguration" in outlook but it seems you need to login to start the test...which I cant do!
(I know that leaving the Ex2003 server on will make outlook change its settings but I want autodiscover to do this and turn off Ex2003)
Akhater
users with an outlook profile should be able to communicate with their old exchange server to know their mailbox was moved.
ASKER
I thought autodiscover fixed this though.
If I manually 'Repair' the profile it works fine and I thought this repair uses the autodiscover service?
If I manually 'Repair' the profile it works fine and I thought this repair uses the autodiscover service?
if you manually "repair" the profile it will work, it will also work if you just open outlook
outlook will connect to the old server and know its mailbox was moved to the new one and the profile will be automatically "repaired'
outlook will connect to the old server and know its mailbox was moved to the new one and the profile will be automatically "repaired'
ASKER
thanks, but the question is about autodiscover. I thought autodiscover was deigned for situations just like this?
From initial Question:
(I know that leaving the Ex2003 server on will make outlook change its settings but I want autodiscover to do this and turn off Ex2003)
From initial Question:
(I know that leaving the Ex2003 server on will make outlook change its settings but I want autodiscover to do this and turn off Ex2003)
did you only create an "A" record for autodiscover, or did you set up an SRV record? an SRV record for _autodiscover is what it looks for
i've had way more problems with autodiscover than not... it never seems to work right when you're outside of the network. even if you dont want to use it, outlook 2007 looks for it every single time you open outlook. this causes all kinds of security mismatch errors when you're trying to log on to "mail.domain.com" but outlook sees "autodiscover.domain.com" with the certificate for mail-dot.
in any case, at a minimum you'll need a public and a private SRV record... private in the local dns to point to the internal ip, and public on your dns host to point to the external ip....
i've had way more problems with autodiscover than not... it never seems to work right when you're outside of the network. even if you dont want to use it, outlook 2007 looks for it every single time you open outlook. this causes all kinds of security mismatch errors when you're trying to log on to "mail.domain.com" but outlook sees "autodiscover.domain.com" with the certificate for mail-dot.
in any case, at a minimum you'll need a public and a private SRV record... private in the local dns to point to the internal ip, and public on your dns host to point to the external ip....
ASKER
Thanks, I'll try the DNS record first. Can you please tell me how to setup a SRV record (rather than A record).
2008 server
2008 server
in your local dns server, in the forward lookup zone for your domain,
new > other record > SRV
_autodiscover, _tcp, port 443, host mail.domain.com (whatever yours is)
that tells the autodiscover feature "for the server offering this service, go to tcp port 443 at this host)
adjust 443 for whatever you're using if not the default
in your external dns, it depends on your host and how their dns manager function works
official how-to:
http://support.microsoft.com/kb/940881
new > other record > SRV
_autodiscover, _tcp, port 443, host mail.domain.com (whatever yours is)
that tells the autodiscover feature "for the server offering this service, go to tcp port 443 at this host)
adjust 443 for whatever you're using if not the default
in your external dns, it depends on your host and how their dns manager function works
official how-to:
http://support.microsoft.com/kb/940881
ASKER
have done this but seems to make no difference. can you please look at attached screenshot of autoconfiguration test from working outlook profile (after repair). ex10 is my new server which all looks correct, so why are my other users (who have previously logged into the ex2003 server) still hanging, looking for ex2003? rather than failing and using the autoconfiguration (autodiscover?) settings?
thanks
autodiscover.doc
thanks
autodiscover.doc
users connected to your domain doesn't use autodiscover dns entry they use the SCP entry.
in the same place where you plased the screen shot move to xml and give me the results
in the same place where you plased the screen shot move to xml and give me the results
ASKER
getting really confused, should I change the Ip address of the 2010 server to that of the 2003 server? took ages to get any account to work.
here's SCP XML output
Thanks
xml-output.txt
here's SCP XML output
Thanks
xml-output.txt
no you should NOT change the IP, can I just understand why you do not want to follow the "standard procedure" to keep the exchange 2003 on ?
ASKER
we are a school with potentially 100's of users per machine and therefore (sometimes) 100's of outlook profiles per machine. even if i left the ex2003 server turned on for a month I would be getting 'outlook profile error' support calls in 3, 4, 5 months time.
OK I understand better your concern now
I assume you have tried to restart outlook on one of the clients, for how long have you waited?
in pure theory outlook should query autodiscovery service every time it is on
what are the results of get-clientaccessserver |fl *aut* and of get-mailboxdatabase | fl name,*rpc*
I assume you have tried to restart outlook on one of the clients, for how long have you waited?
in pure theory outlook should query autodiscovery service every time it is on
what are the results of get-clientaccessserver |fl *aut* and of get-mailboxdatabase | fl name,*rpc*
ASKER
I will take a look (maybe tomorrow now) did you conclude anything from the XML screenshot in previous post?
the XML file you attached proves that autodiscover service is working correctly so is the fact that new profiles are directly configured right.
we are talking about computers joined to your AD domain right ?
we are talking about computers joined to your AD domain right ?
1. Open Exchange 2007 Shell
[PS] C:\Documents and Settings\jchong\Desktop>Se
1. Move the mailbox to a different store on Exchange 2007
2. Verify that inheritance is checked for the user in the security tab, advanced in Active Directory Users and Computers.
I ma suggesting this by looking @
<LegacyDN>/o=Pete Organization/ou=First Administrative Group/cn=Recipients/cn=mar
If the mailbox is moved already it should be pointing to Exchange 2010 and not Exchange 2003
Hope this helps!!
[PS] C:\Documents and Settings\jchong\Desktop>Se
1. Move the mailbox to a different store on Exchange 2007
2. Verify that inheritance is checked for the user in the security tab, advanced in Active Directory Users and Computers.
I ma suggesting this by looking @
<LegacyDN>/o=Pete Organization/ou=First Administrative Group/cn=Recipients/cn=mar
If the mailbox is moved already it should be pointing to Exchange 2010 and not Exchange 2003
Hope this helps!!
ASKER
thanks saakar_rao, can you please explain what I am actually doing by running the command and moving the mailbox to another store?
the mailbox is in the 'staff' store on exchange 2010, should I create another store called 'staff2' and move it there then?
the mailbox is in the 'staff' store on exchange 2010, should I create another store called 'staff2' and move it there then?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just ignore :
"<Server>EX10.X.LOCAL</Ser
<ServerDN>/o=Pete Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi
"<Server>EX10.X.LOCAL</Ser
<ServerDN>/o=Pete Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi
ASKER
OK great, can you please clarify the command? Can I do this for all users at once?
For doing it in bulk
Get-MailboxDatabase -Identity Server01\StorageGroup01\Ma
For outlok to pint to new server you keep the new server up and login in outlook or use some script to redirect the outlook to new server, see this thread:
http://social.technet.microsoft.com/Forums/en/exchangesvrmigration/thread/d042cab9-2309-425b-9e72-6970d028ffa3
Get-MailboxDatabase -Identity Server01\StorageGroup01\Ma
For outlok to pint to new server you keep the new server up and login in outlook or use some script to redirect the outlook to new server, see this thread:
http://social.technet.microsoft.com/Forums/en/exchangesvrmigration/thread/d042cab9-2309-425b-9e72-6970d028ffa3
ASKER
Thanks, I am thinking of trying the exprofre.exe tool, with /s switch -
"Updates profiles based on a change in server name rather than a change in the legacyExchangeDN attribute."
Narayan_singh: you say the problem is not based on legacyExchangeDNso the change for 'server name' may work?
"Updates profiles based on a change in server name rather than a change in the legacyExchangeDN attribute."
Narayan_singh: you say the problem is not based on legacyExchangeDNso the change for 'server name' may work?
This problem is not due to legacyExchangeDN changing server name manually or using the tool will work.
However you can change the legacyExchangeDN using Admodify tool,steps are given in http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx step 5
However you can change the legacyExchangeDN using Admodify tool,steps are given in http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx step 5
ASKER
sorry I don't understand your post.
"This problem is not due to legacyExchangeDN changing server name manually or using the tool will work."
do you mean NOT worK?
if so why then do you point me toward admodify that makes that change...?
"This problem is not due to legacyExchangeDN changing server name manually or using the tool will work."
do you mean NOT worK?
if so why then do you point me toward admodify that makes that change...?
You should change legacyExchangeDN to avoid any issues with Free busy.this is just FYI, not related to your current issue.
And as your issue is changing the exchange server name to new server, that can be done by using exprofre.exe toolor manually.
legacyExchangeDN is not related to the current issue.it was just a information i wanted to give you.
And as your issue is changing the exchange server name to new server, that can be done by using exprofre.exe toolor manually.
legacyExchangeDN is not related to the current issue.it was just a information i wanted to give you.
ASKER
thanks I will set the ApplyMandatoryProperties tomorrow.
i will also test the exprofre tool as well although there is reports on the net of it not working for exchange 2007 onwards.
just as a final note if i leave exchange 2003 on for a bit after the migration what is the minimum state it can be left in. if i move all mailboxes, public folders, policies and connectors will it still be an 'exchange server' able to redirect outlook?
i will also test the exprofre tool as well although there is reports on the net of it not working for exchange 2007 onwards.
just as a final note if i leave exchange 2003 on for a bit after the migration what is the minimum state it can be left in. if i move all mailboxes, public folders, policies and connectors will it still be an 'exchange server' able to redirect outlook?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Whats update ?