after installing everything again from scratch , and then i logged in from client machine with Administrator account , and tried to configure outlook automatically i got this problem shown in this screen shot what is wrong in my lap setting ?!! i disabled all firewall every where also i tried to login to web access , using this url https://exchange2k10MB1/owa which Exchange2K10MB1 is name of the mail box server but i got this page screen shot

It looks like the client machine can't connect to the Exchange server. That could be due to any number of reasons, too numerous to iterate here.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

what it could be , it really disapoint me becuase i install the servers for the second time but still there is a problem ... what you suggest ? plz help

Start with DNS name resolution. Can you ping the server from the client? Are there any firewalls between the client and server?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Yes there can be variety of reasons for this and I wouldn't recommend guessing so let’s run the ExBPA to validate if install/Configuration is correct. You can find this tool available under tools in management console. Regards, Pushkal MishrA

im using vmware workstation , and i disabled all the firewall on all the server , every body can ping each other ..

you mean i should run ExBPA , on mail box server ?

i run the ExBPA on mail box server and i got this result screen shot

You 've installed Exchange 2010 SP1 right...?? Also You need to run ExBPA from Client Access Server as well since the client connectivity (Like OWA, Outlook etc) is from here...Post that result as well. Regards, Pushkal MishrA

i run the exBPA on the client and i got these error below or see this screen shot Active Directory Forest Unknown schema extension version : Active Directory Forest The Exchange schema extensions are from an unknown version. Schema version detected is 14622. Tell me more about this issue and how to resolve it. Domain: GLOBAL Unrecognized Exchange signature Domain: GLOBAL Active Directory domain 'GLOBAL' has an unrecognized Exchange signature. Current DomainPrep version: 12639. Tell me more about this issue and how to resolve it. Organization: Global Global incoming message size not set Organization: Global The maximum incoming message size is not set. This can cause reliability problems. Tell me more about this issue and how to resolve it. Global outgoing message size not set Organization: Global The maximum outgoing message size is not set. This can cause reliability problems. Tell me more about this issue and how to resolve it. Admin Group: Exchange Administrative Group (FYDIBOHF23SPDLT) Server: EXCHANGE2K10MB1 VMware detected Server: EXCHANGE2K10MB1 Exchange server EXCHANGE2K10MB1.global.com appears to be running as a virtual machine. Please review the support policy detailed in Microsoft Knowledge Base article 897615. Tell me more about this issue and how to resolve it. WMI service start-up account Server: EXCHANGE2K10MB1 The Windows Management Instrumentation (WMI) service on server EXCHANGE2K10MB1.global.com is not configured to start-up as the computer account (LocalSystem). This configuration is not supported on Exchange servers. Current start-up account is localSystem. Tell me more about this issue and how to resolve it. Server: SERVER2K8PRIME VMware detected Server: SERVER2K8PRIME Exchange server SERVER2K8PRIME.global.com appears to be running as a virtual machine. Please review the support policy detailed in Microsoft Knowledge Base article 897615. Tell me more about this issue and how to resolve it. WMI service start-up account Server: SERVER2K8PRIME The Windows Management Instrumentation (WMI) service on server SERVER2K8PRIME.global.com is not configured to start-up as the computer account (LocalSystem). This configuration is not supported on Exchange servers. Current start-up account is localSystem. Tell me more about this issue and how to resolve it.

Ok, now first resolve this WMI error using the link http://technet.microsoft.com/en-us/library/aa99676 (EXCHG.80).aspx Then test if autodiscover is working fine http://technet.microsoft.com/en-us/library/bb123573.aspxRegards, Pushkal MishrA

thanks for the reply the first link is not working :(

http://technet.microsoft.com/en-us/library/aa996766(EXCHG.80).aspx Try nowRegards, Pushkal MishrA

i should run this Test-OutlookWebServices -ClientAccessServer "CASServer01" on hub and CAS server , and change the CASserver01 with the CAs server name ? i should run this form power shell or command prompt another thing , where i should do this To configure the WMI service account Open the Services Microsoft Management Console (MMC) snap-in. on host computer or in side vmware please advice

i already checked the MMC , as shown her screen shot , and it was like how it described in the link but any way i stopped and i run it again

Hello, Does this issue occur on all the versions of Outlook clients, such as Outlook 2007 or Outlook 2010? If it does not occur to all the clients, please update the Outlook o he problematic clients and check the issue again. If all the clients cannot be connected to Exchange, do the following tests to narrow down the causes: 1. Ping the CAS server IP from a problematic client. 2. Run “Test-webservices” command on the CAS service to see if there are any issue with the autodiscover service. 3. Try manually configuring the Outlook profile and see if it can pass. For the Exbpa unrecognized signature issue, please check whether a web.config file is present under C:\Program Files\Microsoft\Exchange Server\ClientAccess\OAB. If so, please rename it to web.old. Thanks, Simon