We currently have CMS version 11 and version 12 on our desktops because we administer 2 different CMS servers. We are upgrading one of the servers and will be loading version 14 once the new server is in place. On a test machine we loaded version 14 with the information for the new server but now version 12 will not work. I can set the server up in version 14 to go back to 12 and that works but I want to drop CMS version 14 to my users desktops prior to the cutover and they will not be able to add 12 themselves. Does anyone know why V14 makes V12 stop working?
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!
CMS Version 14, 12 and 11
- Thread starter coachgt1
- Start date
- Thread starter
- #3
We know 14 is backwards compatable but we need 14 and 12 to work together for a couple of days. Our current version is 12 and we use Supervisor 12. When we intall CMS 13 we are going to Supervisor 14. The problem is, the new server will assume the IP address and DNS name of the old one. We would like to push 14 out before the upgrade with the server info pre-laoded. When we do this, Version 12 will not work because 14 is loaded and the users will not be able to use 14 becuase the server will be looking for the new one. The users can't add the server to version 14 because it already exists it's just set up to go to the new one. Does this make sense?
If you're pushing out the CMS Supervisor 14 client first, but the CMS server itself is staying at version 12 they can work together.
On the client side you will have to go to Connect | Cms servers and there will be a drop-down box to identify that the server version is R12. Can't remember if that can be changed with the existing server or if you have to remove / re-add the server IP address.
On the client side you will have to go to Connect | Cms servers and there will be a drop-down box to identify that the server version is R12. Can't remember if that can be changed with the existing server or if you have to remove / re-add the server IP address.
- Thread starter
- #5
Thanks everyone I just talked to the engineer at Avaya and what we wanted can't be done. We wanted 12 to stay active with 14 so the users would not have to do anything after the cut but start using 14. And by anything I mean the user would not have to change the server, or the server name, or the server version, or delete a server. Avaya say's that 14 is a bug fix for 12 and 13 and uses some of the same registry settings so therefore you have to use 14 to access 12 once you load 14. By doing this we either have to have the users change the server info themselves in 14 after the cut, or push the software after the cut. We are going to wait until after the cut because we don't want the users messing with the server versions. It is just more trouble than it is worth. Thanks again everyone.
- Status
Similar threads
