Oh dear, really need your help on this one guys! I decided it was time to update to sp2 on our SBS 2008. I downloaded the files, and the installation tool which is meant to help update SBS 2008 if you don't want to do it all manually. Anyway, I started the update this Sunday evening and ran into problems almost immediately. Once I got through the pre-requisites, it started preparing the setup. It started to 'remove exchange files' and got to 'Hub transport role' where it failed for the first time. It said that it couldn't start the exchange active directory topolgy service as it was disabled. I'm pretty sure the tool had disabled it? In any case, I set that to automatic and ran setup again. This time it went as far as the mailbox role when it had a similar failure, this time for another service. I changed it from 'disabled' to automatic and ran again. This time, everything ticked, it seems to have updated. However, when I restart the server, all the services are still set to disabled. So, I enable them all, and restart again. No outlook now though, and no OWA. I do some research on google, and run the 'fix network' tool and also re-run the self-cert wizard. This fixes OWA and also I can send email and receive. So, exchange does appear to be working but somethings are definitely broken. I can't set up Outlook profiles. I just get the error 'the name cannot be resolved. the connection to exchange is unavailable' . That's weird because if I use a profile that's already set up then I can connect to outlook and send/receive. This is a problem as I have a new starter tomorrow and can't set up his email! Is there a service connected with this? I don't know what it is.... the exchange BPA is not returning anything strange, but I'm getting some weird events. For example: The description for Event ID 17137 from source MSSQL$MICROSOFT# #SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. and The start address <sts3s://sbs. domaint.com: 987/contentdbid= {141945ef-07e8- 47de-b67d- a426426d9710} > cannot be crawled. and The configuration information of the performance library "C:\Windows\ system32\ sqlctr90. dll" for the "MSSQL$SBSMONITORIN G" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted. and The description for Event ID 2803 from source MSSQL$MICROSOFT# #SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. I really hope this is resolvable. If any of you are able to help I would be so grateful! Otherwise, I think a call to PSS will be the first thing I'm doing tomorrow! Thanks, Magnus

Quick update to this - maybe it will help find the solution... I notice I have no problems setting up new profiles on a Windows 7 pro machine with Outlook 07. And the old profiles work too. Interestingly though, it doesn't auto resolve the server name and username as it normally would when connecting from a domain machine; it has to be set manually. However, on a Windows XP machine, I cannot setup new profiles (same error as below) and also, current profiles just remain 'disconnected' and won't send / receive.

Those errors/warnings you posted are related to Windows Sharepoint Services. It sounds like your autodiscovery information is incorrect. That will usually give you the "the name cannot be resolved. the connection to exchange is unavailable". I would run "Test-OutlookWebServices" on the Exchange/SBS server to make sure your autodiscover information is correct. It could also be permissions on the IIS site preventing autodiscover from working.

Hi,I agree with Corey.When we try to configure the outlook profile, it will try to query SCP from DC and get autodiscover URL and then try to connect.So first please ensure that Authenticated Users account on the Client Access server has Read permissions for the SCP object. Note: You will see the SCP object when you use tools like ADSIedit. You can find the SCP at the following location: CN=<CAS_server>,CN=AutoDiscover,CN=Protocols,CN=<CAS_Server>,CN=Servers,CN=Exchange Administrative Group, CN=AdministrativeGroup,CN=<Organization>,CN=Services,[Configuration Naming Context].Then please try to run get-autodiscovervirtualdirectory |fl and then find the URL for autodiscover,please try to manually browse the autodiscover url and then post the result here.Regards,Xiu