Transistion from 2003 to 2010 Exchange. Creating new outlook profiles will only allow you to use old servername not new servername.
We moved 2003 users to 2010 succesfuly and operational. However when creating a new profile in outlook the server wants the old exchange servers hostname. This server is also an AD server and the 2003 exchange is not decomissioned yet so they are co-existant. I'm wondering what steps to ensure when I decomissin 2003 the old accounts are not complaining. If there is a reason behind why this is acting like this that insight would be great.
August 3rd, 2011 10:21am

When you're putting in the ex 2003 it's doing the redirect, however you should be able to put in the Ex2010 server. Are you able to create the profile using autodiscover? Does this happen for a new mailbox created on 2010? Also can you explain your 2010 environment, how many servers, are you using a cas array? Perhaps you're entering your mailbox server name instead of your CAS servername or your CAS array name.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2011 11:58am

Autodiscover doesn't work, happens on new mailboxes as well. The following: Exchange Client Access 1 (server name: clientaccsvr1) Exchange Cluster 1 Exchange Cluster 2 Exchange Hub Transport I'm using clientaccsvr1 when the outlook asks for the servername but it will not checkname, I need to divert to the 2003 server (which is also an AD machine). James James
August 3rd, 2011 1:30pm

Does the check name happen if you point it to a DC (not same DC that your 2003 is on)James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2011 1:38pm

Yes, checkname just dont want to work on the clientaccsvr1 I just want to assure that when i decomission the 2003 server there is nothing im missing and hesitant on doing so. JamesJames
August 3rd, 2011 2:07pm

Yes but if you put a DC name instead of the exchange does the check name work? I want to see if the DC will correctly resolve to the 2010 server.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2011 2:45pm

yes sir.James
August 3rd, 2011 4:44pm

Hi James, Does old created profile (Outlook profile created before mailbox moved to Exchange 2010) redirect to the new Exchange Server? How is the setting on your DNS server, do you add all the records it needed? When you run Dcdiag and netdiag on the CAS server, do you get any error? Please use Exchange Best Practices Analyzer to check whether there is any related information. When you want Transition from Exchange 2003 to Exchange 2010, here are some related documents for you: Upgrade from Exchange 2003 Client Access http://technet.microsoft.com/en-us/library/ee332348(EXCHG.140).aspx Decommission Existing Exchange Servers http://technet.microsoft.com/en-us/library/cc463439(WS.10).aspx#BKMK_outlook Thanks, Evan
Free Windows Admin Tool Kit Click here and download it now
August 9th, 2011 2:48am

On the CAS Server: C:\Users\admin>netdiag 'netdiag' is not recognized as an internal or external command, operable program or batch file. C:\Users\admin>dcdiag Directory Server Diagnosis Performing initial setup: Trying to find home server... ***Error: EXCLIENTACCSVR1 is not a Directory Server. Must specify /s:<Directory Server> or /n:<Naming Context> or nothing to use the local machine. ERROR: Could not find home server. C:\Users\admin The old users work fine and redirect but when I setup a new user or program a new outlook profile for an old user it will not check name using cas.
August 9th, 2011 4:12pm

What is the error message what you get for the new user and using the E2010 server name. Is there any differences if you use FQDN for the E2010? -- Petri
Free Windows Admin Tool Kit Click here and download it now
August 9th, 2011 5:58pm

What is the error message what you get for the new user and using the E2010 server name. Is there any differences if you use FQDN for the E2010? -- Petri There is no error message just a timeout, no different in using fqdn. The fact that the CAS is not an AD Server does this make a difference and the old 2003 cas was an AD still coexistant as ad? Back to the original problem. the new CAS will not checkname (is not an ad).James
August 9th, 2011 6:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics