Suivre ce blog
Administration Créer mon blog

Recherche

5 mai 2015 2 05 /05 /mai /2015 21:53

Tout d'abord, vérifiez quelle édition de SQL Server que vous exécutez est en exécutant "SELECT@@VERSION" dans une fenêtre de requête SSMS.

Démarrez le SQL Server 2012 Enterprise (DVD / ISO). Lorsque l'application SQL Server Centre d'installation apparaît, cliquez sur le lien "Maintenance" sur le panneau en haut à gauche de l'application.

Puis, à la partie supérieure du panneau droit de l'application SQL Server Centre d'installation, cliquez sur le lien "Édition Upgrade".

Une nouvelle boîte de l'application apparaît. Cette application va faire un scan pour "Règles de support d'installation". Si cette analyse réussit, puis cliquez sur le bouton OK dans le coin en bas à droite de l'application.

L'application va disparaître, la il peut apparaître un couple de pop des boîtes qui vont disparaître chacun sur son propre.

La «Mise à niveau de l'édition de SQL Server 2012" application apparaîtra. Ceci effectuera un balayage pour "Règles de support d'installation" les. Une analyse différente, alors celui réalisé avant. Cliquez sur le bouton Suivant lorsque l'analyse est terminée.

L'écran suivant est l'écran clé de produit. Entrez votre clé de produit, si elle ne remplit pas l'auto "Entrez la clé de produit:" zone de texte. Puis cliquez sur le bouton SUIVANT.

L'écran suivant est l'écran Licence à terme. Cliquez sur le "Je accepte les termes de la licence" case à cocher. Ensuite, cliquez sur le bouton SUIVANT.

Le prochain est l'écran Sélectionner instance. Déposez la zone de liste déroulante le bas pour sélectionner l'instance que vous souhaitez mettre à jour. Une liste des instances reconnues sera liste de la boîte cas de grille installée. Ensuite, cliquez sur le bouton SUIVANT. Une boîte s'il vous plaît attendez peut apparaître pendant quelques secondes.

L'écran Édition de mise à niveau des règles apparaît à côté. Une analyse sera exécuté pour valider le processus de mise à niveau de l'édition. Une fois l'analyse terminée, cliquez sur le bouton Suivant.

Le Prêt à évoluer écran édition apparaît à côté. Dans la zone de texte apparaît une liste d'objet qui vont être mis à niveau. Après avoir examiné cette liste, cliquez sur le bouton de mise à niveau.

Une fois le bouton de mise à niveau a été cliqué, il sera grisé. Ensuite, rien ne se passera peut-être pour une minute. Puis l'écran complet si la mise à jour a réussir. Cliquez sur le bouton CLOSE.

Fermez le «Centre d'installation SQL Server" de l'application, par cliquez sur la boîte de X dans le coin en haut à droite.

Vérifiez que SQL Server a mis à jour en exécutant le "SELECT@@VERSION" dans une fenêtre de requête SSMS.

Note finale: Au meilleur de ma connaissance, aucun redémarrage est nécessaire après la mise à niveau est terminée. Je l'ai couru un test sur chaque SQL 2008R2 & SQL 2012. Les deux ne nécessitera un redémarrage. Ce fut sur un système d'exploitation serveur 2008R2. S'il vous plaît tester avant de tenter cela dans un environnement de production.

Source : http://www.thesqlreport.com/?p=349

Partager cet article

Published by SOUSSI Imed
commenter cet article
27 avril 2015 1 27 /04 /avril /2015 11:49

For a SharePoint installation, this page recommends the following best practices and naming conventions for service accounts. In your deployment you many not need all these accounts. For example, if PerformancePoint will not be deployed then you will not need the PerformancePoint service account.

Overview

The account name is arbitrary. But, ensure the length of the account is within the character limits (see below: SharePoint and Managed Service Accounts and SharePoint Service Account Character Length) and the name is short while at the same time descriptive enough.

Service Accounts
SQL Server
SQL Admin
SQL Service
SharePoint Server
SP Admin
SP Farm
SP Web Application
SP Services
SP C2WTS
SP Cache Super User
SP Cache Super Reader
SP Excel User
SP Visio User
SP PerformancePoint User
SP My Site Application Pool Account
SP Profile Synchronization
SP Search Service
SP Search Crawl
Project Server
Accounts
Groups
SharePoint and Managed Service Accounts
SharePoint Service Account Character Length

  • SQL Server Accounts
    • SQL Admin
    • SQL Service
  • SharePoint Server Accounts
    • SP Admin
    • SP Farm
    • SP Web Application
    • SP Services
    • SP C2WTS
    • SP Cache Super User
    • SP Cache Super Reader
    • SP Excel User
    • SP Visio User
    • SP PerformancePoint User
    • SP Profile
    • SP Profile Sync
    • SP Search Crawl
  • Project Server Accounts and Groups
    • PS Project
    • PS Workflow Proxy
    • PS Project Report
    • PS Project Report Authors
    • PS Project Report Viewers
    • PS Project External Report Viewers

Service Accounts

SQL Server
  • Setup User Administrator Account
  • Used for:
    • SQL Server Administrator (this account has unrestricted access to the DB engine)
    • SQL installation/update/upgrade
  • Domain account
  • Local Admin on SQL Server machine
  • Used for:
    • Running SQL Server engine and SQL Server Agent.
  • Domain account
  • Preferably Managed Service Account
  • Optionally, for more secure environments you will want to create multiple account (all domain accounts and MSA) for each of SQL Server services.
    • SQL Service - for SQL DB Engine
    • SQL Agent Service - for SQL Agent
    • SQL AS Service - for SQL Server Analysis Services
    • SQL RS Service - for SQL Server Reporting Services
    • SQL IS Service - for SQL Server Integration Services
    • SQL DR Controller Service - for Distributed Replay Controller
    • SQL DR Client Service - for Distributed Replay Client
SharePoint Server
  • Setup User Administrator Account
  • Used for:
    • SharePoint installation
    • Running the SharePoint Product Configuration Wizard
    • Other Farm configurations
  • Domain account
  • Local Admin on APP and WFE servers
  • SharePoint Database Access Account (AKA SharePoint Farm Service Account)
  • Used for:
    • Central Administration app pool identity
    • Microsoft SPF Workflow Timer Service account
  • Domain account
  • During User Profile Synchronization application provisioning needs to be local admin and have Log On Locally rights on the Server that will be hosting the UPS application
    • After UPS application provisioning remove the local admin privilege but keep the Log On Locally rights
    • After giving this account local admin and Log On Locally rights permissions, it is important that you logout and log back into the server (or restart the server)
  • Web Application Pool Account
  • Used for:
    • Application pool identity for the main web application IIS website
  • Domain account
  • SharePoint Web Services Application Pool Account
  • Used for:
    • Application pool identity for the SharePoint Web Services IIS website
  • Domain account
  • Claims to Windows Token Service Account
  • Used as the identity for the Claims to Windows Token Service account
  • Create this dedicate account if you plan to use Excel, Visio, PerformancePoint, or Office Web Apps Excel services.
  • Domain account
  • Local Admin on SharePoint Servers that will be running any of the following services:
    • Excel Services
    • Visio Service
    • PerformancePoint Service
    • Office Web Apps Excel Service
  • Portal Super User
  • Used for:
    • Super user cache account
  • Domain account
  • This account requires Full Control access to the web application.
  • Portal Super Reader
  • Used for:
    • Super reader cache account
  • Domain account
  • This account requires Full Read access to the web application.
  • Excel Service Unattended Service Account
  • Used for:
    • Connecting to external data sources that require a username and password that are based on OS other than Windows for authentication
  • Domain account
  • Visio Graphics Service Unattended Service Account
  • Used for:
    • Connecting to external data sources that require a username and password that are based on OS other than Windows for authentication
  • Domain account
  • PerformancePoint Service Unattended Service Account
  • Used for:
    • Connecting to external data sources that require a username and password that are based on OS other than Windows for authentication
  • Domain account
  • My Sites Application Pool Account
  • Used for:
    • My Site application pool
  • Domain account
  • If you are hosting My Site site collection under the same web application as other site collections, then you don't need this account. Create this account only if you are creating a dedicated web application of My Site site collection, in which case you set the web application app pool account to this account.
  • Synchronization Account
  • Used for:
    • Connecting to a directory service
    • User Profile Services to access AD
    • User Profile Services to run profile synchronization
  • Domain account
  • This accounts requires Replicate Directory Changes in AD DS on the domain node
    • The Grant Replicate Directory Changes permission does not enable an account to create, change or delete AD DS object. It enables the account to read AD DS objects and to discover AD DS object that were changed in the domain.
  • Search Service Account
  • Used for:
    • Windows user credentials for the SharePoint Search service
  • Domain account
  • Default Content Access Account
  • Used for:
    • For Search service application to crawl content.
  • Domain account
  • This account must have read access to external or secure content sources that SharePoint will be crawling.
  • For SharePoint sites that are not part of the server farm, this account must explicitly be granted full read permissions to the web applications that host the sites
Project Server

If planning to deploy Project Server the following accounts and groups are required for least-privilege scenario

  • PS Project
    • Project Server Service Application Application Pool Account
    • Database owner for content databases with the Web application
    • Read/write access to the associated Project Server Service Application database
    • Read permission on SharePoint_Config database
  • PS Project Report
    • Secure Store Target Application Account
    • This account provides the credentials needed for report viewers to view reports generated from data in the PWA database.
    • This account is used as part of the Secure Store Configuration
    • Add this account to the Report Authors Active Directory group
    • Permission:
      • Database datareader on PWA database
  • PS Workflow Proxy
    • Project Server Workflow Activities Account
    • This account is used to make Project Server Interface (PSI) calls associated with each workflow.
    • Configured as a Project Server user account, with the following permissions:
      • Global permissions:
        • Log On
        • Manage Users and Groups
        • Manage Workflow and Project Detail Pages
      • Category permissions:
        • Open Project
        • Save Project to Project Server
    • If using SharePoint Permission mode, add this account to the Administrators for PWA security group
  • PS Project Report Authors
    • Report Authors Group
    • AD security group - Global
    • Users in this group can create reports
    • If report authors will also be viewing reports, add this group to the Report Viewer Group
    • Permission: db_datareader on PWA database
  • PS Project Report Viewers
    • Report Viewers Group
    • AD security group - Global
    • Users in this group can view reports
    • This group is used as part of Secure Store configuration
      • That is, add the Secure Store account to this group
  • PS Project External Report Viewers
    • External Report Viewer Group
    • This account is optional
    • Users that do not have a PWA user account but require access to the Project Server BI Center to view reports
    • Add the Secure Store Target Application Account to the Report Authors Active Directory group
    • Permissions:
      • Read permission to the BI Center site

SharePoint and Managed Service Accounts

For SharePoint service accounts, do not create Active Directory Domain Services accounts that are Managed Service account or Virtual Service account. These two type of service accounts were introduced in Windows Server 2008 R2 and Windows 7. They are not supported in SharePoint 2013.

For SQL Server services use Managed Service account, if using SQL Server 2012. Managed Service account is now supported in SQL Server 2012. For example, you can use MSA for the SQL Server Engine and SQL Server Agent. Use MSA for SQL Server accounts that will not be used to login to the server. You can't use MSA to login to a server. The use of MSA for SQL Server services is considered as best practice. MSAs are limited to a total of 15 characters (this does not include the DOMAIN\ part). The following provides a good reference on how to enable MSA (http://blogs.technet.com/b/rhartskeerl/archive/2011/08/22/sql-server-code-name-denali-adds-support-for-managed-service-accounts.aspx )

SharePoint Service Account Character Length

SharePoint service accounts (managed accounts) are limited to a total of 20 characters - including the Domain Name (for example Domain\SP_Name - total characters should be less than 20). This limitation is not imposed on SQL Server service accounts or SharePoint's Setup User Account (ex: SPAdmin). But to be on the safe side, I would still follow the 20 to 25 character limit.

Source : http://social.technet.microsoft.com/wiki/contents/articles/14500.sharepoint-2013-service-accounts.aspx#Project_Server_Accounts

Partager cet article

Published by SOUSSI Imed
commenter cet article
18 mars 2015 3 18 /03 /mars /2015 16:34

Whenever you save a list as a template & use it somewhere else, the designer workflow you have associated with the old list will not be restored. There is no option OOB to copy/move a workflow. But luckily this can be done through the SharePoint Designer. Here below two files play a major role,

The .xoml.wfconfig.xml file contains information on the list the workflow is bound to using the List’s ID.
The file .xoml.rules contains the ‘conditions’ you program for the workflow and the “.xoml” file contains the ‘actions’.

To re-use a workflow you have created in one list(Say List A) in another list(Say List B):

  1. Create a new workflow on the new list(B).
  2. Create at least one step, one condition and one action in this workflow. This ensures that the two files above discussed are created.
  3. From the original workflow(in List A) open the .xoml file as XML and copy the entire contents to the clipboard.
  4. Open the .xoml file for the new workflow and replace the entire contents with the content you have copied in the step 3.
  5. Do the same for the xoml.rules file too.
  6. Now open the .xoml file for the new workflow & verify the workflow. Ensure the workflow is correct by clicking Check Workflow.

Copying/Moving SharePoint 2010 Designer Workflows

Most often, we required moving or copying a workflow that is created using SharePoint designer between sites or site collections.

There was an option in SharePoint Designer, Export to Visio which exports your workflow as a .vwi file, and can be imported in to another site using the option Import from Visio. But when you try that option, you will get the below message.

This workflow cannot be imported because it was created in SharePoint Designer for a different site, or the original workflow has been moved or deleted. To move a workflow between sites, use Save as Template (.wsp file) instead of a Visio workflow drawing.

So, to achieve the same follow the steps below.

  1. In the first(source) site, create the required workflow and publish it.
  2. Now select Export to Visio option which allows you to save the workflow with a .vwi extension. (Refer this workflow hereafter as source workflow).
  3. Now go to the destination site where you want the workflow to be copied, and create a new workflow with the same name as the previous one & publish it.
  4. Now select Export to Visio option which allows you to save the workflow with a .vwi extension. (Refer this workflow hereafter as Destination workflow).
  5. Now you will be having two .vwi files (one of source workflow’s – SourceWorkflowName.vwi and other of the destination workflow’s – DestinationWorkflowName.vwi). Now add .zip extension to both the files. Now your files names should be SourceWorkflowName.vwi.zip & DestinationWorkflowName.vwi.zip.
  6. Now open both the zip files, copy workflow.xoml.wfconfig.xml from destination workflow to source workflow. (Its destination to source and not source to destination).
  7. From now on, we will not use the file DestinationWorkflowName.vwi.zip. So ignore that file.
  8. Remove the .zip extension from SourceWorkflowName.vwi.zip which gives you the SourceWorkflowName.vwi file.
  9. Now, go to the destination site, open workflows and click Import from Visio and browse to the SourceWorkflowName.vwi file.
  10. That’s it and your workflow is copied. You can publish the workflow and run it.

PS : In case if your list’s GUID’s (for those lists that you have used in workflow – tasks list, history list or any other lists used in workflow steps) have been changed from source & destination site, you may need to update those steps in the workflow.

Hope this helps.

HarePoint Workflow Migration for SharePoint

​​​HarePoint Workflow Migration for SharePoint – this is an ideal tool for simple, quick, and error-free migration of the most complex workflows from one SharePoint environment to another.

https://www.harepoint.com/Products/HarePointWorkflowMigration/Default.aspx

How to move or copy a SharePoint Designer 2010 List Workflow to another list on the same site or another site.

http://blog.karstein-consulting.com/2011/02/10/walkthrough-how-to-move-or-copy-a-sharepoint-designer-2010-list-workflow-to-another-list-on-the-same-site-or-another-site/

How to copy SharePoint list workflow

We often face a situation where we need to copy a big workflow from list or library to another list or library. This situation can be avoided if we have created the workflow as reusable workflow.

So in this article I will explain in simple steps on how to copy a list workflow to another workflow using SharePoint designer. Using this method we can copy workflow across site collections are web applications.

For this we have the following

List Name

Workflow Name

List 1

List Workflow 1

List 2

List Workflow 2 (Copied from the worlflow1)

Step 1)

We have the list 1 with list workflow 1 to be copied to list workflow 2.

Step 2)

Now create a list workflow 2 , in list 2 with one condition plus once activity and save it.

In our example I have used a condition and sending email to current user. This is used to create the Xoml rules for the list workflow 2

Step 3)

Now in the side of navigation click All Files

Step 4)

In all files click the Workflows

Step 5)

Open the List workflow 1 and also repeat the steps 3,4 and open List workflow 2 in another tab

Step 6)

List workflow 1 and list workflow 2 are will be displaying like this when you have done the steps 3,4,5 correctly.

Step 7)

Copy the .xoml and xoml.rules to the targeted workflow.

In our example List workflow 1.xoml and list workflow 1.xoml.rules are copied from list workflow 1 folder to list workflow 2 folder

Step 8)

Rename the files from List workflow 1.xoml to List workflow 2.xoml

And list workflow 1.xoml.rules to list workflow 2.xoml.rules

While renaming a working message will be displayed click Yes.

Step 9)

Now close and reopen the SharePoint designer.

After opening the List workflow 2 we can notice the workflow has been copied from list workflow 1.

Source : http://www.sharepointbasic.com/2012/04/how-to-copy-sharepoint-list-workflow.html

Partager cet article

27 janvier 2015 2 27 /01 /janvier /2015 13:50

ScreenShot082.png

 

 

Facebook

Partager cet article

29 décembre 2014 1 29 /12 /décembre /2014 22:13

happy-new-year-2015-crismas-hd-wallpapers.jpg

Partager cet article

Published by SOUSSI Imed - dans SOUSSI Imed
commenter cet article
27 décembre 2014 6 27 /12 /décembre /2014 12:22

    

Objectives

 During this lab, you will install the Microsoft Dynamics CRM List Component for Microsoft SharePoint Server 2010 and configure the settings in the application. Download all printscreen of this lab link

 

 ScreenShot045-copie-1.png

Task 1: Start the Microsoft SharePoint Foundation Sandboxed Code

Service

 

Detailed Steps

 

 

 

 Click Start, click All Programs, select Microsoft SharePoint 2010 Products, and then click SharePoint 2010 Central Administration.

 

 Click Manage Services on Server.

 

 Locate the service named Microsoft SharePoint Foundation Sandboxed Code Service and click Start located under the Action column.

 

Task 2: Installation Instructions

 

Detailed Steps

 

 Set Browser File Handling to Permissive

 

 To set this, click Start, click All Programs, select Microsoft SharePoint 2010 Products, and then click SharePoint 2010 Central Administration.

 

 Click Application Management and then click Manage Web Applications.

 

 

 From the list of available sites, click Microsoft CRM SharePoint and then select General Settings

 

 

 

 From the General Settings menu, select General Settings.

 

 

 In the Web Application General Settings window, set the Browser File Handling setting to Permissive.

 

 

 

 Click OK.

 

 Activate the Microsoft Dynamics CRM List Component

 

 Navigate to X:\Labfiles\ShareaPoint\Ch.2

 

 Double-click the CRM 2011-ShraePointList-ENU-amd4.exe file

  

 Select the Click here to accept the Microsoft Software License Terms checkbox and click Continue.

 

 

 In the Browse for Folder window, expand the Computer node, expand New Volume (X), click the Ch.2 folder, and click OK

 

 

 On the Setup for SharePoint List window, click OK

                

 

 Open Internet Explorer.

 

 

 

 Go to http://nyc-dc1/sites/crm.

 

 

 

 Click Site Actions and then click Site Settings.

 

 

 

 

 Under Galleries, click Solutions.

                       

 

 

 Click the white bar next to Current Usage (Today)

 

       

 

 On the Solutions tab, in the New group, click Upload Solution.

 

 

 Click Browse, locate the x:\Labfiles\SharePoint\Ch.2\crmlistcomponent.wsp file,                                                                                                                                                                                                                                   click Open, and then click OK

 

 

 

Click Close

 

 

 

 

Place a checkmark next to the crmlistcomponent record in the view.

 

 

 

On the Solutions tab, in the Commands group, click Activate

 

 

 

Click Close

 

 

 

 

Configure the SharePoint components in Microsoft Dynamics CRM

 

                    A) Open Microsoft Dynamics CRM 2011 (http://nyc-dc1:81)

 

              B)  Click Settings, and then click Document Management.

 

 

c) Click Document Management Settings. This opens the Document Management Settings window. Here you can select multiple entries that will link to a particular SharePoint site.

Leave the check boxes already selected

 

 

On the window, enter http://nyc-dc1/sites/crm.

e)  As soon as the wizard has validated the SharePoint URL, select which entity folders will be created in SharePoint in the context of Microsoft Dynamics CRM. Click the Based On Entity check box.

            f)  Select Account in the drop-down list.

            g) Click Next.

 

 

 

h)  In the dialog box that opens, click OK.

 

I) As soon as the Document Library Creation Statuses all equal Succeed, click Finish.

 

k)  As soon as the integration is configured, browse to Sales and then click Accounts.

                                             

 

L )  Change the view to Active Accounts.

                               

 

m)  Find and open the account named Best o’ Things (sample).

 

 

n)  Click Documents on the left navigation pane

 

o) When you receive the following message, a folder will be created in the location: http://nyc-dc1/sites/crm/account/Best o’ things_ (sample) click OK to continue, click OK.

 

 

P ) As soon as the folder is created, click New, and then click Document.

 

 

 

 

In the Add Document(s) window, click Browse and go to X:\Labfiles\SharePoint\Ch.2\ mscrmsharepointeula.txt.

 

  Select that file and then click OK.

 

 

 

 

 

                      s)  Close the Best o’ Things account form, by clicking the “X” in the upper-right corner of the form

 

Click Settings, click Document Management, and then click Document Management Settings

 

 

u) On the Document Management Settings window, click Case in the Select Entities box.

v) Click Next.

w) In the dialog box that opens, click OK.

z) After the Case entity status displays Success, click Finish.

 

x) Click Sales, and then click Accounts.

y) Change the Account view to Active Accounts.

z) Open the Best o’ Things account.

 

                    

AA) on the account form, click Cases on the left navigation pane of the Best o’ Things record.

 

BB)  Open the case named Contact Information Required (Sample).

 

 

CC) on the case form, click Documents

 

DD)  on the message “A folder will be created in the location: http://nyc-dc1/sites/crm/account/Best o’

things_(sample)/incident/Contact information required (sample) click OK to continue, click OK.

 

 

EE) Click New and then select Document.

 

 

FF)   In the Add Documents window, click Browse and then browse to X:\Labfiles\SharePoint\Ch.2\ mscrmsharepointeula.txt.

 

GG)  Select that file and then click OK.

 

Partager cet article

28 novembre 2014 5 28 /11 /novembre /2014 18:42

SharePoint 2013 includes three new services: 

 App Management Service. SharePoint Server 2013 has embraced the app model, which has become so familiar to mobile device users over the last few years. SharePoint Server 2013 provides a platform for in-house or third-party apps to be used across an organization, with the service application managing permissions and access to individual apps. 

•  Machine Translation Service. The growth of SharePoint as a global platform is enhanced with the new Machine Translation Service application. This provides automatic language translation of document and site pages. This does not mean that SharePoint Server 2013 itself provides a translation engine. When the Machine Translation Service application processes a translation request, the request is forwarded to a cloud-based host that performs the actual translation. This is designed to integrate with the existing Variations functionality. 

•  Work Management Service. For business users, this service is designed to provide an integrated view of their work. The tasks that users need to undertake are aggregated on the users’ My Site. These tasks may be from the SharePoint server, or they may be from external systems, such as Microsoft Exchange or Microsoft Project Server. The architecture of the Work Management Service is such that it will be able to aggregated tasks from other environments in the future. Services that have been deprecated or changed in SharePoint 2013 include: 

•  Web Analytics Service. Rather than have this as a self-contained service application, the Web Analytics functionality has been incorporated into the Search service. 

•  Office Web Apps Service. Office Web Apps is now a separate server product. 

A small farm have between two and approximately five servers,can serve between 10,000 to 20,000 users depending on usage and service requirements.

Medium farms : These farms have between approximately five and 10 servers, separated into three tiers. Can manage up to 40 million items.

 

Partager cet article

16 septembre 2014 2 16 /09 /septembre /2014 20:14

À propos de la planification de la prise en charge des navigateurs

SharePoint Server 2010 prend en charge plusieurs navigateurs Web largement utilisés. Cependant, certains navigateurs pourraient altérer ou limiter certaines fonctionnalités de SharePoint Server 2010 ou ne les rendre accessibles qu’après utilisation d’une procédure spécifique pour des tâches administratives non critiques.

Dans le cadre de la planification de votre déploiement de SharePoint Server 2010, vérifiez les navigateurs qui sont utilisés dans votre organisation afin de garantir des performances optimales avec SharePoint Server 2010.

Phase de planification clé de prise en charge des navigateurs

La prise en charge des navigateurs est une partie importante de votre implémentation de SharePoint Server 2010. Avant d’installer SharePoint Server 2010, assurez-vous de savoir quels sont les navigateurs pris en charge par SharePoint Server 2010. Cet article décrit la prise en charge des navigateurs dans les sections suivantes :

  • Prise en charge des navigateurs

  • Détails relatifs aux navigateurs

  • Compatibilité des navigateurs pour les sites de publication

Prise en charge des navigateurs

Le tableau suivant récapitule les niveaux de prise en charge des navigateurs couramment utilisés.

Navigateur Pris en charge Pris en charge avec limitations Non pris en charge

Internet Explorer 9

32 bits

64 bits

Internet Explorer 8

32 bits

64 bits

Internet Explorer 7

32 bits

64 bits

Internet Explorer 6

X

Google Chrome (dernière version diffusée publiquement)

X

Mozilla Firefox (dernière version diffusée publiquement)

X

Apple Safari (dernière version diffusée publiquement)

X

Détails relatifs aux navigateurs

Vous devez examiner les détails relatifs au navigateur Web dont vous disposez ou que vous prévoyez d’utiliser dans votre organisation afin de vous assurer qu’il fonctionne avec SharePoint Server 2010 et conformément à vos besoins professionnels.

Versions d’Internet Explorer

Le groupe produit s’efforce de vérifier que les fonctionnalités SharePoint marchent correctement avec les versions diffusées d’Internet Explorer. Nous conseillons vivement aux clients qui souhaitent bénéficier d’une interaction du navigateur plus contrôlée d’utiliser Internet Explorer.

Internet Explorer 8 et Internet Explorer 9

Internet Explorer 8 et Internet Explorer 9 sont pris en charge sur les systèmes d’exploitation suivants :

  • Windows Server 2008 R2

  • Windows Server 2008

  • Windows Server 2003

  • Windows 7

  • Windows Vista

  • Windows XP

Internet Explorer 7

Internet Explorer 7 est pris en charge sur les systèmes d’exploitation suivants :

  • Windows Server 2008

  • Windows Server 2003

  • Windows Vista

  • Windows XP

Internet Explorer 6

SharePoint Server 2010 ne prend pas en charge Internet Explorer 6.

Si vous utilisez des sites de publication, voir Compatibilité du navigateur pour les sites de publication plus loin dans cet article.

Autres navigateurs

Google Chrome (dernière version diffusée publiquement)

Les systèmes d’exploitation suivants prennent en charge Google Chrome :

  • Windows Server 2008 R2

  • Windows Server 2008

  • Windows Server 2003

  • Windows 7

  • Windows Vista

  • Windows XP

Mozilla Firefox (dernière version diffusée publiquement)

Les systèmes d’exploitation suivants prennent en charge Mozilla Firefox :

  • Windows Server 2008 R2

  • Windows Server 2008

  • Windows Server 2003

  • Windows 7

  • Windows Vista

  • Windows XP

Apple Safari (dernière version diffusée publiquement)

Les systèmes d’exploitation suivants prennent en charge Safari :

  • Mac OSX (Snow Leopard et Lion)

  • Windows 7

  • Windows Vista

  • Windows XP

Contrôles ActiveX

Certaines fonctions de SharePoint Server 2010 requièrent l’utilisation des contrôles ActiveX. Cela entraîne des limitations sur les navigateurs qui ne prennent pas en charge ActiveX. Actuellement, seules les versions 32 bits d’Internet Explorer prennent pas en charge ces fonctions. Tous les autres navigateurs présentent les limitations suivantes.

Fonctionnalité Limitation

Se connecter à Outlook, Se connecter à Office et Synchroniser avec l’Espace de travail SharePoint

Fonctionne avec un contrôle ActiveX et le protocole stssync://. Par conséquent, la fonctionnalité peut être limitée en l’absence de contrôle ActiveX control, par exemple avec la version fournie avec Microsoft Office 2010. Cette fonctionnalité requiert en outre une application compatible avec le protocole stssync://, telle qu’Microsoft Outlook.

Mode Feuille de données

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle.

Modifier avec application Microsoft Office

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle.

Copie et téléchargement de fichier en amont

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle.

Intégration à Microsoft InfoPath 2010

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle.

Intégration à la Bibliothèque d’images de Microsoft PowerPoint 2010

Requiert un contrôle ActiveX 64 bits, tel que celui fourni avec Microsoft Office 2010. L’utilisateur peut recourir aux solutions de contournement suivantes si aucun contrôle n’est installé.

  • Pour télécharger plusieurs images dans une bibliothèque d’images, il faut télécharger une image à la fois en utilisant Upload.aspx.

  • Pour modifier une image dans une bibliothèque d’images, il faut télécharger l’image, la modifier, puis la télécharger vers la bibliothèque d’images.

  • Pour télécharger plusieurs images à partir d’une bibliothèque d’images, il faut télécharger une image à la fois en cliquant sur le lien d’image.

Création de diagramme Microsoft Visio 2010

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle.

Nouveau document

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle.

Bien que la commande Nouveau document soit susceptible de ne pas fonctionner, vous pouvez utiliser la fonction Télécharger un document. Si vous installez et configurez Office Web Applications sur le serveur, la commande Nouveau document fonctionne et vous pouvez créer un document Office dans votre navigateur.

Envoyer vers

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle.

Sans le contrôle, il est impossible d’envoyer des fichiers d’une batterie SharePoint vers une autre. Cependant, il est toujours possible d’envoyer des fichiers d’un site vers un autre.

Signature de formulaires (InfoPath Form Services)

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle.

Intégration aux feuilles de calcul et aux bases de données

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle. L’utilisateur peut recourir aux solutions de contournement suivantes si aucun contrôle n’est installé :

  • Pour modifier un document, il faut le télécharger, le modifier, puis le réenregistrer sur le serveur.

  • Dans une liste qui requiert l’extraction d’un document pour la modification, il faut extraire le document à l’aide du menu Édition, le modifier, puis l’archiver à l’aide du menu Édition.

  • Exporter vers une feuille de calcul. Pour exporter une liste SharePoint en tant que feuille de calcul, cliquez sur Exporter vers une feuille de calcul sous l’onglet Liste dans le ruban.

Bibliothèque de diapositives et intégration à PowerPoint 2010

Microsoft Office 2010 ne fournit pas la version 64 bits de ce contrôle. L’utilisateur peut recourir aux solutions de contournement suivantes si aucun contrôle n’est installé :

  • Supprimer une diapositive. Pour supprimer une diapositive, cliquez d’abord sur celle-ci, puis cliquez sur Supprimer la diapositive ; répétez l’opération pour chaque diapositive.

Pour Microsoft Office 2010 (64 bits), seuls les contrôles suivants fonctionnent avec des navigateurs 64 bits :

  • ppslax.dll – Bibliothèque de diapositives et intégration à PowerPoint 2010

  • name.dll – Informations de présence

Compatibilité du navigateur pour les sites de publication

Pour les sites de publication, les fonctionnalités de gestion de contenu Web intégrées à SharePoint Server 2010 permettent un contrôle approfondi du balisage et du style de l’expérience de lecture. Les concepteurs de page peuvent utiliser ces fonctionnalités afin de s’assurer que les pages qu’ils conçoivent sont compatibles avec d’autres navigateurs, y compris Internet Explorer 6, pour l’affichage du contenu. Cependant, il leur incombe de créer des pages qui soient compatibles avec les navigateurs qu’ils souhaitent prendre en charge.

Un navigateur normalisé, tel qu’Internet Explorer 9 ou Mozilla Firefox, est requis pour créer du contenu.

Prise en charge des navigateurs mobiles

Le tableau suivant récapitule les niveaux de prise en charge des navigateurs mobiles couramment utilisés.

Système d’exploitation d’appareil mobile

Version minimum du système d’exploitation

Navigateur

Windows Phone

7.0

Internet Explorer

Apple iOS

4.0

Safari

Google Android

2.1

Navigateur Android

Research in Motion (RIM) Blackberry

4.0

Navigateur Blackberry

Nokia Symbian

3

Navigateur Nokia

Planifier la prise en charge du navigateur

Partager cet article

2 septembre 2014 2 02 /09 /septembre /2014 22:22

Impossible d'afficher ce formulaire dans le navigateur, car l'utilisation de cookies de session a été désactivée dans les paramètres actuels du navigateur. Les cookies de session doivent être autorisés afin de charger le formulaire.

 the URL containing a “_” character When opening an InfoPath form in an IE browser (from IE8 up to IE11), the following error was being throwned: 

 

"The form cannot be displayed in the browser because the use of session cookies has been disabled in the current browser settings. In order to load the form, session cookies must be allowed"

Cause:

This behavior is due to the fact that Internet Explorer doesn’t accept cookies with host names that contain the “_” character.

Solution:

 

To solve this problem, the “_” character was removed from the URL. In this example:

http://tenstep_serveur:8080/  doesn’t work

http://tenstepserveur:8080/   work

Partager cet article

4 août 2014 1 04 /08 /août /2014 19:19

Microsoft SharePoint Server 2013 and Microsoft SharePoint Foundation 2013

Using SharePoint Central Administration Web site, under Upgrade and Migration, click Check product and patch installation status
You can also use the Windows PowerShell command, (get-spfarm).BuildVersion, however that can show a different version number from the web page.

Version

CU/PU/SP

SPF 2013

SPS 2013

SPS 2013 +

Project Server

Office Web App Server

15.0.4623

June 2014 CU

KB2881063

KB2881061

KB2881062

KB2881051

15.0.4605

April 2014 CU

KB2863892

KB2878240

KB2880484

KB2863899

 

Note: Office Web Apps Server 2013 fixes will be released with a different cadence to SharePoint in the future.

 

 

15.0.4569

SP1 re-released

KB2880551

KB2880552

KB2880553

KB2880558

 

Note: How to tell which Service Pack 1 you have installed on SharePoint 2013

 

 

15.0.4551

December 2013 CU

KB2849961

KB2850024

Install SP2013 Dec CU + KB2837668

KB2850013

15.0.4551

October 2013 CU

KB2825674

KB2825647

KB2825650

KB2825686

15.0.4535

August 2013 CU

KB2817517

KB2817616

KB2817615

KB2817521

15.0.4517

June 2013 CU

KB2817346

KB2817414

KB2817415

KB2817350

15.0.4505

April 2013 CU

KB2751999

KB2726992

KB2775426

Notes KB2799821

 

15.0.4481

March Update

KB2768000

KB2767999

KB2768001

Notes KB2760486

 

Important: Due to a change in the package configuration introduced after SharePoint 2013 RTM the March Public update is a mandatory requirement in order to install subsequent SharePoint 2013 Updates.

 

 

15.0.4420

RTM

 

 

 

 

15.0.4128  

Preview (Beta 2)

 

 

 

 

Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010

Using SharePoint 2010 Central Administration Web site, under Upgrade and Migration, click Check product and patch installation status to show version numbers. Click the icon to the right of the SharePoint 2010 product name, in the list below, to see a screenshot of the Manage Patch Status page.

You can also use the Windows PowerShell command, (get-spfarm).BuildVersion, however that can show a different version number from the web page. When the BuildVersion from Windows PowerShell is different from the number shown CA web page it is shown in brackets below:

Note: Microsoft has released a SharePoint 2010 Information Worker and Evaluation (SP1) virtual machine, which you can find at the Microsoft download site.

 

Version

CU

SPF 2010

SPS 2010

SPS 2010 +

Project Server

14.0.7125.5002

June 2014

KB2880975

KB2880972

KB2880974

14.0.7121.5000/4

April 2014

KB2878270

KB2878250

KB2878253

14.0.7116.5000

February 2014

KB2863938

KB2863913

KB2863917

14.0.7113.5000

December 2013

KB2849990

KB2849971

KB2849972

14.0.7110.5000

October 2013

KB2825824

KB2825786

KB2825793

14.0.7106.5002

August 2013 re-released 

KB2825990

KB2825949

KB2825959

14.0.7102.5004

June 2013 re-released 

KB2817552

KB2817527

KB2817530

 

The June Cumulative Update for SharePoint 2010 is a Post-SP2 hotfix, which means that the fixes included in June CU are not included in SP2. You have to install SP2 first and then the June CU to get all the latest fixes.

 

 

 

 

 

14.0.7015.1000

SP2 KB2687524

KB2687464

KB2687453

KB2687452

 

If you do not plan to upgrade to SP2 yet, and have installed SP1 you have until 14/10/2014 to do so, when service pack support ends for SharePoint 2010

 

 

 

 

 

14.0.6137.5000

April 2013

KB2794728

KB2775353

KB2775426

14.0.6134.5000

February 2013

KB2760791

KB2767793

KB2767794

14.0.6131.5003

December 2012

KB2596957

KB2596955

KB2596956

14.0.6129.5003

October 2012

KB2687566

KB2687564

KB2687565

14.0.6126.5000

August 2012

KB2687355

KB2687353

KB2687354

14.0.6123.5002

June 2012

KB2598373

KB2598354

KB2598355

14.0.6120.5000

April 2012

KB2598321

KB2598151

KB2598152

14.0.6117.5000

February 2012

KB2597132

KB2597150

KB2597152

14.0.6114.5000

December 2011

KB2597058

KB2597014

KB2597015

14.0.6112.5000

October 2011

KB2596508

KB2596505

KB2596506

14.0.6109.5002

August 2011

KB2553050

KB2553048

KB2553049

14.0.6106.5002

June 2011 re-released 

 KB2536601     

 KB2536599     

KB2536600

The June Cumulative Update for SharePoint 2010 is a Post-SP1 hotfix, which means that the fixes included in June CU are not included in SP1. You have to install SP1 first and then the June CU to get all the latest fixes. But first read the following related post and So What the Fuss? - Service Pack 1 and June 2011 CU for SharePoint 2010. Also see: User Profile Synchronization Service changes in the June 2011 Cumulative Update

 

 

 

 

 

14.0.6029.1000  

SP1 KB2532120

 KB2460058     

 KB2460045     

KB2460047

More information on SP1 can be found at the following locations:

If you do not plan to upgrade to SP1 yet, you have until 13/10/2015 to do so, when mainstream support for installations of SharePoint Server 2010 and SharePoint Foundation 2010 without SP1 retire.

 

14.0.5138.5001

April 2011     

 KB2512804     

 KB2512800     

KB2512801

14.0.5136.5002

February 2011     

 KB2475880     

 KB2475878     

KB2475879

14.0.5130.5002

December 2010

 KB2459125

 KB2459257

KB2459258

14.0.5128.5003  [Updated 2nd Dec 2010]

October 2010 rereleased

 

 KB2394320

KB2394322

14.0.5128.5000

October 2010

 KB2394323

 

 

    Information concerning the out-of-band security update to address ASP.NET issue can be found at: Stefan Gossner blog

14.0.5123.5000

August 2010

 KB2352346

 KB2352342

KB2352345

14.0.5114.5003  (14.0.5114.5000)

June 2010

 KB2028568

 KB983319 KB983497 KB2124512 KB2281364 and KB2182938 (localized Japanese only)

 

14.0.5050.5002  (14.0.5050.5001)

Hotfix

 KB2032588

14.0.4763.1000  (14.0.4762.1000)

RTM

 SPF 2010

 SPS 2010

14.0.4536.1000

Beta 2

Partager cet article

Articles Récents

Liens