Michael Leonard
asked on
Exchange 2010 autodiscover redirect question
not sure if this is possible, but we have Exchange 2010 deloyed in a co-existence mode with our exchange 2003 Org. [same domain / forest]
Does anyone know of a way, that if a user that still has a mailbox on Exchange 2003, but uses a later client like Outlook 2010, is there a way for it to auto discover and realize the mailbox is on 2003 and auto configure for the 2003 user?
other wise, i have to have all 2003 exchange users that are running outlook 2010 clients to choose "manual" config when creating a new profile.
any advice would be appreciated!
S.
Does anyone know of a way, that if a user that still has a mailbox on Exchange 2003, but uses a later client like Outlook 2010, is there a way for it to auto discover and realize the mailbox is on 2003 and auto configure for the 2003 user?
other wise, i have to have all 2003 exchange users that are running outlook 2010 clients to choose "manual" config when creating a new profile.
any advice would be appreciated!
S.
is the computer in question joined to the domain ? if so it should work without any issues
The owa connection has no need to be joined to the domain. It is just a redirect for 2003 users. I do not get Akhaters comment at all.
@PeterSinger the OP never talked about OWA maybe you should re-read the question
ASKER
HI Peter, i was referring to the MAPI clients connecting from outlook 2010, we already had the OWA redirect in place.
Akhater, when i test from a domain PC with a user account on Exchange 2003, i get this error code:
MIcrosoft outlook - an unknown error occurred, error code: 0x80070057
i then get the option to manual configure the profile.
the autodiscover / autoconfigure works fine for any exchange 2010 users, its only the legacy exchange 2003 that get the error.
Akhater, when i test from a domain PC with a user account on Exchange 2003, i get this error code:
MIcrosoft outlook - an unknown error occurred, error code: 0x80070057
i then get the option to manual configure the profile.
the autodiscover / autoconfigure works fine for any exchange 2010 users, its only the legacy exchange 2003 that get the error.
I'm sorry Akhater:is correct.
ASKER
Hi Akhater, yes i did see that hotfix however its not really an option as we have 5000+ users, 90% of which are still on 2003. deploying the hotfix on all users is not really an option.
i guess we'll have to tell them to manually configure any new profiles. was hoping there was a better way to approach it.
i guess we'll have to tell them to manually configure any new profiles. was hoping there was a better way to approach it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks Akhater, i just applied the hotfix and tested and works great!
ill look at deploying via GPO
ill look at deploying via GPO
Glad it worked and thanks for the points
get-set-OwaVirtualDirector
http://technet.microsoft.com/en-us/library/ee332348.aspx