AzureAD and shares
-
@coliver said in AzureAD and shares:
Move everything to Sharepoint or OneDrive for Business. That would make the most sense in this case.
Yeah, Sharepoint is my guess.
-
@brandon220 said in AzureAD and shares:
@IRJ @Obsolesce They actually want a DB for this data but keep finding subpar developers and wasting money.
I happen to know a company that does custom software solutions.
-
@brandon220 said in AzureAD and shares:
@Dashrender I only know if them using OD. I'd have to ask.
OD or ODfB. they are different things.
-
@JaredBusch I am going there this eve and I will mention it. Is it Bundy?
-
@brandon220 said in AzureAD and shares:
@JaredBusch I am going there this eve and I will mention it. Is it Bundy?
Yes, it is something we have done since the 1980's.
But custom software is not cheap. Most likely your client could resolve their problem cheaper with better workflow. -
@JaredBusch They want it to be correct and more efficient. They don't mind spending the money if the end result is a working product. The guy that wrote their current application (in C++) was self-taught. It does what they need for the reporting, but he did not totally finish all the bells and whistles on it.
-
They were using ODfb with the Office 365 Business Premium. I am convinced that the root of the problem is that they had 20 employees syncing to the same "account" such as office.company.com They are trying to do the same thing now with Nextcloud. I can't get through to them that the "field" guys need to only do a file drop to the server and stop trying to sync everything.
-
This company 100% needs a web app with a database backend ASAP. It would alleviate the majority of their problems.
-
@brandon220 said in AzureAD and shares:
This company 100% needs a web app with a database backend ASAP. It would alleviate the majority of their problems.
Most do. It's a really common need.
-
I think my best plan of action is to scrap AzureAD as they will never have servers hosted on Azure. I can pretty much guarantee this. I realize there is a hybrid approach but that just adds more complexity. My best option IMO is to spin up 3 new VMs - 2 AD/DNS and 1 file server. I know AD doesn't make much sense with 20 employees but it seems managing users in a regular "workgroup" with local accounts would take more effort. Am I wrong?
I confirmed yesterday that they prefer to have files accessible on the LAN versus through a web client/webdav. It has to be fast and reliable. They are 100% a MS shop so I think a Linux server with samba shares may not make sense. -
@brandon220 said in AzureAD and shares:
I think my best plan of action is to scrap AzureAD as they will never have servers hosted on Azure.
Not arguing against scrapping AzureAD, but hosting servers on Azure is really in no way a decision factor there. That's neither here nor there in deciding if AzureAD is for your or not.
-
@brandon220 said in AzureAD and shares:
I know AD doesn't make much sense with 20 employees but it seems managing users in a regular "workgroup" with local accounts would take more effort. Am I wrong?
For me, managing local users is normally easier at that size. But you are into the grey area where it can go either way. But two servers, all that cost and management and maintenance and updates and licensing alone, is more time and money than managing the users without it nine times out of ten. I could manage the users of 20 devices faster than you could even discuss getting AD.
-
@brandon220 said in AzureAD and shares:
I confirmed yesterday that they prefer to have files accessible on the LAN versus through a web client/webdav.
WebDAV and LAN is the same thing to most people. Those aren't competing concepts. WebDAV and SMB shares are "the same thing." Both are "LAN mentality mapped drives." WebDAV works better over a WAN than SMB, but both are the same category of item, rather than alternatives.
-
@brandon220 said in AzureAD and shares:
They are 100% a MS shop so I think a Linux server with samba shares may not make sense.
Why? In what way would a Windows FS be superior?
By this logic, no shop would ever use NAS, SAN, or things like BSD, because they are not the OS of the desktops. Or Mac because it can't be used as a server. There can be a case, in extreme circumstances, where homogeneity itself has some value, but it's so rare that it should generally be simply discounted.
-
@brandon220 said in AzureAD and shares:
They are 100% a MS shop
I get this is only true, because it is true, if you know what I mean.
Buy one laptop, it's Windows... you are a 100% Windows shop.
Buy a second desktop, it's Windows... still 100% Windows.
Start saying "we are 100% Windows" and you automatically start making it come true. Not because it made sense, or even was a decision, you just hadn't gotten around to putting in or counting the other equipment yet. At some point, shops tend to be making these decisions based on this quote, more than on business decisions.
-
@scottalanmiller said in AzureAD and shares:
@brandon220 said in AzureAD and shares:
I confirmed yesterday that they prefer to have files accessible on the LAN versus through a web client/webdav.
WebDAV and LAN is the same thing to most people. Those aren't competing concepts. WebDAV and SMB shares are "the same thing." Both are "LAN mentality mapped drives." WebDAV works better over a WAN than SMB, but both are the same category of item, rather than alternatives.
WebDav is painfully slow for me, especially when connected to Nextcloud from a Windows 10 machine. I've tested this with multiple NC servers and different W10 clients, and at different locations. Browsing files and folders is fine. Opening, losing, and saving things take way longer than it should.
-
@scottalanmiller said in AzureAD and shares:
@brandon220 said in AzureAD and shares:
They are 100% a MS shop so I think a Linux server with samba shares may not make sense.
Why? In what way would a Windows FS be superior?
By this logic, no shop would ever use NAS, SAN, or things like BSD, because they are not the OS of the desktops. Or Mac because it can't be used as a server. There can be a case, in extreme circumstances, where homogeneity itself has some value, but it's so rare that it should generally be simply discounted.
My logic here is: If the client wants to add a share on the MS server, they can easily do this themselves. If you throw samba in the mix, I feel they would struggle to understand why they are not using a MS server first, and then struggle to actually create a usable share in a system they know nothing about.
If it were for me, it would be samba 100%. I have to "fight" people all the time who will argue to the death that they don't want a Linux server of any type, because it is "free" and "not secure". I know we talk about audits all the time here on ML. The auditors, especially in the financial sector, argue this all the time and try to penalize you for using FOSS tools.
-
@brandon220 said in AzureAD and shares:
@scottalanmiller said in AzureAD and shares:
@brandon220 said in AzureAD and shares:
I confirmed yesterday that they prefer to have files accessible on the LAN versus through a web client/webdav.
WebDAV and LAN is the same thing to most people. Those aren't competing concepts. WebDAV and SMB shares are "the same thing." Both are "LAN mentality mapped drives." WebDAV works better over a WAN than SMB, but both are the same category of item, rather than alternatives.
WebDav is painfully slow for me, especially when connected to Nextcloud from a Windows 10 machine. I've tested this with multiple NC servers and different W10 clients, and at different locations. Browsing files and folders is fine. Opening, losing, and saving things take way longer than it should.
WebDAV is slow, but SMB is slow compared to NFS
But they are the same tech category, all of them. Some are fast, some medium, some slow, but not different kinds of things. -
@brandon220 said in AzureAD and shares:
My logic here is: If the client wants to add a share on the MS server, they can easily do this themselves. If you throw samba in the mix, I feel they would struggle to understand why they are not using a MS server first, and then struggle to actually create a usable share in a system they know nothing about.
That's good logic, but important to understand that it isn't being Windows or homogenous that makes that true, it's that Samba is a bit complex. EXCEPT, you can get Samba interfaces that are even easier than Windows, and so that same logic could dictate not using Windows.
Also, if they don't 100% understand why they are or are not spending money on an MS server, they are not in any position to ever make these decisions and/or touch any server, Windows or otherwise. In fact, this completely makes Windows the worst option because it will empower them to do all kinds of bad things like break security or functionality.
-
@brandon220 said in AzureAD and shares:
The auditors, especially in the financial sector, argue this all the time and try to penalize you for using FOSS tools.
No actual auditor, quite the opposite.
