Uninstall and Reinstall Secondary Site Management Point Role

Question

Dear Brothers,
I have an issue with one of my SCCM 2012 Sp1 with CU3 Secondary Site Server which the client failed to install on the actual server due to a client issue observed in the CCMSetup.log.
Observation Regarding the issue:
Issue Detail No1.
SCCM Client is not installing to my Secondary Site Server with site code (XYZ), after all the site server are also clients in SCCM hierarchy so it self needs SCCM Client as well. 
CCMSetup.log:
"Error 25150. Setup was unable to register the CCM_Service_HostingConfiguration endpoint" when you try to install the client agent in Configuration Manager"
According to http://support.microsoft.com/kb/2905359
the solution is to :
1. Uninstall the management point role. 
2. Reinstall the client agent on the management point computer. 
3. Reinstall the management point role.
Issue Detail No 2.
When I am trying to uninstall the Management Point Role via SCCM Console as part of the solution posted on the above KB Article, unfortunately the delete or uninstall option is been greyed out.
Now a lot of discussion on the topic "Can not remove management point role is greyed out "under this thread
http://social.technet.microsoft.com/Forums/en-US/1a039893-4a65-4dc9-9feb-e6f09ea1fc0b/can-not-remove-management-point-remove-role-is-greyd-out?forum=configmanagerdeployment
However on the last comment of the above thread from"Trana010"
stated a tool or a command
C:\program files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /deinstall /siteserver:(sec server name) SMSMP
0
Which I never tried yet, and also cannot find a reliable KB supporting the command "rolesetup.exe".
Questions:
1. What is the best way to uninstall/Reinstall the management point on secondary site considering the above issue details?
2. Should I installed CU4 directly instead? Maybe it will resolved the issue even though it is not related to the current case
Regards,

Answer 1

Well, it's by design that you can't remove a management point on a secondary site, so I can imagine that that's why there is nothing "official" written on that subject. I think there are three things you can do:
Try to run the command line (which is probably unsupported)
Submit a CSS call
Upgrade to CU4 and assume the problem is gone.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Dear Peter,
I end up shooting a case with CSS, he guided me and share that this issue is very common.
The reason is that it requires CU3 upgrade (Configmgr2012ac-sp1-kb2882125-x64.msp) to be installed with the SCCM Client installation (The same time) via command line in an elevated permission.
Follow the solution provided by Microsoft Support:
CCMSetup.exe /forceinstall SMSSITECODE=XYZ CCMENABLELOGGING=TRUE CCMLOGLEVEL=0 PATCH=C:\Configmgr2012ac-sp1-kb2882125-x64.msp
It seems the Client Push provided by SCCM 2012 Sp1 Infra, that includes your Hotfix under the "Hotfix" folder under the client source folder somehow doesn't work with this issue, that's why the work around is to help the ccmsetup to grab the Hotfix with
by providing the path for the hotfix instead of relying to take the hotfix for the hotfix folder.
Overall peter thanks for your suggestion. And also to Mr. Jason Sandys opening the option for an R2 upgrade, I will look into the KB for this to plan for implementation. 
Regards,