Asked by:
Running EssentialsTester script

Question
-
Hi everyone, since a couple of days I'm running into some issues with my server. Tried to Google the issues without success, so trying to start my own thread to find someone to help me out before I end up reinstalling from scratch.
My server is a Thecus W4000 with Windows Storage Server 2012 R2 Essentials. First issue I have is I can't remove some computers from the dashboard. I was able to remove 2 clients without issue, but for 3, I get an error saying that an unknown error prevented to remove computer. Please try again. I retried but still unable to remove with the same error message. Restarted the server few times, but the issue remains.
The second issue is about connecting clients to the server. I Can only download the connector from the https but not http. I get a 403 error. Also, after downloading the connector I Can get to the point that the connector finds the server but when clicking next, I get an error message saying unable to get information from server.
I then found the EssentialsTester script from Robert Pearman. After running the script, I get errors at task 1 and 2. Tasks 3 and 4 are all ok. Unfortunately, I don't know where to find a copy of the results so I can post it here.
I will really appreciate any help since I'm totally at lost now!
Thanks,
Claude
Monday, January 18, 2016 5:21 AM
All replies
-
Why are you removing computers? On the failed to connect set dns on the client to the IP of the server
But I would just reinstall to learn more
Grey
Tuesday, January 19, 2016 2:32 AM -
Hi,
>First issue I have is I can't remove some computers from the dashboard.
Try below process:
1. Uninstall the Connector software from the computer.
2. Unjoin the computer from the Essentials domain and join it to the workgroup.
3. Remove the computer from the server using the Dashboard.
>after downloading the connector I Can get to the point that the connector finds the server but when clicking next, I get an error message saying unable to get information from server.
Configure the preferred DNS server on client as the Essentials’ IP address. If the problem persists, check the log which is located at %programdata%\Microsoft\Windows Server\logs.
>the EssentialsTester script from Robert Pearman.
Please provide related link.
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.
Tuesday, January 19, 2016 9:46 AM -
Hi Grey,
The reason for removing the computer is because it was a test computer with Windows 10. Since my tests ended, I did not want to keep the test computer connected to the server. Since I was not able to remove the test computer, I wanted to make sure removing other computers work as intended. And actually it failed for 3 more clients out of 6 including the test computer. Total of 4 could not be removed.
Thanks for your help!
- Edited by Claude Dorion Tuesday, January 19, 2016 4:25 PM
Tuesday, January 19, 2016 4:05 PM -
There is a log located in your user temp folder.
Or can you post which tasks show errors.
Robert Pearman Cloud & Datacentre MVP
@titlerequired | LinkedIn | Google+
Facebook | Windows Server Essentials.comTuesday, January 19, 2016 4:31 PM -
Hi Eve,
Thanks to try helping me. Concerning the first issue I tried the process you describe without success. I have to say that most windows 10 clients connected to the server are from the home edition, so they are not joined to the domain. Going further with your suggestion, I tried adding a step since I was at the point where the worst would end up wiping the server and reinstall the server completely. So, here is the modified process you suggested and succeeded with the removal of computers. I share my experience to help others if they have the same issue.
1. Uninstall the connector from the faulty computer, you'll be asked to reboot. Do so.
2. If your computer was part of domain, unjoin the computer from the Essentials domain and join it to the workgroup
2. Reinstall the connector on the faulty computer. You won't be warn there is a client with the same name.
3. Remove the faulty computer from the server using the Dashboard.
Regarding the second issue, I did some changes suggested by BPA analysis which obviously screw up the install of the connector. Reverting back the suggestion from BPA, the connector installed successfully. Now my issues are solved without having to reinstall the server and the server is up and running well. I really appreciate your help and suggestions.
You also suggested about DNS, but I have a question regarding IP and DNS. Is it better to setup a static IP address on the server or use DHCP reservation on the router, so the server keeps the same IP address. In the case of going with static IP address, how would you setup the preferred and auxiliary DNS? I kept getting warnings from BPA about DNS when it was setup with static IP. I have about 25 warnings in BPA and it's really annoying...
Thanks,
Claude
Tuesday, January 19, 2016 5:08 PM