Don't forget tools to manage the workstations. In a LANLess design, you can treat the workstations like they're on a public network and crank the firewall up, and that means you don't rely on the LAN to manage/access workstations.
I'd say you're most of the way there with just Office 365 or GSuite only if you've gone all the way in (which for GSuite requires Chromebooks unless you're all BYOD)
We actually have GSuite at my part-time position right now, I just need to get people to actually USE IT. Yep.
Good luck with that. We have GSuite at my job too, but there's no incentive to fully use it. There's a disconnect between their regular AD login and their GSuite account, and so it doesn't make sense for users to start using this service that seems separated from everything else, and there doesn't seem to be any way to script Google Drive. It makes sense with Chromebooks, since everything gets linked together, and it would make sense with BYOD since your Google account is "how you get in" to the company resources. So unless company culture and structure changes (i.e. get rid of SMB access to the fileserver) there's no good way to ease them into it.
At with Office 365, from what I hear, you can do SSO with Onedrive and then do redirected folders into the Onedrive folder. Currently I'm working on coming up with a solution using Syncthing.
You can try setting up G Suite Password Sync (GSPS) to get your AD passwords insync with their GSuite account
Yes, but there is still a disconnect even if the password is the same. I sign and access the files I need vs I sign in and access the files I need and also need to sign into Google file sync/stream. An optimum user abstraction would make it seem to the user that there is only one 'place' where their files are and they don't have to think about it.
That's not the way of the world anymore.
Heck MS tried to bring that back (at least in mobile with their HUBS idea - but we all know where that is now). Each vendor wants it's own branding front and center.
It is achievable with open source tools, but it's kind of a stop-gap thing while we are still exposing users to the OS filesystem
Give me an example of your achieved via open source tools solution, please.
I not 100% sure we are talking about the same thing, but here it goes.
I'm almost done creating a Salt collection (I should turn it into a Salt Formula) that uses Syncthing to Sync folders like Desktop, Documents, etc to a Syncthing 'master' server (essentially replacing Folder Redirection). Therefore whenever one of my user logs on to a workstation that I manage with Salt, their files will get synced without needing to be on the same LAN, just internet connection required.
It might be possible to do something similar using the Google Drive API
This sounds good, but is it tenable for someone with many gigs on their desktop? If we discount laptop/mobile users for the moment, the idea of working off cloud only stuff, i.e. no local sync, there's no syncing required at all.
Offline access is the sticking point in this.
If you have policies in place that prevent huge amounts of data/files from needing to be synced, then the above mentioned syncing solution might be doable for regular users, but in the wild west of people having huge amounts of things to be synced, especially to a new machine, that's a super slow logon process.
You're missing the point that the data and apps live on the servers, and not on the local workstation. Syncing to the workstation actively inhibits use.
LANless design should ideally be done under the a DevOps mindset, which in this situation means that you shouldn't be doing something counter-intuitive to users even if it is 'the best way' for IT to do it.
@Dashrender has a good example with CAD. We are still limited by programs that meet business needs, and business needs come first. We can now easily manage workstations, so that should not be an excuse to invest in expensive infrastructure that we say is 'easy for IT' but less intuitive for users.