Beginning with 2012SP1, we have the ability to add a CAS to an autonomous primary site. It could be interesting to reverse the proposition by having the ability to remove a CAS above a Primary when a CAS is no longer needed or has been set for a wrong reason.
I know that it could be done through creating another hierarchy and using migration tasks by this is quite difficult for it requires additional hardware.268 votes
Normally we update to started when the feature is in a TP… but this can’t be in a TP (as CAS isn’t allowed in a TP.) But the code is in TP. :)
- Don't see your idea?