11-03-2010 12:47 PM - edited 03-10-2019 05:32 PM
We have some old, inherited, and soon-to-be-replaced-with-5.1 ACS 3.2 servers. One of them had some serious issues and needs to be rebuilt.
The current OS is Win2k. We were going to upgrade the OS to 2003 while it was down. Are there any compatibility issues with 3.2 and 2003? Has anyone had any success getting 3.2 to run on that?
Thanks,
Solved! Go to Solution.
11-05-2010 11:03 AM
Hello,
ACS 3.2 on Windows 2003 was never tested so it is unknown whether or not you will run into problems with 3.2 on 2003. I can think of one problem that you may run into where the TACACS+ and RADIUS services may not start automatically after a reboot and will have to be manually started:
CSCsb81671 : CSTacacs and CSRadius services fail to start with Windows 2003
I personally would stick with Windows 2000 for ACS 3.2 since you are migrating off of those servers soon anyways.
--Jesse
11-05-2010 11:03 AM
Hello,
ACS 3.2 on Windows 2003 was never tested so it is unknown whether or not you will run into problems with 3.2 on 2003. I can think of one problem that you may run into where the TACACS+ and RADIUS services may not start automatically after a reboot and will have to be manually started:
CSCsb81671 : CSTacacs and CSRadius services fail to start with Windows 2003
I personally would stick with Windows 2000 for ACS 3.2 since you are migrating off of those servers soon anyways.
--Jesse
11-05-2010 11:54 AM
Thanks!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: