How the zone type can affect features
Because the details of the data model depend on the Active Directory schema and the zone type, the zone type can also impact the features a particular zone can support. For example, classic and hierarchical Centrify zones support multiple profiles for each user but SFU zones do not. The following table summarizes key differences between zone types.
| Zone type | Multiple profiles | Delegation | Inheritance |
|
Classic Centrify zones (2.x, 3.x, 4.x) |
Yes |
Yes |
No |
|
Classic RFC 2307‑compatible |
Yes |
Yes |
No |
|
Hierarchical Centrify zones (5.x) |
Yes |
Yes |
Yes |
|
Hierarchical RFC 2307-compatible zones |
Yes |
Yes |
Yes |
|
Hierarchical Services for UNIX (SFU) zones |
No |
No |
Yes* |
|
Services for UNIX (SFU), version 3.5, zones |
No |
No |
No |
|
Services for UNIX (SFU), version 4.0, zones |
No |
No |
No |
| * A hierarchical SFU zone can only be the root parent zone. You cannot create any Service for UNIX zone as a child zone. | |||
For more information about differences in how data is stored in a specific zone type, see Differences between types of zones.
Doc Feedback