Release Engineering SlaveAPI Service Reporter
	Description • 7 years ago

      No description provided.

	Van Le [:van] Assignee
	Comment 1 • 7 years ago

corrupted os or bad drive. please decom, per arr:

XP machines can no longer be reimaged since opsec has asked that we tighten security. This machine should probably be decommissioned instead.

	Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]
	Comment 2 • 7 years ago

After monitoring we came to conclusion that we have to few machines in xp pool so all these are really needed following Bug 1410024.

	Van Le [:van] Assignee
	Comment 3 • 7 years ago

can you let me know when XP reimage/rejoining the domain works again? per :arr XP reimaging was killed by EIS but from experience, I was able to reimage XP but unable to join the domain.

	Van Le [:van] Assignee
	Comment 4 • 6 years ago

are we good to reimage winxp hosts?

	Attila Craciun [:arny]
	Comment 5 • 6 years ago

This server has a bad hdd and need to be replaced.

	Van Le [:van] Assignee
	Comment 6 • 6 years ago

these hosts are out of warranty but i found a spare from one of our decommissioned machines. can you give it another try?

	Attila Craciun [:arny]
	Comment 7 • 6 years ago

The server boots up fine, however cannot find XP image, same situation as https://bugzilla.mozilla.org/show_bug.cgi?id=1416222

	Attila Craciun [:arny]
	Comment 8 • 6 years ago

I have managed to remaige this, booted with the second Lite Touch Windows PE (x86), but I cannot see it in Slave health. In the slave allocator is enabled.

	Attila Craciun [:arny]
	Comment 9 • 6 years ago

From fubar: re-imaging XP isn't possible - it requires rebuilding infrastructure which was upgraded for w10; there is currently no plan to do that as XP is scheduled to die with ESR52.