Client Connector for Server essentials 2016

Not impressed :) Out of 12 computers it is failing to install on 3. Two questions:

1) Can you download the latest and greatest from Microsoft and run as a standalone package?

2) It says it is installed on the workstation but the Dashboard on the server says it is offline. Is it at all configurable on the workstation?
LVL 15
Who is Participating?
Cliff GaliherCommented:
No to both.
1. You have to flush the DNS on those 3 desktops. In CMD (c:\ipconfig /flushdns)
2. Move the desktops back to a workgroup.
3. Delete the PC accounts from AD (for those 3 desktops only if still exists)
4. Run the Client connector on the desktop.
5. Do not run the client on two desktops at the time.
6. Check the network connection on the desktop and confirm it shows as Domain.
LockDown32OwnerAuthor Commented:
No luck. I often wondered what this "Connection Client" brings to the party. Looks like niceties at best. It appears that Windows is corrupt on these workstations. Seems to work OK if you join the domain without it. Other then some reporting and backup do you really need it?
Cliff GaliherCommented:
If you want those features, yes. If you won't be using the essentials dashboard for any management, no. At which point, I'd suggest not bothering with essentials at all then.
LockDown32OwnerAuthor Commented:
For anyone else who comes across this issue the problem turned out to be permissions on the C:\Windows\Temp folder. I have had the same issue cause installer problems on Windows 10. How and why the permissions got changed and weren't correct? All I can say is leave it to Microsoft.......
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.