Connecting a PC to the Server Domain
The Windows 2016 Server Essentials Dashboard supports a wide variety of client operating systems – both Windows and OS X/Mac OS variants. As discussed, not all client operating systems are able to join the server domain and feature support will vary depending on the client OS. Let’s briefly recap the list of supported platforms:
Windows 7 operating systems
- Windows 7 Home Basic SP1 (x86 and x64)
- Windows 7 Home Premium SP1 (x86 and x64)
- Windows 7 Professional SP1 (x86 and x64)
- Windows 7 Ultimate SP1 (x86 and x64)
- Windows 7 Enterprise SP1 (x86 and x64)
- Windows 7 Starter SP1 (x86)
Windows 8 operating systems
- Windows 8
- Windows 8 Professional
- Windows 8 Enterprise
Windows 8.1 operating systems
- Windows 8.1
- Windows 8.1 Professional
- Windows 8.1 Enterprise
Windows 10 operating systems
- Windows 10 Home
- Windows 10 Pro
- Windows 10 Enterprise
- Windows 10 Education
Apple Mac client computers
- Mac OS X v10.5 Leopard
- Mac OS X v10.6 Snow Leopard
- Mac OS X v10.7 Lion
- Mac OS X v10.8 Mountain Lion
- Mac OS X v10.9 Mavericks
- Mac OS X v10.10 Yosemite
- Mac OS X v10.11 El Capitan
Other platforms (with the relevant permissions) may be able to access shared folders and other data on the server via SMB links, but they cannot be monitored and managed from the Windows Server Essentials Dashboard.
To kick off, we will go through the process of adding Windows-based computers that have the ability to join a domain. I’ll use a Windows 10 Pro PC for this walkthrough.
To start the domain join process, we need to open a web browser (Microsoft Edge or Google Chrome) from the computer that you want to connect to the server. Type in http://<servername>/connect in the browser bar where <servername> will be replaced by your actual server name.
The web page that opens allows you to download a small “connector application” (called ComputerConnector) which walks you step by step through the process. Run the application once it has downloaded.
The Connector Configuration wizard starts by showing you the inevitable license agreement, which you’ll need to accept to continue.
The Connector software will then be installed on the client – note that if you have any Windows Updates installing when you try to install the Connector, installation will most likely fail.
The next dialog requires you to enter a network user name and password. This is a user account held on the server; not your local PC account user name/password. If you have not yet set up any additional users on the server, skip ahead to our later chapter that deals with Users, and we’ll walk through creating a new user account.
The process continues and finishes up, at which point you must restart the computer. Once past this point the first time, you are asked if you are setting up one account or more.
If you choose the second option, you are taken on a slight detour to determine what accounts you want to add to the computer and which account will be the local administrator account.
Simply highlight the network accounts you wish to use on the client and click the arrow to move them over to the Selected users panel. Click Next and you’ll then be asked to select accounts to be configured as local administrators on the client. Check the relevant boxes and click Next.
Enter a computer description, if needed, for easy identification later. If you’ve previously set a description for the PC (in the Control Panel’s System area) this field will be populated for you.
Select a backup option (I recommend you select the first option, so the computer is woken for backup, but note that not every PC will sleep once the backup is finished). You can amend this option at any time.
Click Next and the Connector Configuration wizard will finish up.
Once completed, click on the Finish button to take you to the Windows 10 sign-in screen. This screen has now changed to indicate you are signing in using a network account rather than the “old” local or Microsoft account. If desired, you can sign into the PC using your old local account which can be particularly useful if you’re working off-site from where the Essentials server is located.
You’ll experience a Déjà vu moment on a Windows PC, as you are taken back through the “We’re getting your PC ready” sequence once again.
Finally, we are up and running once again on the client computer, except we are now using the network user account rather than the local user account. If this computer has been actively used, you will quickly find out that shortcuts to your applications, your old user settings, and data are no longer available to you. This is a brand new account.
In Windows 10, you’ll need to visit Start > All Apps and then scroll down to W to see the entry for the Windows Server Essentials Dashboard. Alternatively, just use the Search box to find it.
Clicking the Windows Server Essentials Dashboard entry takes you to a Dashboard sign-in window. Enter your server administrator username and password to view the Dashboard. Note the Options drop-down menu too, which exposes settings for remembering your user account details (not a great idea if this is a shared PC) and the ability to select which third-party add-ins to load into the Dashboard. The latter is most useful for troubleshooting add-ins which may be causing Dashboard issues.
The Windows Server Essentials Dashboard loads up. Note that it runs as a Remote App, rather than natively on the Client PC. This means that you actually control the Dashboard instance running on the server. Only one instance of the Dashboard can run at any given time (which prevents conflicts, obviously) so if the Dashboard is already open on the server, it’ll be closed before you are presented with the console on a client PC.