Hi Steve
Thanking you very much for the detailed explaination.
So far I know that i will be changing the existing client ssl profile through GUI, I will login into the BIP-IP BOX through TASCAS, where i can view and access all the box located in different location.
first need to check that what SSL certificate in client profile and if they are using ssl2.0 and TLS 1.0... then change it to the new SSL certificate which include TLS 1.2+RC4 alond with the old string..
If I am change through the GUI what are the things I need to check before changing the profile. Also please could you give brief idea what services could it effect if I am chaning the existing client profile, As I need to draft an change release plan and request to approve what I am changing.
What would be the backout plan/roll back plan ???... as far my understanding what I have seen so far i that the new string will be having old string as well.. so when the client browser try to connect through ssl then first it will go through TSL1.2 and then RC4 and if the broswer is not supported then i will go ahead with the old string, example is :TLSv1_2:RC4:SSLv2:!NULL:!ADH:!LOW:!EXP:+TLSv1:+SSLv3:HIGH:MEDIUM... am i right
Many thanks
R