Disconnect Primary Site from CAS to be a Standalone
I have seen environments where network issues have become such a problem with a CAS and multi Primary sites, that they repeatedly go into maintenance mode. As a result their site(s) basically become inoperable. This repeatedly occurs over time, so even trying to resolve DRS won't fix what's the inevitable.
It would be super awesome if there was a features and ability to remove a primary site from a CAS hierarchy to become a standalone and continue to be fully operational.
Some ideas could be to pull those site boundaries that had belonged to the site to be removed from the CAS so there is no confusion on where clients will report once a Primary is removed. All objects that were replicated from the CAS to the Primary would still be active and valid on the Primary site, though the location of the source content for those packages may be an issue. Perhaps when the Primary is disconnected, during the wizard, there could be an option to copy the source to an appropriate share or it be added to the pre-req checklist.
Thank you for your time.