Is there any any known issues with Active Directory 2008 (not R2) and CLM 5.0?
CLM system requirements for 4.0.6 (https://jazz.net/wiki/bin/view/Deployment/CLMSystemRequirements405406) lists both Microsoft Active Directory 2008 and Microsoft Active Directory 2008 R2 as supported for Jazz identity management. CLM 5.0.x system requirements (https://jazz.net/wiki/bin/view/Deployment/CLMSystemRequirements50) state that Active Directory 2008 R2 is supported but elides mention of the former. Is there any reason to think that if someone is using Active Directory 2008 (not R2) would cause issues with 5.0, i.e. would a user moving from 4.0.6 to 5.0.+ need to upgrade AD, or can they avoid this?
One answer
The requirements under "These platforms were dropped for CLM 5.0" lists Windows Server 2008 (not R2). While that section doesn't specifically mention AD, support usually goes along with the Windows Server release.
Even if no one comes up with known issues, it's the unknowns that cause the most trouble. Considering that 5.x has dropped support for other older systems (including many 2008 releases, and ALL 2008 releases after January 2015), I wouldn't chance fudging on any of the new requirements. Considering AD 2008 is being sunseted in January, your company really should be upgrading to 2012 soon or risk security issues. Let them know if there is a security breach related to using a sunseted version of Active Directory, someone could get fired for not upgrading in time. :) AD 2008 is nearly 7 years old, which is practically dead in computer years.
I'm having to jump through hoops to get a very large company to upgrade from SQL 2008 to 2012 so we can upgrade to RTC 5.x. It's difficult, time consuming, and somewhat annoying (for both me and the infrastructure team), but it is doable. Eventually.
Even if no one comes up with known issues, it's the unknowns that cause the most trouble. Considering that 5.x has dropped support for other older systems (including many 2008 releases, and ALL 2008 releases after January 2015), I wouldn't chance fudging on any of the new requirements. Considering AD 2008 is being sunseted in January, your company really should be upgrading to 2012 soon or risk security issues. Let them know if there is a security breach related to using a sunseted version of Active Directory, someone could get fired for not upgrading in time. :) AD 2008 is nearly 7 years old, which is practically dead in computer years.
I'm having to jump through hoops to get a very large company to upgrade from SQL 2008 to 2012 so we can upgrade to RTC 5.x. It's difficult, time consuming, and somewhat annoying (for both me and the infrastructure team), but it is doable. Eventually.