Exchange Server
Note that the information below is out of date. As of September 2005 we are using Exchange Server 2003, standard edition.
We did experience a problem installing Service Pack 1 of Exchange Server 2003 but the server is still working OK. Hopefully we will be able to install SP2 OK.
Exchange Server 2000 is set up at the library on a trial basis so that we can determine if this is the communications platform we want to use. See our criteria for selection. As of July 16, we have determined that we will be using this software; it is on order now.
To see Exchange Server at work, use Outlook Web Access to see shared folders or mailboxes. For the latter, you need to log on. You can use user name patron, leave password blank, and specify domain gustavus if asked. You can log on to a different mailbox if you have a local Exchange mailbox and know the user name and password.
Note on setting permissions:
From the release notes:
Only Set Public Folder ACLs in Exchange
System Manager
Although Exchange 2000 allows you to set security on public folders in
the public folder heirarchy and using Exchange System Manager, Outlook,
and the Windows 2000 version of Windows Explorer, the tools are not
interchangeable. This is because Windows Explorer uses the Windows 2000
access control list (ACL) format to set security permissions on the
MAPI public folder heirarchy, and Exchange System Manager and Outlook
use the MAPI ACL format. Exchange Web Storage System can correctly
interpret both ACL formats, but the tools are not interchangeable. For
this
reason, you should only use Exchange System Manager when editing
security on the MAPI public folder hierarchy. This problem does not
exist on general purpose, or application folder, heirarchies. For
example, if you originally use Windows Explorer to set permissions on a
public folder, and then try to use Outlook or Exchange System Manager
to change the settings, you will not be able to change public folder
security until you follow the work around steps provided below. Then
you should only use Exchange System Manager to set ACLs on public
folders.
If the folder in question is a subfolder of Public Folders (Public
Folders\TopLevelFolder), complete the following steps so that Exchange
System Manager can be used to modify permissions.
To allow ACLs to be set in Exchange System Manager:
1.In Windows Explorer, right-click the appropriate folder in the M:
drive, and then select Properties.
2.On the Security tab, in Name, select an account, and then click
Remove. Repeat this step for all accounts.
3.Click to clear the Allow inheritable permissions from parent to
propagate to this object, and then click Remove on the confirmation
dialog.
4.To save the changes, click OK.
5.In Windows Explorer, right-click the folder again, and then click
Properties.
6.On the Security tab, select the Allow inheritable permissions from
parent to propagate to this object
check box.
7.To save the changes, click OK.
If the folder in question is a 2nd level folder of Public Folders
(Public Folders\TopLevelFolder\SecondLevelFolder),
complete the following steps so that Exchange System Manager can be
used to modify permissions.
To allow ACLs to be set in Exchange System Manager:
1. Complete the steps above for the TopLevelFolder.
2. Complete perform the steps above for the SecondLevelFolder.
