Enabling TLS 1.2 On Windows Server Essentials
Posted by Mike 
Comments off 
Last updated: January 3, 2024 23
The latest release of WSE RemoteApp (Version 1.255.1836.0 or greater) now allows you to enable TLS 1.2 on Windows Server Essentials, while disabling TLS 1.0 and TLS 1.1, in order to enhance the security of SSL connections made with the server, and to comply with the latest compliance standards for the Federal Risk and Authorization Management Program (FedRAMP). It has long been thought that TLS 1.0 could not be disabled on an Essentials server since it is required for client-to-server communications (such as client computer backups, connecting client computers to the server via http://<YourServerName>/connect, etc.). However, it has recently been brought to my attention that this actually can be achieved when specific .NET Framework security settings are added to both the server and to ALL of your client computers. With TLS 1.2 enabled, and TLS 1.0 and TLS 1.1 disabled, you will be able to obtain an A+ grade (as of this writing), from the SSL Labs SSL Server Test site for your Essentials server’s built-in Remote Web Access websites.
Adding Desktops To The RADC Web Feed
Posted by Mike Comments off Last updated: December 5, 2025 20
The latest release of WSE RmeoteApp (Version 1.255.1811.0 or greater) now allows you to add Desktops (i.e. Computers) to its RADC web feed so that you can access them directly from your favorite RADC web feed client instead of having to always sign in to the Essentials server’s built-in Remote Web Access (RWA) website. The new feature works great from the native RemoteApp and Desktop Connections applet in Windows, and from all of the free Microsoft Remote Desktop client apps for Mac, iOS, Android, and Windows (it even works from the Remote Desktop web client with a bit of persuasion). Continue reading for details on how to enable this feature.
Installing Windows Server Essentials Experience On Windows Server 2019 / 2022 / 2025
Posted by Mike Comments off Last updated: June 3, 2026 13
As mentioned in my previous post, Microsoft has completely removed the Windows Server Essentials Experience (WSEE) server role from Windows Server 2019. However, since the entire Windows Server Essentials Experience is basically just an elaborate .NET application that is installed on top of the Windows Server operating system (and not some tightly integrated system component of the OS itself), it can quite readily be installed onto Windows Server 2019 and beyond.
Connecting From Your Favorite Web Browser
Posted by Mike Comments off Last updated: August 3, 2023 21
I’m pleased to announce that WSE RemoteApp (Version 1.255.1575.0 or greater) now includes support for setting up and accessing Microsoft’s newly released Remote Desktop web client from within the product’s existing RADC web feed feature.
The Remote Desktop web client allows your end users to connect to WSE RemoteApp through a compatible HTML5-based web browser (Chrome, Firefox, Safari, Edge, Internet Explorer 11, etc.) without the need to install or set up additional RADC client software on their computers and devices. This provides a consistent experience across computers and devices, minimizes installation or maintenance costs, and provides quick and easy access from kiosks and other non-personal computers and devices.
WSE RemoteApp takes care of all the hard work of installing, configuring, and updating the web client for you. Enabling the web client only takes a few minutes, and once enabled, you can have your end users browse to the server’s Remote Desktop web client URL from a compatible web browser that’s installed on their computer or device in order to connect to WSE RemoteApp.
How To Manually Set Up A Custom / Vanity Domain Name In Windows Server Essentials
Posted by Mike Comments off Last updated: December 7, 2025 27
Let me start off by saying that I typically recommend folks use a Microsoft personalized domain name (e.g. YourDomainPrefix.remotewebaccess.com) when setting up Anywhere Access / Remote Web Access on their Essentials server. The reason for this is that the domain name, the dynamic DNS update service, and the trusted SSL certificate are all automatically set up and managed for you by the Essentials server completely free of any charge or hassle. If you would rather take this much more convenient route instead, then see the following links for instructions on how to set up a Microsoft personalized domain name on your Essentials server:
Configuring and Customizing Remote Web Access on Windows Server 2012 R2 Essentials
Understand Microsoft personalized domain names
EDIT (11/15/2022): With the increased frequency that Microsoft keeps breaking their online services in Windows Server Essentials (including their remotewebaccess.com personalized domain names and dynamic DNS service), it’s becoming abundantly clear that they no longer care about Windows Server Essentials. Therefore, I now STRONGLY recommend that folks avoid using a Microsoft personalized domain name and just set up their very own custom / vanity domain name instead.
That being said, I also understand that some folks would rather forgo the convenience of using a Microsoft personalized domain name in order to have their very own custom / vanity domain name instead (e.g. YourDomainPrefix.YourCustomDomain.com). Using a custom / vanity domain name presents some additional challenges that must be overcome though; such as purchasing, setting up, and managing the domain name, the dynamic DNS update service, and the trusted SSL certificate. For those folks who are willing to take on those additional challenges, I’ll do my best to try and help by walking you through the entire manual domain name set up process here step-by-step (using either a user-purchased SSL certificate or a free Let’s Encrypt SSL certificate via Certify the web).
How To Manually Set Up A Custom / Vanity Domain Name In Windows Server Essentials
Posted by Mike Comments off Last updated: December 7, 2025 27
Let me start off by saying that I typically recommend folks use a Microsoft personalized domain name (e.g. YourDomainPrefix.remotewebaccess.com) when setting up Anywhere Access / Remote Web Access on their Essentials server. The reason for this is that the domain name, the dynamic DNS update service, and the trusted SSL certificate are all automatically set up and managed for you by the Essentials server completely free of any charge or hassle. If you would rather take this much more convenient route instead, then see the following links for instructions on how to set up a Microsoft personalized domain name on your Essentials server:
Configuring and Customizing Remote Web Access on Windows Server 2012 R2 Essentials
Understand Microsoft personalized domain names
EDIT (11/15/2022): With the increased frequency that Microsoft keeps breaking their online services in Windows Server Essentials (including their remotewebaccess.com personalized domain names and dynamic DNS service), it’s becoming abundantly clear that they no longer care about Windows Server Essentials. Therefore, I now STRONGLY recommend that folks avoid using a Microsoft personalized domain name and just set up their very own custom / vanity domain name instead.
That being said, I also understand that some folks would rather forgo the convenience of using a Microsoft personalized domain name in order to have their very own custom / vanity domain name instead (e.g. YourDomainPrefix.YourCustomDomain.com). Using a custom / vanity domain name presents some additional challenges that must be overcome though; such as purchasing, setting up, and managing the domain name, the dynamic DNS update service, and the trusted SSL certificate. For those folks who are willing to take on those additional challenges, I’ll do my best to try and help by walking you through the entire manual domain name set up process here step-by-step (using either a user-purchased SSL certificate or a free Let’s Encrypt SSL certificate via Certify the web).
Windows Work Folders On-Demand file access feature
Posted by Mike Comments off Last updated: February 28, 2018 28
We’re excited to announce the Windows Work Folders On-Demand file access feature will be available in the next Windows 10 release! This file access feature enables you to see and access all of your files on Windows 10 when using an enterprise managed file server with Work Folders. You control which files are stored on your PC and available offline. The rest of your files are always visible and don’t take up any space on your PC, but you need connectivity to the Work Folders file server to access them.
Revoke Access to Work Files on Compromised Computers
Posted by Mike Comments off Last updated: July 11, 2024 25
With the latest release of WSE WorkFolders you can now revoke access to the work files stored on your Windows 8.1 or greater network computers when they have been lost or stolen, when they are no longer being managed by your organization, or when they have been otherwise compromised.
Work Folders Encryption on Windows
Posted by Mike Comments off Last updated: September 25, 2017 25
At Microsoft, we have Work Folders deployed for our internal users. I have worked closely with people from the IT group to investigate issues and learn about management operations which relate to Work Folders. One such operation is to recover data after an encryption key is revoked. Erez Benari from Microsoft IT is the expert on the data recovery topic, and we collaborated on this blog post to give an in-depth look into the Work Folders data encryption on Windows.
Q&A With Fabian Uhse, Program Manager for Work Folders in Windows Server 2012 R2
Posted by Mike Comments off Last updated: February 28, 2018 4
A few months back I wrote a blog article on Work Folders, one of the new “hero” features in Windows Server 2012 R2 and Windows Storage Server 2012 R2. In this post, I’ll share the perspective of Fabian Uhse, a Program Manager for Work Folders at Microsoft.
Successful Connections Require Secure Remote Web Access Setup!
Posted by Mike Comments off Last updated: May 26, 2020 4
Remote Web Access (Anywhere Access) must be properly configured with a domain name (e.g. YourDomainPrefix.remotewebaccess.com or YourDomainPrefix.YourCustomDomain.com), and a trusted SSL certificate must be associated with the domain name, in order to successfully use Work Folders. If it is determined that Remote Web Access has not been turned on and properly configured when enabling Work Folders, then you will be prompted to do so before you can continue.