![]() ![]() Next we try to launch the Dashboard from the Client. Once it has completed, we can see that the Windows 10 client appears in the Dashboard as expected. The remainder of the wizard is identical to any other client installation. The option to manually enter in the server address is available, however i would only use that myself if i was sure the Essentials Server was functioning correctly. If it doesn’t that may indicate an issue you should investigate before proceeding. It should automatically detect your server on the local LAN. Go into the Start Menu (assuming it is still called that?)įind Your new apps, and expand Windows Server Essentials, Run the Essentials Program. This only installs the connector software.We need now to actually use the connector software to join to the Essentials Server. Once at least one of these has downloaded, run the program. So hitting that link will download the file, now my newness to Windows 10 shows here, as i expected a popup or message to ask me if i wanted to save or run the file, so i ended up with two downloads. Needless to say i shall be focussing on the 圆4 bit version. ![]() (though why anyone wants 32bit is beyond me) Those steps are to download the client connector manually and run it, on the client, without visiting the /connect website.įor a Windows 10 圆4 machine download the client here.įor x86 (32-bit) go here. We can immediately see we need to take manual steps to get Windows 10 working with Essentials R2. Here is the overview table from the Blog Post. In this post we will just be looking at Windows 10 and Server 2012 R2 Essentials. I just want to focus on Windows 10 and in a little more detail. Microsoft published a helpful blog post and table of the various Client OSs supported by the various Essentials Server versions, and any known issues or workarounds required to get them to work. ![]()
0 Comments
Leave a Reply. |