BLOG on SharePoint in English: CLUB UGSF - SHAREPOINT FRENCH
Today is an exciting day for myself and my friends Darrin Bishop, Dan Holme, Gary Lapointe, David Mann, Matthew McDermott and Maurice Prather! Today we launched our new company, Aptillon. Please head on over to our website to learn all about it.
http://www.toddbaginski.com/blog/archive/2010/08/24/66.aspx
A Governance Plan describes how your SharePoint environment will be managed. It describes the roles, responsibilities, and rules that are applied to both the back end (hardware, farm, application, database configuration and maintenance) and the front end (information architecture, taxonomy, user experience). This white paper focuses on the “front end” of the SharePoint environment – the business aspect of governance - the areas that impact business users.
Contents
SharePoint Server 2010 Governance Considerations 5
Keys to an Effective Governance Plan. 8
Content Policies and Standards 17
Design Policies and Standards 20
Delivering the Governance Plan: Training and Communications 23
Download details: SharePoint 2010 Governance Planning
Read also
http://cluboffice2010.blogspot.com/2010/08/sharepoint-upgrade-part1-overview-2007.html
And now here is a Screenshot guide for upgrading via Inplace upgrade?
For this test i use MOSS2007 SP2 and SP2010 public beta. (NOTE: upgrade from SP2010 Beta to SP2010 RTM is not supported!!!)
SharePoint Upgrade (Part1) – Overview 2007 to 2010 - Patrick Heyde - Site Home - TechNet Blogs
Pierre Erol GIRAUDY
Anyone that I've talked to about SharePoint 2010 knows I like MySites. I think everyone should have a MySite. My cat has two. Unfortunately not everyone agrees with me. About once a week I get asked, "How do I disable MySites? I'm a big meanie." I figured it was time to put this into a blog post, so I don't have to fight back tears every time I have to explain how to do this. I'm tearing up now as I type this.
How to prevent users from creating MySites in SharePoint 2010 - Todd Klindt's SharePoint Admin Blog
System Center Virtual Machine Manager (VMM) 2008 R2 is a server application that you can use to manage virtual machines on a variety of virtualization platforms. As an alternative to using the VMM Administrator Console to administer your Virtual Machine Manager environment, you can use the cmdlets in the Windows PowerShell - Virtual Machine Manager command shell, which is an administrator-focused command-line shell. This document provides the Help topics for the VMM 2008 R2 cmdlets.
Microsoft SharePoint Server 2010 (Coll. Études informatiques et logiciels)
GIRAUDY Pierre-Erol, ROBERT-GIRAUDY Martine, GEORGEAULT Nicolas, HAMET Benoit, LEGENDRE Etienne
Date de parution : 08-2010 · Langue : FRANÇAIS · 340p. 15.6x23.4 Broché
80.00 € 
Depuis 10 ans, Microsoft ne cesse d'améliorer sa plateforme collaborative SharePoint® Server. Cet ouvrage permet de découvrir et de mieux appréhender les nouvelles technologies SharePoint® 2010 : SharePoint® Server 2010, SharePoint® Foundation 2010 et Microsoft® Office® 2010. Cet outil de partage de l'information sans équivalent est couplé à des applications de gestion électronique de documents, d'informatique décisionnelle (BI), de moteurs de recherche (FAST), de réseaux sociaux ainsi qu'à My Site. Microsoft® SharePoint® Server 2010 s'adresse aux responsables informatique, DRH, DSI, chefs de produit ou tout décideur souhaitant utiliser une solution de portail pour faciliter le travail collaboratif dans l'entreprise.
Ce guide décrit, de manière didactique, comment piloter Microsoft® SharePoint® Server 2010 en analysant les points suivants : l'architecture et les fonctions avancées, la migration, l'installation, la configuration, la gouvernance et la gestion applicative, l'intégration de réseaux sociaux, My Site, la conservation, SharePoint Designer, STSADM et PowerShell.
Fab 40 templates were free templates released by Microsoft for sharepoint 2007 and wss 3.0 to address some of the common scenarios encountered by SharePoint administrators, developers and event business/Marketing managers to demonstrate and show case some of the capabilities of MOSS to end users.
Discussion about that how good these templates are and in which scenario these are more helpful versus things which needs to be improved in these templates is a separate topic but I have noticed many SharePoint people using these templates either for small clients , for demonstration purpose and even for training purposes etc. ..
I have uploaded some of these Fab 40 templates for SP 2010, so now you can have Fab 40 for SP 2010, at least some of these are available for now…rest coming soon J .
TechSol | Tech Solutions Blog - Fab 40 Templates for MOSS 2010
Developing Applications for SharePoint 2010 contains guidance documentation, detailed examples, and a reusable class library. These resources are designed to help solution developers and architects make the right decisions and follow proven practices when designing and developing applications for Microsoft® SharePoint® 2010. The guidance focuses on the building blocks that every developer needs to understand to become an effective SharePoint developer or architect. The guide is provided as a Help (.chm) file and has four core areas: application foundations, execution models, data models, and client models. Eight reference implementations illustrate the core concepts covered in the guide. The reusable class library provides code to help developers build more manageable, flexible, and testable applications. Source code is provided for all reference implementations and for the reusable library. The reference implementations have automated setup scripts to configure the applications.
Download details: Developing Applications for SharePoint 2010
This document provides you with information that will help you understand the concepts of identity in SharePoint 2010 products, how Kerberos authentication plays a critical role in authentication and delegation scenarios, and the situations where Kerberos authentication should be leveraged or may be required in solution designs. The document also shows you how to configure Kerberos authentication end-to-end within your environment, including scenarios which use various service applications in SharePoint Server. Additional tools and resources are described to help you test and validate Kerberos configuration. The "Step-by-Step Configuration" sections of this document cover several SharePoint Server 2010 scenarios.
Download details: Configuring Kerberos Authentication for SharePoint 2010 Products
Microsoft products have a lifecycle that determines how long they remain in a supported state. Review the Microsoft Support Lifecycle site for details on the product support lifecycle and where each product is in its own lifecycle.
The following Windows SharePoint Services/Office SharePoint Server products are currently supported by the SPRAP program:
Operating System
Windows Server 2003
Windows Server 2008
Operating System
SharePoint Server 2010
SharePoint Foundation 2010
Office SharePoint Server 2007
Windows SharePoint Services 3.0
Operating System
SQL Server 2005
SQL Server 2008
MOSSRAP Service Delivery Pre-requisites
SharePoint PowerShell Community Toolkit
The SharePoint PowerShell Community Toolkit is a community based project to add additional command line functionality to SharePoint using PowerShell cmdlets.
SharePoint ToolBox 12 - Michael Greth [SharePoint MVP] - SharePointCommunity
SharePoint Learning Kit is a SCORM 2004 certified e-learning delivery and tracking application built as a Windows SharePoint Services 3.0 solution. It works with either Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007, and has the following core features:
- Supports SCORM 1.2, SCORM 2004, and Class Server content, allowing users to store and manage this content in SharePoint document libraries.
- Supports learner-centric and instructor-led (assigned) workflows.
- Allows assignment, tracking and grading of both e-learning and non-e-learning content.
Announcements / Requests
- SLK version 1.5 Beta now available at 1.5 Beta. Main feature is support for SharePoint 2010.
This book includes information to help IT professionals use Microsoft Office Web Apps on Microsoft SharePoint 2010 Products in an organization.
Microsoft SQL Server Migration Assistant (SSMA) for Access is a tool for migrating databases from Microsoft Access to SQL Server 2005, SQL Server 2008 and SQL Server 2008 R2. SSMA 2008 for Access also supports migrating to SQL Azure.
SSMA for Access converts Access database objects to SQL Server database objects, loads those objects into SQL Server, and then migrates data from Access to SQL Server. You can also link Access tables to SQL Server tables so that you can continue to use your existing Access front-end applications with SQL Server or SQL Azure.
SSMA for Access supports migration from Access 97 and higher to any edition of SQL Server.
-- Pierre Erol GIRAUDY
Président du Club MOSS 2007 et MUG.Vice-Président Club UGO2007
http://clubmoss2007.org/
http://www.viadeo.com/fr/profile/pierreerol.giraudy
Microsoft SharePoint Server 2010 (Coll. Études informatiques et logiciels)
Auteur(s) : GIRAUDY Martine, GIRAUDY Pierre-Erol, HAMET Benoit Nicolas GEORGEAULT Etienne LEGENDRE.
Date de parution: 09-2010
Langue : FRANÇAIS
15.6x23.4 Broché
Etat : à paraître, réservez-le dès maintenant.
Résumé
Ce guide décrit, de manière didactique, comment piloter Microsoft® SharePoint® Server 2010 en analysant les points suivants : l'architecture et les fonctions avancées, la migration, l'installation, la configuration, la gouvernance et la gestion applicative, l'intégration de réseaux sociaux, My Site, la conservation, SharePoint Designer, STSADM et PowerShell.
Sommaire
Plan de lecture. Introduction.
Chapitre 1. Construire l'architecture SharePoint® 2010. Chapitre 2. La gouvernance. Chapitre 3. Configuration : les installations et migrations. Chapitre 4. Création : de nombreux outils au service des acteurs. Chapitre 5. Cadrer SharePoint® dans son propre environnement et/ou dans son environnement spécifique. Chapitre 6. Applications fonctionnelles : Office Web Applications et réseaux sociaux. Chapitre 7. Conserver : les restaurations et les sauvegardes de SharePoint® 2010.
Conclusion.
Bibliographie.
Liens.
Glossaire.
Index.
Latest Office & SharePoint Videos
This track enables IT professionals to learn about Office server and client applications via sessions covering security, deployment, management, customization, and administration. It also enables developers to learn how to leverage their ASP.NET expertise within the SharePoint ecosystem, craft the next generation of “Office Business Applications”, creating applications involving Microsoft Office, composition, collaboration, software-plus-services, VOIP, Open XML, Silverlight™, and more!
Project Description
A set of tools for managing upgradable Features in SharePoint 2010. (Upgrading Features is a means of deploying code/artifact updates to existing SharePoint sites).You have developed Features for SharePoint 2007, you’re probably aware of a very serious limitation of Feature Development: upgradability. Deploying version 1 of your customization is no problem, but If you want to deploy a bug fix or additional functionality in version 2, you’re basically on your own. In SharePoint 2010, this problem is solved, you can now build features that are upgradable. You can built your feature as usual, and optionally you’ve got the opportunity to specify what should happen when the feature gets upgraded from a previous version.
Background of the TOOL CODEPLEX
SharePoint 2010 introduces the concept of 'versioned' or 'upgradable' Features, as a means of applying updates to existing sites. A new version of a Feature is created by modifying the definition (with new XML or code) and incrementing the version number. For the change to be applied, existing Feature instances (e.g. in each web for a web-scoped Feature) must be upgraded. SharePoint 2010 does not ship with any admin screen, STSADM command or PowerShell cmdlet to manage this process. The only way to upgrade Features is to write code - however, this kit provides tools so that no code is required on your behalf; I've done it for you.
(Read a 4 part series on Feature upgrade on my blog - http://www.sharepointnutsandbolts.com/2010/06/feature-upgrade-part-1-fundamentals.html)What's in the kit
The kit is comprised of 3 things:
- An application page in Central Admin - administrators can use this to upgrade Features of any scope across the entire farm
- An OPTIONAL page in each site collection's Site Settings - this can be used to devolve responsibility for upgrading Features (and therefore updating functionality provided by developers) to local site administrators. A Feature must be enabled on each site to enable this.
- COMING SOON - a PowerShell cmdlet which allows Feature upgrade to be run from script. (This is the final piece and will be ready shortly, since the core logic is implemented already.)
Usage
Central Admin page…
http://weblogs.asp.net/jan/archive/2010/08/08/upgrading-features-in-sharepoint-2010.aspx
http://www.sharepointnutsandbolts.com/
http://spfeatureupgrade.codeplex.com/
http://www.sharepointnutsandbolts.com/2010/06/feature-upgrade-part-1-fundamentals.html and 4 articles on this subjects on this blog
SharePoint 2010 introduces additional lifecycle management capabilities with the ability to version and upgrade Features. There are some declarative elements such as ApplyElementManifests and AddContentTypeField, but using the CustomUpgradeAction element allows you to shell out to code where necessary.
The only way to actually perform upgrade on a Feature once it has been updated is to call SPFeature.Upgrade() on each instance of the Feature (e.g. in each web) which should be upgraded – new QueryFeatures() methods help you locate Feature instances which can be upgraded. I’ve written a custom application page which helps manage this process, to be discussed next time.
SharePoint 2010 Feature Upgrade Kit
You can use this tool to configure an existing installation of Microsoft Office SharePoint Server 2007 or Microsoft SharePoint Server 2010 for use with Microsoft Visual Studio Team Foundation Server 2010. The tool automates the configuration of the following features with certain default values, which are explained in the configuration instructions that are included with the tool. The tool will skip configuring a feature if it is already enabled and configured.
The configuration tool is designed to configure relatively simple deployments of Office SharePoint Server 2007 or SharePoint Server 2010. The tool uses default settings to configure the features. You should not use this tool if any of the following is true:
Microsoft Team Foundation Server 2010 MOSS Configuration Tool
This book includes information deployment scenarios, step-by-step installation instructions, and post-installation configuration steps for deploying Microsoft SharePoint Server 2010.
Download details: Deployment guide for SharePoint Server 2010
