FSAE and Windows 2008 R2

[Carlos_Menezes]

Hi All, We are planning to migrate our DC´s to Windows 2008R2 in april 2010, the latest FSAE version available today are compatible? Any rummors about new release? Thanks,

[abelio]

from 4.0.MR1 release notes FSAE 3.00B048 (collector 3.5.048) is supported for 32 and 64 bits Win2008 server.

[billp]

Makes you wonder if R2 is supported, though. We' re in the same boat, and will be testing. We' re moving from eDirectory (Novell) to AD soon. My guess is that R2 will be officially supported in the 4.2 firmware.

[TopJimmy]

ORIGINAL: billp We' re moving from eDirectory (Novell) to AD soon.

Good lord why would anybody want to do that!

[billp]

We' re not a Linux shop. Netware is dead. Waning support. Difficult to locate expertise. No 3rd party training materials/books. If you have a big IT department that can master the new Novell products, they have a nice offering. If you' re a one-man shop, can' t see why you' d want to go down the (lonely) Novell road. But don' t want to hijack this thread. . .

[#6]

Hi Carlos We are using FSAE on 2003 R2 and 2008 R2 It works on both but take care with your 32 bits compatiblity on Win 2008 R2 (the FSAE is not 64 bits native) The only bug that we have reported to Fortinet is about the 8000 and 8002 ports that should be opened (firewall and AD) When we snif the AD server we could see that we have more ports (ranges) that should be opened ... => this could give you some problems if you have strict firewall configurations on your DC servers

[#7]

Hi, We are also new to Fortigate: a fresh install of just 2 weeks old. We have decided to deploy everything step by step and are now at configuring FSAE and user authentication. We can' t find a way to connect FG unit and Windows 2008 server (not R2). What ports should be opened? There is nothing else between the server and FG unit except windows firewall. Tried to put the application in exception list, added port 8000 as UDP/TCP in exceptions, nothing worked. Note: as a test only, we have configured FSAE on 2003 server (different domain) in less then 20 minutes. No headache with windows firewall or anything else.

ORIGINAL: Jerome Hi Carlos We are using FSAE on 2003 R2 and 2008 R2 It works on both but take care with your 32 bits compatiblity on Win 2008 R2 (the FSAE is not 64 bits native) The only bug that we have reported to Fortinet is about the 8000 and 8002 ports that should be opened (firewall and AD) When we snif the AD server we could see that we have more ports (ranges) that should be opened ... => this could give you some problems if you have strict firewall configurations on your DC servers

[Carl_Wallmark]

In MR2, there will be support for polling the DC from a domain member, you dont need to install anything on the DC.

[#9]

Good news, any dates ? I' ve seen the 3.5.53 using this kinf of configuration, somebody had made some tests ?

[Carl_Wallmark]

They said Mars 12, but you never know ;) The beta is out but it does not contain the FSAE, so i have not checked it out.