Hi,
We have the following setup:
Business Objects XI R2 FP2.6
Windows 2003 domain (recently upgraded to 2008 R2)
Using Vintela SSO that comes with XI R2 (using DES encryption)
We recently upgraded our AD schema to 2008 R2, and introduced one 2008 R2 DC into our environment. Now, we've seen issues where SSO breaks for some users, and for others no. For those who can't access BO through SSO, they reboot, and then it starts working again. For some, it may take 2 or 3 reboots, and then it starts working again. But for some, their SSO always works. I assume this sporadic behavior is because at times, a 2003 KDC is found during the query process, resulting in success, and at other times, the 2008 DC is found, resulting in an error.
Now I know, according to SAP document 1429980 - Windows Active Directory 2008 supportability for Business Objects Enterprise XI Release 2, that our XI R2 is not compatible with 2008, but I want to know if there are any immediate workwounds for us, considering we only have 1 2008 DC, and we cannot immediately upgrade to XI 3.1.
I'm wondering if it is the schema update to 2008 or the presence of the 2008 domain controller itself that is causing the SSO issues.
Is there any way to specify during the SSO TGS process to only target 2003 domain controllers, thus preventing the 2008 domain controller to respond as a KDC?
Thanks for any assistance.
Moogeboo
We have the following setup:
Business Objects XI R2 FP2.6
Windows 2003 domain (recently upgraded to 2008 R2)
Using Vintela SSO that comes with XI R2 (using DES encryption)
We recently upgraded our AD schema to 2008 R2, and introduced one 2008 R2 DC into our environment. Now, we've seen issues where SSO breaks for some users, and for others no. For those who can't access BO through SSO, they reboot, and then it starts working again. For some, it may take 2 or 3 reboots, and then it starts working again. But for some, their SSO always works. I assume this sporadic behavior is because at times, a 2003 KDC is found during the query process, resulting in success, and at other times, the 2008 DC is found, resulting in an error.
Now I know, according to SAP document 1429980 - Windows Active Directory 2008 supportability for Business Objects Enterprise XI Release 2, that our XI R2 is not compatible with 2008, but I want to know if there are any immediate workwounds for us, considering we only have 1 2008 DC, and we cannot immediately upgrade to XI 3.1.
I'm wondering if it is the schema update to 2008 or the presence of the 2008 domain controller itself that is causing the SSO issues.
Is there any way to specify during the SSO TGS process to only target 2003 domain controllers, thus preventing the 2008 domain controller to respond as a KDC?
Thanks for any assistance.
Moogeboo