How to change ownership of files and folders in Onedrive for Business?
Do anyone know?
I have finally figured out how to copy file trees but now I want to set the ownership back to the original creator of the files.
(I'm trying to convince my fellow board members of a small local youth sports club to move all the documents regarding running the club away from scattered number of private laptops into Office365. I find the Shared folders concept in Onedrive for Business hard to comprehend...)
onedrive shared-folders office365
add a comment |
Do anyone know?
I have finally figured out how to copy file trees but now I want to set the ownership back to the original creator of the files.
(I'm trying to convince my fellow board members of a small local youth sports club to move all the documents regarding running the club away from scattered number of private laptops into Office365. I find the Shared folders concept in Onedrive for Business hard to comprehend...)
onedrive shared-folders office365
You are setting these locally or trying to set these in the service itself? What problem are you actually trying to solve?
– Jesus Shelby
Dec 21 '15 at 23:39
Users are creating their documents in their Shared with everyone folder and I'm trying to collect these documents into a common folder structure. Something along these lines UserA has this in her shared folder /dirX/document1 UserB has this in his shared folder /dirY/document2 I would like to collect the information in a common folder structure keeping the original ownership. Something like this /dirY/document2 /dirY/dirX/document1 So that everyone that looks into /dirY will see the subfolder dirX and seeing who has created the documents. Thanks for the response.
– dragz
Dec 22 '15 at 14:39
Augh, the formatting got screwed up. Hope you get my meaning.
– dragz
Dec 22 '15 at 14:39
Also, I had to do the file structure copying locally. I could not figure out how to do it on the web interface.
– dragz
Dec 22 '15 at 14:40
add a comment |
Do anyone know?
I have finally figured out how to copy file trees but now I want to set the ownership back to the original creator of the files.
(I'm trying to convince my fellow board members of a small local youth sports club to move all the documents regarding running the club away from scattered number of private laptops into Office365. I find the Shared folders concept in Onedrive for Business hard to comprehend...)
onedrive shared-folders office365
Do anyone know?
I have finally figured out how to copy file trees but now I want to set the ownership back to the original creator of the files.
(I'm trying to convince my fellow board members of a small local youth sports club to move all the documents regarding running the club away from scattered number of private laptops into Office365. I find the Shared folders concept in Onedrive for Business hard to comprehend...)
onedrive shared-folders office365
onedrive shared-folders office365
asked Dec 21 '15 at 20:36
dragz
16112
16112
You are setting these locally or trying to set these in the service itself? What problem are you actually trying to solve?
– Jesus Shelby
Dec 21 '15 at 23:39
Users are creating their documents in their Shared with everyone folder and I'm trying to collect these documents into a common folder structure. Something along these lines UserA has this in her shared folder /dirX/document1 UserB has this in his shared folder /dirY/document2 I would like to collect the information in a common folder structure keeping the original ownership. Something like this /dirY/document2 /dirY/dirX/document1 So that everyone that looks into /dirY will see the subfolder dirX and seeing who has created the documents. Thanks for the response.
– dragz
Dec 22 '15 at 14:39
Augh, the formatting got screwed up. Hope you get my meaning.
– dragz
Dec 22 '15 at 14:39
Also, I had to do the file structure copying locally. I could not figure out how to do it on the web interface.
– dragz
Dec 22 '15 at 14:40
add a comment |
You are setting these locally or trying to set these in the service itself? What problem are you actually trying to solve?
– Jesus Shelby
Dec 21 '15 at 23:39
Users are creating their documents in their Shared with everyone folder and I'm trying to collect these documents into a common folder structure. Something along these lines UserA has this in her shared folder /dirX/document1 UserB has this in his shared folder /dirY/document2 I would like to collect the information in a common folder structure keeping the original ownership. Something like this /dirY/document2 /dirY/dirX/document1 So that everyone that looks into /dirY will see the subfolder dirX and seeing who has created the documents. Thanks for the response.
– dragz
Dec 22 '15 at 14:39
Augh, the formatting got screwed up. Hope you get my meaning.
– dragz
Dec 22 '15 at 14:39
Also, I had to do the file structure copying locally. I could not figure out how to do it on the web interface.
– dragz
Dec 22 '15 at 14:40
You are setting these locally or trying to set these in the service itself? What problem are you actually trying to solve?
– Jesus Shelby
Dec 21 '15 at 23:39
You are setting these locally or trying to set these in the service itself? What problem are you actually trying to solve?
– Jesus Shelby
Dec 21 '15 at 23:39
Users are creating their documents in their Shared with everyone folder and I'm trying to collect these documents into a common folder structure. Something along these lines UserA has this in her shared folder /dirX/document1 UserB has this in his shared folder /dirY/document2 I would like to collect the information in a common folder structure keeping the original ownership. Something like this /dirY/document2 /dirY/dirX/document1 So that everyone that looks into /dirY will see the subfolder dirX and seeing who has created the documents. Thanks for the response.
– dragz
Dec 22 '15 at 14:39
Users are creating their documents in their Shared with everyone folder and I'm trying to collect these documents into a common folder structure. Something along these lines UserA has this in her shared folder /dirX/document1 UserB has this in his shared folder /dirY/document2 I would like to collect the information in a common folder structure keeping the original ownership. Something like this /dirY/document2 /dirY/dirX/document1 So that everyone that looks into /dirY will see the subfolder dirX and seeing who has created the documents. Thanks for the response.
– dragz
Dec 22 '15 at 14:39
Augh, the formatting got screwed up. Hope you get my meaning.
– dragz
Dec 22 '15 at 14:39
Augh, the formatting got screwed up. Hope you get my meaning.
– dragz
Dec 22 '15 at 14:39
Also, I had to do the file structure copying locally. I could not figure out how to do it on the web interface.
– dragz
Dec 22 '15 at 14:40
Also, I had to do the file structure copying locally. I could not figure out how to do it on the web interface.
– dragz
Dec 22 '15 at 14:40
add a comment |
1 Answer
1
active
oldest
votes
What you are trying to do will be extremely difficult to implement and maintain. Users have full access to their OneDrive and move or change that structure at any time. Also be aware that new users you create should not have a "Share with Everyone" folder - Microsoft stopped created that folder a few months ago for new users.
If a document is in that folder, or shared with anyone - it's exposed thru Delve and is searchable for those that have access. So you can click on the "Shared with Me" and get access to these document and even refine from there. You can also just arbitrarily search for these document if you know part of the name or content. I would advise against using folders in the fashion you intent - instead their use should be limited to breaking up collection to avoid view limits or attached per-defined metadata to file collections.
That being said to do this locally you would need to sync to each users folder, make the changes and sync back. You can use something like this:
#Get ACL of file before you change it (includes owner)
$objFile = Get-Acl C:TestFile.txt
#Set file back to original permissions after you alter it
Set-Acl -aclobject $objFile -path C:TestFile.txt
If that doesn't work you can use the takeown command
Single File takeown /f c:TestFile.txt
Entire directory takeown /f c:Directory /r
That's a pretty clunky way to do it as you have to sync back all the changes. But if you want to do it directly in O365 you need create a custom script that leverage the REST API or find a 3rd party tool (I'm not sure of any that provide this particular functionality, but there are plenty that handle the file migration aspect of it) .
Another alternative - is to deploy a SharePoint Team site or take advantage of O365 Groups. These provide a central location for sharing information. Groups in particular are handy as they create distribution lists for sharing discussions and create a shared library for storing associated content.
Office 365 is a very powerful platform - however to get the most out of it, there is a slight paradigm shift in how you manage objects.
Thanks for sharing your insights. This is very useful information, I think the teamsite option seems to be the way to go. Again, thanks, and happy holidays!
– dragz
Dec 29 '15 at 9:08
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1016448%2fhow-to-change-ownership-of-files-and-folders-in-onedrive-for-business%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
What you are trying to do will be extremely difficult to implement and maintain. Users have full access to their OneDrive and move or change that structure at any time. Also be aware that new users you create should not have a "Share with Everyone" folder - Microsoft stopped created that folder a few months ago for new users.
If a document is in that folder, or shared with anyone - it's exposed thru Delve and is searchable for those that have access. So you can click on the "Shared with Me" and get access to these document and even refine from there. You can also just arbitrarily search for these document if you know part of the name or content. I would advise against using folders in the fashion you intent - instead their use should be limited to breaking up collection to avoid view limits or attached per-defined metadata to file collections.
That being said to do this locally you would need to sync to each users folder, make the changes and sync back. You can use something like this:
#Get ACL of file before you change it (includes owner)
$objFile = Get-Acl C:TestFile.txt
#Set file back to original permissions after you alter it
Set-Acl -aclobject $objFile -path C:TestFile.txt
If that doesn't work you can use the takeown command
Single File takeown /f c:TestFile.txt
Entire directory takeown /f c:Directory /r
That's a pretty clunky way to do it as you have to sync back all the changes. But if you want to do it directly in O365 you need create a custom script that leverage the REST API or find a 3rd party tool (I'm not sure of any that provide this particular functionality, but there are plenty that handle the file migration aspect of it) .
Another alternative - is to deploy a SharePoint Team site or take advantage of O365 Groups. These provide a central location for sharing information. Groups in particular are handy as they create distribution lists for sharing discussions and create a shared library for storing associated content.
Office 365 is a very powerful platform - however to get the most out of it, there is a slight paradigm shift in how you manage objects.
Thanks for sharing your insights. This is very useful information, I think the teamsite option seems to be the way to go. Again, thanks, and happy holidays!
– dragz
Dec 29 '15 at 9:08
add a comment |
What you are trying to do will be extremely difficult to implement and maintain. Users have full access to their OneDrive and move or change that structure at any time. Also be aware that new users you create should not have a "Share with Everyone" folder - Microsoft stopped created that folder a few months ago for new users.
If a document is in that folder, or shared with anyone - it's exposed thru Delve and is searchable for those that have access. So you can click on the "Shared with Me" and get access to these document and even refine from there. You can also just arbitrarily search for these document if you know part of the name or content. I would advise against using folders in the fashion you intent - instead their use should be limited to breaking up collection to avoid view limits or attached per-defined metadata to file collections.
That being said to do this locally you would need to sync to each users folder, make the changes and sync back. You can use something like this:
#Get ACL of file before you change it (includes owner)
$objFile = Get-Acl C:TestFile.txt
#Set file back to original permissions after you alter it
Set-Acl -aclobject $objFile -path C:TestFile.txt
If that doesn't work you can use the takeown command
Single File takeown /f c:TestFile.txt
Entire directory takeown /f c:Directory /r
That's a pretty clunky way to do it as you have to sync back all the changes. But if you want to do it directly in O365 you need create a custom script that leverage the REST API or find a 3rd party tool (I'm not sure of any that provide this particular functionality, but there are plenty that handle the file migration aspect of it) .
Another alternative - is to deploy a SharePoint Team site or take advantage of O365 Groups. These provide a central location for sharing information. Groups in particular are handy as they create distribution lists for sharing discussions and create a shared library for storing associated content.
Office 365 is a very powerful platform - however to get the most out of it, there is a slight paradigm shift in how you manage objects.
Thanks for sharing your insights. This is very useful information, I think the teamsite option seems to be the way to go. Again, thanks, and happy holidays!
– dragz
Dec 29 '15 at 9:08
add a comment |
What you are trying to do will be extremely difficult to implement and maintain. Users have full access to their OneDrive and move or change that structure at any time. Also be aware that new users you create should not have a "Share with Everyone" folder - Microsoft stopped created that folder a few months ago for new users.
If a document is in that folder, or shared with anyone - it's exposed thru Delve and is searchable for those that have access. So you can click on the "Shared with Me" and get access to these document and even refine from there. You can also just arbitrarily search for these document if you know part of the name or content. I would advise against using folders in the fashion you intent - instead their use should be limited to breaking up collection to avoid view limits or attached per-defined metadata to file collections.
That being said to do this locally you would need to sync to each users folder, make the changes and sync back. You can use something like this:
#Get ACL of file before you change it (includes owner)
$objFile = Get-Acl C:TestFile.txt
#Set file back to original permissions after you alter it
Set-Acl -aclobject $objFile -path C:TestFile.txt
If that doesn't work you can use the takeown command
Single File takeown /f c:TestFile.txt
Entire directory takeown /f c:Directory /r
That's a pretty clunky way to do it as you have to sync back all the changes. But if you want to do it directly in O365 you need create a custom script that leverage the REST API or find a 3rd party tool (I'm not sure of any that provide this particular functionality, but there are plenty that handle the file migration aspect of it) .
Another alternative - is to deploy a SharePoint Team site or take advantage of O365 Groups. These provide a central location for sharing information. Groups in particular are handy as they create distribution lists for sharing discussions and create a shared library for storing associated content.
Office 365 is a very powerful platform - however to get the most out of it, there is a slight paradigm shift in how you manage objects.
What you are trying to do will be extremely difficult to implement and maintain. Users have full access to their OneDrive and move or change that structure at any time. Also be aware that new users you create should not have a "Share with Everyone" folder - Microsoft stopped created that folder a few months ago for new users.
If a document is in that folder, or shared with anyone - it's exposed thru Delve and is searchable for those that have access. So you can click on the "Shared with Me" and get access to these document and even refine from there. You can also just arbitrarily search for these document if you know part of the name or content. I would advise against using folders in the fashion you intent - instead their use should be limited to breaking up collection to avoid view limits or attached per-defined metadata to file collections.
That being said to do this locally you would need to sync to each users folder, make the changes and sync back. You can use something like this:
#Get ACL of file before you change it (includes owner)
$objFile = Get-Acl C:TestFile.txt
#Set file back to original permissions after you alter it
Set-Acl -aclobject $objFile -path C:TestFile.txt
If that doesn't work you can use the takeown command
Single File takeown /f c:TestFile.txt
Entire directory takeown /f c:Directory /r
That's a pretty clunky way to do it as you have to sync back all the changes. But if you want to do it directly in O365 you need create a custom script that leverage the REST API or find a 3rd party tool (I'm not sure of any that provide this particular functionality, but there are plenty that handle the file migration aspect of it) .
Another alternative - is to deploy a SharePoint Team site or take advantage of O365 Groups. These provide a central location for sharing information. Groups in particular are handy as they create distribution lists for sharing discussions and create a shared library for storing associated content.
Office 365 is a very powerful platform - however to get the most out of it, there is a slight paradigm shift in how you manage objects.
answered Dec 22 '15 at 16:06
Jesus Shelby
1,163169
1,163169
Thanks for sharing your insights. This is very useful information, I think the teamsite option seems to be the way to go. Again, thanks, and happy holidays!
– dragz
Dec 29 '15 at 9:08
add a comment |
Thanks for sharing your insights. This is very useful information, I think the teamsite option seems to be the way to go. Again, thanks, and happy holidays!
– dragz
Dec 29 '15 at 9:08
Thanks for sharing your insights. This is very useful information, I think the teamsite option seems to be the way to go. Again, thanks, and happy holidays!
– dragz
Dec 29 '15 at 9:08
Thanks for sharing your insights. This is very useful information, I think the teamsite option seems to be the way to go. Again, thanks, and happy holidays!
– dragz
Dec 29 '15 at 9:08
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1016448%2fhow-to-change-ownership-of-files-and-folders-in-onedrive-for-business%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You are setting these locally or trying to set these in the service itself? What problem are you actually trying to solve?
– Jesus Shelby
Dec 21 '15 at 23:39
Users are creating their documents in their Shared with everyone folder and I'm trying to collect these documents into a common folder structure. Something along these lines UserA has this in her shared folder /dirX/document1 UserB has this in his shared folder /dirY/document2 I would like to collect the information in a common folder structure keeping the original ownership. Something like this /dirY/document2 /dirY/dirX/document1 So that everyone that looks into /dirY will see the subfolder dirX and seeing who has created the documents. Thanks for the response.
– dragz
Dec 22 '15 at 14:39
Augh, the formatting got screwed up. Hope you get my meaning.
– dragz
Dec 22 '15 at 14:39
Also, I had to do the file structure copying locally. I could not figure out how to do it on the web interface.
– dragz
Dec 22 '15 at 14:40