Due to a disjointed namespace issue I need to specify the user that Exchange use when running all the test-connectivity* power shell checks. When new-TestCasConnectivityUser.ps1 creates the user it use the mailserver domain after the user name, but in this case, that will not work as the script only looks at the FQDN of the mailserver, not the real domain membership of the server. I have tried to edit the script, but it seems like Exchange always use a CAS_* account to run the scripts, even if the TestCasConnectivity script creates another account. Any ideas? Another solution would be to "hack" the information direct on the exchange server, if anyone knows where it is stored.Anders Bengtsson | Microsoft MVP - Operations Manager | http://www.contoso.se

Hi, Please check whether the RU7 for service pack 1 has been installed. For your reference: All Test commands that are related to the Client Access Server fail when you run the commands on an Exchange 2007 server in a disjoint namespace http://support.microsoft.com/kb/954213/en-us Mike

We have installed all patches. The problem is that it is not a disjointed namespace in form of a extra domain, it is only a DNS namespace extra.Anders Bengtsson | Microsoft MVP - Operations Manager | http://www.contoso.se

Hi, I do not find a method to specify a user when running test-*connectivity commands. It alwaysuse the CAS_GUID account when running the commands. You may need to run test-*connectivity commands with -MailboxCredential switch to specify user account when test CAS connectivity. Mike

Hi Anders,Any updates?Mike

yes, I finally solved this with a custom script, look at http://www.contoso.se for the scriptAnders Bengtsson | Microsoft MVP - Operations Manager | http://www.contoso.se