I’ve been a happy user of ownCloud for a few years now to dish shared calendar and contacts personally in addition to some image backup stuff with Android. I have no idea beyond the published reports of the split with the founder that started the Nextcloud variant, but it did seem like that is the future. So, getting over to it now made some sense to me. Here is what I did. YMMV.
Backed-up up my ownCloud directory, mysql db, etc. via tar cvf and phpmysql.
Moved my ownCloud directory off it’s usual path to something else (i.e. /var/www/owncloud to now /var/www/owncloud-old
Downloaded the Nextcloud zip here. Unzipped it and gave it the orginal path of owncloud.
Chmod’d and chown’d -R the permissions to get them the way I wanted of the new Nextcloud install.
Moved the config.php from the old owncloud into the same dir of Nextcloud (from owncloudpath/config/config.php to netxcloudpath/config/config.php) and this was the old file I brought over from the previous OC folder.
Hit the Nextcloud url path via browser and watched it go through the upgrade/update. It recognizes the situation and plays the required changes.
I did have to go into admin on nextcloud and re-enable calendar and contacts for some reason. Not sure why. Maybe licensing or something?
Took a while, but after I was able to access everything that was done in my previous owncloud.
Really clean drop-in upgrade/sidegrade IMHO.
I wasn’t on the very latest version of owncloud, but it still went fine. I was ballpark though (like 8.x something)
I’m running on a 32bit Ubuntu 14.04 server. Apache, mysql, etc. Pretty standard from a few years back. I realize all the cool kids are nginx, but Apache has always been fine for me.
I didn’t have a lot of other OC apps loaded. So, I wasn’t too worried about disabling stuff prior to NC.
I am doing a lot of caldav and carddav stuff and that was back online right after. No probs.
I hope all goes well for you if you go down this route and move off ownCloud.
Perhaps, it was in Windows 8 or when I was getting early builds of Windows 10, but no matter what I did, I couldn’t get Windows 10 to change the pre-login background screen that was selected at some point. It was stuck on the stock cave beach image of img100.jpg and it eventually drove me crazy.
Windows 10 only rendered the image at reboot or before I logged-into the laptop. After I logged-in, any screen lock or wake from sleep used my background image setting. It might be stuck on a different image of the stock ones from Windows 8 or 10 on your laptop. It always bugged me, but finally I had to do something about it. There are numerous posts on the web on how to handle this or variants of this. I always assumed there was just a problem because of the beta nature of the earlier Windows 10 builds and eventually it would work itself out. It never did.
All the various tricks on the web to change the background and lock image in Windows 10 didn’t work for me. All the regedit hacks, search and destroy ideas out there were of no help for me to kill this pre-login background screen. But, I finally killed it. Here is what I did.
Make sure you have folder item view options to show hidden and system protected files.
Go to C:\ProgramData\Microsoft\Windows and right-click SystemData if it exists.
Change ownership of SystemData so you can full control it.
Under SystemData, I had a couple of subfolders
Under the S-1-5-18 folder, there was a Read-Only folder
In that folder, there was an odd little “LockScreen_Z” folder with three images of that img100.jpg pic.
I moved that LockScreen_Z folder out to the desktop and did a reboot and I was freed from the image!
For some reason, Windows 8.x or 10 created this C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_Z directory that held on to that pre-login screen image no matter what I tried to do via regedit or via deleting every img100.jpg under C:\Windows.
If you suffer from this same issue, and Personalization or regedit hacks never worked, seek and destroy that LockScreen_Z folder. I hope that helps.
Ran into a tough issue with a Samsung Digital Signage unit that turned out to be quite a hassle. The unit was inconsistent on the wireless network and unable to reliably push content from MagicInfo. After numerous attempts to correct directly with the unit, I called tech support and eventually got through this solution. If you are having the some inconsistency with a DBE series unit, be sure to go into the Menu/Support and get the latest firmware. The issue with the unit we purchased was that the unit was too many versions behind the current firmware, so it wouldn’t perform an over the air update.
Here is the manual way to accomplish the update. My unit model was a DB55E and my version was 1014.
Check the version via the remote control from Menu/Support/Update and try to play the other the air update. If it is too many versions behind current, it will come back that you have the latest update. This would be incorrect.
If the update went well, you can stop here. If it didn’t, download this file. I am posting this because it was oddly difficult to obtain. It’s ~700megs.
Unzip that zip and put the contents of the unzipped folder on a USB memory stick.
Make sure to name the folder “T-GFSLE2AKUC” only and it should reside on the root level of the memory stick.
Connect it to the display USB port.
Run the update via the menu again, but this time you will be prompted if you want to search the USB storage. You do.
Let the screen run the update all the way through. It will take a few minutes then bring it back to the source search and or static snow.
Go back into Menu / Setup and confirm the update ran.
YMMV but hope this helps you without consuming the time it took me to get to a solution.