Answered by:
Server 2012 Essentials R2 Connector

Question
-
Trying to add a brand new, virgin install of Windows 7 SP1 Enterprise desktop. Its a fresh, clean install with nothing else installed except the drivers. Server is Server 2012 R2 Essentials with all the updates and patches. I tried the http://computername/connect, downloaded and ran the connector, it finds the server, I type in the domain username and password, and I get a "The Server is not available" error. I've gone through every troubleshooting step of making sure the times match, that the DNS of the Server is the only DNS listed in the Network settings of the desktop, I've restarted, I've done a FlushDNS, I've restarted the server, I uninstalled the Essentials tool and went online and downloaded the latest essential connection, still the same result. I've installed all 250+ windows updates on the desktop, same result, I've tried manually typing in the IP of the server during wizard, same result. LOSING MY MIND.
- Moved by Eve WangMicrosoft contingent staff Thursday, July 7, 2016 6:55 AM Essentials
Thursday, July 7, 2016 12:38 AM
Answers
-
Hi,
According to your description, my understanding is that Connector failed to be installed/configured on the client with error "The Server is not available"(after typing in the domain username and password).
On your Essentials server, make sure that Certification Authority Role has been installed.
On the client, try to disable IPV6 if it is not in use. Besides, you may try to configure this client with an available static IP address, then, check the result.
If the problem persists, is this a Windows Server 2012 R2 Essentials, or, with Essentials Experience Role installed?
Does this problem also happen on other client?
Provide the log files - ClientDeploy.log/ClientDeploy.log, the client-side log files are located in the folder %programdata%\Microsoft\Windows Server\logs.
Best Regards,
Eve WangPlease remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
- Proposed as answer by Eve WangMicrosoft contingent staff Sunday, July 17, 2016 5:31 AM
- Marked as answer by Eve WangMicrosoft contingent staff Monday, July 18, 2016 6:42 AM
Thursday, July 7, 2016 6:54 AM -
make sure the essentials services are started on the server. Most of the time the issue is dns, but the services have to be started also
Grey
- Proposed as answer by Eve WangMicrosoft contingent staff Sunday, July 17, 2016 5:31 AM
- Marked as answer by Eve WangMicrosoft contingent staff Monday, July 18, 2016 6:42 AM
Friday, July 8, 2016 4:48 PM
All replies
-
Something here may help.
https://technet.microsoft.com/en-us/library/jj635102(v=ws.11).aspx
Might also try them over here in essentials forum.
https://social.technet.microsoft.com/Forums/en-US/home?forum=winserveressentials
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.Thursday, July 7, 2016 1:02 AM -
Hi,
According to your description, my understanding is that Connector failed to be installed/configured on the client with error "The Server is not available"(after typing in the domain username and password).
On your Essentials server, make sure that Certification Authority Role has been installed.
On the client, try to disable IPV6 if it is not in use. Besides, you may try to configure this client with an available static IP address, then, check the result.
If the problem persists, is this a Windows Server 2012 R2 Essentials, or, with Essentials Experience Role installed?
Does this problem also happen on other client?
Provide the log files - ClientDeploy.log/ClientDeploy.log, the client-side log files are located in the folder %programdata%\Microsoft\Windows Server\logs.
Best Regards,
Eve WangPlease remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
- Proposed as answer by Eve WangMicrosoft contingent staff Sunday, July 17, 2016 5:31 AM
- Marked as answer by Eve WangMicrosoft contingent staff Monday, July 18, 2016 6:42 AM
Thursday, July 7, 2016 6:54 AM -
make sure the essentials services are started on the server. Most of the time the issue is dns, but the services have to be started also
Grey
- Proposed as answer by Eve WangMicrosoft contingent staff Sunday, July 17, 2016 5:31 AM
- Marked as answer by Eve WangMicrosoft contingent staff Monday, July 18, 2016 6:42 AM
Friday, July 8, 2016 4:48 PM