Archive

Posts Tagged ‘OneDrive for Business’

Office 365 News – OneDrive for Business now supports 10GB files and much more

February 9, 2016 Leave a comment

 Office365logo       SP2013logo

Short story: The OneDrive for Business improvements are here!

This was promised to us a long time ago, and it has now finally come to be. At the same time, the 20.000 file limit from before has also been removed (Improved)
Here is the proof:

Proof

The file was in addition, uploaded using the new OneDrive sync client!
(Dropped the file in the local cache and let the sync do its stuff)

  • The OneDrive for Business Next Generation Sync Client is available for Windows 7, 8 and 10 (8.1 support will be added in the first quarter of 2016) and Mac OS X 10.9 and above.
  • Storage, rolling out is an increase from 1TB to 5TB, upon request, more will be made available until unlimited is achieved? (Valid for: Enterprise E3, E4 and E5, Government E3, E4 and E5, Education, OneDrive for Business Plan 2 and SharePoint Online Plan 2)
  • 10GB filesize limit
  • No more 20.000 file limit
  • !! With this first release of several, the Next Generation Sync Client supports OneDrive for Business only, but we will add support for SharePoint document libraries in future releases. (This is the best news in a long time)
  • In the interim, if customers require sync for both OneDrive for Business and SharePoint document libraries, the Next Generation Sync Client is designed to work side-by-side with the existing sync client.
  • the OneDrive for iOS app will support offline storage. You can selectively flag files for local availability and open them when disconnected
  • For developers: https://dev.onedrive.com/ (OneDrive developer portal)

References:

Read the official story on the Office 365 blog about the (then upcoming) news here:

OneDrive for Business update on storage plans and Next Generation Sync Client
https://blogs.office.com/2015/12/16/onedrive-for-business-update-on-storage-plans-and-next-generation-sync-client/

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Office 365 News – Move and Copy files and folders in OneDrive for Business

April 16, 2015 1 comment

 Office365logo       SP2013logo       SharedLove

Now, finally, we can move and copy files within our OneDrive for Business web GUI

Dokument

Some random document…

Some time, early 2015, Microsoft introduced the ability to move/copy files in OneDrive for Business. This has been one of the major obstacles for using OneDrive for Business as a E1 user without the Office applications installed locally. Or rather, as a Online only user no matter what license. As a long time SHarePoint user and technician, this is a long awaited feature in SHarePoint as well, so now I’m keeping my fingers crossed for this ‘simple’ little feature to appear there as well. (I do not for one second think that this has been easy to implement at all) In addition, the function is quick!

Want to see how it looks and works?

The following table lists the tested and verified behaviour of the Copy/Move functionality in OneDrive for Business:

Action Behavior Notes
Move File(s) Moves the selected file(s) to the designated target container Retains metadata Retains sharing Does not overwrite if filename exists, reports back error
Move Folder(s) Moves the selected folder(s) to the designated target container Recreates a new copy of the folder Retains sharing Does not overwrite if filename exists, reports back error
Copy File(s) Copies the selected file(s) to the designated target container Recreates a new copy of the file(s) with new metadata Does not retain sharing Does not overwrite if filename exists, reports back error
Copy Folder(s) Copies the selected folder(s) to the designated target container Recreates a new copy of the folder with new metadata Does not retain sharing Does not overwrite if filename exists, reports back error
Copy or Move in SharePoint N/A – ‘Send to’ a predetermined location is the closest we get in SharePoint Server or SharePoint Online N/A

How it looks in reality:

Move or Copy a single file

SingleFileMove1

Move or Copy multiple files/folders

MultipleFilesMove1

Select the target, check the ‘Copy’ box if you want to Copy and not Move

MultiMoveDialog

After copying/Moving, you will get a Little reciept in the top right corner

Shared15

Ok

or

SharedCopy

If one or many of the files allready exist at the target, they are not overwritten, not even with a new name or new version. You will instead get a note on this and the result

Error

Now, we all hope for the same in SharePoint! Until it comes, we all to this ‘simple’ feature say: FINALLY!

References and Credits

None at this time…

Credits & many thanks to

Everyone!   SP2013logo

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Office 365 guide series – Manage files and folders with PowerShell and CSOM

February 24, 2015 Leave a comment

 Office365logo       SP2013logo

How to manage files and folders with PowerShell and CSOM

DocLib1

How can we manage these items…?

This is a pure guide to using PowerShell to manage and manipulate files and folders, libraries and all document management related tasks in a SharePoint Online or OneDrive for Business environment.

The sections in this guide are:

– Prerequisites
– Load assemblies
– Load a CSOM Context
– Web
– List/Library
– GetFileByServerRelativeUrl and GetForlderByServerRelativeUrl
– Create a file from a local copy
– Create a folder from a local copy
– Set properties on a file
– Set properties on a folder
– ResolveUser (Function)
– GetItemProperties (Function)

Prerequisites

Before beeing able to do much in SharePoint Online or OneDrive for Business, you have to start using CSOM, or Client Side Object Model, this allows us to do pretty much everything we could do before using regular PowerShell and the SharePoint CMD’lets from the SharePoint PowerShell add-on.
Install assemblies:
Download and install ther latest version of the SharePoint Server 2013 Client Components SDK, this can be downloaded from here: http://www.microsoft.com/en-us/download/details.aspx?id=35585
After the SDK and the CSOM assembly DLL’s are in place, make sure you load the assemblies before calling them.

Load assemblies

 Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.dll"
 Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.Runtime.dll"

This will open up for usage of CSOM in PowerShell.

Load a context

$SPOUser = "administrator@blksthl.onmicrosoft.com"
# Uses a hardcoded password, use only during test/lab:
$SPOPassword = convertto-securestring "Password01" -asplaintext -force
# Better: $SPOPassword = Read-Host -Prompt "Please enter your password" -AsSecureString
$SPOODfBUrl = "https://blksthl.sharepoint.com/personal/jeffrey_lebowski_blksthl_com"
$Context = New-Object Microsoft.SharePoint.Client.ClientContext($SPOODfBUrl)
$Credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($SPOUser,$SPOPassword)
$Context.RequestTimeout = 16384000
$Context.Credentials = $Credentials
$Context.ExecuteQuery()

Returns: $Context

Web

(Using $Context from the section on Context above)

$Web = $Context.Web
$Context.Load($Web)
$Context.ExecuteQuery()

Returns: $Web

List/Library

$SPODocLibName = "Documents"
$SPOList = $Web.Lists.GetByTitle($SPODocLibName)
$Context.Load($SPOList.RootFolder)
$Context.ExecuteQuery()

Returns: $SPOList

GetFileByServerRelativeUrl and GetForlderByServerRelativeUrl

In order to use the ‘Get…ByServerRelativeUrl’ methods you have to supply a relative path to the file or folder, this means a path starting from the FQDN.

Example 1
https://company.sharepoint.com/get/fileorfolder/by/relative/url
FQDN: https://company.sharepoint.com
ServerRelativeUrl: /get/fileorfolder/by/relative/url

Example 2
https://company-my.sharepoint.com/personal/firstname_lastname_company_com
FQDN: https://company-my.sharepoint.com
ServerRelativeUrl: /personal/firstname_lastname_company_com

Example file:

"/personal/jeffrey_lebowski_blksthl_com/documents/report1.xlsx"

Example folder:

 "/personal/jeffrey_lebowski_blksthl_com/documents/subfolder"

Create a file from a local copy

This can be accomplished in several ways, this is one:

1.
$LocalFile = Get-ChildItem -path "C:\Homedirs\jeff\report1.xlsx"
$FolderRelativeUrl = $SPOList.RootFolder.ServerRelativeUrl
$FileName = $LocalFile.Name
$FileUrl = $FolderRelativeUrl + "/" + $FileName
[Microsoft.SharePoint.Client.File]::SaveBinaryDirect($Web.Context, $fileUrl, $LocalFile.OpenRead(), $true)

Returns: New file created in SPO/ODfB

Create a folder from a local copy

$SPOFolder = $SPOList.RootFolder
$LocalFolder = Get-ChildItem -path "C:\Homedirs\jeff\" -Recurse -Include "folder1" 
$FolderName = $LocalFolder.Name
$NewFolder = $SPOFolder.Folders.Add($FolderName)
$Web.Context.Load($NewFolder)
$Web.Context.ExecuteQuery()

Returns: New folder created in SPO/ODfB

Set properties on a file

Input: $FileRelativeUrl, $SPOItemModifier, $SPOItemOwner, $ItemCreated, $ItemModified

$CurrentFile = $Context.web.GetFileByServerRelativeUrl($FileRelativeUrl)
$Context.Load($CurrentFile)
$Context.ExecuteQuery()
$ListItem = $CurrentFile.ListItemAllFields;
$ListItem["Editor"] = $SPOItemModifier; # Get object from ResolveUser
$Listitem["Author"] = $SPOItemOwner; # Get object from ResolveUser
$Listitem["Created"] = $ItemCreated;
$Listitem["Modified"] = $ItemModified;
$ListItem.Update()
$Context.Load($CurrentFile)
$Context.ExecuteQuery()

Returns: Folder stamped with new properties in SPO/ODfB

Set properties on a folder

Input: $FolderRelativeUrl, , $SPOItemModifier, $SPOItemOwner, $ItemCreated, $ItemModified

$CurrentFolder = $Context.web.GetFolderByServerRelativeUrl($FolderRelativeURL)
$Context.Load($CurrentFolder)
$Context.ExecuteQuery()
$SPOFolderItem = $CurrentFolder.ListItemAllFields;
$SPOItemOwner = ResolveUser $UserEmail # For ResolveUser see separate function described later in this post
$SPOFolderItem["Editor"] = $SPOItemModifier # Must be a userobject, see 'ResolveUser'
$SPOFolderItem["Author"] = $SPOItemOwner # Must be a userobject, see 'ResolveUser'
$SPOFolderItem["Created"] = $ItemCreated # In the format: "8/10/2013 7:04 PM", see 'GetItemProperties'
$SPOFolderItem["Modified"] = $ItemModified # In the format: "8/10/2013 7:04 PM", see 'GetItemProperties'
$SPOFolderItem.Update()
$Context.Load($CurrentFolder)
$Context.ExecuteQuery()

Returns: Folder stamped with new properties in SPO/ODfB

ResolveUser (Function)

Function ResolveUser ($InputUPN)
# Resolves a user to a userobject
{
    $OutputUserObject = $Web.Context.web.EnsureUser($InputUPN)
    $Web.Context.Load($OutputUserObject)
    $Web.Context.ExecuteQuery()
    Return $OutputUserObject
}

Returns: UserObject for $InputUPN (UserPrincipalName/Email)

GetItemProperties (Function)

Function GetItemProperties ($InFileObject)
# Gets basic properties to set on files and folders
{
    $Global:ItemCreated = $InFile.CreationTime
    $Global:ItemModified = $InFile.LastWriteTime
}

Returns: Global: Variables for ItemCreated and LastWriteTime of $InFileObject (File or Folder)

Thats all for now, I hope that you let me know if there is anything that seems to be wrong or does not work. The problem with describing all this in a complete way, is that it is easy to leave something out and it is also difficult to test every aspect while writing. Time is limited for all of us…
Anyway, my goal was to write a post that covered what I was myself missing…I hope that this is it. And again, please let me know if there are any mistakes in here.

References and Credits

None at this time…

Credits & many thanks to

LabCenter – you guys always publish my articles!

My family, my parents, Ia and the kids!

SP2013logo

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Office 365 News – New document now supports Content types in SharePoint Online

February 18, 2015 2 comments

 Office365logo       SP2013logo

‘new document’ now supports Content types in SharePoint Online

Thank you Microsoft, Content types just got user friendly and easy to use and promote!

ContentTypes1x

The new- new document dialog

Before yesterday, I knew that the ‘new document’ button in a document library became useless when you enabled Content types in a document library. This has for me and many of my customers been a huge drawback since the ‘new document’ button was still there, in plain view and for the regular user, what they were meant to use.

This old behavious was that when you pressed on ‘new document’ in a document library with multiple content types, you got the upload document dialog.

Upload dialog2

Old behaviour

What I was so glad to discover yesterday, during a live demo at a customer, that this has been fixed now in SPO! Instead of the upload dialog, I could now get this:

ContentTypes1

Fixed!

One down!
Next step, make content types available to Office Online…(They still seem to require the Office Applications installed on the client, nothing for E1 users or less in other words…)
I would also like the new folder option back with the content types 🙂

References and Credits

None at this time…

Credits & many thanks to

Cramo, this is where I did the demo when this change presented itself to me! A pleasure to work with you guys!

 

SP2013logo

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Office 365 News – Unannounced Microsoft change to SharePoint Online access

February 17, 2015 2 comments

 Office365logo       SP2013logo

Microsoft recently made a change to the way users can access SharePoint Online, this may affect many thousands of customers without them knowing…

Licensex

It has been disclosed to me that Microsoft has implemented a change on all Office 365 tenants to the way an unlicensed user can access SharePoint Online services…in a bad way…

Previously, the behaviour was that if you did not give a user a the SharePoint license in Office 365, the user could not access SharePoint.
This is the expected behaviour and this is how most companies restricted access to SharePoint Before they were ready to offer the service to their organizations.
This is no more, or at least not the current behaviour…Microsft has ‘temporarily’ made a change that allows ALL users, with a license or not to have access to all SharePoint Services.
The imidiate affect may be that your organization sleeps safely in the belief that SHarePoint may not be accessed, except by you in IT or by a limited number of individuals, meanwhile, the users go crazy and start using SharePoint in ways you never intended…

Well, this is something I don’t like, I would like this change to be limited to the ones who specifically asked for it, and if you needed it, you could request it, not the other way around.

Note 1: If you find that you do not want this behaviour, you want access only to your licensed users. Open a Service Request with Microsoft and ask them to change it back, they will help you then.

Note 2: The change does not affect OneDrive for Business, unprovisioned users do not get access to their ODfB without the SharePoint license.

The reason given by Microsoft representatives is this: Microsoft recognizes assigning licenses to users that are synced to the O365 services is cumbersome for larger tenants, to alleviate this pain point; a temporary change has been released to SharePoint Online that will allow users to access SharePoint Online even without license.’

 

References and Credits

None at this time…

Credits & many thanks to

Pihlen!

 

SP2013logo

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn