2012 Essentials rant

Can you clarify what exactly you're looking for in responses? It might help you get the kind of thread you're clearly going for.

2012 Essentials worked fine running in a VMware environment managing 8-10 machines at any given time. It's not great but it's not that bad, the addins from WHS make it quite useful in small scale environments. Frankly most of the small businesses I see should probably be running thin clients to an AWS or Azure infrastructure anyway with how poorly they're setup.

Yeah and all small businesses want to go the cloud. :rolleyes: and pay absurd amount for hosting VDI. VDI cloud hosting is not viable for small businesses.
Its a turd. Its an abomination, try to get exchange working with it with out hacking the shit out of this castrated piece of shit. SBS Essentials is a POS.

Why the would you virtualize this for 8 machines?
 
100% truth.

The same people whined about the XP start menu.

The great thing about win8/srv2012 is that I can literally never leave the kybd. I love it. I barely use my mouse anymore when working.

Your both noobs. Powershell.
//
enter-pssession
//
End of story.

Actually I leave my Keyboard all the time because I use Kaseya, N-Able, and SCCM. If you are managing server directly that's your problem.I hate the start menu because it lags the shit out of RDS.
Still I use Powershell more and more. Soon enough we will be back in Novell days.
 
The sole difference is the lack of the start menu, a useless tree of mousable shortcuts buried within menu nodes, which nobody uses because it's much slower than using the search functionality or other means of opening things. Regardless of which OS you're using, the efficient way of doing things is to utilize the expressiveness of the keyboard. You may be in the small minority who would rather waste time clicking through a start menu, but that is an old style of GUI and will remain in old operating systems only. Sometimes to move things forward, you have to leave legacy behind. Microsoft kept the desktop the same sans its one dated shortcoming, and if you're not concerned with the old world start menu, the desktop interface on both operating systems is the same.

Heh you're so out of touch with reality. Only the power users who know the OS and the apps like the back of their hands use keyboard or search. The 99% of the users have to use menus to guide them towards the things they need.

You're a typical example of a techie who lives in a bubble. There's even a study that found out that Microsoft personnell had lost touch with every day users because they were living in a tech oriented environment all the time and interacting mostly with other professionals.
 
Your both noobs. Powershell.
//
enter-pssession
//
End of story.

Actually I leave my Keyboard all the time because I use Kaseya, N-Able, and SCCM. If you are managing server directly that's your problem.I hate the start menu because it lags the shit out of RDS.
Still I use Powershell more and more. Soon enough we will be back in Novell days.

Where did you get that I manage all my servers directly? LOL. I am talking in the GUI on my laptop (8.1) and on my primary mgmt server GUI (2012). Most of the other servers are core installs and I never even look at them directly. Running about 75 currently, about 35 of them are core installs. The gui in 2012 and 2008r2 is shit. Lags like nobodies business, especially in RDP. I try to avoid using the start menu in our 2008 GUI servers at all costs, especially the VM's. Lag fest.

Still great that MS is moving to a more hands on kybd approach. Faster.
 
There's even a study that found out that Microsoft personnell had lost touch with every day users because they were living in a tech oriented environment all the time and interacting mostly with other professionals.

Which is why they got rid of all the file menus in office for the strip, and now in windows... oops, you just killed you entire argument.

lol
 
Heh you're so out of touch with reality. Only the power users who know the OS and the apps like the back of their hands use keyboard or search.

Oh? You mean like, the kind of people who would use Windows Server?

You're a typical example of a techie who lives in a bubble. There's even a study that found out that Microsoft personnell had lost touch with every day users because they were living in a tech oriented environment all the time and interacting mostly with other professionals.

You came into a thread about Windows Server. The only people who use Windows Server are tech oriented.

Also, if you believe that study (assuming such a dumb study exists), I would recommend you google the phrase 'program manager'.
 
Oh? You mean like, the kind of people who would use Windows Server?

You came into a thread about Windows Server. The only people who use Windows Server are tech oriented.

Not true at all. Only the people who administer the server are likely to be technically inclined. The people who access the server as clients (these are the users) are regular people, and they far outnumber the administrators in any real organization. By far the most common reason for installing the GUI on a Server 2012-class system is to offer Remote Desktop Services. Server Core is the recommended install mode for almost every other purpose. Therefore, the most common reason for connecting to a Windows Server 2012+ install with a GUI is to use Remote Desktop Services. To this end, it makes sense for the server to send clients the same GUI as any other Win8+ system.

The real problem here is that MS even offers the GUI on Server Essentials when it only supports 2 active users in the first place. The only point of installing the GUI on Essentials is to run legacy server applications that require it. Essentials should be like Hyper-V Server: available in Core only. Only Server 2012 versions with the capability to act as Remote Desktop infrastructure should even support installing a local GUI in the first place. This is clearly the direction MS is heading with their Server products, so it should only be another generation or two before the GUI is unsupported for any role besides RDS/RDI.

To people complaining about managing the server while it's running the Modern interface: what are you even doing? Why aren't you managing remotely with Powershell or snap-ins? For the occasional time you need to interact with the GUI (infrastructure failure, during install, managing a legacy application), it's only one click to dismiss the Start screen and get to the Desktop where your work is. Why lose any sleep over it? Finish up what you need to do locally and get back to remote management using reliable tools.
 
Not true at all. Only the people who administer the server are likely to be technically inclined. The people who access the server as clients (these are the users) are regular people, and they far outnumber the administrators in any real organization. By far the most common reason for installing the GUI on a Server 2012-class system is to offer Remote Desktop Services. Server Core is the recommended install mode for almost every other purpose. Therefore, the most common reason for connecting to a Windows Server 2012+ install with a GUI is to use Remote Desktop Services. To this end, it makes sense for the server to send clients the same GUI as any other Win8+ system.

The real problem here is that MS even offers the GUI on Server Essentials when it only supports 2 active users in the first place. The only point of installing the GUI on Essentials is to run legacy server applications that require it. Essentials should be like Hyper-V Server: available in Core only. Only Server 2012 versions with the capability to act as Remote Desktop infrastructure should even support installing a local GUI in the first place. This is clearly the direction MS is heading with their Server products, so it should only be another generation or two before the GUI is unsupported for any role besides RDS/RDI.

This is valid. I was not considering terminal services users as being 'Windows Server users' when I mentioned that. However, from my understanding, in Windows Server 2012, the focus and recommendation for that type of application is the virtualization host rather than the session host.
 
Oh? You mean like, the kind of people who would use Windows Server?



You came into a thread about Windows Server. The only people who use Windows Server are tech oriented.

The Windows 8 UI is not server specific, troll.
 
What boggles the mind is that people fucking complained to many roles on one server. Problem is MS is still following the same bullshit Monolithic structure. When the world revolves around the world of Internet of things yet MS hasn't pulled its head out of their collective asses. Why I like VMWare and what they really did a good job is "server appliances" So instead of releasing a Sharepoint Appliance, SQL appliance and just get rid of the whole server bullshit and complicating with crap.

They will not get rid of the UI because fuck wad Microsoft can't even release a version of exchange with out THE requirement of GUI.
 
The Windows 8 UI is not server specific, troll.

Feel free to find a Windows 8 thread talking about it, if that's what you wish to discuss. I'm sure you will not be short on choices.
 
What boggles the mind is that people fucking complained to many roles on one server. Problem is MS is still following the same bullshit Monolithic structure. When the world revolves around the world of Internet of things yet MS hasn't pulled its head out of their collective asses. Why I like VMWare and what they really did a good job is "server appliances" So instead of releasing a Sharepoint Appliance, SQL appliance and just get rid of the whole server bullshit and complicating with crap.

They will not get rid of the UI because fuck wad Microsoft can't even release a version of exchange with out THE requirement of GUI.

Ok this is rich. VMwares appliances are your example of well done segmentation? Seriously? The VCSA wasn't even something to take seriously until 5.5 came out. Hell VMware still hasn't figured out how to unify their management tools but they're the shining example you're using?
 
Ok this is rich. VMwares appliances are your example of well done segmentation? Seriously? The VCSA wasn't even something to take seriously until 5.5 came out. Hell VMware still hasn't figured out how to unify their management tools but they're the shining example you're using?

I am not talking about VMWare directly, I am talking about the availability of 3rd party appliances. I know VCSA was a joke but at least they are heading in the right direction. If you compare that to the gigantic mess that MS has.
VMWare management is much better then MS.

Have you run HyperV? Its a GONG show compared to VMWare.
 
Have you run HyperV? Its a GONG show compared to VMWare.

You lost me here. Hyper-V has been getting better every single release. vSphere is stagnating and they're destroying the user interface by migrating it to terrible browser-based "cloud" tools. I'm a big fan of VMWare's virtualization technology. It's the best in the industry. But Hyper-V Server Core is a good product and, unlike the free version of ESXi, is actually suitable for use in a business environment. There's a reason MS eats into VMWare's market share every time they come out with a new HV release. I'll use VMWare on the desktop forever, but I've stopped rolling out new vSphere installs as a result of the horribly broken interface and corresponding license model. VMWare has systematically gimped the free version of their product every single release, while Microsoft continues to add new features to make its free product more robust.
 
You lost me here. Hyper-V has been getting better every single release. vSphere is stagnating and they're destroying the user interface by migrating it to terrible browser-based "cloud" tools. I'm a big fan of VMWare's virtualization technology. It's the best in the industry. But Hyper-V Server Core is a good product and, unlike the free version of ESXi, is actually suitable for use in a business environment. There's a reason MS eats into VMWare's market share every time they come out with a new HV release. I'll use VMWare on the desktop forever, but I've stopped rolling out new vSphere installs as a result of the horribly broken interface and corresponding license model. VMWare has systematically gimped the free version of their product every single release, while Microsoft continues to add new features to make its free product more robust.

To each its own. If your talking about silly tools like the cloud and web interface.. Try new Sharepoint, CRM, Exchange, Half its in stupid web browser some are in mmc and some are in powershell. If you want to talk about Schizophrenia you should deal with MS products.
 
Back
Top