How Do You Enforce Governance in SharePoint?

Governance is the set of policies, roles, responsibilities, and processes that control how an organization's business divisions and IT teams work together to meet organizational goals.

http://veroniquepalmer.com/2013/11/11/how-do-you-enforce-governance-in-sharepoint/?goback=%2Egde_3854668_member_5812545286442086403#%21

A poster you can download in PDF or Visio format. It shows the major governance areas (IT governance, information management, and application management) and summarizes the key information you need to understand about each area.

            http://zoom.it/vb5G#full

Learn how to govern applications for SharePoint 2013 by creating a customization policy and understanding the app model, branding, and life-cycle management.

             http://technet.microsoft.com/en-us/library/dn531035.aspx

I use this tool for the governance and to make a Dashboard (Automate it):

 
            http://www.spdockit.com/features/sharepoint-best-practices-reports/

            http://mossgouvernance.blogspot.fr/2013/12/des-outils-pour-la-gouvernance.html

            https://spdocumentor.codeplex.com/ 

Or you can use also in fonction of what you want to do:

            http://sharepoint-community.net/page/sharepoint-admin-tools

 

Pierre Erol GIRAUDY

MVP – AZEO – UGSF

www.ugsf.fr

Des outils pour la Gouvernance Techniques de SharePoint 2013

 

1 - Project Description
Easily compare server configuration.

"Grid" layout shows configuration of the full farm in one table. Export to Excel for filter, sort, and pivot chart.

http://spdash.codeplex.com/

Benefits

• Do admin tasks faster
• Scale up beyond RDP
• Add new servers without fear
• Verify consistent configuration

 

2 - Project Description
This solution is designed for SharePoint

(not tester on SharePoint 2013 yet).
It helps administrators extract informations from the ULS logs.

http://ulslogextractor.codeplex.com/

 

3 - Project Description
SPSFarmReport.exe 2013SPSFarmReport.ps1
This one is a powershell'd version that works on 2013 farm environments.

You will need to run "Set-ExecutionPolicy -ExecutionPolicy Unrestricted" to allow the execution of this PowerShell script.

The ouput is written in the form of an XML file.

Run the "{[}Environment{]}::CurrentDirectory" command to know where the output XML is written to.

http://spsfarmreport.codeplex.com/

 

4 - Project Description

First Release of Export Version History SP2013

Export version history can be used to export the version history of SharePoint 2013 List items to Microsoft Excel.

It provides button in Ribbon to do bulk export and also in the ECB menu to export single items.

http://exportversionhistorysp2013.codeplex.com/releases/view/114917

 

5 - Project Description
ULS Deobfuscator is a viewer for SharePoint ULS log files.
When having to analyze SharePoint log files, I think that there are 2 difficulties:

• Finding the right log file.
• Reading the log file contents.

http://ulsdeobfuscator.codeplex.com/

 

Pierre Erol GIRAUDY

MVP – AZEO – UGSF

www.ugsf.fr

MEG-MEDIATION PRO: LE LOGO de MEG-MEDIATION PRO

MEG-MEDIATION PRO: LE LOGO de MEG-MEDIATION PRO:
Créé par une professionnelle : Geneviève KRIEFF Graphiste Créatif
Le site : http://meg-mediationpro.blogspot.fr/

EROL

SharePoint Migration Tools - by SharePoint-Community.Net

 

SharePoint Migration Tools - by SharePoint-Community.Net

Collé à partir de <http://sharepoint-community.net/page/sp-migration-tools>

Introducing DocAve Governance Automation Service Pack 4 for Microsoft Sh...

---
Pierre Erol GIRAUDY
MVP SHAREPOINT
Président du Club UGSF
http://www.ugsf.fr
http://about.me/giraudyerol

Application management and governance in SharePoint 2013

Planifier dans SharePoint 2013

Articles TechNet sur la planification de SharePoint 2013

Les articles qui suivent abordent la planification de SharePoint 2013 et peuvent être consultés en ligne. Les rédacteurs mettent régulièrement à jour les articles dès que de nouvelles informations sont disponibles et en réponse aux commentaires des utilisateurs.

Planification des solutions
Planification de l’architecture de batterie de serveurs

Vidéos sur la planification de SharePoint 2013

Les enregistrements vidéo suivants sur la planification de SharePoint 2013 sont disponibles en ligne ou au téléchargement.

Ressources supplémentaires concernant la planification de SharePoint 2013

Les ressources suivantes consacrées à la planification de SharePoint 2013 sont disponibles auprès d’autres experts aux spécialités diverses.

http://technet.microsoft.com/fr-fr/library/cc261834.aspx

 

Learn how to govern applications for SharePoint 2013 by creating a customization policy and understanding the app model, branding, and life-cycle management.

http://technet.microsoft.com/en-us/library/dn531035.aspx

How will you manage the applications that are developed for your environment? What customizations do you allow in your applications, and what are your processes for managing those applications?

For effective and manageable applications, your organization should consider the following:

• Customization policy   SharePoint 2013 includes customizable features and capabilities that span multiple product areas, such as business intelligence, forms, workflow, and content management. Customization can introduce risks to the stability, maintenance, and security of the environment. To support customization while controlling its scope, you should develop a customization policy.

• Life-cycle management   Follow best practices to manage applications and keep your environments in sync.

• Branding   If you are designing an information architecture and a set of sites to use across an organization, consider including branding in your governance plan. A formal set of branding policies helps ensure that sites consistently use enterprise imagery, fonts, themes, and other design elements.

• Solutions or apps for SharePoint?   Decide whether a solution or an app for SharePoint would be the best choice for specific customizations.

Get developer guidance about customizing and branding SharePoint 2013 on MSDN: Build sites for SharePoint 2013.

Customization policy

Determine the types of customizations you want to allow and how to manage them. Your customization policy should include:

• Service-level descriptions   What are the parameters for supporting and managing customizations in your environments? See Service-level agreements.

• Guidelines for updating customizations   How do you manage changes to customizations, and how do you roll out those changes to your environments? Consider ways to manage source code, such as a source control system and standards for documenting the code.

• Processes for analyzing   How do you understand whether a particular customization is working well in your environment, or how do you decide which ones to create, change, or retire?

• Approved tools for customization   Consider development standards, such as coding best practices and the tools that you will to use across your organization. For example, you should decide whether to allow the use of SharePoint Designer 2013 and Design Manager, and specify which site elements can be customized and by whom.

• Process for piloting and testing customizations   How do you test and deploy customizations? How many people should be in a pilot testing group? What are your standards for testing and validating customizations?

• Who is responsible for ongoing support   Who will be responsible for supporting customizations in your environments—individual teams or a central group?

• Guidelines for packaging and deploying customizations   Do you have individual packages for each, or do you include several in a feature or solution? Which customizations should be apps for SharePoint instead of solutions? How do you ensure that customizations in one environment do not affect the rest of your SharePoint implementation?

• Specific policies regarding each potential type of customization   What types of customizations do you allow?

  For more information about kinds of customizations and their potential risks, see the Customizations table later in this article. For more information about processes for managing customizations, see the white paper SharePoint Products and Technologies customization policy. Most of this content still applies to SharePoint 2013.

• Policies around using the App Catalog and SharePoint Store Which apps for SharePoint do you want to make available to your organization? Can users purchase apps directly? See Solutions or apps for SharePoint? later in this article for more information.

Test Lab Guides

Table of Contents

• Base Configuration TLG
• Modular TLGs
• Test Lab Extensions
• Troubleshooting TLGs
• Test Lab Troubleshooting Scenarios
• TLG Mini-Modules
• TLG Stacks
• TLG Portal Pages
• Additional Resources
  • Hyper-V Articles in the TechNet Wiki for TLGs
  • TLGs Under Development

http://social.technet.microsoft.com/wiki/contents/articles/1262.test-lab-guides.aspx#Troubleshooting_TLGs

Test Lab Guides (TLGs) allow you to get valuable hands-on experience with new products and technologies using a pre-defined and tested methodology that results in a working configuration. When you use a TLG to create a test lab, instructions define what servers to create, how to configure the operating systems and system services, and how to install and configure any additional products or technologies. A TLG experience enables you to see all of the components and the configuration steps on both the front-end and back-end that are required for a product or technology or for a multi-product or technology solution.

A challenge in creating useful TLGs is to enable their reusability and extensibility. Because creating a test lab can represent a significant investment of time and resources, your ability to reuse and extend the work required to create test labs is important. An ideal test lab environment would enable you to create a basic lab configuration, save that configuration, and then build out multiple test lab scenarios in the future by starting with the base configuration.

For a test lab based on physical computers, you can image the drives for future test labs. For a test lab based on virtual machines, you can create snapshots for future test labs. This allows you to easily return to a desired configuration for further learning and experimentation.

Base Configuration TLG

The Base Configuration TLG (overview video ) allows you to create the base configuration test lab, upon which you can build test labs based on other TLGs from Microsoft, test lab extensions in the TechNet Wiki, or a test lab of your own design that can include Microsoft or non-Microsoft products. This base configuration test lab uses computers running Windows Server 2008 R2 and Windows 7 and consists of two subnets: the Corpnet subnet that hosts the Contoso Corporation intranet and the Internet subnet that simultates the Internet.
The following figure show the base configuration test lab with the Corpnet (required and consisting of the DC1, APP1, and CLIENT1 computers) and Internet (optional and consisting of the EDGE1 and INET1 computers) subnets. When both the Corpnet and Internet subnets are configured, the CLIENT1 computer can be moved between the subnets to show intranet and Internet behaviors and functionality.

The base configuration TLG is just the beginning of the test lab experience. Other TLGs, test lab extensions, or TLG mini-modules focus on Microsoft products or platform technologies, but all of them use the Base Configuration TLG as a starting point.

After configuring the computers of the base configuration test lab, make sure that you perform a disk image on each computer if you are using physical computers, or perform virtual machine snapshots if you are using virtual machines.
For a base configuration test lab that consists of just the Corpnet subnet and is connected to your production network, allowing scalability and ongoing access to the Internet for public cloud technologies, see Configuring the Corpnet Subnet of the Base Configuration Test Lab for Public Cloud Technologies.
For a base configuration test lab that uses computers running Windows Server 2012 and Windows 8, see Test Lab Guide: Windows Server 2012 Base Configuration (overview video ). For a list of other TLGs that use this base configuration, see Windows Server 2012 Test Lab Guides.
For a base configuration test lab that uses computers running Windows Server 2012 R2 Preview and Windows 8.1 Preview, see Test Lab Guide: Base Configuration TLG for Windows Server 2012 R2 Preview .

Governance Services for SharePoint®

La collaboration est essential dans nos environnements de travail modernes. Des outils de collaboration tels que Microsoft® Sharepoint® améliorent l’efficacité des individus et des équipes, et accélère les processus métier et la prise de décision dans toute l’entreprise. Cependant, l’un des effets critiques qui en découle est la création de vastes quantités de contenu, records et autres informations, rapidement incontrôlables et non-conformes aux réglementations en vigueur. Les entreprises d’aujourd’hui faisant face à cela, sont donc amenées à un besoin urgent d’une solution/plateforme de gouvernance de l’information pour rester conformes avec les lois et réglementations en vigueur.

La solution RSD GLASS Governance Services for SharePoint 2010 permet aux entreprises utilisant SharePoint de régir et gouverner toutes les informations créées dans Microsoft SharePoint à partir d’une plateforme centrale, sans avoir à migrer le contenu SharePoint vers d’autres systèmes ECM plus onéreux. Ce qui est dans SharePoint reste dans SharePoint.

RSD GLASS® offre aux entreprises un mécanisme d’application des politiques et impose les niveaux d’accessibilité, de protection et de rétention des données à toute l’information d’entreprise.

La solution aide à gérer de manière proactive le cycle de vie de leur information en toute facilité (sur tous les sites SharePoint et toutes les entités pays). RSD GLASS est une solution simple et non intrusive, qui facilite le contrôle de gouvernance sans empêcher ou freiner la croissance et les bénéfices des environnements SharePoint.

La solution Governance Services for SharePoint aide les entreprises à mieux gérer les vastes quantités d’information et de records contenues dans les sites SharePoint:

• Gouvernance “in-place”: éviter les migrations risquées et coûteuses.
• Gestion unifiée des politiques s’appliquant à tous types de référentiels de données, y compris SharePoint.
• Gestion du cycle de vie des records sur tous les sites SharePoint
• Intégration intuitive et configurable.
• La productivité des employés n’est pas impactée.

http://www.rsd.com/fr/produits/governance-services-sharepoint