RE: [Samba] Replace NT4 PDC
> > Give yourself plenty of time - this isn't something you cobble together in > a > weekend. I did it (planning/lab/roll-out) in about 2-and-a-half months > and > I feel I rushed it. Make sure your PDC/BDC has plenty of RAM. I've got > no > less than 768M in my machines and I feel pretty comfortable with that. > I've > not had to "hit the swap" once - yet! You must not work in "The Real World", I had to make the NT 4.0 to Samba PDC change-over in three days... So, it is possible to make the switch VERY quickly if you need to. It ended up taking another handful of days to work out all the wrinkles of permissions and rights. Of course, I only had one PDC and one office to deal with... I just had no extra machines to muck about with... The real pain I had was making the change-over to roaming profiles... BTW, you can make a Samba BDC for a Samba PDC, within the same office space. I have that configured right now as a fail-over system. That took a few extra weeks to build, but in the end it has all turned out pretty darn good. I also have to agree that you should have as much RAM as you can cram into those servers. With a large amount of RAM you can run an amazing number of processes with little to no slow-down or server error. Regards, Robert Adkins IT Manager/Buyer Impel Industries, Inc. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Replace NT4 PDC
* Collins, Kevin <[EMAIL PROTECTED]> [030716 13:26]: > > I have an NT4 PDC that I would like to replace with a Samba server. My > > network also has a box running MS Exchange and Backoffice > > (not the same box as the PDC). > > > > What's the general roadmap for doing this? > > Phil: > > Funny you should ask :-) I'm two-thirds of the way down this path as I > write this. > > What I did was create a new domain and do a cut-over. I've a get a > semi-complete blog of the server build-up process here: > http://web.qx.net/kcollins Cool. My setup is a little simpler. I also have three offices: NY, DC and Baltimore connected with frame relay. Please allow me the following disclaimer: "I inherited this network configuration from the previous systems guys!" I have one domain, the PDC is in DC and the BDC's are in Baltimore. NY logs in over the WAN . Yes, it takes a while. Since the PDC is in DC and the overall configuration is kablooey anyway. I'd like to remove the PDC in DC and install a Samba PDC in Baltimore. Yes, that's not good. But I feel I have to break things a bit to get the network into good shape. I'll eventually drop separate Samba PDCs/domains into DC and NY but there are a lot of other things that have to be changed before I do this. Try not to laugh, but print jobs spool to Baltimore and then back to whatever city the printer is in. The good news is that we are a small shop. Not many workstations per site. I do not have a spare box for running another copy of Exchange. What is this scary method of Exchange cutover? Phil -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Replace NT4 PDC
> I have an NT4 PDC that I would like to replace with a Samba server. My > network also has a box running MS Exchange and Backoffice > (not the same box as the PDC). > > What's the general roadmap for doing this? Phil: Funny you should ask :-) I'm two-thirds of the way down this path as I write this. What I did was create a new domain and do a cut-over. I've a get a semi-complete blog of the server build-up process here: http://web.qx.net/kcollins I will be adding *much* more information to the site over the next month as I complete the cut-over and roll out. I may even try to put a HOWTO on there showing everything I did - step by step. I can tell you what I did and if needed, we can talk details later on... My NT Setup was: I had three offices each with their own NT4 PDC. My main office had a PDC, an Exchange 5.5 box and a print server/BDC. Each of my remote offices had a PDC serving their little part of the world. I had 2 one-way trusts enabled between each of the offices so everyone could *see* everyone else. The first thing I did was to build a lab of 4 or 5 machines, played around with some things and finally settled on building an LDAP enabled PDC here and placing a "BDC" in each remote office that would be LDAP replicas. This is because Samba 2.2.x doesn't support traditional BDCs nor Domain Trusts. This forced me to re-think and re-design my Domain layout. All of this became obvious in the lab, as did most of the roll-out/cut-over procedures. Because there was so much at stake and I couldn't have the working domain down, I did a side-by-side buildup of the new PDC on new hardware and did a cutover of the main office over the 4th of July weekend. This severed the trusts and pretty much isolated each of my remote offices. This past weekend I rolled out one of the new "BDCs" in a remote office and brought them back online. I'm planning on pulling the last office in this coming weekend. The tricky-est thing I had to do was "transplant" Exchange. I did it in a "non-typical" way that worked, but it's not for the weak-hearted. If you want to know, I'll tell you... If you are fortunate enough to have a "spare" Exchange box, the process is would be a little more forgiving. Samba 3.x is supposed to be a must more complete replacement for NT4. This would include TRUSTS and PDC/BDCs as well. If you have the time, I would probably wait for 3.x to come out. Circumstances in my situation wouldn't allow it. Give yourself plenty of time - this isn't something you cobble together in a weekend. I did it (planning/lab/roll-out) in about 2-and-a-half months and I feel I rushed it. Make sure your PDC/BDC has plenty of RAM. I've got no less than 768M in my machines and I feel pretty comfortable with that. I've not had to "hit the swap" once - yet! Good luck and yell if you need anything. -- Kevin L. Collins, MCSE Systems Manager Nesbitt Engineering, Inc. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
