RE: Server Migration W2K to Linux
"Geoffrey Scott" <[email protected]> Wed, 1 Nov 2006 12:25:16 +1100
| Newsgroups | gmane.org.user-groups.mlug.main |
|---|---|
| Message-ID | <9DE681DC93551E4FA4C5B50D8BD90F303777DB@gfh-mail-01.guestsfurniturehire.com.au> |
Christopher M Bailey wrote: > Hi All, >=20 > I'm looking for some advise in migrating a small SOHO network from a > Doze backend (Win 2K with AD) to a Linux one.=20 >=20 > In brief my client has been running a 2K box since 1999 until now > with very little problems, only one was running out of HD space on > user drive. They have a nice new server ready to go, but do not want > to pay for Doze 2K3, as all the server dose is domain auth and file > and print sharing. Front end PCs are a mix of Linux (FC 4 & 5) and > Doze XP, (Needed for some apps) =20 >=20 > So here is my list > Needs:- > 1. Domain Controller (if I can migrate users from AD great if not > only small user base, never done this before) 2. File & Print sharing > (my SaMBa knowledge is up to this) 3. No noticeable change for end > users =20 >=20 I can think of 2 OK scenarios that would be of help to you. 1. Build the new server as a Samba domain member server using idmap_rid with samba. This give you consistent SID's across any other samba server you care to implement. Leave the old W2K server as the DC and auth off it. You could use Open-xchange or Zimbra in this scenario with it's own separate user accounts. The web interface for OX is not as slick as Zimbra's and the connectors don't always work in Outlook as you would hope, although I am sure that Leonardo di Lella and the other OX guys have put in a lot of work on this since I tested it a year or so ago. In this scenario I would lean more towards using Zimbra on the same box as the samba file & print server. It will install it's own openldap server etc and you will have to use separate accounts. Use it only with the web interface. 2. Make the new server a Samba PDC. Samba currently works in this capacity like a NT4 PDC. Samba doesn't as yet have a working net rpc vampire command for sucking user accounts off W2K servers. So in the event that you decide to go and turn the new Samba box into the DC you will have to make the user accounts manually. =20 In this scenario the idealx guys and the OX guys have been working together to get an integrated samba Open-xchange server running and user account management tools through some modified smbldap-tools. This is a very complicated server though..... If you were going to do this I would again suggest a separate Zimbra server (on Centos / Redhat es ) and the Samba dc to be using openldap. The Zimbra server can be configured to auth off the samba DC. But it can't be a domain member server. The side benefit is SSO. One set of user accounts. Don't let them use thick clients and everyone should be happy. > Wish List:- > 1. Exchange style shared address book & calendars 2. Centrally > monitored Virus Control (Currently using Symantec Corporate=20 > Edition) I have just finished trailing Kaspersky. I think it easily walks all over Symantec Corporate (which I use as well). They have one of the fastest response times to new viruses of any company. You can get their product for both Linux (including Debian) and Doze boxes. And the admin kit is quite good (although you need Doze to run it). If you want to trial it, they can give you trial licence keys which will run for a bit over 1 month. Make sure you call them to organise this though. > Cheers, > Chris >=20 As for TCO, I faced that problem myself. I opted for 2 year Suse SLES licences which is slightly less than W2K3 over a 4 year server life span. If I was to do it all over again I would do Debian on the file servers and then have chroot installs of Redhat or Centos on the Debian servers. The first thing I get asked when I call IBM for support on my new servers is "What OS do you have on there?" If you have a Redhat chroot install on your Debian server you can get into that and then run their RPM based support utilities from there. Also make sure that the RAID bios & SCSI HDD firmware etc is 100% up to date. The tech guys like to be able to blame Linux and old firmware for problems so make sure you download and apply all updates to your servers before you build them.... Regards Geoff Scott