2009-12-01 01:31 AM
Hi & welcome to the communities!
Typically that can be handled in two ways:
1) on a clustered system each controller can join different domains (or only one can join a domain)
2) if this is a single-controller setup, or more granularity / domain joins are required, then MultiStore license will help - this can split a physical filer into multiple vFilers & each of them can join different domains
2009-12-01 10:57 AM
Be careful about the clustered systems, it's not recommended for the failover reasons. If the 2 controllers are participating in different domains, then during the failover, the taking over system won't be able to join the other domain.
2009-12-01 01:22 PM
If the 2 controllers are participating in different domains, then during the failover, the taking over system won't be able to join the other domain.
And why is that?
Failed over controller exist as a virtual entity inside the other controller memory, so it still has its unique host name, separate CIFS server, different IP addresses, etc. - so IMHO it shouldn't be a problem.
Let me know if I am missing something.
2009-12-01 01:34 PM
It works to have different domains... the partner does share some options, time, etc. in failover, but not domain settings... supported per the link below.
They can reside on the same Windows domain or on different domains.
2009-12-01 01:57 PM
OK.. sorry I missed that earlier. Earlier this was not the case, so seems like it is supported now. But as Radek had also pointed out towards the multistore option, that's an excellent feature to be able to join different Windows domains.