Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Warning: RCC5 Discontinued

Status
Not open for further replies.

snd1234

IS-IT--Management
Mar 10, 2006
123
US
So I found out today from ITEL that

RCC 5.0 has official reached the end of product life following Avaya end of sale of the Nortel BCM by Avaya March 1, 2012. RCC 5.0 product was made available in 2010 by ITEL. The product manager for ITEL has official end all sales and renewal of service contracts related to the RCC 5.0 as of October 31, 2014.

My RCC5 was running on Server 2008 x64 and I wanted to upgrade to 2012 R2. So after running through three levels of in-place upgrade to get to that platform I ended up with an invalid keycode warning because my site ID had changed.

I run RCC as a virtual machine inside of Hyper-V. In the process of upgrading I raised the # of processors to make the updates go faster. Changing the processors back to two seems to solved the issue and gotten me back to being licensed.

I will just say... be careful when tinkering with the foundations of the system that RCC5 is running on. Too fundamental a change in the underlying hardware could trigger a site ID change which will maroon your software without any support from iTel.

I initially attributed the problem to the three upgrades to the OS I did within the course of 36 hours, but I don't actually think that was the problem but rather increasing the virtual processors caused it. If you are running the RCC on a dedicated physical computer this would seem to imply you may be stuck on that piece of hardware indefinitely.
 
The Site Code is partial built around a MAC address - I can't remember whether it is a network card (adapter) or a processor.
As such, any virtual system should try and have the same MAC addresses (for the virtual hardware) as existing, working ones (I know it can be done quite easily for "bridged network adapters").

In any case, ITEL should really be able to re-keycode as a courtesy - their North American/Canadian contact does.
Any functional changes/reinstalls/environmental impacts would not be supported by ITEL.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top