Skip to main content

SharePoint 2003 and Exchange 2003 Integration

There are 3 possible ways to integrate SharePoint 2003 and Exchange Server 2003:
  1. Using the Exchange Web Parts
  2. Displaying Exchange Data in a Page Viewer Web Part
  3. Creating an E-Mail-Enabled Document Library
Using the Exchange Web Parts:
SharePoint 2003 provides 4 web parts that can display Exchange mailbox data. These web parts are:
  • My Calendar
  • My Inbox
  • My Mail Folder
  • My Tasks
Display Exchange Data in a Page Viewer Web Part:
You can use Page Viewer web part to display content in Exchange Server 2003 public folder. Configure the URL in page viewer web part to point to:

http://exchangeservername/public/company%20meetings/?cmd=contents&view=monthly

Possible view parameter can be daily, weekly and monthly. It is case sensitive.

Creating an E-Mail-Enabled Document Library
SharePoint 2003 document library can be linked to Exchange public folder, so any files attached to the message sent to public folder will be copied to linked document library. Exchange will also populate some other columns from e-mail message:
  • From address
  • E-mail subject
In order to set up e-mail enabled document library, you need to configure on both SharePoint server virtual server level and Exchange public folder.

For more detailed information: see this link:
http://www.microsoft.com/technet/windowsserver/sharepoint/V2/reskit/c4161881x.mspx

Comments

Post a Comment

Popular posts from this blog

X509Certificate2: The system cannot find the file specified.

When I use the new X509Certificate2(fileName, password, X509KeyStorageFlags.DefaultKeySet) to create certificate from certificate file containing private key in my web application, I got following error message: System . Security . Cryptography . CryptographicException : The system cannot find the file specified . at System . Security . Cryptography . CryptographicException . ThrowCryptogaphicException ( Int32 hr ) at System . Security . Cryptography . X509Certificates . X509Utils . _LoadCertFromBlob ( Byte [] rawData , IntPtr password , UInt32 dwFlags , Boolean persistKeySet , SafeCertContextHandle & pCertCtx ) at System . Security . Cryptography . X509Certificates . X509Certificate . LoadCertificateFromBlob ( Byte [] rawData , Object password , X509KeyStorageFlags keyStorageFlags ) at System . Security . Cryptography . X509Certificates . X509Certificate2 .. ctor ( Byte [] rawData , String password , X509KeyStorageFlags keyStorageFlags ) In orde...
10 comments
Read more

Forms authentication ReturnUrl strange behavior and fix

When working with .NET forms authentication, I have found a strange behavior: For example, we have a web site using form based authentication. There are only two pages in the site: login.aspx and default.aspx. Default.aspx is the protected page. Without login to the site, if you type directly the URL to the default.aspx page with ReturnUrl as QueryString like this: http://localhost/YourWebApp/Default.aspx?ReturnUrl=Default.aspx Instead of redirect you to the login.aspx page, you will directly get http unauthorized error (401.2). However, if you remove the ReturnUrl query string or change it to something else, you will get expected behavior: redirect to login.aspx page. It seems .NET has some special treatment to ReturnUrl parameter. In order to fix this, we need to intercept the 401 response before it sends to client and redirect user to login.aspx page. In global.asax page, we need to add this event handler:         protected void Applica...
Post a Comment
Read more

Manage IIS 7 remotely using PowerShell and AppCmd

We can use  Windows PowerShell remoting features  to manage IIS 7 websites remotely.  Currently, remoting is supported on Windows Vista with Service Pack 1 or later, Windows 7, Windows Server 2008, and Windows Server 2008 Release 2.  Start Windows PowerShell as an administrator by right-clicking the Windows PowerShell shortcut and selecting Run As Administrator .  Enable PowerShell Remoting with Enable-PSRemoting -Force Starting a Remote Session using:  Enter-PSSession -ComputerName <COMPUTER> -Credential <USER> Now the PowerShell connected to the remote server. Any commands issued with work against the remote server. We can use the Appcmd.exe command line tool to manage remote server just as what we do locally. For example, to add an application pool: c:\windows\system32\inetsrv\appcmd add apppool /name:"Contoso" /managedPipelineMode:Integrated /managedRuntimeVersion:"v4.0" /enable32BitAppOnWin64:true To change application p...
Post a Comment
Read more