Installing Cisco ACS Remote agent v4.2 on Server 2008R2

I am having a heck of a time figuring out if I can install the ACS Remote agent onto my new DC.  The last one was server 2008 standard and I had installed the agent successfully and then had upgraded the server to 2008R2 so the program is working.  I now try to install with the same install package onto the new DC running Server 2008R2, and it gives an error about needing to be Server 2000 or greater ( not recognizing this OS as valid)  
I have asked my friend Google and only found posts from a year ago talking about cisco not supporting server 2008R2 yet.
Anyone have luck setting this up yet? I have submitted a TAC on this but thought I'd throw this question out in the assumtion that someone has also had this problem.  If you have a link to the working installer, that would be most appreciated.  I log into cisco.com and they only present the two supported versions 4.2.1.15 which offers no full installer and requires 4.2 to be previously installed, and 4.2.0.124 which has a bin installer that reports error mentioned above> ( OS must be at least Server 2000)
BlakeISSAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BlakeISSAuthor Commented:
The current version I tried is Remote-Agent-ACSse-win-v4.2.1.15-K9
Update: I ran the installer in compatability mode for server 2008 and it installed.  it is registered in the ACS successfully but would still like to know.
Anyone else try this and have problems?
0
BlakeISSAuthor Commented:
One Note, I did see in reserching that you can only use two DC entries so this third DC I just successfully registered, is not being used for logging or for authenticating, it is pretty handy to have a third server waiting in the event the primary or secondary die.

0
BlakeISSAuthor Commented:
TAC came back and did confirm this as a non supported work-around.   Just a heads up.  I'm going to close out this question since it's maintaining the popularity of flatulence in an elevator.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BlakeISSAuthor Commented:
No input provided by community
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Wireless Networking

From novice to tech pro — start learning today.