About two weeks ago we migrated our mail from an external Exchange hosting company named MailStreet to our own internal Exchange 2007 server. Most of the migration went extremely smoothly, however our poor Creative team has had to use Outlook Web Access (OWA) the entire time because Entourage 2004 wasn't playing nicely with Exchange 2007. I blame Entourage because it is the client rather than the server. 
Over the past two weeks I have tried various things before finally resolving the issue today. Initially I thought that Entourage connected to Exchange via IMAP but I soon learned that it actually connects via WebDAV in the same manner that OWA does. In the end I had three different items that I needed to have setup properly.
- WebDAV has to be enabled on the IIS site where OWA is running.
- Exchange 2007 uses a new method for OWA to connect to the CAS backend server, however it has legacy virtual directories for connecting applications that use the Exchange 2003 methodology. The two folders you need to point your Entourage to are "server.domain.com/exchange" for the mail and "server.domain.com/public" for the public folders.
- The final piece that you need is to append the user's email address to the mail server address like this: "server.domain.com/exchange/user@domain.com"
MS has this support article: http://support.microsoft.com/kb/931350/en-us
You cannot connect to your mailbox on Exchange Server when you use Entourage 2004 for Mac
SYMPTOMS
When you use Microsoft Entourage 2004 for Mac, you cannot connect to your mailbox on Microsoft Exchange Server.
CAUSE
This issue can occur when the URL that is used by Entourage 2004 to connect to Exchange Server is in the wrong format.
RESOLUTION
To resolve this issue, manually configure the Exchange Server account properties in Entourage. To do this, follow these steps:
| 1. | Start Entourage. |
| 2. | On the Tools menu, click Accounts. |
| 3. | If you already have configured an account, click Exchange, click the account that you want, and then click Edit. Go to step 6.
If you have not configured an account, click Exchange, and then click New. |
| 4. | If you do not receive the New Account dialog box, go to step 5.
If you receive the New Account dialog box, click Assist me. |
| 5. | Click Configure account manually. |
| 6. | In the various entry boxes, type suitable values. Alternatively, keep previously entered values. |
| 7. | In the Exchange server box, type the value in one of the following formats, as appropriate for the network that you are using:
| • | On the internal network, use the following format: server01.contoso.com/exchange/user@contoso.com
| | • | On the external network, use the following format:
mail.contoso.com/exchange/user@contoso.com
|
Important If the
mailbox resides on a computer that is running Microsoft Exchange Server
2007, you must provide the name of the computer that is performing the
Client Access Server role. |
| 8. | On the Advanced tab, enter other details as necessary. Alternatively, keep previously entered values. Then, click OK. |
| 9. | Exit
and then restart Entourage. This makes sure that Entourage uses the
newly entered Exchange Server account settings to connect to the
mailbox on the server that is running Exchange Server. |
Well as always I hope this helps someone else, cause it sure has given me much consternation and I found very little info out there until finding the MS Support article at the very bottom of the comments on this blog.
A couple of days ago I needed to set my instance of Windows Server 2008 up so that appcmd.exe worked without having to be in the %system%\system32\inetsrv folder. Well as you know there two ways to do this, move the exe to another folder that is in the path, or add the inetsvr folder to the path. I chose the later because I don't like moving files from thier home folder. The first tool I used to try and get this set up was setx, but it just didn't work for me. I'm not sure if it doesn't do what I needed (it sure looks like it should have) or if I wasn't using it properly. I ended up going with a PowerShell cmdlet named set-itemproperty. This allowed me to modify the path through the registry so that the change "sticks" even after reboots. You'll need to enable PowerShell on your server and run it with administrator permissions.
The complete cmdlet to make the registry change is:
set-itemproperty -path
"HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment"
-name path -value "%systemroot%;%systemroot%\system32; %systemroot%\system32\WindowsPowerShell\v1.0\; %systemroot%\system32\inetsrv"
I have inserted spaces in the path to make it readable for the site. Make sure you remove them before running the cmdlet.
Make sure you run "path" first to determine what your existing path is so you can append "%systemroot%\system32\inetsrv" to it.
As always hope this helps someone as much as it helped me.