Jan 13, · Install Windows Server with GUI (Desktop Experience) Select Language, Time, and keyboard language and click Next to continue. Click the Install now button to continue. Here, select the version of Windows Server you are about to install. What you need to keep in mind is selecting the Desktop Experience version, which means the version Estimated Reading Time: 2 mins. Nov 04, · Free download Windows server ISO file from the below link. The Windows Server is the cloud-ready operating system that delivers new layers of security and Azure-inspired innovation for the applications and infrastructure. Microsoft Imagine users may download and use for experimentation, learning, and academic lab purposes s: Apr 28, · If you have installed Microsoft Windows Server and are wondering where the GUI now called Desktop Experience is, then unfortunatly the only way to have the Desktop is to re-install the OS. I have just installed Windows Server today for the first time, and as its just for testing purposes, never really paid much attention to the installation ted Reading Time: 1 min.
Nov 04, · Free download Windows server ISO file from the below link. The Windows Server is the cloud-ready operating system that delivers new layers of security and Azure-inspired innovation for the applications and infrastructure. Microsoft Imagine users may download and use for experimentation, learning, and academic lab purposes s: Apr 28, · If you have installed Microsoft Windows Server and are wondering where the GUI now called Desktop Experience is, then unfortunatly the only way to have the Desktop is to re-install the OS. I have just installed Windows Server today for the first time, and as its just for testing purposes, never really paid much attention to the installation ted Reading Time: 1 min. Jun 11, · Enabling the desktop experience is opening security concerns for your server especially if it has internet access. Windows Server Core is too limited for normal use and should only be used for appliances. Use your PluralSight and learn PowerShell and RSAT as you have suggested.
Install Windows Server 2016 with GUI (Desktop Experience)
Windows Server and the Desktop Experience feature
Windows Server products & resources
Install Server with Desktop Experience | Microsoft Docs
So, I’m probably about to reveal to the world my inexperience, but here we go. I’m looking at implementing a server migration next from Windows Server to Windows Server To prepare, I’m researching Server , hitting Pluralsight, watching a udemy course on Server , just bumping up my knowledge where I can.
So, anyway, while I started with the udemy course, which so far has been exclusively taught in the desktop experience, I started watching the Pluralsight instruction, and a lot of that is done in Server Core with command line interface and Powershell. Powershell wasn’t even a discussion topic when I was studying this stuff back in the day.
My questions for you guys are these: Am I holding my company back if I roll out Server with the Desktop Experience I’ve read that updates for the Desktop Experience are sporadic instead of Server Core? Secondly, I haven’t looked at RSAT for Windows 10 to manage Server yet, but will that provide the interfaces I have greater proficiency with to manage the server?
That’s a lot, and maybe this should be a Discussion and not a question, but I thank you all for your time. Multiverse Enterprises is an IT service provider.
The attack surface isn’t THAT much larger Further, the performance hit taken by the extra services running to support the desktop experience are also likely to be negligible to MOST organizations, even when virtualizing. Additionally, while there are many tools that you can use to manage remotely Instead of having to google that powershell command to restart a service or disable the firewall or, or, or.
If you are an “expert” in powershell or other methods of Windows server management and you want that extra inch of security, go core Server core is good for say hosting a domain controller. Something you can manage almost exclusively remotely via RSAT. However, some components still require a GUI and for you to remote into the machine. Looking at you NPS. However, server core will do you little to no good if you can’t effectively manage it without GUI tools. You should use the version that will help you achieve what you are looking to do.
Powershell is a great tool to have in your bag. It can help automate and do bulk operations in your environment and ease administration. Powershell in a month of lunches is a good book to start with. That is very good to know.
Thank you, thank you. The RSAT tools are all tools you probably have used before. It just allows you to turn your Windows workstation into a management station. That makes perfect sense. Thank you very much for all of the information. I’m going to check that book out, too. I’ve winged some Powershell here and there when I’ve had to, but I’m all for learning without having to have Google on the 2nd monitor.
I deeply appreciate your insight. I’ve never seen anyone enable the Desktop Experience for a production server. Enabling the desktop experience is opening security concerns for your server especially if it has internet access.
That is a lot to do for now and you will know where to go later. It is absolutely worthwhile learning PowerShell. It is growing in popularity rapidly and is apparently the defacto standard for server core. It is based on PowerShell 3.
The only really common downfall of using the desktop experience is that you waste some resources and lose a small amount of performance.
RSAT tools are great to know as well as powershell if you want to go without the desktop experience. That way you can test all the things you need to do via Powershell and check via GUI and deploy some ready to use Scripts for the live-Core Server. Powershell is powerful and definitely worth learning. But this is Powershell advanced. That’s a good idea. I was just using it to make sure I could administer just as effectively as , but I see there is potential for even greater testing that never crossed my mind.
Thanks for the ideas, gentlemen! Just for clarity sake I want to point out that there’s a difference between some terms. There’s core, which is shell only. Shell-GUI, which is similar to a traditional install with a graphical shell. Then there is the desktop experience role which adds the bells and whistles of the traditional desktop OS. The question is that if you already have the hardware? Then how many servers will you be “migrating”? Biggest question: What are you going to run on the server?
Some applications will only work on the desktop experience, for example, Exchange couldn’t run on a core install amazingly enough. As for learning powershell, I tried for a while and didn’t get all that far I’m a bash person , so in the end I stopped trying to learn it as an academic excercise and instead just got on with looking at how to accomplish tasks I’m actually faced with, once you’ve got that basic familiarity you’ll then find constructing loops and using variables easier to deal with trickier things.
Powershell still annoys the bells out of me at times though, for example some Exchange cmdlets which show data on the screen but when you export to CSV the data is missing, because you have to parse the object for output to text but it can display on screen.
Despite the bits the annoy me, I’m happy we’re no longer in the days of making my arm ache with mouse overuse. As others have said it really depends on what you’re doing with it. For a lot of the Windows builtin roles you can set it up and get things running with the GUI, such as Hyper-V switch it to command line and do what you need to remotely.
Can’t you turn it on and off now without having to reinstall everything anyway? I thought I read that you could do that now. So maybe spin up a trial and try it for a while both with and without it.
I’d say although Justin makes some excellent posts, MultiverseIT nailed it. But, if you might ever need the GUI, it does not hurt to have it available. You can still shut down RDP if you are that worried about it even if only available internally to your network.
Can’t hurt and gives you a fallback to a comfortable position. The only real downside I can think of to installing the GUI, a crutch is still a crutch. Although it might be a pain to carry around, sometimes we still have a hard time putting them down. You are stuck with the selection you choose during install. You can’t switch back and forth like you could in That is something you can learn over time. I agree with most folks that you should use what is most comfortable to you.
However, I also would encourage you to learn as much Powershell as you can. It is not difficult to learn and there is so much information available out there to help you. For my Virtual Environment I am running Server Core and I have had very little issues as a matter of fact it just runs.
Again, if you need to get something going in production and have a tight time line and not enough time to experiment, I would go with what you know. But I would also suggest that you start getting proficient in Powershell and server core.
Good Luck! I think that Windows Admin Center makes server core less daunting for organizations with inexperienced staff. Yes you do need a GUI for some applications but for many use cases it’s really not necessary these days.
Another argument is if you’re running servers in the Cloud there is less RAM overhead to use server core. If you do have an inexperienced team as others mentioned maybe try to move to server core in baby steps. First prohibit access to VMs except in “break glass” scenarios and force your staff to do their work remotely. Once they are used to working like that they’ll find that not having a GUI on a server is not that big of a deal. Old dog, old tricks. I don’t like Core.
Plus one for the “run what you know” camp. Have fun! The biggest advantage with core over full GUI for most organizations is less windows updates and less that require a reboot, For servers that have a specific task like being a Hyper-V host or domain controller or file server you really only miss the GUI stuff when you are first setting up the server installing drivers under Core is a little tricky as you can’t run Device manager “remotely”.
Once you figure out the “basic” powershell commands you will be using with the server though most of them involve installing windows updates you never need to really remote into them. Just don’t forget sconfig. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Hi Spiceheads!
Best Answer. MultiverseIT This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. View this “Best Answer” in the replies below ». Popular Topics in Windows Server.