Just make sure that secrets.tdb comes with you. In fact, take a record of
your current domain SID so that you have something to set it back to in
case of some corrupting factor.
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | | Ryan Novosielski - User Support Spec. III
|$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630
On Tue, 22 Feb 2005, Andreas Ntaflos wrote:
On Tue, Feb 22, 2005 at 02:11:32 +0100, Joan Ramos Ramos wrote:
Hello, i have a question, i have a samba 2.2.8 pdc with a lot of windows
clients, ~1000
approximately. What happens with the joint clients if i upgrade to 3.0.11 ?
I don't want to return to join 1000 computers!
I did a similar upgrade (from 2.0.3 to 3.0.6) on our company's Samba PDC
(although it serves only around 40 Windows clients) and all went well, no
client needed to be rejoined to the domain. I did it on a weekend
though, just to be sure to have some time for desaster recovery, should
any desaster happen because of the upgrade. But a weekend might not be
enough for 1000 machines.
You can read up on upgrading to Samba 3.0 here:
http://us2.samba.org/samba/docs/man/Samba-HOWTO-Collection/upgrading-to-3.0.html
--
Andreas "daff" Ntaflos
daff AT dword DOT org
Vienna, Austria
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
