Isn't OneDrive/Sharepiont the exact OPPOSITE of a shared drive?
Isn't OneDrive/Sharepiont the exact OPPOSITE of a shared drive?
Background:
- At work we use MS Office, because who doesn't. We used to have a central file server with lots of well sorted directories.
- Then Corporate decided to ditch that, everything must move into OneDrive so there's always a Data Owner.
- The local boss had to move everything from the network share into his own OneDrive, and then share, with each of us, the folders that were relevant to each of us.
- This sounds like distributed storage, which is probably smart in some way.
In reality, it's shit. Everything is now a link to "corporateName.sharepoint.com" in the browser, and it's a hassle to find that in the file explorer. SOmeone just shared a folder with me. I see it in my browser. How do I get it from the browser into a normal folder view? Should I forget about on-disk storage; is everything today just a browser bookmark?
Worse, I have no idea what's where. Some people share some stuff and somehow it ends up in my OneDrive, but what's the context of it?
This seems so wrong to me. Am I just not "getting" it??
It. Is. The. Worst.
Someone shares a file directly, another shares the whole folder, someone else makes a Team, which automatically creates its own sharepoint site that has its own document library. Now someone else shares a file via a Community sharepoint site they have, which is somehow different than a Teams site. The Community site also has its own document library.
Oh and sharepoint is also onedrive? But also isn’t, somehow. I never know. I can sync some stuff to one onedrive folder, and some to another onedrive folder. But it’s all also the same.
To answer your question, you are not alone.
Permanently Deleted
I'm pretty sure in an Enterprise Environment OneDrive is just a SharePoint Frontend.
OneDrive is really just an alias for a networked drive that points to a cloud location and is baked into every instance of Windows. Most OneDrive instances are for personal computers and they're inaccessible to everyoen else. But you can manually share files.
SharePoint is a flexible enterprise website and fileserver for an organization to customize.
Teams is a Slack ripoff that allows employees to create teams with channels within those teams, and freeform chats. It also has a filesharing component to it.
It is awful to work around the half-dozen ways to store and share files. Really. Microsoft needs to unfuck this.
The difference between one drive and SharePoint is their intended use, nothing physical.
OneDrive is for personal files you occasionally want to collab on. Sharepoint is for collaborative files you want occasionally restrict. They have opposite purposes and are tooled around those purposes.
Both are sitting on the same hardware and have very similar underpinnings, but their front ends serve two distinct purposes.
A lot of your frustrations are stemming from your M365 environment being misconfigured. While all that is possible behavior, in a well-configured environment it makes sense and works well. It sounds like many of the features that are open there should in reality be restricted in order to allow a better user experience as much of that function is unneeded by your particular group.
This constant bundling is crazy for actually finding things. Always like four places to check.
Your boss did this not the best way*. They should have created a SharePoint site, maybe a few extra document libraries within that site, and have the files in there. Then added people as members to the site, maybe lock down a few of the document libraries/folders as required to specific people.
Then for ease of use people can open the libraries and click the sync button. Although if you have too many it'll slow down/break.
OneDrive/SharePoint is not a drop in replacement for a file server, and those honestly still find their use, but a lot of places with a bit of re-structuring can work just as well if not better through SharePoint . Especially if they put in the effort to start using other SharePoint features.
Exactly! If it's a small company, it may be an option to make a Teams everyone has access to and adapting the SharePoint behind it as the home page for the company, with different libraries depending on who needs access. At my company there is constant confusion between the SharePointsites the IT team set up for them and the SharePointsite behind their Teams, makes me think it is probably better to just use the SharePoint that's forced on you by creating a Teams.
Can I view sharepoint in the file explorer, or is that only in the browser?
Once the SharePoint site is set up, your team should then sync the directory
This allows for 'local' file browsing. Works very well and keeps my entire team in sync. I've never had any major issues with this setup. I also make sure to set important files that I work on regularly to "always keep on this device' (https://support.microsoft.com/en-us/office/save-disk-space-with-onedrive-files-on-demand-for-windows-0e6860d3-d9f3-4971-b321-7092438fb38e)
The sharepoint itself - browser only
The document libraries (the sections of a sharepoint site that store files)* - there is a "sync" button you can press to get them into the OneDrive client on your PC, and therefore into file explorer. (It's also possible for admins to automate this)
You could with the old SharePoint, but they took that feature away. The way around it is to open the SharePoint link in Edge, then bottom left "Return to classic SharePoint", then Edge settings > Launch in Internet Explorer mode. After that you should now have a SP tab called library (you may need to click around the SP ribbon for it to appear) and in that tab should be "Open in File Explorer".
The problem is that your files are in OneDrive instead of SharePoint. OneDrive is for personal files that you occasionally want to collab with others on. SharePoint is for collaborative files that you occasionally want to restrict.
One is meant to be closed most of the time, the other open most of the time. And the way sharing and other features work within the tends to reflect that charactistic.
Your team files need to be in a SharePoint library. It is possible to have a direct link in the file explorer to the SharePoint files and run everything as if it is a local file server. MS is seemingly trying to move away from that and keeping the browser open to the document library has mostly the same functionality with some minorly different steps.
But it sounds to me like your IT dept doesn't have enough experience with M365 to know how to handle this properly.
Yeah. 100% missing it. Having owners as well as the ability to set labels and restrictions is an incredibly important part of keeping data sensitive.
Get them in explorer following https://support.microsoft.com/en-gb/office/view-sharepoint-files-in-file-explorer-66b574bb-08b4-46b6-a6a0-435fd98194cc
Wait until Corporate sees the new data storage rates for 365 for next year and their potential new bill for cloud storage.
They'll be spinning up those server room file servers in no time.
Working in IT, I understand the frustration.
There's a couple ways to do it, but you can add SharePoint to your OneDrive on your PC, it shows up basically the same as any of your OneDrive files in Explorer.
Apparently there's a way to map it to a drive letter as well, but it gets complex pretty quickly and as far as I know, you need to get the link to paste into the mapped drive dialog from the object owner... I might be wrong here.
Google it. You'll improve your life so much.
As an IT person, I was going to suggest this too. Glad you brought it up first.
Hello fellow IT Patsy. I hope you're having an uneventful day.
This seems so wrong to me. Am I just not "getting" it??
You are right. It is all chicken shit.
If you still use the desktop versions of MS Office, you can use the 'favorites' feature inside each program, for some files at least, to avoid the ugly URLs
Or, what I even prefer, 'pin' some files to your task bar.
I'm not going to pretend that it works great but it sounds to me like you need to know how it works a little better
Heh, if only I were in a position to change anything. Maybe bosmang should be smarter, and move it from OneDrive to SharePoint. Who gonna explain it to him?
If you do a little research and figure out how to get it setup you can share that knowledge with your boss. There are SOME things that could depend on how IT or the SharePoint owner configured things - like at my job there's one SharePoint where they turned off linking it in my OneDrive - but otherwise you should be able to get it close to how it used to be.
It's definitely silly for your boss to keep it all in his onedrive and sharing it out. OneDrive is supposed to be personal storage that you CAN collaborate on. SharePoint and Teams (basically SharePoint on the back end) are where team-wide storage should be. But, having gone through a transition to M365 I understand they probably just don't understand and did what they thought they could.
You're perfectly right. But those who decide, sales or decision makes, don't understand that. So it's easy to sell them some shitty thing and empty promises. They trust another salesman a lot more than their own tech guys anyway.
I'm sure everyone working in office 365 has this problem to some degree. My (pessimistic) guess is that Microsoft is aware of these problems and in stead of solving them in SharePoint itself, they create more programs to help organising. Like now you can find your files through Bing connected to your workspace (which is just to try and get people to use bing?). There is also delve and such that shows you what you last worked on regardless of its location. And soon we will have the AI co-pilot, which I'm expecting will make things even worse since it will grab anything you have access to and not bother with original context. I don't know what the endgame is here, maybe make people and companies dependent on these kinds of programs?
In SharePoint: Add shortcut to OneDrive In OneDrive: tell it if, or how, to save the folders locally.
Use File Explorer, like I think you'd prefer.
It does not work perfectly.
And it freaks the fuck out if that folder name exists. Like if you have a documents folder in a project's sharedrive, you can't add it to yours because documents exists.
The "add shortcut to onedrive" option defaults to your root onedrive, and doesn't differentiate what the original one drive name was.
I didn't see an option to change where the shortcut is made, it just defaults to root. You can manually move the shortcut after it is created though. But this was a pain last time I tried it.
Same with mapping a teams group shared folder. We have a teams for each project, and a resources folder in that. It is a pain to open teams, so I tried mapping it to my one drive where I already have a folder for each project. So you go to teams, "add shortcut to onedrive", go to your one drive folder and drag that shortcut to the appropriate folder, then repeat. Oh but project 3 is named differently and that folder name already exists in your one drive, here is some vague error. Ok, rename what I have in my onedrive, try to add the shortcut again, move shortcut, rename the file in my onedrive root back to what it was.
That dialog should just ask for a export location.
Using MS Teams for class is the worst... I do not know most of the time where the files in those assignments' turn-in will end up.
We use it at work and send pics attached and I never know where to find these pictures again other than scrolling through messages. Apparently they're saved somewhere because I often get warnings that attachments "already exist" due to having the same filenames. We often hop around to different shared PCs and OneDrive has the lovely effect of duplicating desktop shortcuts along with not transferring the icon images to each PC so they're all the same generic shortcut icon.
Click on the files tab. It's right there.
You can add a second OneDrive to your local folders. Right click the little cloud icon, navigate to your account details and add an account from there.
I added my orgs Sharepoint so that I could see everything locally without all the palaver.
We use SharePoint and everything just shows up on my desktop computer as a drive like it always did before when it was on a local server. Works really well.
Until the directory structure and filename, including your SharePoint hostname, exceeds 400 characters and then it just breaks. Because, Microsoft.
Surprisingly easy to do with some quite nested folders with spaces in the names (as that takes 3 characters per space) and a long filename.
Does it show up as a local drive or a network drive?
Considering my personal onedrive wants to share everything I share with write permissions to the general public I've had a different experiance. But I certainly understand your point.
That - good sir - is a very valid argument
How do I get it from the browser into a normal folder view?
There's a setting which the sharepoint admins can set which allows Windows Explorer view.
To access https://sharepoint.company.com/team_a what you'll do is open windows Explorer and navigate to "\\sharepoint.company.com\team_a" (starts with double back slash, without the quotes)... You can even map it as a network drive on your system, so you can have an X: drive which maps to that same location and you can use it like a normal shared drive...
Edit: I take back my comment. This method doesn't work anymore, except for pre-SharePoint 2019 on-prem environments...
Permanently Deleted
Well that's sad...
I could not make this work; I think the other commenters are right, this does not work.
Serious answer. You are getting it. Who decided to set up your processes and system doesn't do daily business neither understand of computer.
I am sorry. Best option for you is to search a place better managed. Alternatively accept the loss of productivity. And go on. All your company is going to be less productive anyway.
Hmmm do we work for the same company?... or are all the big ones doing this?
I sincerely hope for your sake we're not in the same boat. This one ain't fine.
You kind of are. All large corporations have similar annoyances, but slightly different people and technologies. After a while (maybe 20 years of working for 10 different corps) it feels like you have seen it all, and it's just mediocre crap everywhere.
My guess is that the problem is it is cheaper to implement in SharePoint than to teach the company to do it with files and enforce policy. A lot of people don't know how computers work.