Home

My compliments to One Drive for Business Next Generation Sync Client (ODFB NGSC) development team.

%3CLINGO-SUB%20id%3D%22lingo-sub-22238%22%20slang%3D%22en-US%22%3EMy%20compliments%20to%20One%20Drive%20for%20Business%20Next%20Generation%20Sync%20Client%20(ODFB%20NGSC)%20development%20team.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-22238%22%20slang%3D%22en-US%22%3E%3CP%3EI%E2%80%99m%20not%20an%20early%20adopter%2C%20and%20held%20off%20implementing%20NGSC%20for%20ODFB%20for%20a%20long%20time.%20I%20finally%20decided%20to%20try%20V%202016%20(Build%2017.3.6517.0809)%20two%20weeks%20ago%2C%20and%20the%20deployment%20and%20daily%20operation%20have%20been%20smooth%20as%20silk.%20This%20isn%E2%80%99t%20the%20preview%20version%20that%20syncs%20Team%20Sites.%20Again%2C%20I%E2%80%99m%20not%20an%20early%20adopter.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%E2%80%99s%20an%20excellent%20dynamic%20response%20diagnostic%20that%20pops-up%20messages%20when%20the%20sync%20client%20chokes%20on%20files%20that%20have%20unacceptable%20characters%20in%20their%20names%2C%20or%20too%20long%20folder%20nest%2Ffile%20names.%20Since%20my%20Tenant%20Name%20is%20long%2C%20I%20was%20particularly%20concerned%20about%20the%20latter.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20diagnostic%20messages%20pop-up%20and%20tell%20you%20exactly%20where%20the%20problem%20is%2C%20and%20you%20can%20click%20on%20a%20link%20to%20take%20you%20to%20the%20offending%20file.%20It%20even%20tells%20you%20exactly%20how%20many%20characters%20to%20remove%20from%20the%20folder%20nest%2Ffile%20name%20to%20resolve%20a%20length%20error.%20While%20these%20pop-ups%20are%20waiting%20for%20you%20to%20correct%20the%20error%2C%20the%20sync%20continues%20with%20other%20folders.%20After%20you%20correct%20an%20error%2C%20the%20diagnostic%20detects%20the%20correction%20and%20automatically%20dismisses%20itself%20or%20shortens%20the%20pop-up%20list%20by%20removing%20the%20corrected%20file%20(that%E2%80%99s%20why%20I%20refer%20to%20it%20as%20%E2%80%9Cdynamic%20response%E2%80%9D).%20If%20it%20finds%20another%20error%2C%20it%20pops-up%20another%20notification%20or%20expands%20the%20current%20list.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESelective%20folder-sync%20is%20fantastic%2C%20and%20solves%20many%20problems%20that%20previously%20existed%20with%20large%20libraries%20in%20the%20cloud%20that%20had%20to%20sync%20with%20thin%20clients%20in%20the%20field.%20Even%20if%20your%20mobile%20device%20isn%E2%80%99t%20thin%2C%20why%20carry%20around%20folders%20you%20don%E2%80%99t%20need%20and%20subject%20them%20to%20exposure%20if%20you%20lose%20your%20device%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENGSC%20eliminated%20my%20concern%20that%20%E2%80%9COpen%20with%20Explorer%E2%80%9D%20is%20going%20away%20in%20the%20modern%20UI%2C%20because%20syncing%20is%20so%20fast%20and%20smooth.%20Anything%20I%20want%20to%20do%20with%20Windows%20Explorer%2C%20I%20can%20do%20with%20my%20local%20ODFB%20folder.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%E2%80%99m%20speculating%2C%20but%20it%20seems%20like%20the%20client%20and%20its%20server%20counterpart%20use%20some%20type%20of%20extremely%20efficient%20compression%20algorithm%2C%20along%20with%20a%20quick%20wake-up%20call%20when%20it%E2%80%99s%20time%20to%20take%20some%20sync%20action.%20My%20initial%20sync%20of%2032%2C000%20files%20took%20about%2075%25%20less%20time%20than%20I%20expected%2C%20given%20my%20available%20bandwidth.%20Day-to-day%20sync%20operations%20are%20much%20snappier%20than%20Groove.%20Using%20selective-sync%2C%20as%20long%20as%20I%20remember%20to%20put%20a%20checkmark%20next%20to%20the%20folders%20I%E2%80%99ll%20need%20tomorrow%2C%20and%20uncheck%20the%20ones%20I%20won%E2%80%99t%2C%20my%20thin%20mobile%20clients%20are%20ready%20to%20go%20much%20faster%20than%20I%20anticipated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%20opinion%2C%20NGSC%20is%20ready%20for%20primetime%20use%20with%20ODFB%2C%20and%20the%20MSFT%20developers%20deserve%20kudos.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-22238%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOneDrive%20for%20Business%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESync%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-22349%22%20slang%3D%22en-US%22%3ERe%3A%20My%20compliments%20to%20One%20Drive%20for%20Business%20Next%20Generation%20Sync%20Client%20(ODFB%20NGSC)%20development%20tea%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-22349%22%20slang%3D%22en-US%22%3EGreat%20feedback%20and%20very%20detailed%20explanation%20about%20your%20experience%20with%20NGSC!!%3C%2FLINGO-BODY%3E
Highlighted
Steven Seligman
Contributor

I’m not an early adopter, and held off implementing NGSC for ODFB for a long time. I finally decided to try V 2016 (Build 17.3.6517.0809) two weeks ago, and the deployment and daily operation have been smooth as silk. This isn’t the preview version that syncs Team Sites. Again, I’m not an early adopter.

 

There’s an excellent dynamic response diagnostic that pops-up messages when the sync client chokes on files that have unacceptable characters in their names, or too long folder nest/file names. Since my Tenant Name is long, I was particularly concerned about the latter.

 

The diagnostic messages pop-up and tell you exactly where the problem is, and you can click on a link to take you to the offending file. It even tells you exactly how many characters to remove from the folder nest/file name to resolve a length error. While these pop-ups are waiting for you to correct the error, the sync continues with other folders. After you correct an error, the diagnostic detects the correction and automatically dismisses itself or shortens the pop-up list by removing the corrected file (that’s why I refer to it as “dynamic response”). If it finds another error, it pops-up another notification or expands the current list.

 

Selective folder-sync is fantastic, and solves many problems that previously existed with large libraries in the cloud that had to sync with thin clients in the field. Even if your mobile device isn’t thin, why carry around folders you don’t need and subject them to exposure if you lose your device?

 

NGSC eliminated my concern that “Open with Explorer” is going away in the modern UI, because syncing is so fast and smooth. Anything I want to do with Windows Explorer, I can do with my local ODFB folder.

 

I’m speculating, but it seems like the client and its server counterpart use some type of extremely efficient compression algorithm, along with a quick wake-up call when it’s time to take some sync action. My initial sync of 32,000 files took about 75% less time than I expected, given my available bandwidth. Day-to-day sync operations are much snappier than Groove. Using selective-sync, as long as I remember to put a checkmark next to the folders I’ll need tomorrow, and uncheck the ones I won’t, my thin mobile clients are ready to go much faster than I anticipated.

 

In my opinion, NGSC is ready for primetime use with ODFB, and the MSFT developers deserve kudos.

1 Reply
Great feedback and very detailed explanation about your experience with NGSC!!
Related Conversations