Thanks for the quick reply. So the schema extensions should only be needed if i wanted local accounts for say SSH to be integrated with active directory, otherwise i would need to just create local accounts on each machine to allow logon?
Would this mean that it isn't needed for clustering also? At some point I would want to try and see if i can get 2 servers to run in clustered mode and have them connected to a direct attached storage (SAS). Does the current implementation of CIFS support clustering (would it need to)? My overall plan is to do the following, probably a little off topic and should post elsewhere: Have a clustered server, with shared directly attached storage, probably in active/passive mode (unless active/active is possible and not troublesome). This would provide CIFS and iSCSI (comstar) access to servers and workstations. This server would then replicate to a remote server, initially I was thinking that I would use real time, but found that it could impact the performance a bit, so have been thinking that a scheduled replication should be used. Would all this be possible without the need to extend the schema, I probably will extend it anyway, but due to time constraints and the amount of changes that need to be done before to our current domain I didnt want to change the schema just yet. Would extending and integrating the schema with solaris after joining it to the domain be a great deal of work, or would it just be pointing it to use the schema values instead of the local accounts and editing any used uid's and gid's in active directory for specific accounts that have been locally created? Sorry if this was way off topic Thanks -- This message posted from opensolaris.org _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
