none
Server 2016 Essentials - Remove Duplicate Device from Essentials Dashboard RRS feed

  • Question

  • Windows 10 1903 was installed onto two systems.  Afterwards, the computers were no longer connected to the server.  Their Windows Essentials Server services were all removed.  I've confirmed that this is an issue but that's not the problem.  One of the computers was restored easily enough by uninstalling and reinstalling the connector software.  The successful re-established connection allowed the backups to work and enabled the computer to be accessible via remote web access.  Now, the problem is with the other computer.  Due to office furniture being moved around the clients had connected this computer to Wi-Fi (waiting for new wiring to be installed).  Uninstalled the connector software successfully, rebooted system, tried to reinstall the connector software and it failed.  Deleted the computer from Active Directory Users and Computers and removed the DNS entry for the computer name.  Ended up removing the computer from the domain from the workstation itself, rebooted, logged into local admin account, re-installed connector software, rebooted, and now the computer is rejoined to the 2016 Essentials server.  Now, there are two computers with the same name.  The old one shows up under the Dashboard as an archived system.  The new system is online and working.  I can't remove the old computer, with the same name, from the Dashboard.  The old computer appears in the list of systems when using the Powershell command "Get-WSSComputer".  It shows up with a unique deviceid but has the same name as the other computer with a different deviceid.  Using "Remove-WSSComputer" fails to remove the computer.  Is there a way to remove a system by its deviceid or is there something else that can be done?
    Sunday, October 20, 2019 8:40 AM

All replies

  • HI

    1 "Deleted the computer from Active Directory Users and Computers and removed the DNS entry for the computer name.  Ended up removing the computer from the domain from the workstation itself, rebooted, logged into local admin account, re-installed connector software, rebooted, and now the computer is rejoined to the 2016 Essentials server.  Now, there are two computers with the same name."
    did you delete the computer name of problematical computer(like hostname :pc01) on ADUC but before you rejoin this computer to the domain,you not change the host name of problematical computer?
    2 did you consider uninstall the connector software and add the problematical computer to workgroup, then change the host name of problematical computer, then rejoin this computer to AD domain by using wse connentor ?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, October 21, 2019 3:24 AM
    Moderator
  • HI
    Is there any progress on your question?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 25, 2019 3:01 PM
    Moderator
  • No.  I did not change the host name because two other computers in the network were able to rejoin the WSE domain by uninstalling the connector software and then rebooting and reinstalling the WSE connector software.  They rejoined with no problems and were immediately picked up.  The only thing different between the other two computers and the one that needed more work to get joined with the same computer name was the network connection.  The two successful computers remained connected to the network via Ethernet.  The other computer with WKS01 was switched to the private Wi-Fi to keep network shares running since VLANs are in use.  So, I can only think that by switching the network profile the computer was treated as a different computer and now there are duplicate names.  However there are different IDs for the computers with the same name.
    Saturday, October 26, 2019 2:34 AM