The 6268.0000 version of DirSync changes the CoexistenceSync cmdlets

Recently, I had to configure with the Active Directory (AD) guy of our organisation the DirSync tool to sync the on-premises user attributes to the cloud. The Windows Azure Active Directory team regularly updates the DirSync client with new features and functionality. Not all additions are applicable to all audiences.

On each blogpost that you can find on the Internet has the same PowerShell commands to kick off a Directory Synchronization:

  • Open PowerShell
  • Add-PSSnapin Coexistence-Configuration
  • Start-OnlineCoexistenceSync

More in detail

At the Windows PowerShell prompt, one of the following cmdlets are necessary: 

Install-OnlineCoexistenceTool -UseSQLServer -Verbose
  • To install the Directory Synchronization tool on the same server that has SQL Server 2008 Express
Install-OnlineCoexistenceTool -UseSQLServer 
-SqlServer <SQLServerName> 
-ServiceCredential (Get-Credential) 
–Verbose
  • To install the Directory Synchronization tool by using a remote installation of SQL Server 2008 Express
Install-OnlineCoexistenceTool 
-UseSQLServer 
-SqlServer <SQLServerName> 
-ServiceCredential (Get-Credential) 
-SqlServerInstance <SqlInstanceName>

 

  • To install the Directory Synchronization tool by specifying the installation of SQL Server, add the “-SqlServerInstance” parameter.

Well, this is not true anymore. Since the 6268.0000 version, relased on 6/5/2014 this way has changed.

DirSync Full SQL

Be aware! The new way now is

Import-Module DirSync

Install-OnlineCoexistenceTool -UseSQLServer –SqlServer <ServerName> -Upgrade -Verbose -ServiceCredential (Get-Credential)

Please check this TN Wiki page to see all the changes on the Directory Synchronization tool: http://social.technet.microsoft.com/wiki/contents/articles/18429.microsoft-azure-active-directory-sync-tool-version-release-history.aspx

 

References

Over 1 Million FREE Microsoft eBooks Given Away in 2 days! And what about our #SharePoint eBooks?

 

Free #eBooks

Eric Ligman, Microsoft Sr. Sales Excellence Manager wrote a blogpost about the largest collection of FREE Microsoft eBooks ever, including: Windows 8.1, Windows 8, Windows 7, Office 2013, Office 365, Office 2010, SharePoint 2013, Dynamics CRM, PowerShell, Exchange Server, Lync 2013, System Center, Azure, Cloud, SQL Server, and much more…

Over 130 free eBooks, Step-By-Steps, Resource Guides, etc., for your enjoyment. Plus Eric also included links to the free eBooks he shared in the past so you have all of them here in one single post, making this his single largest collection ever (Almost 300 total)! You can have a look to all the eBooks on this link: http://blogs.msdn.com/b/mssmallbiz/archive/2014/07/07/largest-collection-of-free-microsoft-ebooks-ever-including-windows-8-1-windows-8-windows-7-office-2013-office-365-office-2010-sharepoint-2013-dynamics-crm-powershell-exchange-server-lync-2013-system-center-azure-cloud-sql.aspx

 

Eric is absolutely THRILLED to see the overwhelming response you have had to the FREE eBook giveaway again this year and we he is happy to announce that not only did you hit the ONE MILLION free eBooks downloaded in a week, but you did it in just TWO DAYS! That’s right; the community surpassed the ONE MILLION mark within 48 hours! So a lot of thanks to the community to taking advantage of this offer and getting the free Microsoft eBooks!

My role, herein?

Well, as being a TechNet WikiNinjas Member one of my tasks is to evangelize the WikiNinjas with eBooks. With the fellow SharePoint WikiNinjas we wrote all together 2 wonderful ebooks named:

Wiki Ninjas Guide to SharePoint 2013

The Wiki Ninjas Guide to SharePoint 2013 – Part II

What are the most popular eBooks being downloaded

Eric created stats about the downloaded eBooks. Our eBooks are ranked #27 and #53 (of 300 free ebooks!) of the “most popular eBooks being downloaded”. We can all be proud about our SharePoint eBooks! Please refer here: http://blogs.msdn.com/b/mssmallbiz/archive/2014/07/10/over-1-million-free-microsoft-ebooks-given-away-in-2-days-and-soon-to-be-2-million.aspx

Again a special thanks to all fellow SharePoint-WikiNinjas-lovers

Thank You !!!

 

  • Ed Price – MSFT
  • Joe Davis – MSFT
  • Thuan Soldier – MVP
  • Magriet Bruggeman – MVP
  • Luigi Bruno
  • Craig Lussier
  • Hezequias Vasconcelos
  • Matthew Yarlett
  • Marcelo Sincic – MVP
  • Benoit Jester – MVP
  • Fernando Lugão Veltem – MVP
  • dplotnikov – MVP
  • Bjorn H Rapp – MVP
  • Inderjeet Singh Jaggi
  • RaghuAriga
  • Brent Groom – MSFT
  • Dan Christian
  • Aulakh Amardeep – MVP
  • Rashu Rahul
  • Melick – MVP
  • Jason Barkes
  • Steven Andrews
  • Jesper Arnecke
  • Nikolas Charlebois-Laprade
  • Viivek Jagga ( He’s name is not on the ebooks, but has an article as well!)

 

The SharePoint WikiNinja

- Gokan

GUSS Webcast : Juillet 2014, Sharepoint 2013, Azure Machine Learning

Bonjour à tous,
Le GUSS (Groupe utilisateur SQL Serveur) nous propose 2 sessions de 30 minutes pour les webcasts de Juillet 2014.

Guss_PRO

La 1ère session concernera SharePoint 2013 et SQL Server 2012 sur les bonnes pratiques à adopter. J’animerais cette session. Le but de cette session est de vous montrer/expliquer les bonnes et mauvaise pratiques de SharePoint Server avec SQL Server. Voici un synopsis de ma session :

Quand votre responsable annonce l’acquisition de SharePoint en tant que DBA le devoir de « configuration et installation » de SQL Server vous attend. Malgré que SharePoint soit l’outil de collaboration (ECM) le plus convoité de Microsoft la méfiance s’installe car vous avez peu ou pas de connaissance technique concernant SharePoint. Le contenu des sites de collaboration, sites publics ainsi de configuration est stocké dans SQL Server d’où l’importance de ceci ! Dans cette session, nous allons explorer les tendances de SharePoint pour DBA. Pourquoi SharePoint aime faire les choses à sa manière? Que pouvez-vous ne pas faire avec les bases de données de SharePoint? Quels sont les paramètres spécifiques de SharePoint à savoir et maitriser pour une utilisation optimale? Comment maintenir les bases de données SharePoint sans ruiner le soutien de Microsoft? Après la session vous aurez les bases fondamentales pour commencer n’importe quel projet SharePoint en tant que DBA.

Guss_PRO

La seconde session concernera Microsoft Azure Machine Learning, qui est désormais disponible en preview et qui vous permet de réaliser vos analyses de données dans le cloud. Elle sera animée par Franck Mercier à partir de 19h30.

Les webcasts auront lieu le : mercredi 30 juillet 2014 de 19h à 20h

Un chat vous permettra de poser vos questions directement pendant la session. Les informations de connexion vous seront communiquées la veille des webcasts. Remarque technique : pensez à valider votre configuration. Toutes les informations pour se connecter aux sessions en ligne du GUSS

Au plaisir de vous voir tous et nombreux !

Enjoy !

collaborating with external users in SharePoint Online

One of the biggest reasons why organizations and/or companies are migrating to the cloud is the possibility of collaborating with external users. This out of the box feature doesn’t require any infrastructure expand and is free with your plan. If you want to have the same feature on-premises, well you’ll have to setup and configure many other things…

This feature isn’t that simple as it looks. First you have to authorize Sharing with External Users on your Site Collection level. Therefore connect to your tenant and select a select a Site Collection. Then click on Share.

collaborating with external users

Be sure to select the last combo box to allow both external users who accept sharing invitations and anonymous guest links.

collaborating with external users

Let’s test. Surf to a site and share it with an external user. Fill the email address and a little message for the external user. If necessary – under show options – you can select the permission level for the external user.

collaborating with external users

Connect to your email provider and check the invitation. If the external user accepts the invitation, he will be redirected to the Office 365 login page. If his account is already an existing Office 365 he can provide his Office 365 credentials, otherwise he will need a live ID account ( provided by Microsoft)

collaborating with external users

Select the appropriate option. In our case, as we are using the LIVE account, please select the first.

collaborating with external users

Provide your credentials and hit connect.

collaborating with external users

If you followed this guideline everything should work smoothly. You should be able to connect to your tenant with your live ID account.

Let’s test. Connect to your site, and check your settings. The account name should be something like i:0#.f|membership|live.com#MAILADRESS.

collaborating with external users

If you want to delete the added user from your site, well there is no real option, way to that in SharePoint Online. You can delete the user under User Policies but if you have several users you’ll have to do it “one by one”.

collaborating with external users

You can also use the SharePoint Online Management Shell that you can download at http://www.microsoft.com/en-us/download/confirmation.aspx?id=35588

  1. Install SharePoint Online Management Shell.
  2. From the Start button, choose All Programs, and then select SharePoint Online Management Shell.
  3. Run Connect-SPOService. For example, type this command at the prompt: Connect-SPOService -Url https://contoso-admin.sharepoint.com -credential admin@contoso.com, where -URL is your tenant and –credential is your tenant administrator

collaborating with external users

3 cmdlets are enough to delete an External User from your SharePoint Online.

  • Get-SPOExternalUser
  • Remove-SPOExternalUser
  • Give the Unique ID from the user that you want to delete.

In a well-known organization where thousands of SharePoint online users, you’ll maybe forgot the invitations you send and want to see a history.

With SharePoint Online, that’s possible. To manage requests go to the site menu settings and click on “Access requests and invitations

collaborating with external users

The site owner is automatically the request access owner. But you can change this. Under Site permissionsè Access Request Settings è change the owner and set another user who will invite external partners and moderate the partners who wants to join your site.

collaborating with external users
The only thing that needs to be “redefined” is the “delete users”, but otherwise, this feature is complete on SharePoint Online!

Happy Configuring!

Auditing SQL Server Database Engine changes for SharePoint 2013.

Why the hell would you audit SQL Server changes for SharePoint Server as there is a “don’t touch“policy. As a SharePoint administrator or database administrator you can’t directly write into a database. If you touch the databases, you’ll lose your support.

On a proof of concept (POC) machine for SharePoint, all the databases were deleted, including the config and admincontent database. We couldn’t find who did it, because there was no logging foreseen therefore.

Well, how do we activate logging on SQL Server for any Server Change?

The general process for creating and using an SQL Server audit is as follows:

  1. Create an audit and define the target.
  2. Create either a server audit specification or database audit specification that maps to the audit. Enable the audit specification.
  3. Enable the audit.
  4. Read the audit events by using the Windows Event Viewer or Log File Viewer

More in dept., open SQL Server Management Studio.

Auditing SQL Server changes for SharePoint 2013

Under the Object Explorer expand Security. For the SQL Server logging we’ll need to configure 2 sections:

  • SQL Server Audit: used when you want to audit an activity that occurs at the SQL Server instance level, such as auditing login and logout activity. According to TechNet: The SQL Server Audit object collects a single instance of server or database-level actions and groups of actions to monitor. The audit is at the SQL Server instance level. You can have multiple audits per SQL Server instance. When you define an audit, you specify the location for the output of the results. This is the audit destination. The audit is created in a disabled state, and does not automatically audit any actions. After the audit is enabled, the audit destination receives data from the audit.
  • Server Audit Specification: used when you want to audit an activity within a database, such as who is select data from a particular table. Also according to TechNet: The Server Audit Specification object belongs to an audit. You can create one server audit specification per audit, because both are created at the SQL Server instance scope. The server audit specification collects many server-level action groups raised by the Extended Events feature. You can include audit action groups in a server audit specification. Audit action groups are predefined groups of actions, which are atomic events occurring in the Database Engine. These actions are sent to the audit, which records them in the target.

Auditing SQL Server changes for SharePoint 2013

 

Right click on Audits and hit New Audit…

Auditing SQL Server changes for SharePoint 2013 

 Provide an audit name and select the Audit destination. You can choose between a File (where you have to specify a physical path), an Application or Security Log. In my case I’ll chose Application Log and hit ok.

  • The application log: to log successful and/or failed logins to the Application log in the Windows® operating system and the SQL Server Error Log
  • File: a physical place on your root or other drive.
  • Security log: This is significant in that the Windows Security log is considered to be resistant to tampering and nonrepudiation. http://technet.microsoft.com/en-us/library/dd392015(v=sql.100).aspx
  • Queue delay (in milliseconds) specifies the amount of time in milliseconds that can be elapsed before audit actions are forced to be processed. A value of 0 indicates synchronous delivery. The default minimum value is 1000 (1 second). The maximum is 2,147,483,647

Auditing SQL Server changes for SharePoint 2013

Your Audit is created but disabled by default. Right-click and hit Enable Audit.

Auditing SQL Server changes for SharePoint 2013
Create a New Server Audit Specification

Auditing SQL Server changes for SharePoint 2013

Provide a name and select our newly created Audit. As last step, specify what you want to audit for your SQL Server under “Audit Action Type”. I selected the DATABASE_CHANGE_GROUP. This event is raised when a database is created, altered, or dropped. This event is raised whenever any database is created, altered or dropped.

The following TechNet Site describes the server-level audit action groups and provides the equivalent SQL Server Event Class where applicable.

Auditing SQL Server changes for SharePoint 2013

When creating or deleting a database or changing anything on the SQL Server Database you’ll be notified on the Event Viewer with the exact message and the correct user.

Auditing SQL Server changes for SharePoint 2013

You can also audit the databases. Operational stuff like updating or deleting a record can be audited. It’s the same way of working but you’ll have to select a database before specify anything to audit.

 Auditing SQL Server changes for SharePoint 2013

More information about SQL Server Audit (Database Engine) here: http://technet.microsoft.com/en-us/library/cc280386(v=sql.110).aspx

Happy Config!

SharePoint Code Analysis Framework : Mise en Avant

Nous nous étions mis d’accord avec Benoit Jester d’écrire plusieurs articles concernant SPCAF : SharePoint Code Analysis Framework :

SPCAF

Benoit a déjà écrit une série consacrée à l’outil SPCAF que vous pourrez lire sur son blog. Voici les liens :

SharePoint a grandi au fil des années et est aujourd’hui largement utilisé dans les entreprises. SharePoint est utilisé dans les entreprises comme un intranet ou un portail collaboration. Une des principales raisons du succès de SharePoint est l’extensibilité. Je m’explique ; L’API puissante offre des possibilités illimitées pour personnaliser et étendre SharePoint avec un code personnalisé.

Parfois, cette extensibilité est bonne et parfois mauvais. La personnalisation inappropriée peut conduire un environnement SharePoint, impossible à gérer. Des problèmes de performance, des problèmes d’autorisations et beaucoup d’autre que j’oublie de citer. Souvent, la migration vers les nouvelles versions de SharePoint est impossible à quasi impossible à cause de ces personnalisations qui conduit à d’énormes efforts pour migrer.

Cependant interdire la personnalisation de SharePoint n’est pas une option pour de nombreuses entreprises, car ce serait limiter la potentiel de SharePoint. Nous (SPCAF) devons donc trouver un moyen de personnaliser SharePoint mais empêcher l’impact négatif.

Une façon est d’établir des règles, des conventions et des politiques qui définissent la façon dont SharePoint peut être utilisé. Ces règles et politiques doivent être définies et doivent être acceptés par toutes les personnes concernées, comme les développeurs, architectes et aussi par le côté de l’entreprise parce que ces politiques peuvent limiter la capacité d’adaptation de SharePoint. Si cette gouvernance n’est pas applicable pour vous ou votre société vous pourrez opter pour l’achat un outil gratuit/payant comme le SharePoint Code Analysis Framework (SPCAF).

Le SPCAF est un Framework des outils qui analyse vos solutions de plusieurs angles. Le SPCAF est divisé en 4 parties :

  • SPCop: Rule Checker: SPCop vérifie les WSP et les applications pour les violations commises contre ~ 400 règles dans différentes catégories, comme exactitude, la sécurité, de prise en charge, de conception, de déploiement des meilleures pratiques, de dénomination, localisation, etc
  • SPMetrics: Metric Calculator: SPMetric calcule des chiffres et des indices pour permettre la mesure de la complexité des paquets. Il peut compter par exemple le nombre de caractéristiques, les types de contenu, des champs, des modèles de liste, les instances de listes etc, ou les lignes de codes pour chaque langue comme XML, HTML, ASPX, CSS, JavaScript etc …
  • SPDepend: Dependency Analyzer : SPDepend scanne le code pour les dépendances entre les composants. Il détecte les dépendances d’activation fonction, les fichiers de référence et des images, le type de contenu, les références entre objets SharePoint comme instances de liste. Il détecte également les dépendances externes de composants SharePoint ou des composants tiers.
  • SPInventory: Solution Documentation : SPInventory recueille tout le code et les informations sur les objets et les composants mis en œuvre et génère une documentation de la solution. Il enregistre les assemblées, les caractéristiques, les types de contenu, des modèles de liste et fournit des informations sur leurs principales propriétés importantes comme identifiants, noms, titres, etc.

SPCAF

L’équipe (RENCORE AB) a également divisé les solutions par expertise par expertise. Dépendant de votre expertise vous pourrez sélectionner l’outil dont vous avez besoin.

SPCAF

En tant que Architecte :

SPCAF

En tant que Développeur :

SPCAF

En tant que Quality Manager :

SPCAF

Et au final, en tant que Administrateur :

SPCAF

Je vous conseille vivement de lire la série publiée par Benoit et de demander votre license trial chez Matthias eining (@mattein) ou sur le site suivant : http://www.spcaf.com/trial/. Vous pourrez également acheter le produit si vous avez déjà l’expérience =)

SPCAF