Butchered
I'm with Kuch
- Apr 30, 2004
- 6,338
- 1
Morning everyone.
I have a question for tech folks familiar with One Drive.
Our company has recently gone away from PC Backup and is moving entirely to One Drive for storage purposes.
We needed folders to automatically sync to OneDrive, but didn't want to actually point the folders to OneDrive, so we've been using /mklink /j to make a junction between their desktop, favorites and documents folders. Our users are very spoiled and are not expected to do anything themselves, so trying to explain to them they will need to periodically copy their files into OD didn't go over well.
In small tests, this has worked well on our machines, but we're having some debate between us on how functional this would be in the case of a crash/HD needing to be wiped, etc.
I did a test where I created a file in one of my junctioned folders, forced a sync and verified the file was mirrored into OneDrive. I then removed the file from the folder on my local machine and verified it was still in the one drive web app. I then forced a sync and the file was removed.
My team member is arguing that if the HD were to crash/need to be wiped/reimaged, the mklink would be broken and the files would be removed from One Drive.
My thought is that it is the act of syncing that removes/adds the files to OD in this junction situation and that if the machine were to crash, OD won't sync since there's no connection for it to be able to do so.
I haven't really found any concrete answers on this anywhere since it seems like most of the things I've read suggests actually pointing the folder location to OneDrive instead of creating a junction.
Any ideas?
I have a question for tech folks familiar with One Drive.
Our company has recently gone away from PC Backup and is moving entirely to One Drive for storage purposes.
We needed folders to automatically sync to OneDrive, but didn't want to actually point the folders to OneDrive, so we've been using /mklink /j to make a junction between their desktop, favorites and documents folders. Our users are very spoiled and are not expected to do anything themselves, so trying to explain to them they will need to periodically copy their files into OD didn't go over well.
In small tests, this has worked well on our machines, but we're having some debate between us on how functional this would be in the case of a crash/HD needing to be wiped, etc.
I did a test where I created a file in one of my junctioned folders, forced a sync and verified the file was mirrored into OneDrive. I then removed the file from the folder on my local machine and verified it was still in the one drive web app. I then forced a sync and the file was removed.
My team member is arguing that if the HD were to crash/need to be wiped/reimaged, the mklink would be broken and the files would be removed from One Drive.
My thought is that it is the act of syncing that removes/adds the files to OD in this junction situation and that if the machine were to crash, OD won't sync since there's no connection for it to be able to do so.
I haven't really found any concrete answers on this anywhere since it seems like most of the things I've read suggests actually pointing the folder location to OneDrive instead of creating a junction.
Any ideas?