Daphne has her knickers in a twist

The MB server went in fine but the CAS has got problems.

Daphne, my new client access server has had the relevant setup /option commands run on her. She's fine and dandy, if I can mix Scooby Doo characters and children's comics on the OS side. But after installing the CAS and HT roles I had 2 errors that alternated, one about HT (hub transport) and one about AD (active directory). One or other was unhappy and consequently the hub transport was not working so no emails were flowing. CAS (client access server) was fine so anyone in the organisation can login, but emails just sit there sulking.

Uninstall Exchange will not remove it all due to the error so you cannot go backwards.
Install Exchange will not fix the problem.
Henrik Walther's msiexec.exe /x trick does not work to remove Exchange either.

Cannot go forwards or backwards. Reapplying rollup 3 does not help.

Pulling Daphne out of active directory is possible but in the interim, meet my new CAS / HT box - Shaggy.

Exchange 2007 and yet not

Now that I'm going live with Exchange 2007 I'm coming across problems I would never have seen during the beta including this one.

The CAS was having problems and I couldn't use the CAS to move mailboxes from 2003 to the MB but I could use the MB. I could use the MB to manage the CAS. I could move mailboxes but once there I could not access them over OWA.

Scratching of head ensued and Mr Arnold couldn't help. Maybe reapplying rollup 3 would cure it? Instead of copying from CAS to MB as per last time, this time the copying was on the CAS by going \\MBname and it failed.

There was the problem - can ping, can't access. Remarkably odd one that is cured by uninstalling the Client for Microsoft Networks from the network stack, restart, re-add it (because it isn't the first server that's suffered from that).

Now OWA works, MB and CAS talk to each other and more to the point, Outlook can now connect as the autodiscover record points to the CAS that is now accessible.