3

I have the following computers connected to my Windows Server 2012 R2 Essentials: enter image description here

When I try to Remove the computer with the tasks menu, it fails unexpectedly with the following error: enter image description here

Following the provided link (https://technet.microsoft.com/library/jj730365.aspx) does not give me any information on how to troubleshoot this issue.

How can I do so?

The machine is not available anymore, as I forgot to remove the instance upon reinstallation (which is now DESKTOP-03JUF28), so there's no chance to reconnect (except with a fresh installation, with the same naming - which I want to avoid).

Andreas Niedermair
  • 135
  • 1
  • 7
  • 2
    Did you already try it with the `Remove-WssComputer` cmdlet in PowerShell? The Shell is always the strongest option in my opinion. – SimonS Oct 14 '15 at 13:28
  • @SimonS not yet - thanks for that hint. If it works, can you expand your comment to answer, so that I can accept? – Andreas Niedermair Oct 14 '15 at 13:30
  • sure thing! if that command doesn't work, you could maybe try another one from this list https://technet.microsoft.com/en-us/library/dn205088%28v=wps.630%29.aspx – SimonS Oct 14 '15 at 13:31
  • @SimonS yes, `Remove-WssComputer` worked. Thank you very much! Could you please add it as an answer? – Andreas Niedermair Oct 14 '15 at 13:39

1 Answers1

2

Did you already try it with the Remove-WssComputer cmdlet in PowerShell? The Shell is always the strongest option in my opinion.

SimonS
  • 767
  • 3
  • 13
  • 28
  • 1
    Please write a complete answer - as requested by OP. – guntbert Oct 14 '15 at 14:36
  • 2
    @guntbert The challenging part is to iterate through `Get-WssComputer` to select the item you want to remove with `Remove-WssComputer`. This crucial part is covered in the documentation (https://technet.microsoft.com/en-us/library/dn205092.aspx), but you are right: for a fully fledged answer this should be included! – Andreas Niedermair Oct 14 '15 at 14:41
  • 1
    since the question is now answered, and my answer was actually intended to be a comment (as you can see if you read through the comments), I won't do that anymore. – SimonS Oct 14 '15 at 14:43