Depends on the politics of your situation. Usually the reason for separate servers has little to do with technical merit and everything to do with administrative fiefs. Trying to consolidate many to one usually fails due to political control problems, which is why most of the historical "consolidate everything onto one big z/OS-based file server" efforts were such horrible failures (performance issues aside). Great idea technically, but doesn't take into account the reality of most organizations.
The safest bet is to do physical to logical (ie, one to one) as a first step, and then start working on the political problems to try to do many to one. If the one to one step goes smoothly, then the next step is a lot easier. One caveat -- printing tends to transfer a lot of data. You may want to keep separate servers dedicated to printing only to avoid throughput issues for consolidated servers. -- db David Boyes Sine Nomine Associates > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Lionel Dyck > Sent: Saturday, March 22, 2003 12:26 PM > To: [EMAIL PROTECTED] > Subject: Samba - 1 for 1 or 'n' to 1 > > > When doing a file/print server consolidation using Samba what is the > recommended approach? > > Is it better to do a one for one (windows server to linux > samba server) or > to take some number of windows servers into a single samba server? > > thx > -------------------------------------------------------------------- > Lionel B. Dyck, Systems Software Lead > Kaiser Permanente Information Technology > 25 N. Via Monte Ave > Walnut Creek, Ca 94598 > > Phone: (925) 926-5332 (tie line 8/473-5332) > E-Mail: [EMAIL PROTECTED] > Sametime: (use Lotus Notes address) > AIM: lbdyck >
