Live Communications Server 2005 Webcasts

Introduction to Live Communications Server 2005 - Overview of Real-Time Collaboration and Presence (Microsoft Executive Circle)

Unlock Real-Time Communication in the Enterprise with Failover and Scalability in Live Communications Server 2005 EE (Level 300)

Develop Enterprise Communication with Live Communications Server 2005 and SIP (Level 300)

Maximizing Security Features within Microsoft Office Live Communications Server 2005 (Level 300)

Enable Real-Time Communication with Live Communications Server 2005 and Public IM Connectivity (PIC) (Level 200)

Using Live Communications Server 2005 Technical Troubleshooting Tools and Resource Kit (Level 200)

Live Communications Server and Windows Messenger: Architecture and Automation (Level 300)

How Microsoft IT Deployed Office Live Communications Server 2005 (Level 200)

Real-time Collaboration and Secure Instant Messaging with Office Live Communications Server 2005 (Level 200)

Web Based Conferencing Solutions for Team Collaboration (Microsoft Executive Circle )

XML DataSource Controls in .NET 2.0

XML DataSource Controls in .NET 2.0 by Jesse Liberty -- With .NET 2.0's XML DataSource control, you can bind to an XML document just as easily as you bind to tables in a database. If the XML document you load is hierarchical, the data is exposed hierarchically, which makes it ideal for mapping an XML document to a TreeView control. Jesse Liberty explains how the XML DataSource works in ASP.NET.

Microsoft's Expanding Collaboration Strategy

Collaboration Software
Collaboration Software is sophisticated software to organize team work over the web. Collaboration software solutions offer the ability to communicate complex information within groups and to customers, to organize thoughts and ideas, and to manage information for meetings, presentations, projects, proposals, research, contacts, etc.

Project management tools automate and simplify task management, while web conferencing tools such as screen sharing, instant messaging and polling enable instant real-time collaboration regardless of where each of your team members are located. So your team can work with resources outside your organization as effectively as if they were down the hall.

Please check out some good articles on Microsoft Collaboration Platform
Microsoft's Expanding Collaboration Strategy !!

Microsoft's varied collaboraboration platform strategies !!

Enterprise Collaboration - It's time to consider a platform !!

Optimizing Collaboration and Communications using Microsoft Technologies !!

Team and Enterprise Collaboration Platform !!

Hey that's me !!

Deploying SharePoint Portal Server 2003 on extranet – My Findings

The purpose of this article is to outline the alternative approaches that can be taken to make SharePoint Portal available on extranet.

SharePoint Portal Server provides a great way of sharing data with employees at remote offices, suppliers, partners or anyone else who needs access to private data through an extranet. However, before you can make SharePoint workspaces available through an extranet, there are some security settings that need to be taken care of.

By default, SharePoint is set to use NTLM authentication. Although NTLM is the best choice for authentication, it may be impractical in some environments. For example, you may have users in remote offices who need to access SharePoint data, but who aren’t using Windows machines.

Though SharePoint is designed inherently for Intranets, there are many ways in which I can configure SharePoint for extranet access. However a lot would depend on the current configuration settings and security requirements.

Alternate Access Mappings.
Basically, alternate access mappings are a table which states which URL to use in which scenario. There is default, intranet, extranet, and custom URLs.
Open up SharePoint Portal Server Central Administration and click on the Configure Alternate Portal Access Settings.

On that page, edit your existing SharePoint portal mapping and add your extranet URL. You need to make sure when creating portals not to use your extranet URL as the default URL for the portal.

You can deploy SPS 2003 with or without SSL, but I would strongly recommend using it along with MS ISA 2004.

If you are NOT using SSL…………

If you are NOT using SSL (you should), then after configuring the Alternate Access Settings, add any additional mappings you need – exchange, other intranet URLs, etc. Then make sure DNS is configured properly to point the extranet URL to your SPS box and make sure there are no host headers setup on the Virtual Server in IIS manager.

Also be sure that you have a port rule setup on your router to allow port 80 traffic to pass to your SharePoint Portal Server machine.

If you are using SSL…………

If you are using SSL, then u need (at least) 2 different physical servers hosting the same portal. One for intranet and other for extranet. If u do it this way intranet users will be authenticated automatically based on their windows credentials but extranet users will have to enter their credentials. In most cases you would basic authentication for the server over SSL.

Why you can not use SSL (Secure Sockets Layer) with Host Headers?
When a client requests a "Web site" by using Secure Hypertext Transfer Protocol (HTTPS) over Transport Layer Security (TLS) or over SSL, the HTTP header with the HOST field is contained in the encrypted part of the packet. Therefore, the Web server cannot decrypt the host-header name to determine which Web site the client requested. For this reason, when you use SSL connections, you cannot use host headers as the primary means of identifying a Web site.

To configure https access, you must first setup an additional virtual server in IIS manager.

Open IIS manager and browse to Web Sites, then right-click New -> Web Site. Follow through the wizard changing the port to something that isn’t currently in use and make sure to pick a path that is not the same as the Portal’s current path (something like c:\Inetpub\wwwroot\https).
Right-click on the newly created Virtual Server and choose properties.
Go to Directory Security and click server certificate. Import or request a certificate for this virtual server. Now, test the newly created Virtual Server by opening it in IE. You will probably get an HTTP 403/Forbidden.

This is OK because you don’t have any content in your site yet, but does show that https is working.

For more information about obtaining and installing SSL certificates, see:
Obtaining and Installing Server Certificates in the IIS 6.0

Once you have verified that the Virtual Server works, you need to extend it to connect it to your portal.

Open SharePoint central administration. Click on the “Extend an existing virtual server …” link. Select the newly created HTTPS Virtual Server.

Click Extend and map to an existing Virtual Server link.

This will tell the new Virtual Server to use the same information and configuration database as the existing virtual server, basically allowing users to access the same portal from two different access points.

Choose the portal your want to map to and choose to use an existing Application Pool and choose MSSharePointPortalAppPool. Then click OK to finish the extending process.

If you want (You should) create your application pool for use with this site. Just Go to IIS Manager, Right Click Application Pools, Create New one with your choice of name and leave the rest to defaults. Then go to the newly created web site and from Home Tab, change application pool to whatever App pool you’ve just created. Hit iisreset..

Now We just have to setup alternate access settings, so go back to Central Administration and click “Configure Alternate Access …”. Edit the existing mapping name. If you are using the https site as the extranet url, then enter it into the extranet section. If you already have an extranet access URL, then use the custom URL field.

Now, open your https site (http://test-server.domain.com in my case) in IE to make sure the portal loads and you see the lock (SSL) in IE.

That's it..

Lastly we can use MS Internet Security and Acceleration (ISA) Server 2004. This is the recommended approach.

Following is a list of whitepapers/Articles available from Microsoft which discusses this issue in great details.
SharePoint Portal Server 2003 Document: Deploying on an Extranet by Using ISA Server 2000 and ISA Server 2004


Reverse Proxy Configurations for Windows SharePoint Services and Internet Security and Acceleration Server

Enabling Secure Sockets Layer for SharePoint Portal Server 2003

Enabling Client Certificates and Using Client Certificates When Crawling Content with SharePoint Portal Server 2003

There are webcasts available from Microsoft, you should view it.
SharePoint Portal Server 2003 - Deploying as an Extranet

Enabling Web and SharePoint Applications on the Internet with ISA Server 2004 - Demo 1: Publishing Web Sites with ISA Server 2004

Microsoft SharePoint Products and Technologies Resource Kit has step by step setup instruction. Great resource !!

Other Resources
Tips for a Successful SharePoint Portal Server Extranet Deployment

Configuring SharePoint Portal Server for Extranet Access

SharePoint Portal Server and SSL (Bill English)

ENJOY !!

Office 2003 Web Parts on Multiple Virtual Servers hosting WSS Sites

I ran in a situation where I needed Office Web Parts to be available on multiple Virtual servers on the same machine. I have portal installed on port 80 and several other site collections on other virtual servers on the same machine. By default when you install the Office 2003 Add ins and Web Parts, they get installed in Global Assemly cash and are accessible only on default web site' Visrtual Server Web Part Gallery.

The trick is not too intutive but it works jus fine.

Here's what I did

1. Copy the Office web parts folder from the bin directory of the virtual server on which we've installed the office web parts.. mostly this would be c:\Inetpub\wwwroot

2. Paste this folder on the target virtual server's bin directory

3. Open web.config again from the source location (c:\Inetpub\wwwroot\)

4. Copy the SafeControls entry for office web parts (single line)

5. Open web.config again from the target location (c:\Inetpub\wwwroot\)

6. Paste it onto web.config of the target virtual server..

7. hit iisreset

8. Repeat the steps on each virtual server

you're done

You can download these web parts at this location.


Hope this helps

Parag