SharePoint / MOSS 2007 User Management Explained

There is a really good article on MOSS User Management published by Bamboo solutions

Microsoft Codename "Astoria" CTP toolkit enables developers to create and consume Data Services for the Web

The goal of Microsoft Codename Astoria is to enable applications to expose data as a data service that can be consumed by web clients within corporate networks and across the internet. The data service is reachable over regular HTTP requests, and standard HTTP verbs such as GET, POST, PUT and DELETE are used to perform operations against the service. The payload format for the data exchanged with the service can be controlled by the client and all options are simple, open formats such as plan XML and JSON. The use of web-friendly technologies make it ideal as a data back-end for AJAX-style applications, Rich Interactive Applications and other applications that need to operate against data that is across the web.

Read More & Download....

Team System Web Access (formerly known as TeamPlain) released

Team System Web Access (formerly known as TeamPlain) is a Web interface to Visual Studio 2008 Team Foundation Server. The following features are available in the new release:

1. NEW: Display custom controls on work item forms
2. NEW: view queued builds new, queue new builds
3. Add new work items or edit existing ones
4. Work with any type of work item, including custom ones
5. Add new work item queries or edit existing ones
6. View, download, upload, check-in and check-out documents on SharePoint team portal
7. View reports, export as PDF or Excel
8. Browse source control repositories, download files, view changesets, diffs, histories, and annotated views
9. View build results, start or stop builds
10. Search for keywords in work items

DOWLOAD this awesome tool from Microsoft website today

SharePoint Project Management: Better Handling of Multiple Project Sites (3rd Party Tool for MOSS)

http://store.bamboosolutions.com/kb/article.aspx?id=10739

SharePoint 2007 / MOSS 2007 Backup Pros and Cons, Evaluation Standards & Strategies (3rd Party tool for MOSS)

With SharePoint quickly becoming the preferred platform for team collaboration, protecting it against data loss and damages is a key concern for today’s administrators. Can you distinguish various types of data based on its importance? Can you backup critical, frequently changing sites and documents to separate storage tiers? Though improved, the native SharePoint 2007 backup tools still have major issues with recovery granularity, performance, fidelity, and usability. This webinar discusses MOSS 2007 backup Pros and Cons, and recommends new evaluation standards and practices for SharePoint backup.

AvePoint specializes in award winning, enterprise-strength backup solutions for MOSS 2007, WSS 3.0 and Project Server 2007. Today, with 700+ production customers (many of them Fortune 500 companies) and well over 2000 trial customers across 6 continents, AvePoint has become the dominant market leader in SharePoint staging, backup, and disaster recovery solutions.

eMail Management and Outlook Integration through nSynergy (3rd party tool for MOSS)

I came across a product from nSynergy that specializes in email and document management using SharePoint 2003/2007. They have developed Drag&DropIt™ to integrate SharePoint and Outlook and finally solve the problem of managing emails within SharePoint. Drag&DropIt™ allows you to easily save emails and email fields into SharePoint document libraries both online and offline. View this demonstration to find out more about dragging and dropping emails into SharePoint and accessing your SharePoint document libraries without ever leaving Outlook


Why is eMail Management so critical?

eMail management has become a high priority for all businesses, both large and small, with most written correspondence being delivered in email form. Businesses can use tools like SharePoint to manage most of their important business documents, but the inability to easily place emails into SharePoint and share those files within a document library is a problem that many SharePoint users have encountered.

You can now use Outlook to drag and drop emails directly into SharePoint document library folders. You can also view, open, create and access documents and emails directly within Outlook. With emails, documents and other files being accessible through Outlook, everyone in your workplace can use Outlook and SharePoint together to create a powerful yet simple document management tool.

The ability to automatically move emails from Outlook into SharePoint and create document library folders from Outlook is a process that will energize your SharePoint 2007 workflows.

nSynergy product that leverages the familiarity of the Outlook interface and the powerful searching features of SharePoint is needed. Metadata from emails such as Date Received, Date Sent, From and other fields are transferred automatically into a document library’s columns by simply dragging and dropping emails into Outlook folders. This makes it easier to filter and search for these emails and utilize the power of the SharePoint document library views.

How to index PDFs in MOSS 2007 document libraries

SharePoint document libraries are phenomenal tools for collaborative environments where files are shared. And SharePoint's ability to search files in document libraries makes finding files easy. Well, unless the document is a non-Microsoft file type, such as the ever-present PDF file.


The sad fact of the matter is that Windows SharePoint Services (WSS) 3.0 and Microsoft Office SharePoint Server (MOSS) 2007 can't index PDFs by default. That's not news to many veteran SharePoint professionals. Nor is the fact that you can add an icon for PDFs, reindex existing documents, and so forth. However, many administrators are new to SharePoint, and will hit their heads hard against this problem. I was disappointed to see that, despite extensive searching on Google, I could find no single, authoritative, and (most importantly) complete guide for how to do so.

The "bottom line" is that you must install an iFilter for PDFs on your SharePoint servers--specifically, any server that performs search, which would be all WSS servers and your MOSS search server. iFilters are plug-ins that enable indexing of file types. Although iFilter is a Microsoft specification, it is generally through vendors or third parties that you'll get iFilters--not through Microsoft itself.

After you add the iFilter, you must configure SharePoint to index the file type (.PDF). But then, you still have two problems. The biggest is that SharePoint will index only files that are added or existing files whose properties change. So SharePoint will not index existing PDFs when you add the PDF iFilter. You must rebuild your index. The second challenge, purely a cosmetic one, is that you enable SharePoint to display an appropriate icon for PDFs.

This installment will focus on 32-bit WSS servers. Both of these documents contain the word "iFilter" in them, but a search produces only the Word document. Now, let's fix the problem!

1. You will need two downloads: The Adobe PDF iFilter version 6.0, available from Adobe click here
An icon for PDFs, also available from Adobe. Check their licensing page then download the gif


2. Install the iFilter. Note: Many guides on the Internet suggest shutting down Microsoft IIS or the Shared Service Provider (SSP) or the WSS application(s). I found this was not necessary, and Microsoft's own KB article 927675 did not specify it was necessary.


3. Add a registry entry for the .pdf extension in the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\\Gather\Search\Extensions\ExtensionList. (Open the registry editor. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\\Gather\Search\Extensions\ExtensionList\. Identify the highest "number" value in the key. On a default installation of WSS, the highest entry is 37. Note they are not sorted in numeric order because registry value names are strings. Create a registry value for the next number, e.g. 38, by choosing Edit à New à String Value then naming the value the next highest number (e.g. 38). Double-click the value you just created and, in the Value Data box, type: pdf. Note there is no dot preceding the extension.


4. There are two registry keys with specific values that must exist. Verify that these exist and, if not, create them: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf - Value Name: Default; Type: REG_MULTI_SZ; Data: {4C904448-74A9-11D0-AF6E-00C04FD8DC02})
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Setup\Filters\.pdf (Value Name: Default; Type: REG_SZ; Data: (value not set) - Value Name: Extension; Type: REG_SZ; Data: pdf
- Value Name: FileTypeBucket; Type: REG_DWORD; Data: 0x00000001 (1)
- Value Name: MimeTypes; Type: REG_SZ; Data: application/pdf


5. Restart the Windows SharePoint Services Search service. Open a command prompt. Type net stop spsearch, then net start spsearch. Perform a search, and existing PDFs will not be returned. But newly added PDFs will (once indexed by SharePoint) appear in search results. If you modify any property of an existing PDF, it will be indexed. But who wants to modify all existing PDFs in a document library? This is where I found a lot of misinformation online. Even Microsoft's KB 927675 didn't suggest the right solution! It's easy! STSADM, SharePoint's ubercommand, to the rescue!


6. Rebuild the WSS search index.- Open a command prompt.- Navigate to Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN and type the following commands
stsadm.exe -o spsearch -action fullcrawlstop
stsadm.exe -o spsearch -action fullcrawlstart
The existing PDFs will, after being indexed, appear in search results. But they will still not have correct icons. So, while your site is being indexed, keep going with these steps to configure the icon.


7. Open the folder Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images.


8. Copy the gif you downloaded in Step 1 into the folder.


9. Open the folder Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml.


10. Right-click the file docicon.xml and choose Open With and select Notepad.


11. In the element, you'll see a number of elements. You will add one for pdf. It does not have to be in alphabetical order. The element you need to add is:


12. Save that file and close Notepad.Now, the moment of truth. A search now provides the results.

Microsoft is finally using Microsoft Team Foundation Server internally

Microsoft is finally using Microsoft Team Foundation Server 2008 Beta 2 internally. Click here to get some great statistics

Rich Internet application job trends and salaries

This is a good reference for all you interactive developers to know what you are worth in the marketplace

How to generate RSA public and private keys as well as export to XML

The following method shows how RSA keys can be saved to disk as an XML file. The XML files can then be used to make an RSA secure channel -- the public key is used for encryption and the private one for decryption.

///

/// Generates 2 XML files (public and private key)
///

/// RSA private key file path
/// RSA private key file path
/// secure size must be above 512
public static void GenerateRsa(string privateKeyPath, string publicKeyPath, int size)
{
//stream to save the keys
FileStream fs = null;
StreamWriter sw = null;
//create RSA provider
RSACryptoServiceProvider rsa = new RSACryptoServiceProvider(size);
try
{
//save private key
fs = new FileStream(privateKeyPath, FileMode.Create, FileAccess.Write);
sw = new StreamWriter(fs);
sw.Write(rsa.ToXmlString(true));
sw.Flush();
}
finally
{
if (sw != null) sw.Close();
if (fs != null) fs.Close();
}
try
{
//save public key
fs = new FileStream(publicKeyPath, FileMode.Create, FileAccess.Write);
sw = new StreamWriter(fs);
sw.Write(rsa.ToXmlString(false));
sw.Flush();
}
finally
{
if (sw != null) sw.Close();
if (fs != null) fs.Close();
}
rsa.Clear();
}