Team
This is more of a bleet than a fault...
I installed a servewr with DSFW and the installtion progresses as expected (no errors so far).
Having to use 1636 for the LDAP port for the DNS/DHCP configuration tool was a surprise but not a "show stopper", I assume that the server is actually running two LDAP servvices, one with the MS scheme on the default LDAP ports and one with the Novell schema on the alternate ports...
Anyway, what I'm upest about.
When you install a new server it creates the "DNS" based OU structure and the OU's are a different schema type than the "normal" eDirectory 'OU' and 'O' types.
I'm concerned that this may introduce difficulty with maintaining eDirectory trees that "started" as a DSFW install and then "morphed" into a production eDirectory tree with the addition of OES/NCP servers and new user OU's etc.
This behavour is different if you introduce a DSFW server into an exisiting eDirectory tree, where the alternate schema applies from the DSFW partiiton downwards but not tpo the top level 'O' and 'OU' structures.
I personally think the second behaviour (when installed into an exisiting tree) to eb the more correct, but opinions may vary, in any case it's confusing to have the two differnt behaviours and jaring to have the alternate schema applied to the top level tree objects.
Regards
Darren
This is more of a bleet than a fault...
I installed a servewr with DSFW and the installtion progresses as expected (no errors so far).
Having to use 1636 for the LDAP port for the DNS/DHCP configuration tool was a surprise but not a "show stopper", I assume that the server is actually running two LDAP servvices, one with the MS scheme on the default LDAP ports and one with the Novell schema on the alternate ports...
Anyway, what I'm upest about.
When you install a new server it creates the "DNS" based OU structure and the OU's are a different schema type than the "normal" eDirectory 'OU' and 'O' types.
I'm concerned that this may introduce difficulty with maintaining eDirectory trees that "started" as a DSFW install and then "morphed" into a production eDirectory tree with the addition of OES/NCP servers and new user OU's etc.
This behavour is different if you introduce a DSFW server into an exisiting eDirectory tree, where the alternate schema applies from the DSFW partiiton downwards but not tpo the top level 'O' and 'OU' structures.
I personally think the second behaviour (when installed into an exisiting tree) to eb the more correct, but opinions may vary, in any case it's confusing to have the two differnt behaviours and jaring to have the alternate schema applied to the top level tree objects.
Regards
Darren