cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.

2006
Views
0
Helpful
4
Replies
yannick.menard
Beginner

acs 4.2 active directory 2008

Hi,

we plan to migrate our active directory 2003 to 2008.

right now our DC are running on windows server 2003 R2, the Domain server will run on windows server 2008 R2

our acs is 4.2(1) Build 15 Patch 3, running on a windows server 2003 R2.

I want to know if my acs 4.2 running on windows server 2003 R2 will be able to connect to the DC server to get group membership.

thank you,

4 REPLIES 4
kussriva
Beginner

Hi Yannick,

Windows 2008R2 is not supported with ACS 4.2.1. The Supported version windows 2008 R2 is the ACS 5.2 and above which is altogether a different product.

You can go to

http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_for_windows/4.2.1/Installation_Guide/windows/install.html#wp1041324 for more information.

Regards,

Kush

ACS will stay on windows server 2003 R2

but ACS will have to communicate with our new domain wich will be on a Domain controller running windows 2008 R2

and ACS will stay on a windows 2003 R2 connected to the domain

from this line in the documentation i would say it will work:

ACS 4.2.1 on a 32-bit OS to Windows AD on a 64-bit OS

anyone can clarify this, What I understand is I can't install ACS on windows server 2008 R2 but can I let ACS on a windows server 2003 R2 connected to an active directory 2008 domain running on a Windows server 2008 R2

Hi Yannick,

Cisco ACS 4.x version doesn't support Windows authentication (External User Databases > Windows Database) to Windows 2008, R2.

Anim Saxena
Beginner

Hi Yannick,

I  also encountered same sort of issue while  integrating ACS 4.2 with AD  (Active Directory) on Win 2008 R2 platform. I  lowered down the  functional level of AD from WIN 2008 R2 to WIN  2003 and integration was  smooth.

This workaround worked in my scenario.

Below mentioned link can give you more insight of the functional levels.

http://technet.microsoft.com/en-us/library/cc787290%28v=ws.10%29.aspx

Regards

Anim Saxena

*kindly rate helpful post*

Content for Community-Ad