Server 2019 Essentials - Domain controller requirement
-
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Is there any reason to use Essentials vs Windows Server Standard? Is there a good argument to have local hardware vs hosting on the cloud? It would take a while to get hardware costs back on such a small installation for so few users.
Essentials is cheaper. And there is no use case for the second VM of Standard. Has to be local for performance and reliability. Most customers using the software he is talking about have flaky Internet. And hosting on cloud would be quite expensive given the Windows requirement. Would take no time for the cloud to cost way more than the on-premises deployment.
-
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Why not just use Linux at this point? If you aren't using AD and don't want any additional overheard. Then just use Linux
They have a Windows based application that runs on the server. Linux isn't an option.
Why not segregate duties virtually then? Have file shares on Linux and have your app run on Windows?
That wouldn't work for this program. Windows is a requirement for this case.
I hear companies say that alot, but they dont always have a valid reason. SMB is SMB.
Fine but the question is about Windows 2019 as to if you have to promote it to a DC
From what I can find here and in the Work Remotely section there is no requirement for a domain.
-
@DustinB3403 said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Why not just use Linux at this point? If you aren't using AD and don't want any additional overheard. Then just use Linux
They have a Windows based application that runs on the server. Linux isn't an option.
Why not segregate duties virtually then? Have file shares on Linux and have your app run on Windows?
That wouldn't work for this program. Windows is a requirement for this case.
I hear companies say that alot, but they dont always have a valid reason. SMB is SMB.
Fine but the question is about Windows 2019 as to if you have to promote it to a DC
From what I can find here and in the Work Remotely section there is no requirement for a domain.
That's what I was thinking but wanted to verify in case I was missing something.
-
You could also download the essentials trial from microsoft, deploy it and confirm that everything will work as expected before having the client buy Essentials (and have worries about needing a domain).
-
@DustinB3403 said in Server 2019 Essentials - Domain controller requirement:
You could also download the essentials trial from microsoft, deploy it and confirm that everything will work as expected before having the client buy Essentials (and have worries about needing a domain).
We purchased Essentials and have loaded it. We had the expectation that we would need to setup a domain and just not use it. When it didn't force us into creating a domain this question came up.
-
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Why not just use Linux at this point? If you aren't using AD and don't want any additional overheard. Then just use Linux
They have a Windows based application that runs on the server. Linux isn't an option.
Why not segregate duties virtually then? Have file shares on Linux and have your app run on Windows?
That wouldn't work for this program. Windows is a requirement for this case.
I hear companies say that alot, but they dont always have a valid reason. SMB is SMB.
Fine but the question is about Windows 2019 as to if you have to promote it to a DC
No one here knows - we don't run that software.
-
@scottalanmiller said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Is there any reason to use Essentials vs Windows Server Standard? Is there a good argument to have local hardware vs hosting on the cloud? It would take a while to get hardware costs back on such a small installation for so few users.
Essentials is cheaper. And there is no use case for the second VM of Standard. Has to be local for performance and reliability. Most customers using the software he is talking about have flaky Internet. And hosting on cloud would be quite expensive given the Windows requirement. Would take no time for the cloud to cost way more than the on-premises deployment.
Cheaper, but shittier. Essentials has had more weird problems ever since I can remember.
-
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
No one here knows - we don't run that software.
No one here runs Server 2019 Essentials?
-
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
Why not just use Linux at this point? If you aren't using AD and don't want any additional overheard. Then just use Linux
They have a Windows based application that runs on the server. Linux isn't an option.
Why not segregate duties virtually then? Have file shares on Linux and have your app run on Windows?
That wouldn't work for this program. Windows is a requirement for this case.
I hear companies say that alot, but they dont always have a valid reason. SMB is SMB.
Fine but the question is about Windows 2019 as to if you have to promote it to a DC
No one here knows - we don't run that software.
Read the documentation, it's clearly available.
Also "Get Connected", nothing list a DC as a requirement.
-
This is the only think on Getting Connected that raises a flag.
A client computer that is already joined to another Active Directory domain cannot join a Windows Server Essentials domainWhich, I would read as "if you have a domain, then essentials needs to be the DC". Not that you are required to have a domain. But that MS made an assumption you would have one anyways.
-
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
No one here knows - we don't run that software.
No one here runs Server 2019 Essentials?
No - most here run standard Windows Server or some flavor or Linux. Essentials is only for SUPER tiny environments (I think it's limited to 25 connections)... a version that at least with 2012 didn't require User CALs, making it significantly cheaper for super tiny shops that required Windows, but once you hit over 25, you got a HUGE upgrade cost i.e. full server license and 25+ CALs.
-
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
No one here knows - we don't run that software.
No one here runs Server 2019 Essentials?
No - most here run standard Windows Server or some flavor or Linux. Essentials is only for SUPER tiny environments (I think it's limited to 25 connections)... a version that at least with 2012 didn't require User CALs, making it significantly cheaper for super tiny shops that required Windows, but once you hit over 25, you got a HUGE upgrade cost i.e. full server license and 25+ CALs.
I understand most prefer linux, but I doubt that no one here runs Windows Server 2019.
-
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
No one here knows - we don't run that software.
No one here runs Server 2019 Essentials?
No - most here run standard Windows Server or some flavor or Linux. Essentials is only for SUPER tiny environments (I think it's limited to 25 connections)... a version that at least with 2012 didn't require User CALs, making it significantly cheaper for super tiny shops that required Windows, but once you hit over 25, you got a HUGE upgrade cost i.e. full server license and 25+ CALs.
Yep. It is generally not reliable either. At least earlier version weren't. Throw all MS services on one piece of underpowered hardware and then throw all your apps over it. What could go wrong?
-
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
No one here knows - we don't run that software.
No one here runs Server 2019 Essentials?
No - most here run standard Windows Server or some flavor or Linux. Essentials is only for SUPER tiny environments (I think it's limited to 25 connections)... a version that at least with 2012 didn't require User CALs, making it significantly cheaper for super tiny shops that required Windows, but once you hit over 25, you got a HUGE upgrade cost i.e. full server license and 25+ CALs.
I understand most prefer linux, but I doubt that no one here runs Windows Server 2019.
Server 2019 sure, but not essentials
-
@scottalanmiller said in Server 2019 Essentials - Domain controller requirement:
@Mike-Davis said in Server 2019 Essentials - Domain controller requirement:
@CCWTech Even with only 4 users, wouldn't that mean create 4 user accounts on the server and then manage 4 user accounts on 4 machines. I supposed you could use the net user command in screen connect, but setting up a domain is so easy.
Not as easy as running "net user". One command sequence four times is nothing.
But why the assumption of four user accounts per machine? That's not normal in small businesses. People with AD always assume that, but I've almost never seen an SMB that used more than a couple like that. The "everyone will log in as their own account, and on every machine" theory is an extreme niche edge case, not at all the norm.
Assuming the OP uses the router to host DNS instead of the server, I'm assuming the router will also have an internal DNS table to make finding internal resources easier as well?
Of course in a mostly static environment - it could all be setup manually by hand in the first place - but gawd... talk about suck.
-
Here is you answer, although it's completely convoluted answer. Read the purple bit, and then the highlighted bit.
-
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
No one here knows - we don't run that software.
No one here runs Server 2019 Essentials?
No - most here run standard Windows Server or some flavor or Linux. Essentials is only for SUPER tiny environments (I think it's limited to 25 connections)... a version that at least with 2012 didn't require User CALs, making it significantly cheaper for super tiny shops that required Windows, but once you hit over 25, you got a HUGE upgrade cost i.e. full server license and 25+ CALs.
Yep. It is generally not reliable either. At least earlier version weren't. Throw all MS services on one piece of underpowered hardware and then throw all your apps over it. What could go wrong?
I guess i was lucky - when they started calling it Essentials - there weren't that many services left - File/Print/AD/DNS/DHCP and what WSUS? that's all pretty typical single box stuff in my mind. WSUS could be shit for sure, but the rest can work together no issues.
Back when it was SBS server and had Exchange and possibly a corporate firewall and SQL server - OMG - yeah, kill me now!.
-
@DustinB3403 said in Server 2019 Essentials - Domain controller requirement:
Here is you answer, although it's completely convoluted answer. Read the purple bit, and then the highlighted bit.
Sure that says you can add a computer to it - not that a Domain isn't required.
Though - Since it doesn't seem to be making you setup a domain - I can't imagine it would be required any longer... though the idea of using a server in a 25 user environment and not having one, not my choice.
-
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
No one here knows - we don't run that software.
No one here runs Server 2019 Essentials?
No - most here run standard Windows Server or some flavor or Linux. Essentials is only for SUPER tiny environments (I think it's limited to 25 connections)... a version that at least with 2012 didn't require User CALs, making it significantly cheaper for super tiny shops that required Windows, but once you hit over 25, you got a HUGE upgrade cost i.e. full server license and 25+ CALs.
Yep. It is generally not reliable either. At least earlier version weren't. Throw all MS services on one piece of underpowered hardware and then throw all your apps over it. What could go wrong?
I guess i was lucky - when they started calling it Essentials - there weren't that many services left - File/Print/AD/DNS/DHCP and what WSUS? that's all pretty typical single box stuff in my mind. WSUS could be shit for sure, but the rest can work together no issues.
Back when it was SBS server and had Exchange and possibly a corporate firewall and SQL server - OMG - yeah, kill me now!.
That's just the out of the box stuff that can be simple solved off windows very easily
Dont forget that these businesses like to throw quickbooks and other poorly made sofware on their Essentials server including these other services which are already too much to have on one box IMO. It's 2019, virtualize
-
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
@IRJ said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
@CCWTech said in Server 2019 Essentials - Domain controller requirement:
@Dashrender said in Server 2019 Essentials - Domain controller requirement:
No one here knows - we don't run that software.
No one here runs Server 2019 Essentials?
No - most here run standard Windows Server or some flavor or Linux. Essentials is only for SUPER tiny environments (I think it's limited to 25 connections)... a version that at least with 2012 didn't require User CALs, making it significantly cheaper for super tiny shops that required Windows, but once you hit over 25, you got a HUGE upgrade cost i.e. full server license and 25+ CALs.
Yep. It is generally not reliable either. At least earlier version weren't. Throw all MS services on one piece of underpowered hardware and then throw all your apps over it. What could go wrong?
I guess i was lucky - when they started calling it Essentials - there weren't that many services left - File/Print/AD/DNS/DHCP and what WSUS? that's all pretty typical single box stuff in my mind. WSUS could be shit for sure, but the rest can work together no issues.
Back when it was SBS server and had Exchange and possibly a corporate firewall and SQL server - OMG - yeah, kill me now!.
That's just the out of the box stuff that can be simple solved off windows very easily
Dont forget that these businesses like to throw quickbooks and other poorly made sofware on their Essentials server including these other services which are already too much to have on one box IMO. It's 2019, virtualize
Right?!
Oh we also have QuickBooks (is it at least from this year?) No, it's from 2000 (Wonderful. . . )
