TN - AppSrv - 26051802 Remove Platform That's Stuck in Platform Manager
Last updated: May 18th, 2026Description
- Author: Josh Andrade
- Published: May 18th, 2026
Details:
- Document Version: 001
- Applies to Version(s): All

Description
Platform shows up in Platform Manager as part of a Galaxy, but that machine actually belongs to a completely separate galaxy.
Problem Description:
There are times when platforms do not properly undeploy, which causes the Platform folder to not delete. These should remove themselves when a platform is undeployed.
In this case, the platform ending in “OP2” was undeployed, the platform object was deleted from the original galaxy, but it still showed up in OCMC:

We knew for a fact that this platform belonged to separate galaxy, and was currently deployed to that new galaxy:

Solution Details
Solution Steps:
Open up Registry Editor, and go to -
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ArchestrA\Framework)
You’ll end up finding a Platform folder where the Machine row will show the Computer Name:

Take a backup of this Platform folder, and delete it. After that, the machine reference will be removed from OCMC Platform Manager.
_____________________________________________________________________________________________


Recommended articles
[ISS Support Case] Platform deployment failure
Failed to deploy failed to find target platform aa bootstrap register platform failed.
Read More[ISS Support Case] Platforms stuck connected but in store forward
After a historian reboot, many platforms will not come out of store forward. the connected is off then back on when historian reboot is complete but stuck in store forward. two ways to clear - reboot the client. or browse to client via SMC and take platform off scan and put back on scan. toggling the connect statecmd nor toggling scanscate command will clear issue.
Read More[ISS Support Case] Platform Deployment Failure
Client reached out as when user was attempting to deploy WinPlatform user was receiving the following error: "Cannot find the target PC on the network OR target PC can not communicate back to the Galaxy Repository using the NIC that is top in the binding order."
Read More