@JaredBusch said in Crashplan vs Backblaze in 2018:
@dafyre said in Crashplan vs Backblaze in 2018:
@JaredBusch said in Crashplan vs Backblaze in 2018:
@dafyre said in Crashplan vs Backblaze in 2018:
@Donahue said in Crashplan vs Backblaze in 2018:
@JaredBusch said in Crashplan vs Backblaze in 2018:
@dafyre said in Crashplan vs Backblaze in 2018:
@black3dynamite said in Crashplan vs Backblaze in 2018:
@dafyre said in Crashplan vs Backblaze in 2018:
@black3dynamite said in Crashplan vs Backblaze in 2018:
@Markferron said in Crashplan vs Backblaze in 2018:
@DustinB3403 said in Crashplan vs Backblaze in 2018:
Can I ask why you are protecting user devices though? Generally these have very little on them and through simple policy can everything be saved on your servers or cloud and thus don't need backup.
I would really like to do this. We have onedrive available for all of our users and I was thinking of coming up with some sort of system that just uses their onedrive as the primary source of their homefolder.
That's how I do it but we are using Nextcloud.
All users root folders under their user profile is linked to the actual folders in C:\Users\john.doe\Nextcloud{Desktop, Documents, etc...}. And the data is synced back to the Nextcloud server and that server is backed up.
How do you go about doing that? Editing the location of Desktop, Documents, etc... ?
Use Junction Points. Its like using symbolic links in Linux.
Oh... Duh, lol. Thanks.
I'm just trying to figure out how that would work if you have to do more than a few client machines at a time.
Something like this. It is not ready for prime time, but was my starting point last week when setting up a new desktop.
$User = Read-Host "Enter UserName"
Remove-Item -Path "C:\Users\$User\Desktop"
New-Item -ItemType Junction -Path "C:\Users\$User" -Name "Desktop" -Target "C:\Users\$User\Nextcloud\Desktop" -Force
Remove-Item -Path "C:\Users\$User\Documents"
New-Item -ItemType Junction -Path "C:\Users\$User" -Name "Documents" -Target "C:\Users\$User\Nextcloud\Documents" -Force
Remove-Item -Path "C:\Users\$User\Downloads"
New-Item -ItemType Junction -Path "C:\Users\$User" -Name "Downloads" -Target "C:\Users\$User\Nextcloud\Downloads" -Force
Remove-Item -Path "C:\Users\$User\Favorites"
New-Item -ItemType Junction -Path "C:\Users\$User" -Name "Favorites" -Target "C:\Users\$User\Nextcloud\Favorites" -Force
Remove-Item -Path "C:\Users\$User\Music"
New-Item -ItemType Junction -Path "C:\Users\$User" -Name "Music" -Target "C:\Users\$User\Nextcloud\Music" -Force
Remove-Item -Path "C:\Users\$User\Pictures"
New-Item -ItemType Junction -Path "C:\Users\$User" -Name "Pictures" -Target "C:\Users\$User\Nextcloud\Pictures" -Force
Remove-Item -Path "C:\Users\$User\Videos"
New-Item -ItemType Junction -Path "C:\Users\$User" -Name "Videos" -Target "C:\Users\$User\Nextcloud\Videos" -Force
where would this be run from, the DC?
This would have to be run from the End-user's computer from the looks of it.
You are trying to screw with the end user's folders. they have to exist, and you have to have rights to them. neither of which are true of an admin account.
Are you automating this -- then How?
If you're not automating it, then why not just manually add the folders to the NextCloud client?
/sigh FFS...
@JaredBusch said in Crashplan vs Backblaze in 2018:
Something like this. It is not ready for prime time, but was my starting point last week when setting up a new desktop.
lol. I thought you were talking about the code...
Time to research a way to do that.
