I\u2019ve written a few posts about Server 2012 R2 Essentials and I\u2019ve made it pretty clear that I am a \u201cfan\u201d.\u00a0 For small shops it\u2019s a pretty sweet deal as it makes it very easy to manage your systems.<\/p>\n
One of the features provided by Essentials is the \u201cConnector software.\u00a0 The Connector sets up the link between the client PC\u2019s and the server and provides the \u201cLaunchpad\u201d and \u201cDashboard\u201d apps which are central points for accessing server services (Launchpad) and server management (Dashboard).\u00a0 The connector software will install on Windows 7, 8, 8.1 and 10 machines (both Home and Pro versions) as well as on Mac\u2019s.\u00a0 And, once the Connector is installed, the client machine is accessible from the Remote Web Access (RWA) webpage served up by the Essentials server.\u00a0 However, there is a tiny fly in the ointment \u2026<\/p>\n
The remote access to client machines that is provided via the RWA is predicated on the client machine being able to support Remote Desktop (RDP) connectivity.\u00a0 RDP connectivity to<\/em> a client machine is only provided by Pro and Enterprise versions of Windows.\u00a0 So, while a Home machine may be displayed in the RWA, it will display with a red dot indicating that connections are not possible to the client machine.\u00a0 The Connector does not \u201cmagically\u201d enable RDP connectivity to Windows Home machines.\u00a0 You can<\/em> use a Windows Home machine to make an RDP connection to<\/em> a machine that supports RDP but the reverse is not possible.<\/p>\n So, if you are planning to make use of RWA supported RDP connectivity to machines on your internal network, make sure that the machines you want to connect to are running a Pro version of Windows.<\/p>\n","protected":false},"excerpt":{"rendered":"