I setup a lab to test an ex2003 to 2010 upgrade. Outlook 2007 client was connecting to ex2003 server just fine prior to schema update. After running the schema updates my client can't connect to the exchange 2003 server. Is it necessary to install a CAS server at the same time as the schema update or is there something else going on? Here are the commands I ran in order: Setup.com /PrepareLegacyExchangePermissions Setup.com /PrepareSchema Setup.com /PrepareAD Setup.com /PrepareDomain Thanks for your help Jacen

The schema update doesn't affect the client at all. It is basically putting things in place ready for the Exchange installation. Therefore I would suspect that is something unrelated. If you are in a single forest deployment there is no need to run the prep separately anyway, the GUI will do it all for you. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Agree with Simon. Per my knowledge, schema update will not affect the clients, please check whether you have done any other changes on the Exchange Server. If you recreate Outlook profile to connect Exchange Server, will it connect or not? If cannot connect, what error do you get? Thanks, Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Thanks for the replies. Sure enough, the issue was not related to the schema update. It seemed to be more of an Outlook and/or networking issue with the virtual machine that I was using. The virtual machine has two network adapters. One for the test network and one for the production. The problem seemed to arise after I disconnected the production interface. To get the client to work again this is what I did: 1) Reconnected the production network interface 2) Start outlook (Automatically connected succesfully to the test ex2003 machine) 3) Disconnect the production network interface After disabling the production network interface again everything was working fine in test. I have no idea at this point what the significance of re-enabling the prod interface was but everthing seems to be working at the moment.Jacen

Glad your problem has resolved. Thanks for your sharing. Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com