No, we have stayed on 220.127.116.11 on the controllers per Cisco TAC, Cisco TMEs and other folks we have talked to as well so our WCS is still at 18.104.22.168. I will be moving the OS to CentOS 5.x soon from 4.7 as we are implementing Spacewalk https://fedorahosted.org/spacewalk/ for our servers and would like to get all our linux boxes up to the same level.
We have tried to use it without success. All our previous WCS software has run on a 64 bit Redhat 4 OS, but once we installed Redhat 5 and tried to install 22.214.171.124 it would't install.
Cisco have seemingly, 'in order to enhance your user experience', stopped WCS installing itself on 64 bit OS. This is a real pain, as when we specced our server based on their WCS documentation, there was no mention of it having to be 32 bit (that we saw).
anyway, this issue is covered by Cisco bug id: CSCsj79103
All of the reasons listed above are why I suggest running WCS in a Microsoft environment. I know, that's a dirty word with a lot of you guys but you must understand that TAC support is more comfortable and experienced with the Windows version and the doc is kept better up to date. For those of you who don't mind the extra work using Linux, I suggest you always call TAC and ask for an agent with Linux experience and validate any version changes to your OS or WCS. It's much better than it was with Airespace, trust me.
WLSE appliance Running 126.96.36.199 and 188.8.131.52 on 4402 and 4404. I won't mention my RH version... I love the new features, especially the scheduled radio tasks. I would second Dennis' suggestion of the MS environment.