this post was submitted on 12 Mar 2024
1949 points (99.2% liked)
Technology
57435 readers
3682 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One drive is the one that really ruffles my feathers.
It turns itself back on randomly, which wouldn’t be too much of a problem except for that it fucking remaps the desktop.. a file that was previously located at C:\user\desktop\ is now at C:\user\One Drive\desktop…
Note the space in the path, they didn’t even have the decency to use an underscore… \one_drive\… even though it’s one of their own rules in powershell scripting.
For those of us using powershell to automate stuff this remapping is a nightmare and should be illegal.
Too bad I am in the US and will just have to continue to get support calls from time to time when a users desktop gets remapped behind the scenes.
Maybe there is a way using powershell and windows scheduled tasks to check to see if one drive turned itself back on, then auto turn it off and remap the desktop back to normal.
The absurdity of having windows check to see if windows screwed itself up, then if so have it fix itself is just laughable.
OneDrive redirection is hilariously bad. Official Microsoft documentation recommends against using it. Imagine having that little faith in your own product.
Why aren't you string quoting all of your paths anyway? I'm confused because the vast majority of paths wouldn't work the way you're suggesting.
Yeah, I reflexively double quote every path. It's still stupid though.
Even something as simple as:
Stops working as intended when your desktop no longer resides at that path.
Also, I have the same functions running on multiple machines with different names so I have to dynamically resolve the path and piece it together using strings.
Okay, so if your source path changes, your script stops working? Who knew. Try ([Environment]::GetFolderPath("Desktop"))
I am using that already, but if I recall, it’s the space in the path ‘\one drive\’ that makes that not work correctly.
Edit: I am actually using $Env:UserName
Yeah the deeper path might help.
Basically the thing to remember about powershell that separates it from other scripts is you want to pipe pipe pipe your data as far as possible so it stays an object, and then output a string at the very end - there's no tons of awk sed string manipulation like in bash, partly because of what you pointed out with how terminal input is interpreted.
It’s only happened twice, after updates, that windows turned one drive back on and remapped my desktops. In those cases I have just turned it back off and remapped back to normal. Then env:username works again and I think the only difference is the space in the path with one drive, though it could be something else breaking when the desktop gets remapped.
I’m probably using powershell all wrong anyways because I am an amateur.
I use it to grab a file from an sftp by calling on winSCP, then convert from csv to xlsx using the excel module, then run a bunch of VBA to reformat the file, then save the xlsx with a date stamp. I use task scheduler to run it daily and I have it on like 10 machines.
Works great when one drive doesn’t mess with my desktop path.
What pisses me off even more is if you start saving too much stuff in your documents/desktop etc you start getting emails from microsoft that your drive is full and you have to purchase more storage (because your harddrive is likely much bigger then your free drive account).
So I know quite a few elderly people who think they now need to pay money to unlock more memory on their computer to save more stuff.
That’s criminal, preying on the elderly. Basically a tech support scam but it’s actually Microsoft running it
I'm always surprised at how brazen the corporations are in the US. That kind of shit wouldn't fly in Europe.
I spend so much more time reading labels in the US than in Europe (with so much head shaking).
Sounds like a weird behavior, are you using Microsoft account for sign-in? Maybe that somehow triggers enabling sync back. Switch to local account if you do not want any benefits MS account gives.
That OneDrive feature is called Known Folder Move and it can be easily disabled. In theory it's a great feature for most, but I dislike it as well.
I have OneDrive disabled and have never seen it restart automatically.
I have like 10 machines at 5 different locations. In order to share my 365 subscription across multiple machines, I have to have them signed into a Microsoft account. I need excel and ms access working on all my machines.
It’s happen twice since I implemented windows 11, both times after major windows updates.
Not too much trouble to re disable one drive and switch everything back to normal but it breaks a bunch of stuff for me when it happens.
You know you can completely disable onedrive using GPOs?. I have done so on a DC i have but it shut also be possible using local GPOs.
That's so weird. I was just praising M$ to myself because I noticed that they are using \OneDrive\ and \Documents\ now and no spaces to be found.
Nice that might have been something they fixed.