Outlook 2007 will allow for drag-n-drop from the following:

1. Tasks to a Task List
2. Calendar to a Calendar List
3. Contacts to a Contact List

What is missing here is Mail directly into a SharePoint List or SharePoint Library.  “What do you mean.”  Outlook does not support drag-n-drop to a SharePoint List or Library.  You will receive a read-only error.  

Because of Web-Dav this is not possible without setting up synchronization or a third party utility.  Todd Klindt has several blog entries on Outlook and Sharepoint one of which discusses synchronization. 

Drag-n-Drop into a Document Library

Manage your document libraries from Outlook 2007 using drag-n-drop.  If you have a SharePoint Library synchronized with Outlook, you can drag e-mail attachments directly to it.  Select and drag it to the folder.  This will be sent automatically to SharePoint when the next synchronization occurs.

If that solution does not work for you there are several vendors with solutions.

• Colligo Contributor
• nSynergy myDocs
• Macroview Wisdom Message

I have not fully tested any of the above add ons for SharePoint but have heard great things about all of them.

The Technical Specification is posted here.

See the blog post at Enterprise Content Management Blog.

Press Release

1. User Profile Replication Engine (Office SharePoint Server)
2. Batch Site Manager (Office SharePoint Server)
3. Updatealert Stsadm operation (Office SharePoint Server)

There are two tools for WSS V3:

1. Batch Site Manager (Windows SharePoint Services)
2. Updatealert Stsadm operation (Windows SharePoint Services)

For a full overview and installation instructions see both Zach’s blog and the SharePoint Team Blog.

Microsoft has published their Support guidlines for running SharePoint on a Virtual Environment.  They have taken the stance on supporting SharePoint running on Hyper-V and support for third parties as defined in a KB Article.  Additionally Microsoft has established the Server Virtualization Validation Page (SVVP).  For full details see the blog entry from the SharePoint Team from August 18th. 

Michael Donovan has done a great job evaluating Hyper-V versus Virtual Server.  This is a great comparison and has convinced me to switch to Hyper-V where possible.

Now for the Infrastrucute recommendations Microsoft has stated they will have something shortly.  But until then I tend to go with the experience I have gained.

1. WFE’s as a single role can be built on a Virtual Server
2. Index and Query should be evaluated for load and IO and when necessary located on physical hardware.
3. The SQL Backend for SharePoint should always be placed on a physical server, clustered whenever possible.   This is due to the Processor, RAM and IO requirements.
4. Test and Development environments should be evaluated on an ongoing basis on whether physical environments are necessary.

I am willing to reevaluate and plan differently I look forward to comments and feedback.

Patterns and Practices for SharePoint Guidance this is published and updated on a regular basis and while not a complete guide to all there is, it is a great place to start.

It turns out the fix is not too difficult and I wanted to repost here.

1. Open up FireFox
2. Type about:config in the address bar
3. Locate the key named network.automatic-ntlm-auth.trusted-uris.
4. Set that key’s value to a comma separated list of servers you want NTLM auth for

This was posted on various blogs but wanted to point this out as the client couldn’t seem to locate themselves.

Note: This is not a problem for those clients using Kerberos

The long and the short of it is that this is not a good idea and you will be left with a series of uninstalls and reinstalls for the .Net Framework. 

Here is the link for the SharePoint Team blog alert on this issue. 

Microsoft Knowledge base article 957254.

The MOSS 2007 SDK 1.4 was released and added additional coverage for Federated Search, Documentation and Records Management API.  See the Link below.

The Best Practice Resource Center for SharePoint is now available and is based on real world MCS experience.

The SharePoint Administration Toolkit 2.0 is now available and assists with High Availablity for SSP and synchronizing User Profiles.  This is a must have for all of those geographically dispersed environments.

1. WSS 3.0 and MOSS 2007 SDK 1.4 Download and Online MSDN Library
2. Best Practice Resource Center for SharePoint 2007
3. SharePoint Administration Toolkit 2.0

One of the students had created an SSP and needed to delete it because of a misspelling.  While this is normally a straight forward process it is a little more complicated when it is the first/default SSP.

As we quickly discovered you can not delete the default SSP from the Central Administration interface.  A little quick digging and we came up with three different options which I thought I would share here.

1. Create a new SSP, move all of the web apps associated with it using the change associations button.  Make it the default with the change default button.  Delete the original SSP as it is no longer the default.
2. stsadm.exe -o deletessp -title <name of the SSP> it may require -force as well
3. http://SharePointandBeyond:8830/_admin/deletessp.aspx?sspId=”GUID of SSP”

These should help if you run into the need to delete the default SSP.