Archiv
Next Generation Sync Client | Sync now with # and % in filename
 |
 |
A few days ago, Microsoft announced a new feature for OneDrive for Business and SharePoint Online. The user may now sync data with “#” and “%” in the files- or folder name. Perfect for the users, but wait: The admin has to switch this feature on, and there is no switch in the admin console.
I have had about 120.000 files synced to the cloud into different Office 365 areas: SharePoint Team sites, Groups and OneDrive for Business. And there were some documents, where the Next Generation Sync Client gives out an error message and I have to change that manually (There were old documents about the language C # in the filename…)
Many user do not understand this. Yes, we know from past: here were many characters, that may not used in file and folder names. And Microsoft has promised, that the last 2 characters will be removed in the first quarter of 2017. And now it’s ready.
Requirements
All things, that followed, has nothing to do with all OnPremise versions of SharePoint and the old Groove client respectively. If you are a frequent reader of my blog posts, you know, that the Next Generation Sync Client (NGSC) will work only with Office 365 and OneDrive Personal.
| Storage | Omission of “#” und “%” |
| SharePoint Server on Prem | NO |
| OneDrive for Business on Prem | NO |
| SharePoint Online Libraries in Team Sites und Groups |
YES |
| OneDrive for Business | YES |
When is this feature available?
No, because there is no switch for the admin; the adminstrator has to deal with PowerShell. For all Office 365 tenants, that will be established after June 2017, this function is set automatically.
So the cmd-lets for Showing / Changing is: Get-SPOTenant / Set-SPOTenant
and the parameter for changing are: SpecialCharactersStateInFileFolderName
There are three different values:
| Value | description |
| Allowed | Allows # and % characters in file and folder names in SharePoint Online and OneDrive for Business document libraries. |
| Disallowed | Disallows the # and % characters in file and folder names in SharePoint Online and OneDrive for Business document libraries. |
| NoPreference | # and % support will be enabled by Microsoft on your Office 365 Tenant when available. NoPreference state is the default state before we enable # and % on behalf of Office 365 Tenants following the schedule mentioned previously. In this state, # and % are turned off and tenant admins can run Set command to switch it to either Allowed or Disallowed. Once it is set by tenant admins, Microsoft will not change the setting when we enable on # and % on behalf of Office 365 Tenants. In addition, this is a read-only state, so it can not be set by running the Set command. |
Before we use PowerShell to connect with SharePoint Online you must ensure, that the SharePoint Online Management Shell is installed. You may download it from this Microsoft site. Even you have it installed, look for the latest version. Start the Powershell online Management Shell, or you use Windows Powershell ISE.
Bevor wir uns per Power Shell mit SharePoint Online ver
Even if you are not use PowerShell each day, I will describe the few steps.
| Picture | descriptions |
 |
Login into Office 365 as a SharePoint Administrator or a Global Teanat admionistrator and switch to the SharePoint Admin Center
We need the part with the tenant name from the URL. Here |
Now a few lines of PowerShell code:
$TenantURL="https://mvpt01-admin.sharepoint.com"
$SharePointAdmin="Hans.Brender@mvpt01.onmicrosoft.com"
Connect-SPOService -Url $TenantURL -credential $SharePointAdmin
Get-SPOTenant
So the first line shows the assign of SharePoint URL, in the second Line the assignment of your SharePoint Administrator or your Global Tenant administrator. In the third line we use the function Connext-SPOService to connect to the Tenant, a popup window will open and ask for the admin’s credential. The last line we call the function Get_SpoTenant and then we get:
after the first Call you see the value NoPreference for SpecialCharactersStateInFileFolderNames
With Get-SPOTenant you read the data, with Set_SPOTenant you could write or change the data. To Allow # and % as a valid character in a file- or folder name, you have to write:Set-SPOTenant -SpecialCharactersStateInFileFolderNames Allowed
to Disallow:
Set-SPOTenant -SpecialCharactersStateInFileFolderNames Disallowed
To Disconnect from you teanant you write Disconnect-SPOService ein.
Important: If you have changed the value, it takes a while, until the changes are affected!
Keep in mind , the changes are for Files /and or folders, not for SharePoint sites (web objects) or Site collections. Developers should also read for API changes
Summarize:
There are only a few lines of code, but then administrators of companies will have less work with their users, because they do not understand, why there is a problem. Unfortunately is code only works in Office 365 and not on Premise
Users with a NAS like Synology will get into trouble, if you switch and have data in OneDrive for Buisness with these characters. The reason is, that they will use the old API
Who knows SaRA?
Microsoft Support and Recovery Assistant for Office 365 with version 16.00.1702.0000 also do not know theses characters, but Microsoft has confirmed me, that this will be changed in the near future.
Source and Original: Microsoft Tech Community
Bill Baer describes the original and also has changed his FileChecker Migration Assistant
Next Generation Sync Client | Jetzt auch # und % im Dateinamen
|
|
Nur ein paar Tage über der ursprünglichen Ankündigung hat Microsoft ein weiteres Feature für OneDrive for Business und SharePoint Online angekündigt. Der Benutzer wird jetzt auch Dateien mit “#” und “%” im Dateinamen synchronisieren können. Noch ist es nicht soweit. Und der der SharePoint-Online Admin wird das auch explizit freischalten müssen. Noch ist es aber nicht soweit
Vor kurzem habe ich über 120.000 Dateien in die Cloud synchronisiert. Dabei sind auch ein paar Dokumente dabei gewesen, welche die noch unzulässige Zeichen enthielten. Dann gibt es eine Fehlermeldung und der Benutzer muss manuell eingreifen. (Bei mir waren das alte Dokumente, als C# als Programmiersprache etabliert wurde)
Das ist für viele Benutzer nicht nachvollziehbar. Und Microsoft wollte das im ersten Quartal 2017 bereinigen. Mit ein paar Tagen Verzögerung ist es jetzt implementiert.
Voraussetzungen:
Dies gilt nur für den Next Generation Sync Client, der alte “Groove Client” wird nicht unterstützt. Wer regelmäßig meine Blog Posts liest, weiß, das der Next Generation Sync Client “derzeit” nur mit Office 365 und OneDrive Personal (also in der Cloud) funktioniert.
| Speicherort | Wegfall von “#” und “%” |
| SharePoint Server on Prem | NEIN |
| OneDrive for Business on Prem | NEIN |
| SharePoint Online Bibliotheken in Team Sites und Groups |
JA |
| OneDrive for Business | JA |
Ist dieses Feature sofort verfügbar?
Nein, denn, und das werde ich noch beschreiben, der Administrator muss dazu selbst Hand anlegen. Und das nicht über die Web-Oberfläche, nein PowerShell ist angesagt. Für alle Office 365 Mieter, die ab dem Juni 2017 erstellt werden, ist diese Funktion dann automatisch eingestellt.
Das Kommando für die Anzeige / das Ändern lautet: Get-SPOTenant / Set-SPOTenant
der dazugehörige Parameter: SpecialCharactersStateInFileFolderName
Der Wert kann dabei 3 Eigenschaften einnehmen
| Wert | Beschreibung |
| Allowed | Erlaubt # und % Zeichen im Datei- und Ordnernamen in SharePoint Online und OneDrive for Business Dokumenten Bibliotheken |
| Disallowed | # und % Zeichen im Datei- und Ordnernamen in SharePoint Online und OneDrive for Business Dokumenten Bibliotheken werden nicht unterstützt. |
| NoPreference | Das ist die Default Einstellung. Die Unterstützung von # und % Zeichen im Datei- und Ordnernamen wird durch Microsoft unterstützt. Dies geschieht nach und nach bei den unterschiedlichen Mietern. War der Zustand bis zur Unterstützung bereits in einem anderen Zustand, wird dieser nicht überschrieben. Diese Eigenschaft ist Read-Only, man kann Sie , wenn einmal geändert, nicht wieder setzen. |
Bevor wir uns per Power Shell mit SharePoint Online verbinden, muss sichergestellt sein, dass die SharePoint Online-Verwaltungsshell installiert haben. Diese können Sie hier herunterladen. Auch wer die SharePoint Online-Verwaltungsshell bereits auf seinem Rechner installiert hat, sollte diese auf die neuste Version updaten. Starten Sie SharePoint Online Management Shell oder aber Windows PowerShell ISE.
Nicht jeder benutzt PowerShell jeden Tag. Deshalb werde ich die einzelnen Schritte hier beschreiben.
| Bild | Beschreibung |
 |
Melden Sie sich im Browser als SharePoint Administrator oder globaler Administrator an und wechseln Sie dort in das SharePoint Admin Center
wir benötigen den Part mit dem Mieter-Namen: hier |
hier jetzt die paar Zeilen PowerShell Code:
$TenantURL="https://mvpt01-admin.sharepoint.com"
$SharePointAdmin="Hans.Brender@mvpt01.onmicrosoft.com"
Connect-SPOService -Url $TenantURL -credential $SharePointAdmin
Get-SPOTenant
In der ersten Zeile wird der Variablen $TenantURL Ihre SharePoint Verwaltung zugewiesen. Zeile 2 ist der Anmeldename des SharePoint Administrators oder des globalen Administrators. In der dritten Zeile werden diese Variablen dem Connect-SPOService zugewiesen, ein Fenster öffnet sich und Sie müssen Sich mit dem SharePoint-Administrator authentifizieren. Das ist die Anmeldung. Die letzte Zeile ruft Get-SPOTenant auf und hier erhalten Sie das Ergebnis
beim ersten Aufruf steht bei SpecialCharactersStateInFileFolderNames natürlich NoPreference
Wenn Get-SPOTenant für das Auslesen zuständig ist, kann mit Set-SPOTenant etwas geschrieben werden. Wenn wir also # und % als Zeichen in einem Datei- oder Ordnernamen erlauben wollen so lautet das Kommando
Set-SPOTenant -SpecialCharactersStateInFileFolderNames Allowed
das Verbieten:
Set-SPOTenant -SpecialCharactersStateInFileFolderNames Disallowed
Um sich wieder abzumelden geben Sie Disconnect-SPOService ein.
Wir der Wert mittels PowerShell geändert, so dauert dies eine geraume Weile, bis das Kommando wirkt!
Die Funktion bezieht sich auf Dateinamen und Ordner, nicht jedoch auf SharePoint Sites (Web objects) und Site Collections
Für alle Entwickler: Man sollte sich die API Änderungen anschauen
Zusammenfassung:
ein paar Zeilen Code und schon haben Administratoren weniger Arbeit mit Benutzern, die sich schon oft gefragt haben, warum hier ein Problem vorliegt. Leider bisher nur in der Cloud verfügbar.
[12.04.17 Nachtrag] wer eine NAS wie Synology benutzt, wird Probleme bekommen, wenn er Daten aus OneDrive for Business sichert, den derzeit benutzt die NAS noch die nicht erweiterte API.
[13.04.17 Nachtrag] Kenn jemand SaRA?
Microsoft Support and Recovery Assistant for Office 365 in der Version 16.00.1702.0000 kennt die unzulässigen Zeichen noch nicht. Dieses, nennen wir es einmal Microsoft Universal Fehlerbereinigungstool wird aber fortlaufend erweitert, wir mir gestern Microsoft mitgeteilt hat.
Quelle: Microsoft Tech Community
Next Generation Sync Client | Registry key vs Admin-Center
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
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
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
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
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
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.
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
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
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 collaboration.com 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.
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.
Summary:
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
The administrator of the company Collaboration.com creates the first Team Site. This Site is for the finance department.
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
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.
Summary:
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.
Groups
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.
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.
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.
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.
Summary:
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
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.
Note:
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.
Links:
NGSC (German language only)
Next Generation Sync Client – Was ist das ?
Installation
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
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
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:
| OneDrive – Tenant-Name | 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:
 |
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…
 |
at this time, you do not see, where the data comes from.
Finance: Team-Website Julian Versuch… : Shared with me synced data (from User Julian Versuch) Marketing I: Team Website |
Conclusion
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.
