Browsed by
Month: August 2015

Turning off Telemetry for Office 2013

Turning off Telemetry for Office 2013

There have been several articles about privacy issues with Windows 10 and by extent Office. Microsoft does a pretty decent job explaining what it collects (at least for office) and how to disable it on this article:

I condensed the registry commands into a single file which you can download here: TurnOffTelemtry
Simply rename the .txt file to .reg and off you go. Or if you’d rather create your own file you can do so by copying and pasting these commands into a new file in notepad that could be saved as a .reg file of your choice.


SharePoint Online Cloud High Speed Migration Test Summary

SharePoint Online Cloud High Speed Migration Test Summary

Thanks to Mikael Svenson for the helping generate data for these tests and providing feedback.

Over the last couple months  I have been testing and experimenting with the new SharePoint Import Service provided by the Office 365 team. It is interesting to see where the investment dollars are going in the SharePoint team these days. Once I saw that the beta was opened to the public, I jumped at the chance to test it. It was a bit slow going at first however now that they’re sharing more information on technet and on yammer, it should be easy to find resources necessary to support migration activities. Long story short, the service is much faster than migration capabilities functioning in a client context, creating a new highway directly SharePoint Online and below you can find a table describing the tests that occurred. Please note that your results will vary based on your region/region of your azure accounts, network speeds, lunar cycle, and the hamsters powering your computer, so take them with a very big grain of salt. Without further ado, the results!

Test NameTest TypeData SizeData CompositionObserved TimeObserved Speed GB/HRObserved Speed per TBNotes
Large File Test (Test 1)Serial294 GB Large Video Files and Small Power Points1 day 16 hours7.3 GB / Hour5 Days 16 Hours per TBIgnite Videos and Presentations
Small File Test (Test 2)Serial316 GBWord Documents Between 1-5 MB4 days 1 hour3.26 GB / Hour12 Days 19 Hours per TBLots and Lots of Small Files
Small File Test (Test 3)Parallel316 GB Word Documents Between 1-5 MB1 day 1 hour12.6 GB / Hour3 days 8 hours per TB30 Individual Migrations, submitted at the same time

Migrating at 13GB an hour may not seem fast copying data compared to a fileshare, given the complexity involved getting data from 1 environment to the other, its a large improvement. I am excited to see how ISVs harness this power in their tools to migrate at cloud speed.

If you have any questions about the test Contact Me or Tweet me


Make sure you check out the Migration Guide on TechNet to get started and join the preview yammer group.

Speculation on the SharePoint 2016 Public Preview Release Date

Speculation on the SharePoint 2016 Public Preview Release Date

While researching the SharePoint Hybrid Search options that are being released, I happened upon this recently published support article: As you can see in the article, the hybrid search functionality will released for public preview on September 7th, 2015.

Support article screenshot

Back in July at the World Partner Conference, it was announced that the first preview of SharePoint 2016 was coming to the public in August. See this ITUnity article by Dan Holme for more information:

Knowing what was announced at WPC and now what was published by Microsoft in the support article, its a safe bet that the next release of SharePoint is just around the corner. Perhaps its on September 7th.

For further measure we know that Microsoft has been getting crafty with its numbers, Read: Windows 10’s Final Build Number delightfully clever. So releasing on September 7th would be clever as well since 9+7 = 16.

In any case we’ll see in under three short weeks



300GB Test3 Migration Results via SharePoint Online High Speed Migration (Small Files and Parallel Jobs)

300GB Test3 Migration Results via SharePoint Online High Speed Migration (Small Files and Parallel Jobs)

Updated Aug 19th: Quick Synopsis 25 hours @ 12.6GB/hr

Individual performance tests below,

Test 1 – Serial – 300GB of Large (video) files [here]
Test 2 – Serial – 300GB of Small (document) files [here]
Test 3 – Parallel – 300GB of Small (document) files [this post]

The last two tests I ran against the SharePoint Online High Speed Migration service were both Serial jobs, meaning that the files were processed one by one in the single solitary migration package. This allowed for simplicity and debugging of the jobs across the environment, there was a single files container in azure and a single package container as well. Even more simply there was one migration guid to track on the logs or in the migration queue.

What I decided to do following the last test was to create several migration packages from my file share and upload them all to Azure. I would then launch/submit all the jobs at once to get a gauge of how quickly the parallel jobs could work. The complexity comes from managing several containers per migration jobs, which can bog down any Azure storage explorer tool. The additional problem is that I needed to separate the upload & submission steps  from each other so I could finish uploading all the packages prior to submitting the jobs for ingestion into SharePoint.

I ended up creating a Powershell script that would treat each top level folder of a file share as its own individual package and create its own file and package containers in azure for that folder to use. I will share this script in another post where I can explain how the batching process I used works in detail.

small file migration resultsAs you can see in the file properties view, I have 31 different folders in my file share, which means that I’ll have 62 different containers in azure that will be used. Also since this is a semi-controlled test I know that each of the folders has 10.2GB of data for a total of 316GB overall.

small file migration results parallel

You can see here that the each of the folders now has a related package & file container. Please note though that the folder numbers do not necessarily correlate to the folders listed in the fileshare as seen below.

This is just a small result of one of the packaging processes, however it does let you track which folder links up to which containers in Azure in case you do need to troubleshoot any issues.

small file migration results parallel2

Another addition was the export of the results from the job upload. Its important to keep these results since they have the SAS URIs generated by the tool. Exporting these URIs to the files system lets me submit the jobs separately from the upload.


small file migration results parallel3You can see that this exported Powershell object contains all the URI’s generated from the tool. You would think that if you could export the object to a file, that you could import the object as well from a CSV? unfortunately that doesn’t work with this specific type of object using Import-CSV/Export-CSV, however you can reference the URIs manually when submitting the Job for ingestion.

Its evident that it took a bit more thinking to create and submit these jobs in parallel, however not so much that the process is unrepeatable. Once I confirmed that all the packages were uploaded and ready I submitted the job and waited for it to finish and below are the results.


Start Time:8/5/2015 7:23 AM (PST)
End Time: 8/6/2015 8:31 AM (PST)
Elapsed: 25 hours and 8 minutes

Migration Rate 12.6GB/HR (316GB/25.133 hours)

Its important to note that this is more than ten times what I have seen in migrations for small files during migrations, and for 1TB of data it would only take 80 hours to migrate.

300GB Test2 Migration Results via SharePoint Online High Speed Migration (Small Files)

300GB Test2 Migration Results via SharePoint Online High Speed Migration (Small Files)

Updated Aug 19th: Quick Synopsis 97 hours @ 3.26GB/hr

As a followup from my last post regarding the migration speed during a high speed migration, Mikael Svenson (@mikaelsvenson) pointed out the dataset that I was using was comprised of very large video files. He postulated that that smaller files would slow the migration process down during the import.

The problem I had with this is I didnt have a good way to generate the test data for a test migration That is until he offered to create me a tool which would generate test data.

So without further ado, my new dataset for testing:

small file migration results

What you see here is 31 folders of documents with 131k files ranging in between 1Mb and 5MB with the overall dataset size of 316GB. A big factor that affects this test is that all of these folders and documents are part of one package (think serial) and thus would not take advantage of parallel processing. (more to come on that soon).

In addition I wont cover here the individual steps I took to package and ship this information to Office 365, you can find more information about that here.

The DataSet

  • Size: 316GB
  • Files: 130,862 Files and 31 Folders
  • Target: One Drive for Business on Office 365

The Results

After submitting the jobs for migration I saw documents start being created almost immediately after the job was submitted at 5:20 PM on 7/20/2015. The last file was migrated on 7/24/2015 at 6:24PM.

  • Duration: 4 days, 1 hour, and 4 minutes
  • Speed: 3.26GB/Hr (316GB/97.06666666666667

In the end the migration speed was cut in half from the large speed migration, however this is still more than 3GB an hour is not bad at all for a small file comprised dataset.