Posts Tagged ‘Groups’

Next Generation Sync Client | Registry key vs Admin-Center

OneDrive for Business, Microsoft

some people ask me: Do I have to set the registry Key TeamSiteSyncPreview in each Client, to sync document libraries from team sites or groups from SharePoint Online to my local device? With the Next Generation Sync Client, not the old Groove client!

My answer: Yes / No, it depends.


You know, that the Next Generation Sync Clients comes with Windows 10 OS or you may install it manually with other OS, and you will have selective sync with

  • OneDrive (Personal)
  • OneDrive for Business

Sync with Next Generation Sync Client  without  settings  in the  Admin-Center or installing the Reg-Key

If you want to sync data from other document libraries in Office 365 you need to set some switches in the admin portal of Office 365 and you need therefore admin credentials OR you install the registry Key TeamSiteSyncPreview  on you local device. But in this case you need local admin rights.

The difference is, that with the registry Key you open access to sync for other document libraries only for this device.. So you may read it from Microsoft. All other devices of your Office 365 tenant have no access. That’s ideal for testing with a test group of users.

If you want to enable the sync process with the Next Generation Sync Client  for all of your users you need the SharePoint admin of Office 365. And, you do not need to set this registry Key on local devices.

If you have set the Registry Key or having changed the settings in Office 365 you may then sync data from

  • OneDrive Personal
  • OneDrive for Business
  • document libraries in SharePoint Team Sites
  • document libraries in SharePoint  Groups
  • document libraries in SharePoint  Planner*)
  • document libraries in Teams

*) 03/23717 There is a known bug. You have to change to classic view

Sync with Next Generation Sync Client  with settings  in the  Admin-Center or installing the Reg-Key

What and where do I have to change/set in the admin Center of Office 365?

Open the SharePoint admin center.
In the left pane, click settings.
Make sure "OneDrive Sync Button" is set to "Start the new client." To sync SharePoint files with the new client, you must also sync OneDrive files with the new client.
For "Sync Client for SharePoint," select Start the new client.
Click OK

SharePoint Admin Center: OneDrive Sync

If you have made these changes and the users clicks on the sync button, the Next Generation Sync Client is launched. You also have the chance to install the newest version from the popup window.

But You have to know, and that’s very important:

These changes take several hours to propagate. To check that they’ve propagated, go to a SharePoint Online site and click Sync. In the browser dialog box that confirms the request to open a program, the "Program" should appear as "Microsoft OneDrive" and the "Address" should start with "odopen://"

Many issues I have heard, come from this point.

Next Generation Sync Client | Registrierungsschlüssel vs Admin-Center

24. März 2017 1 Kommentar

OneDrive for Business, Microsoft

Ich wurde schon des Öfteren gefragt: Muss ich den Registrierungsschlüssel TeamSiteSyncPreview im Client setzen, um auf Dokumentenbibliotheken von SharePoint Teamsites oder Groups in Office 365 mit meinem lokalen Windows Client zu synchronisieren? Wohlgemerkt mit dem Next Generation Sync Client, nicht mit dem alten Groove Client.

Die Antwort: Ja / Nein, das kommt darauf an.


Der Next Generation Sync Client, Bestandteil des Windows 10 Betriebssystems oder aber für diverse Betriebssysteme nachträglich installierbar, beherrscht von Haus aus selektive Synchronisation mit

  • OneDrive (Personal)
  • OneDrive for Business

Synchronisation mit dem Next Generation Sync Client  ohne Einstellungen im Admin-Center


Will ich mit mit anderen Dokumenten-Bibliotheken in Office 365 eine Synchronisation herbeiführen, so benötige ich geänderte Einstellungen im Administrationsteil für Office 365 und damit den SharePoint Administrator oder ich installiere den Registrierungsschlüssel TeamSiteSyncPreview  auf meinem Rechner. Dazu benötige ich natürlich lokale Admin-Rechte auf meinem Gerät.

Der Unterschied ist der, dass ich mit dem Registrierungsschlüssel genau dieses und nur dieses Gerät freischalte für die Synchronisation anderer Dokumenten-Bibliotheken. Das ganze hat Microsoft hier beschrieben. Alle anderen Geräte die sich mit Office 365 verbinden und synchronisieren bekommen keinen Zugriff. Damit kann ich bestimmte, ausgewählte  Benutzer zu Testzwecken für eine Synchronisation weiterer Dokumentenbibliotheken bestimmen.

Soll für alle alle Benutzer der neue Next Generation Sync Client benutzt werden, so kann dies der SharePoint-Administrator für Office 365 durchführen. Am lokalen Client muss dann kein weiterer Registrierungsschlüsse mehr eingetragen werden.

Ist der Key eingetragen oder sind die Einstellungen in Office 365 gesetzt, kann eine selektive Synchronisation mit dem Next Generation Sync Client mit

  • OneDrive Personal
  • OneDrive for Business
  • Dokumentenbibliotheken in SharePoint Team Sites
  • Dokumentenbibliotheken in SharePoint Groups
  • Dokumentenbibliotheken in SharePoint Planner*)
  • Dokumentenbibliotheken in Teams
    *) 23.03.17 Hier existiert noch ein Bug. Es muss zur klassischen Darstellung gewechselt werden.

Synchronisation mit dem Next Generation Sync Client  mit Einstellungen im Admin-Center

Was muss wo in der Admin Konsole von Office 365 eingestellt werden?

Öffnen sie das SharePoint Admin Center in Office 365
Klicken Sie auf Einstellungen
Wählen Sie für “Synchronisationsclient für SharePoint” die Option “Neuen Client starten” Und bestätigen sie das ganze mit OK

SharePoint Admin Center: neuen Sync-Client starten

Durch diese Selektion werden Benutzer, welche auf einen Synchronisations-Butten klicken, den neuen Client (New Generation Sync Client ) verwenden. Ist dieser auf dem Client nicht vorhanden, kann er von dem Popup Fenster aus installiert werden.

Das wichtigste ist im nachstehenden Satz beschrieben:

Diese Änderungen im SharePoint Admin Center können mehrere Stunden in Anspruch nehmen. Das ist abhängig davon, wie viele Benutzer in Ihrem Office 365 vorhanden sind und wie viele Objekte betroffen sind.

Hier ist die häufigste Ursache zu finden. Hier hilft nur abwarten.

Office 365 | OneDrive for Business, Team Sites and Groups – Overview

31. Oktober 2016 6 Kommentare

in this blog post I will show, where you store your documents in Office 365 and how do you sync these files to your local device. For better understanding I have created some pictures.

The company is migrated to Office 365. The CEO (User A) is happy, because the first step into the cloud was the mail migration and he may work as usual, send and receive Mails with his Outlook client. But he is not alone. All employees feeling the same. New for all Users of the company is the possibility, to save documents and files to the cloud storage called OneDrive for Business. But the Users accustomed, working with local saved documents on their devices. Therefore the administrators have installed the Next Generation Sync Client to sync all the cloud files to their local devices. The Users then will have access to their relevant documents, even if they are Offline.

Sharing of a document in OneDrive for Business

Only if  they want to share a document in their OneDrive for Business document libraries, they have to switch to the Web Browser,  (So the above picture shows, that User E shares a document with User K). User K may also access this shared document on his local device, when he has synchronized it.

But this Sharing feature is inconvenient. Users want to have a place, where they may store documents for her department and only certain Users may have access.


Each Employee get storage in Office 365 for his business documents and he may sync these documents (or part of theses documents) to his local device.


Team Sites

Creation of a team site (admin)

The administrator of the company creates the first Team Site. This Site is for the finance department.

Who has access to the Team Site?

Only the CEO (User A) and another User G have access to this site. Now they may store finance documents into the Team site document library and also may sync these documents to their local devices.

more Team Sites

Three diffrent Team sites and their members

The admin creates two more Team sites on SharePoint Online for department Marketing and HR. So you see, only the CEO (User A) have access to all of the three Team Sites. But the admin also provide different organization Units (OU) in the AD of Azure for future use. If the company growth, the admin have to assign new Users only to the right OU and automatically the new User get access to the Team Site.


With Team sites in SharePoint Online department Users may collaborate with the different documents, without sharing these documents or folders. And the best: The documents may synced to their devices.



Some involved employees have a wish to establish a place, where they may exchange new ideas, have a calendar for all members of this place and also a Mail address. And they think they may do it without asking the administrator.

User A creats a Group

In our example the CEO (User A) creates a Group and called this Group G-Marketing. As mentioned, he’s not the admin. But he has ask his experts for a naming convention. The expert told him, if he creates a Group with the Name “Sales”, the  administrator is not able to create a team site with this name.

Other members of the Group

During the creation process, User A invites User D and K as members to this new group. So for discussion all three members may save documents in the document library of this group and, what surprise, they may also sync these documents to their local machines.

Groups and members: Mail and calendar

the Company Employees G and C for department HR and Sales do the same. But you also see, they have access via Mail and Calendar to their groups.


You may create a group without Admin rights. Mails and a Group shared calendar will established automatically. Documents inside the document library may synchronized locally.

Sync to local devices

the last picture shows all synced places to a local device of the User A

local sync from diffrent areas to a users device

But you have to know: If a User has more than one device, you have to initiate all syncs to each different device. And the Next Generation Sync Client  (NGSC) supports selective sync, so the syncs may look different on each client. Also they my use the OneDrive App. This App substitutes the Web Browser, is quick, and the password credentials may stored inside the app.This app do not sore data locally, you need an internet connection. (I use this app to share a document, because it’s quicker)

Where should I store the documents?

My Business documents belong to OneDrive for Business. If more people come together, f.e talking about new ideas and store documents, you may use Groups. So Groups are dynamic. Inside a Group you do not have to share a document to another group member. So for Standard processes and their documents you should save the documents inside a document library of a Team site.

At this time, I write this blog post, you may Copy a document to another area. In the near future you will also have a Move function in the Web Browser.

For all this Sync possibilities you need to install the Preview Version of the Next Generation Sync Client with the Version 17.3.6673.1011.


NGSC (German language only)
Next Generation Sync Client – Was ist das ?

Next Generation Sync Client – new Preview Version available

Sync to all different areas in Office 365
Next Generation Sync Client | Sync to all doc libraries in Office 365

Naming convention in  Windows Explorer
Naming Convention in Explorer with the Next Generation Sync Client

OneDrive Group policies for Companies
OneDrive – Next Generation Sync Client |Group Policies

Sharing Teilen
Freigaben in OneDrive for Business | externe Benutzer

OneDrive App
OneDrive Universal App for Windows 10 available | a short test

Call That Girl’s Office 365 Show for Technicians Only | Show 68

23. Oktober 2016 Hinterlasse einen Kommentar

OneDrive, Podcast, Yammer, Groups, OneDrive for Business, Next Generatiun Sync Client, Call That Girl's Office 365 Show

Weekend? Relaxing? Not for Lisa and me.  Today I was a guest in Lisa’s

Call that Girls Office 365 Show

and we have talked about OneDrive,Yammer and Support.
If you have 92 Minutes free of time, click, download and hear Show 68

Thanks Lisa.

Naming Convention in Explorer with the Next Generation Sync Client

12. Oktober 2016 10 Kommentare

Syncing to OneDrive, OneDrive for Business, team sites, groups and Shared with me data with the Next Generation Sync Client

If you use the Preview Version of the Next Generation Sync Client, you also should be familiar with the Naming Convention in the Windows Explorer. All pictures are made with the Preview Version 17.3.6642.0922 of the NGSC. (If you want to install this version, read here)

But you must note, that all changes, you will do in Office 365, like renaming the tenant name or team sites or Groups do not reflect in the Windows Explorer. Microsoft needs to improve. But as mentioned, it’s a preview.

Keep in mind:

OneDrive (Personal) is represented in the notification area with a white cloud symbol, all other (OneDrive for Business, Teamsites, Groups and Shared with Me) are represented with a blue cloud symbol. Many of you will only see two cloud symbols. And if you sync data with the old Groove client, you will have another blue cloud symbol. There is an easy way to look, which cloud symbol belongs to which sync client. You may read here.

With the the Next Generation Sync Client you may sync files with one(!) OneDrive (Personal), but also with data from an Office 365 tenant. Additional you may, if the admins allow that, sync data to other tenants. So for each tenant you will have at least one blue cloud symbol.

So lets go into deep for the naming convention:


This is for all synced data with OneDrive for Business

With OneDrive (Personal) the tenant name is replaced with the word “Personal”

Tenant-Name if you have only the tenant name you see inside all synced data form team sites, Groups and data “Shared with me

the next picture will show an example:

Two Tenants and one OneDrive (Personal) 1) OneDrive (Personal)

2) OneDrive for Business Tenant Hbsoft

3) OneDrive for Business Tenant BitTitan

4) Team-Sites, Groups und Shared with me data form the Tenant Hbsoft

If you drill down number 4…

Teamsites, Groups and Shared with Me synced data folder structure at this time, you do not see, where the data comes from.

Finance: Team-Website

Group Marketing: Group
(I have given this group name “Group Marketing” during the creating process, but normally users will not do that!)

Julian Versuch… : Shared with me synced data (from User Julian Versuch)

Marketing I: Team Website


If you change f.e. the Name of a group or a Team-Website, there is no reflection in the Explorer. As an workaround you have to “unlink this PC” or “End of Sync” , delete the data on your local machine and start the sync process again. And I know, that’s not a practical solution, if you have a lot of data. But let’s give Microsoft a change until the global availability of the final version.

Microsoft Synchronization – Roadmap (NGSC, ODFB)

21. März 2016 7 Kommentare

OneDrive for Business, Microsoft

This article is about synchronization. Synchronization between the client and SharePoint Team sites and One Drive for Business. And the Microsoft Roadmap.

Yes, there are some news. To get to the point: It will take a while.

Microsoft has to be accused. There is not only one way to communicate with partners and customers. Although there is a site with a Roadmap for Office 365, where you may show all new and released components of Office 365, but also a Blog about OneDrive. So if you look about news about the OneDrive Blog, you do not find News about new releases nor a roadmap about OneDrive (for Business) and the Next Generation Sync Client (NGSC). The last news about the roadmap was published on the Microsoft Virtual Academy. Reuben Krippner, Microsoft Director Product Management. You may also be able to download the slides, but the roadmap slide looks different.

Here is a screenshot out of the Video of Microsoft Virtual Academy:

Microsoft Roadmap , ODFB, NGSC, Next Generation Sync Client

The roadmap shows functions in three sections, First quarter 2016, second quarter 2016 and the future, where the developer and engineers are working, but not with an exact timeline.

1st Quarter 2016
for the User

  • Outlook Mobile iOS integration
  • PDF annotation support for Android
  • Drive discovery and recent files view in browser client
  • Windows 8.1 support for Next-Gen Sync
  • Streamlined Microsoft Account creation

for the IT

  • Outlook Mobile iOS integration
  • PDF annotation support for Android
  • Drive discovery and recent files view in browser client
  • Windows 8.1 support for Next-Gen Sync
  • Streamlined Microsoft Account creation

2nd Quarter 2016

for the User

  • iOS access to SharePoint Online files
  • Self-service NGSC (Next Generation Sync Client) setup and groove.exe takeover
  • Pause Sync
  • Curate the "Share with Me" view

for the IT

  • iOS access to SharePoint Online files
  • Self-service NGSC (Next Generation Sync Client) setup and groove.exe takeover
  • Pause Sync
  • Curate the "Share with Me" view

Committed (without any time lines)

for the User

  • Sync of shared folders
  • Sync of SharePoint document libraries
  • Notifications
  • SharePoint on-prem support for iOS
  • Android access to SharePoint Online files"Shared by Me" view

for IT

  • Sync of shared folders
  • Sync of SharePoint document libraries
  • Notifications
  • SharePoint on-prem support for iOS

I do not want to go into detail, but I want to draw attention, that Microsoft has some fundamental problems, and not just today, but more than a year. The issue with Prioritizing, what customers want.

Development of an easy to use, error free Sync client to

  • Synch to OneDrive Personal
  • Synch to OneDrive for Business
  • Synch to SharePoint Team Sites
  • Synch to Documents in Groups

this chronological order is not chosen arbitrarily. Microsoft has done so. We have seen such things first in February 2015, where both developer teams come together with one management. But the first error was made my Microsoft Marketing. From the first day Microsoft have spoken only form “OneDrive”. The have not done (and don’t  do it  till today) spoken about OneDrive Personal and OneDrive for Business. And the normal User does not know the difference and unsettled until today. At first, the GUI of OneDrive  (Personal) was better. But not all people have the technical overview, that OneDrive (Personal) data is stored in Azure files, there is no Active directory, no SharePoint Limits. For customers with SharePoint, and I do not speak about on Premise versions, it is more difficult. SharePoint Online has a few limits, they have to be eliminated.

So different Microsoft developers have to do the code changes and at then Microsoft announced at Ignite in May 2015  the Next Generation Sync Client. And it was easier to develop a sync client for OneDrive (Personal), but the customers have to wait until October 2015. This new client was released with a Preview Version and finally arrive at the customers at December 2015. All Windows 10 Users with an OneDrive (Personal) account sync since the release of Windows 10 with the NGSC . And with the same sync client, you are now able to sync to their OneDrive for Business account. That also works for Users with Windows 7,8.0 but not for users with the OS Windows 8.1

The major difference with between the old “Groove” sync engine and the NGSC is, that you may select, which folder you may sync to your local device. If you sync with the old “Groove”, you only have the choice: All or nothing

So this time it looks like:

Next Generation Sync Client: destinations

The NGSC allows the administrators, via GPO and Register Keys automatically connect the different Users client devices directly with their OneDrive for Business. That’s is not only a wish, that’s really important for companies.

Microsoft announced more storage for SharePoint Team Sites, but this makes no sense, because for this kind of Synchronization you still need the old Groove-Client. And again: This Client has errors, is limited to sync max. 20000 items… And: All or nothing

But back to the Beginning of my Blog Post: The Roadmap

  • NGSC also for Windows 8.1

Microsoft has left over 11 days of time, then this Update should also released, So after these days, I would prevent to ask the people on Sync questions on social media like Yammer, Facebook or LinkedIn: Which Operating System do you use?

The Microsoft Roadmap says, in the second quarter they will release a Setup, that the users Groove Data will convert to NGSC data. Three months? (Do they have only 5 developers left?)

And at what time we may connect via NGSC to SharePoint Team Sites and Groups?

There is no answer about dates in the roadmap, Microsoft delivers.
So only: “we are working on that.”

So this stops several projects and also some users are frustrated. To sync their data, they have to install the old Groove-Client and the NGSC parallel. With all known and unknown errors.


Microsoft is not able to have this NGSC available within one year. Microsoft also do not know, when this will be done by date. And I think, the prioritization of all components was in the wrong order.

  • Admins of companies despair on “unknown” and wrong errors of the groove.exe
  • Companies want first ONE sync client, which syncs to all destinations
  • All destinations: SharePoint Online and SharePoint on premise
  • All other functions, like Shared Files, notifications,… must wait.

    articles in English language to Next Generation Sync clients
    articles in English language to OneDrive for Business

            Mary Foley has written a notice at 3/872016, but there was no rebellion from the market. Do the companies come to terms with?

            So in the old school days we have said: Good idea, poor execution

      Microsoft Synchronisations – Roadmap (NGSC, ODFB)

      19. März 2016 3 Kommentare

      OneDrive for Business, Microsoft

      Hier geht’s um Synchronisierung. Synchronisierung vom Client zu SharePoint Team Sites und zu OneDrive for Business. und einer Roadmap

      Ja, da gibt es schon was Neues. Um es vorweg zu nehmen. Es wird noch eine Weile dauern.

      Eins muss sich Microsoft vorwerfen lassen: Die unermüdliche Art, auf den unterschiedlichen Kommunikationswegen mit seinen Partnern und Kunden zu kommunizieren. Es gibt zwar für Office 365 eine Seite, wo man sich durch die Roadmap der unterschiedlichen Komponenten von Office 365 durchklicken kann, die aber nur in englischer Sprache. Dann gibt es Blogs. Und in der Vergangenheit war es üblich, dass auf den Blogs Neuigkeiten angekündigt wurden. Zum Thema Synchronisierung gibt es jedoch keine einheitliche Stelle. Mal hier, mal da. Auf dem Blog, von wegen. Die letzten Neuerungen wurden am 24.2.2016 über die Microsoft Virtual Academy  verbreitet. Ein Link im offiziellen Microsoft OneDrive Blog fehlt. Wiederum interessant ist die Tatsache, dass die von Reuben Krippner, Microsoft Director Product Management gezeigten Neuerungen und die Roadmap nicht mit der PowerPoint, die man sich ebenfalls herunterladen kann, übereinstimmt.

      Hier ein Screenshot aus dem Video der Microsoft Virtual Academy


      Die Roadmap beschreibt Funktionen in drei Abschnitten, 1. Quartal 2016, 2. Quartal 2016 und woran die Entwickler arbeiten, aber noch kein exakter Zeitpunkt ausgegeben wurde

      1. Quartal 2016

      Für den Benutzer

      • Outlook Mobile iOS integration
      • PDF annotation support for Android
      • Drive discovery and recent files view in browser client
      • Windows 8.1 support for Next-Gen Sync
      • Streamlined Microsoft Account creation
        Für IT
      • Outlook Mobile iOS integration
      • PDF annotation support for Android
      • Drive discovery and recent files view in browser client
      • Windows 8.1 support for Next-Gen Sync
      • Streamlined Microsoft Account creation

        2. Quartal 2016
        Für den Benutzer
      • iOS access to SharePoint Online files
      • Self-service NGSC (Next Generation Sync Client) setup and groove.exe takeover
      • Pause Sync
      • Curate the "Share with Me" view
        Für IT
      • iOS access to SharePoint Online files
      • Self-service NGSC (Next Generation Sync Client) setup and groove.exe takeover
      • Pause Sync
      • Curate the "Share with Me" view

        Commited (ohne Zeiten)
        Für den Benutzer
      • Sync of shared folders
      • Sync of SharePoint document libraries
      • Notifications
      • SharePoint on-prem support for iOS
      • Android access to SharePoint Online files"Shared by Me" view
        Für IT
      • Sync of shared folders
      • Sync of SharePoint document libraries
      • Notifications
      • SharePoint on-prem support for iOS

      Ich möchte hier nicht auf die einzelnen Einträge eingehen, sondern hier einmal beschreiben, dass Microsoft hier ein grundsätzliches Problem hat, und das nicht erst heute, sondern schon über ein Jahr. Die Priorisierung, was die Kunden wünschen.

      • Entwicklung eines einfachen, fehlerfreien Synchronisierungs-Dienstes
        • Synchronisierung zu OneDrive Personal
        • Synchronisierung zu OneDrive for Business
        • Synchronisierung zu SharePoint Team Sites
        • Synchronisierung zu Dokumenten in Groups

      Die Reihenfolge ist nicht willkürlich gewählt. Denn genau so hat das Microsoft auch getan. Dien Anzeichen dazu wurden bereits im Februar 2015 hat man beide Entwicklungsteams zusammengebracht. Der grundsätzliche Fehler wurde durch die Microsoft Marketing-Abteilung hervorgerufen. Bei Microsoft spricht man schon immer von OneDrive. Nicht von OneDrive (Personal) und OneDrive for Business. Die Benutzer wurden und werden bis heute verunsichert. Zum damaligen Zeitpunkt war die Oberfläche von OneDrive (Personal) wesentlich besser. Der Hintergrund ist aber einfach zu beschreiben. Kein Active Directory, Kein SharePoint, Daten werden in Azure Files gespeichert. Für die SharePoint Kunden, und ich gehe hier nicht auf die On Premise Kunden ein, ist das ganze wesentlich komplizierter. SharePoint hat ein paar Einschränkungen, die erst einmal eliminiert werden mussten.

      Während also die Entwickler sich mit all diesen Unterschieden herumschlagen mussten, wurde der Next Generation Sync Client angekündigt (Ignite Mai 2015). Und weil es einfacher ist, eine Synchronisation für OneDrive (Personal) zu bauen, mussten die Kunden warten. Warten bis Oktober 2015. Dort wurden dann eine Preview angekündigt. Im Dezember 2015 wurde dann der NGSC für OneDrive for Business veröffentlicht.  Während Millionen Windows 10 schon mit NGSC Daten gegenüber OneDrive Personal synchronisierten, gab es jetzt erst einmal die Möglichkeit, “meine Business Dokumente”  in OneDrive for Business zu synchronisieren. Nicht jedoch für das Betriebssystem Windows 8.1

        Der wesentliche Unterschied zwischen dem alten Groove Client und NGSC ist der, dass ich mit NGSC selektieren kann, was ich synchronisieren möchte. Beim Groove Client gilt, alles oder gar nichts.
        Also haben wir nach einem Jahr folgenden Zustand:

      Next Generation Sync Client, Destination, Ziele

        Der NGSC erlaubt es den Administratoren endlich, via GPO und Register Keys die verschiedenen Clients direkt mit OneDrive for Business zu verbinden. Das war nicht nur der Wunsch, sondern dies ist eine zwingende Voraussetzung für Firmen.

        SharePoint Team Sites wurden von Microsoft mit mehr Speicher versorgt, was aber nichts bringt, weil wir für deren Synchronisation zu lokalen Geräten immer noch den alten Groove-Client verwenden müssen. Und nochmal, der Client ist fehleranfällig, limitiert auf 20000 Einträge,… und entweder alles oder Nichts.

        Kehren wir zum Angang dieses Blog-Artikels zurück. Die Roadmap…

        • NGSC auch für Windows 8.1

        Microsoft bleibt noch knappe 14 Tage, dann sollte dieses Update verfügbar sein. Damit fällt für mich bei Fragen in sozialen Netzwerken wie Yammer, Facebook, Twitter, Linkdin und auch direkt per Mail zur Synchronisation eine Rückfrage weg: welches Betriebssystem setzten Sie derzeit ein?

        Im zweiten Quartal wird dann an einem Setup gearbeitet, damit Groove Daten übernommen werden können. 3 Monate ? (sind da nur 5 Programmierer beschäftigt?)

        Und wann endlich kann ich den NGSC verwenden um Daten aus SharePoint Team Sites und Groups zu synchronisieren?

        Eine Antwort liefert Microsoft nicht. Keine Zeitlinie, Es steht noch nicht einmal auf der Roadmap. “Wir arbeiten daran.”

        Das führt derzeit bei Benutzern zu kuriosen Zuständen. Um Daten zu synchronisieren, müssen der alte und der neue Synchronisierungs-Client parallel installiert werden. Mit den bekannten und unbekannten Fehlern.



        Microsoft hat es in einem Jahr nicht geschafft, NGSC fertig zu stellen. Microsoft kann derzeit nicht einmal einen Zeitpunkt nennen, wenn es denn soweit sein wird. Die Priorisierung einzelner Komponenten im letzten Jahr war völlig falsch angelegt.

        • Administratoren verzweifeln an den “nicht vorhandenen Fehlern” von Groove.exe
        • Firmen wollen erst einmal einen NGSC, der zu allen Zielen funktioniert.
        • alle Ziele: SharePoint Online und SharePoint OnPremise
        • Alle weiteren Funktionen, wie Shared Files, Benachrichtigungen, etc. können warten

        deutsche Artikel zu Next Generation Sync Client
        deutsche Artikel zu OneDrive for Business



        Ein Blog ist ein Tagebuch. Man schreibt, wenn es etwas neues gibt. Und wenn man Zeit hat. Und genau an letzterem hapert es derzeit bei mir. Der Tag hat ja wie jeder weiß, nur 25 Stunden. Das aber auch nur, wenn man während der Mittagspause durcharbeitet. Bei diesem Artikel habe ich aber nicht nur keine Zeit gehabt, sondern sehen wollen, wie groß der Aufschrei der Netzgemeinde ist, als Mary Foley am 8.3.2016 eine kurze Beschreibung dieser Roadmap in englischer Sprache veröffentlicht hat.

        Ich werde täglich um Hilfe gebeten. Per Mail oder über Soziale Netzwerke. Und manche meiner MVP Kollegen haben sich längst von OneDrive und Co. abgewendet und benutzen andere Dienste. Firmen, die die Möglichkeit, mit mehreren Kollegen an einem Dokument zu arbeiten, schätzen gelernt haben, werden jedoch zunehmend frustrierter. Das fängt beim Benutzer an, und hört nicht beim Administrator oder Helpdesk auf.

        In der Schule hätte man früher gesagt.

        Idee gut, Ausführung mangelhaft

        %d Bloggern gefällt das: