Decision Maker

Exaggerated: Reports of the Windows GUI Death

Don Jones clarifies his earlier statements regarding the pending doom of the GUI in Windows Server OSes -- and yes, death is still in the picture.

In my July column, I pronounced the impending doom of the GUI on Windows Server OSes. It caused a bit of a stir: In addition to some pretty flaming e-mails, several folks took the time to post and articulate counterarguments on their own blogs. I fear that some of the differing opinions, however, come from a misunderstanding -- my fault, though it can be tough to squeeze a lot of meaning into a one-page column.

So let me try and clarify: I was referring to what I believe is Microsoft's direction going forward, something I believe I'm seeing validated in the Windows 8 Developer Preview builds. Specifically: I think the GUI will go away on the server. I don't think the GUI will go away entirely, and I don't even think it'll go away for server management. The GUI just won't exist on the server computer.

Think about it this way: When you need to manage Active Directory, don't you just pop open the Users and Computers console on your client computer? When DNS tasks beckon, isn't the console available on your workstation? Those are GUIs. Yet they don't run on the server.

And before you say it, yes, I know that today's Windows servers can't be fully administered from a remote GUI, especially when it comes to server setup and provisioning tasks. I'm pretty sure Microsoft is working really, really hard to fix that.

The main "the-GUI-had-better-not-be-dying" argument I hear typically revolves around, "I don't want to learn command line." Fine. You don't have to. The whole point of Windows PowerShell is that it provides a command-line interface (CLI) for those who want it, and a way to build a GUI atop that same functionality. To developers building an admin GUI, Windows PowerShell is essentially a set of classes that they can call to actually make their GUI work. Exchange Server 2007 and 2010 admins know exactly what I'm talking about: They've got a GUI that's all Windows PowerShell underneath. Don't want to see the Windows PowerShell bits? You don't have to look. Need to automate something, or perform some task that the GUI makes too difficult? You have the option -- but not the requirement -- of dropping down to the shell.

If you have to manage a thousand servers, you might appreciate the power a CLI can offer. If you need to manage a few dozen, you might prefer a GUI. Either way, Microsoft has your back, I think. If you prefer to point-and-click your way through the day, I don't think you'll ever lose that capability in a product called "Windows." It's just that the GUI will run on your client computer, reaching out and telling the server what to do remotely. What's so scary about that? Getting the GUI off the server improves performance markedly (this isn't an assertion I'm making; it's a pretty well-documented fact), and reduces the number of patches (security or otherwise) that need to be written, which improves uptime and lowers overhead.

So, yes, I'm still predicting the death of the GUI... on the server machine. I think the GUI has a long life ahead of it on our client computers. GUIs are easy to learn, easy to operate, and they're definitely more efficient for tasks that you don't perform very often, because they can walk you through whatever steps are necessary. But I truly believe that servers should be servers, not workstations.

Thanks for all of you who commented on the prior column. Now, I'll ask you to do so again: Assuming Microsoft gave you a proper, supported way of remotely doing anything you might need to administer about the server OS... why would you want to do that stuff right on the console?

Notwithstanding, I'm sure there are some legitimate reasons out there for having to log onto the server console and get a GUI there. Let's hear your reasons, and try to make sure Microsoft hears them, so it can factor them into whatever its strategy turns out to be.

I think the GUI will go away on the server. I don't think the GUI will go away entirely, and I don't even think it'll go away for server management. The GUI just won't exist on the server computer.

About the Author

Don Jones is a 12-year industry veteran, author of more than 45 technology books and an in-demand speaker at industry events worldwide. His broad technological background, combined with his years of managerial-level business experience, make him a sought-after consultant by companies that want to better align their technology resources to their business direction. Jones is a contributor to TechNet Magazine and Redmond, and writes a blog at ConcentratedTech.com.

comments powered by Disqus

Reader Comments:

Fri, Jan 27, 2012 Mark United States

It really seems that there is a circular nature to the IT field. Mainframes weren't versatile enough so they invented the PC for distributed computing. Now with Virtual Servers and Virtual Desktops, we are returning to Big Iron. The same seems to hold true here too. It seems that if this comes to pass then Windows server will equal Novell Netware of some 15 years ago. Same management structure. Microsoft beat Novell in part because their server had an integrated GUI. I wonder who'll come next?

Thu, Dec 15, 2011 David Smith

Don, I read with interest, your article "Exaggerated: Reports of the GUI Death". You made several comments indicating that the GUI is still available but PowerShell provides a second option. I do not find this to be completely true and have on several occations discussed this with Microsoft technicians. There seems to be a number of task that the Exchange 2010 GUI is not capable of performing, forcing the use of the Exchange management shell. I have found the commands for it to be very cumbersome and even Microsoft techs seem to have dificulty getting many of the commands to work. So it seems in some cases, Microsoft is not giving me a choice. This makes me wonder how far it will go in this direction before they realize the pain they are causing administrators of smaller environments.Thanks.

Sat, Dec 10, 2011 Tarek Egypt

Well , Great article , but I don't think that GUI is going to die , What put Microsoft on the top is simplicity & part of this simplicity is the GUI , powershell or command lines indeed do their job in simplifying the day-to-day tasks & troubleshooting so does the GUI .. If your environment is secured , your ports are well monitored & your hardware is capable So why not keeping GUI ?? ;) ;)

Mon, Dec 5, 2011

What are you suppose to do when your client tool can't connect? Hop on the server with command-line only to troubleshoot?

Add Your Comment Now:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Comment:
Please type the letters/numbers you see above

Redmond Tech Watch

Sign up for our newsletter.

I agree to this site's Privacy Policy.