When searching sharepoint 2010 you may receive the following error:

The Web application at http:/// could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

This often happens because the proper alternate access mappings is not configured.  For instance if you are webbing into the server via IP you need to make sure you have an intranet or internet setting in the alternate access mappings.  If you have a public DNS then you will need to configure an internal URL with the internet zone.

This is done by going to central  administration

• clicking application management
• click configure alternate access mappings

How to configure Exchange 2003 to work with Droid. 

1. Login to your exchange 2003 server
2. Launch exchange System Manager
3. Expand Global Settings
   1. Goto properties of Mobile Services
   2. Make sure that everything is checked on this page as seen below:

Device Security should be all unchecked (at least that’s what I did)

Now that you have done that goto the following site:

https://[URL of Your Server]/oma/

you should receive a page that has the following content:

If you receive an error it might say this:

Outlook(R) Mobile Access is supported only on Microsoft(R) Exchange Server 2003. Currently your mailbox is stored on an older version of Exchange server. Please contact your system administrator for additional assistance.”

Follow this link from MS which will resolve your issue:

http://support.microsoft.com/kb/817379

Most of your commands will be in the Exchange Management Shell so open that up.  First command you will need to run is:

Get-WebServicesVirtualDirectory | Select name, *url* |fl

Which will output something like this:

Name                 : EWS (SBS Web Applications)

InternalNLBBypassUrl : https://site.domain.local/EWS/Exchange.asmx

InternalUrl          : https://mail.site.com/ews/exchange.asmx

ExternalUrl          : https://external.site.com/EWS/Exchange.asmx

In my case I registered mail.site.com and the mismatch was with external.site.com.  above is my final product as only InternalUrl needed to be changed.  I didn’t mess around with ExternalUrl as the issue is fixed now. One you run the above command you will need to take note of everything after Name (EWS (SBS Web Applications)).

You will then need to run some commands.  Please reference the following Microsoft article:

http://support.microsoft.com/kb/940726/en-us

CAS_Server_Name = your registered url or internal server name, I didn’t find that it mattered.

Note that the KB article is intended for regular exchange and not SBS 2008 so my commands have some modifications.  In a nutshell we need to substitute Default Web Site with SBS Web Applications.

below are the commands that I used based on this article:

Set-ClientAccessServer -Identity site.domain.local -AutodiscoverServiceInternalUri https://mail.contoso.com/autodiscover/autodiscover.xml

Set-WebServicesVirtualDirectory -Identity “EWS (SBS Web Applications)” -InternalUrl https://mail.site.com/ews/exchange.asmx

Set-OABVirtualDirectory -Identity “oab (SBS Web Applications)” -InternalUrl https://mail.site.com/oab

Set-UMVirtualDirectory -Identity “unifiedmessaging (SBS Web Applications)” -InternalUrl https://mail.site.com/unifiedmessaging/service.asmx

Once you run the above commands you can continue on step 6 of the referenced MS KB article.

After I completed this I noticed that a send and receive did not complete successfully.  I got to about 97% and received the following error:

task microsoft exchange reported error (0x8004010f) the operation failed. an object cannot be found

to fix this error you need to make sure you are managing a forward zone for your domain, in this case site.com.  for my internal users I needed mail.site.com to resolve to the internal IP address of my server.  I noticed the internal IP wasn’t set so I changed this value.  Once that was completed everything worked like a charm.

Hope this helps, please comment if you need anything else.

 Run a full backup on your MS 2003 standard server

1. Make sure your domain has been  promoted to domain functional level and forest function level of Windows Server 2003.
   1. To upgrade open up Active Directory Domains  and Trustes
   2. Right click Active Directory Domains and Trusts and click Raise Forest Functional Level

                                    i.      Upgrade to windows server 2003

                                    ii.      This will upgrade your forest

1. Now right click your domain and click raise domain functional level

                                     i.      Upgrade to windows server 2003

                                    ii.      This will upgrade your domain

1. To verify everything is setup properly open up Active Directory Users and Computers
2. Right click your domain and go to properties

                                     i.      Both domain and forest functional levels should have windows server 2003 underneath them

1. Check event viewer and make sure there are no errors, especially dns or replication errors
2. Stick in SBS 2008 disk 1 DVD into the Windows 2003 Standard server (source server)
   1. Open up a command prompt
   2. Change directories to cdrom drive\tools\adprep
   3. Run “adprep /forestprep”

                                      i.      Let this complete and make sure everything is successful

1. Run “adprep /domainprep”

                                        i.      Let this complete and make sure everything is successful

1. Run “adprep /domainprep gpprep”

                                        i.      Usually this wont run because the above commands did the trick

1. Now open execute cdrom drive \tools\sourcetool.msi (this is a gui)
   1. Install the migration program
   2. After you install it run the wizard
2. Now you will need to create an answer file
   1. You can now follow the SBS 2003 to SBS 2008 migration guide provided by Microsoft.
   2. This document is located here: http://www.microsoft.com/downloads/details.aspx?FamilyID=52b7ea63-78af-4a96-811e-284f5c1de13b&displaylang=en
   3. I started on page 17, but you are welcome to start at page 1

To uninstall windows internal database you will need to do the following:

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
Edit the “InstalledInstances” value and remove “MICROSOFT##SSEE”

2) Remove the “MICROSOFT##SSEE” subkey under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

3) Remove the “MSSQL.2005″ subkey under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

4) Rename the following folder:
\%Windir%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data to \%Windir%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data.old

After you are done with this step, try to uninstall windows internal database, it should work.

Now that you have windows internal database uninstalled, we will need to uninstall wsus 3.0

You will need to do the following:

Go to:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup]

Change the value for “wYukonInstalled” from 1 to 0

After you do this you will need to uninstall wsus, this is done by clicking the same file you use to install wsus.

After you do this you should be able to install wsus 3.0