800xA 6.0.3 SCC: Clean up Invalid node
The node was correctley part of a previus test-deploy, but has been removed via the 'remove node' in the configuration wizard.
How can I avoid making a new windows installation on the Invalid node. (See capture)
I seems a little excessive to go that far back!
(I did do a Repair Invalid Media on Node).
Voted best answer
I honestly speaking, don't even know.
I assume its location will eventually be found and subsequently beaconed at AKS.
However, the underlying problem remain: The System Installer runs unattended scripts that may or may not succeed to run a certain action more than once. The whole purpose of this protection was to avoid unnecessary work.
As long as we do not have a System Uninstaller, we should find other ways of bringing back a machine to its virgin state.
I strongly suggest using drive imaging software to clone the computers at a few critical stages (after OS load & activation, after NPT, before & after rollup/revision, etc.) for later recall if it should become necessary.
From 6.0 onwords node addition/removal strictly from Scc.
In general Scc controls node management hence whenever node has crashed/deletion of operateit data/temp folders/modifying node name doesn't gets identified in Scc hence u have to do the fresh install of xa of same version as running in Prias and do the replace node(keep all settings same as earlier)