I had an occasion where all things pointed to .NET 4.5 being corrupted and needed to be reinstalled. In my case, MMC kept crashing on me no matter what I did.
If you remove .NET 4.5 from your server, after the requisite restart, you’ll be presented with a handy little thing called a Command Window…aaaaaaaand nothing else. So crack your knuckles and get ready to do some typin’ ladies & gents…
The only way to get the GUI back and Powershell, for that matter, is to run the following DISM commands from the handy Command Window.
DISM being the Deployment Image Servicing and Management tool.
With thanks to Sanup Kumar Bishla in his LinkedIn article p
Type the following two commands and wait for the completion of each…then type in the third and final command to force a restart; When you come back up, you’ll need to invoke a few PowerShell commands before you have your GUI back!
- DISM.exe /Online /enable-feature /featurename:NetFx4 /all
- DISM.exe /online /enable-feature /featurename:MicrosoftWindowsPowerShell /all
- shutdown /r
…now that you’re back… Press CNTL-ALT-DEL and bring up the Task Manager.
NOTE: If you’re RDP’ing into the server, type CNTL-ALT-END instead.
- Once Task Manager Opens select File and Run new task
- You should now see the Create new task menu, type PowerShell.exe and select OK
- NOTE: PowerShell prompt should now be open
- Run the following commands in PowerShell:
- Install-WindowsFeature Server-Gui-Shell (this one took a while to complete for me!)
- Install-WindowsFeature Server-Gui-Mgmt-Infra
- Once the GUI Shell is installed, you will need to restart the server with the following command:
…when it comes up you should be back in business. This should convey the lesson that it really helps being familiar with the Command Line Interface (CLI) and PowerShell especially. It can pull your ass out of some serious situations, for sure!
A GUI-Only SysAdmin isn’t really a SysAdmin, IMHO.
I hope this helps you out!
Microsoft Is Officially Not the Windows Company Anymore
Shared from my Google feed
This has been a feature for at least several weeks. I’m not sure what kind of utility it will have unless they can bridge PowerShell into it but…sounds great for profiling and testing w/o creating a Linux box in Amazon Web Services. Check it out. B
For you Citrix Admins, if you just want the link, here it is
For you non Citrix Admins who want a long, boring explanation of the who, what, why, how and where, continue below:
So this morning I ask my boss to use an application on our Citrix server and he can’t get on. The reason why he can’t get on is because the the default website isn’t set properly and he doesn’t know the EXACT website URL to use. So, now I’m looking like a complete ass because the Citrix servers are MY BABY and they’re supposed to be EASY to access.
I had not yet made the Citrix Storefront website for our storefront the DEFAULT website. It’s actually quite easy but first, for the uninitiated…
…Some prelims for those of you that aren’t into Citrix:
- Citrix is a server software that allows you to stream applications to your company employees wherever they are in the world securely and many times in real time. That is, they can use it for video, IM, audio, etc.
- The Citrix Storefront is the interface that you install that provides the interface between your Citrix servers (anywhere from 1 to a gazillion) that serve the apps and the users out there in the real, cold world just trying to get stuff done.
- With just a few exceptions, the software is plug and play. That is a serious oversimplification but for the most part, you can leave things as their defaults and you’ll be up & running in just an hour or so.
When you install Citrix Storefront, it creates a website on your Windows server using IIS. IIS is Microsoft’s very robust way of serving websites. In most cases it’s pretty solid & secure software. But like all Microsoft stuff, it’s configurable to the nth degree so it can be complex when it doesn’t really need to be. This compares to something like Tomcat which is in comparison faster and easier to configure. The tradeoff here is that Tomcat can be a bitch to troubleshoot when it’s not working because it too has a billion switches and is open source software (a double-edged sword of FREE vs. ‘you get what you pay for’). You definitely need to be a webby to know how to do detailed or non-standard configurations in either system.
All these things said, I guess it’s obvious I’m not a web-kinda-guy. So when I find a fix for something or a method that works for me, I’ll post it here on my tech blog.
Now back to Citrix Storefront. Unfortunately, right out of the box, the Storefront software doesn’t make your Citrix web interface (storefront) the default website in IIS. In a lot of cases where more than one website is being served on the same server, you don’t WANT Storefront to be the default site. However, this also means that when you type this in your web browser:
https://RemoteOffice.emcorp.com (the base URL for your web server)
You’ll see this, the default website for IIS:
The actual Citrix website on your server is usually somewhere here:
The problem is that typing remoteoffice.emcorp.com is a hellofa lot easier for your users to remember and type than remoteoffice.emcorp.com/citrix/mystoreweb.
So, how do you get IIS to change the default website to your Citrix Storefront website? The answer is here. And, thanks for sticking with me to the bitter end. If you need any assistance with this procedure, just leave a comment below. B$
FINALLY someone explains to my simple brain the who, what, why, when and especially HOW of UEFI booting! Thank you, Michael!