This is promising news, but after reading through various large chunks of documentation last night, I have a few more worries.
1. We have an MS Exchange 5.5 server in place that we will not be able to phase out this cycle. Hopefully by 2006... 2. We have a handful of remote branch offices. These offices currently reside in their own NT domains with WAN connections back to the main office. All their e-mail and Internet access is handled through the main office via the WAN. Questions: 1. Does MS Exchange 5.5 play nice with a Samba PDC? We use (cough) Outlook on the desktop, which is something else we will not be able to phase out this cycle, and the MAPI interface. Exchange needs to auth users against the PDC. 2. If I collapse all the users into a single NT domain and turn the remote branch office PDCs into Samba BDCs with a Samba PDC at the main office (some documentation has been written on how to do this, anyone actually doing it?) would that work? 3. Is Samba 3.0 stable enough to consider using in production? Six months from now, is it going to be "officially" production-ready? (I know, I know - "when it's ready." :) ) Thanks to everyone who has given feedback, I greatly appreciate it. Chris -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
