diff --git a/blog-vault/.obsidian/workspace.json b/blog-vault/.obsidian/workspace.json
index 97eaf730345d802133960a4e2226a741e6c404ef..53197852d9e644c757dfa8ea4c03124368640195 100644
--- a/blog-vault/.obsidian/workspace.json
+++ b/blog-vault/.obsidian/workspace.json
@@ -13,12 +13,12 @@
"state": {
"type": "markdown",
"state": {
- "file": "posts/2025-02-05 Make Beautiful Reports with Pandoc.md",
+ "file": "posts/2025-03-07 Fixing weird Nextcloud client sync issues.md",
"mode": "source",
"source": false
},
"icon": "lucide-file",
- "title": "2025-02-05 Make Beautiful Reports with Pandoc"
+ "title": "2025-03-07 Fixing weird Nextcloud client sync issues"
}
}
]
@@ -185,12 +185,14 @@
},
"active": "243320f073b2669e",
"lastOpenFiles": [
+ "posts/2025-03-25 Deleting Intune Users.md",
+ "posts/2025-03-07 Fixing weird Nextcloud client sync issues.md",
+ "posts/2025-02-05 Make Beautiful Reports with Pandoc.md",
+ "posts/2025-01-24 Use multiple audio outputs at once on Ubuntu 24.04.md",
"posts/2024-11-27 First Blog Post.md",
"templates/Blog Post Template.md",
"images/Pasted Image 20250210233211.png",
- "posts/2025-02-05 Make Beautiful Reports with Pandoc.md",
"images/Pasted image 20250210233148.png",
- "posts/2025-01-24 Use multiple audio outputs at once on Ubuntu 24.04.md",
"images/Pasted image 20250124112849.png",
"images/Pasted image 20250124112639.png",
"images/Pasted image 20250124112342.png",
diff --git a/blog-vault/posts/2025-03-07 Fixing weird Nextcloud client sync issues.md b/blog-vault/posts/2025-03-07 Fixing weird Nextcloud client sync issues.md
new file mode 100644
index 0000000000000000000000000000000000000000..09eb882b7875127d933aa16fd970b8c3e6b879ea
--- /dev/null
+++ b/blog-vault/posts/2025-03-07 Fixing weird Nextcloud client sync issues.md
@@ -0,0 +1,25 @@
+---
+title: Fixing weird Nextcloud client sync issues
+date: 2025-03-07T23:36:41+00:00
+draft: true
+tags:
+ - windows
+ - sysadmin
+---
+Sometimes the Nextcloud client just doesn't work properly. I've had the following error message which can be caused by the client sending files that are too big:
+```
+Expected filesize of 1680396914 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.
+```
+Apparently this may be due to the LimitRequestBody apache setting, but I'm gonna do a crazy thing and force the client to chunk. This has helped in the past too when uploading files larger than the PHP memory limit (but apparently the php mem limit doesn't exist on my install anymore?).
+
+Open the nextcloud.cfg file. On Windows, this is stored in `%appdata%\Nextcloud\`.
+Add this line under the `[General]` heading:
+```ini
+maxChunkSize=50000000
+```
+This sets the max chunk size to 50MB.
+
+If you haven't already changed this on the server, too, now is the time to do that:
+```bash
+sudo -u www-data php occ config:system:set --type int --value 50000000 files.chunked_upload.max_size
+```
\ No newline at end of file
diff --git a/blog-vault/posts/2025-03-25 Deleting Intune Users.md b/blog-vault/posts/2025-03-25 Deleting Intune Users.md
new file mode 100644
index 0000000000000000000000000000000000000000..13b2914ffb87b66e93d201f11cebcca585ffb828
--- /dev/null
+++ b/blog-vault/posts/2025-03-25 Deleting Intune Users.md
@@ -0,0 +1,21 @@
+---
+title: Deleting Intune Users (Because I forgot about the registry)
+date: 2025-03-25T12:51:26+00:00
+draft: false
+tags:
+ - windows
+ - sysadmin
+ - intune
+---
+So, you ran out of space on an Intune managed device.
+Like mine, your first inclination may be to delete the user folders in the c:\users directory via booting into a USB drive. However, this will break those deleted users when they try to sign in again, instead logging them into a temporary account.
+When running CMD, your user profile location seems to be `C:\Users\YOURDOMAIN.TEMP` but `whoami` returns `yourdomain\user`. Hmm.
+
+The solution? Delete the users from the registry too, else Windows will complain.
+
+Go to regedit from a local account (or from a recovery USB importing the hive):
+`HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList`
+
+Then delete all the Intune users whose folders you deleted. These will probably begin with `S-1-12-1`. Be careful not to delete the folder or the registry entry of the user who enrolled the computer, otherwise bad things may happen - I don't know but I suspect that user disappearing may be a problem for how Intune works.
+
+Log out, reboot, and it should work.
\ No newline at end of file
diff --git a/content/posts/2025-03-07 Fixing weird Nextcloud client sync issues.md b/content/posts/2025-03-07 Fixing weird Nextcloud client sync issues.md
new file mode 100644
index 0000000000000000000000000000000000000000..09eb882b7875127d933aa16fd970b8c3e6b879ea
--- /dev/null
+++ b/content/posts/2025-03-07 Fixing weird Nextcloud client sync issues.md
@@ -0,0 +1,25 @@
+---
+title: Fixing weird Nextcloud client sync issues
+date: 2025-03-07T23:36:41+00:00
+draft: true
+tags:
+ - windows
+ - sysadmin
+---
+Sometimes the Nextcloud client just doesn't work properly. I've had the following error message which can be caused by the client sending files that are too big:
+```
+Expected filesize of 1680396914 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.
+```
+Apparently this may be due to the LimitRequestBody apache setting, but I'm gonna do a crazy thing and force the client to chunk. This has helped in the past too when uploading files larger than the PHP memory limit (but apparently the php mem limit doesn't exist on my install anymore?).
+
+Open the nextcloud.cfg file. On Windows, this is stored in `%appdata%\Nextcloud\`.
+Add this line under the `[General]` heading:
+```ini
+maxChunkSize=50000000
+```
+This sets the max chunk size to 50MB.
+
+If you haven't already changed this on the server, too, now is the time to do that:
+```bash
+sudo -u www-data php occ config:system:set --type int --value 50000000 files.chunked_upload.max_size
+```
\ No newline at end of file
diff --git a/content/posts/2025-03-25 Deleting Intune Users.md b/content/posts/2025-03-25 Deleting Intune Users.md
new file mode 100644
index 0000000000000000000000000000000000000000..13b2914ffb87b66e93d201f11cebcca585ffb828
--- /dev/null
+++ b/content/posts/2025-03-25 Deleting Intune Users.md
@@ -0,0 +1,21 @@
+---
+title: Deleting Intune Users (Because I forgot about the registry)
+date: 2025-03-25T12:51:26+00:00
+draft: false
+tags:
+ - windows
+ - sysadmin
+ - intune
+---
+So, you ran out of space on an Intune managed device.
+Like mine, your first inclination may be to delete the user folders in the c:\users directory via booting into a USB drive. However, this will break those deleted users when they try to sign in again, instead logging them into a temporary account.
+When running CMD, your user profile location seems to be `C:\Users\YOURDOMAIN.TEMP` but `whoami` returns `yourdomain\user`. Hmm.
+
+The solution? Delete the users from the registry too, else Windows will complain.
+
+Go to regedit from a local account (or from a recovery USB importing the hive):
+`HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList`
+
+Then delete all the Intune users whose folders you deleted. These will probably begin with `S-1-12-1`. Be careful not to delete the folder or the registry entry of the user who enrolled the computer, otherwise bad things may happen - I don't know but I suspect that user disappearing may be a problem for how Intune works.
+
+Log out, reboot, and it should work.
\ No newline at end of file