--beast
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
I tried, but had too issues joining domain (beta2), and with logging via
lanmanager.
However from samba.org :
"While significantly closer to the final release, it should still be
considered a non-production release provided for testing purposes only."
Regard's
Vincent
>>Does anybody here using samba 3 (b3) on production server (with at least
> 500
>>client)?
>>
>>
>>--beast
> I tried, but had too issues joining domain (beta2), and with logging via
> lanmanager.
> However from samba.org :
> "While significantly closer to the final release, it should still be
> considered a non-production release provided for testing purposes only."
I'm planning fresh migration from WNT 4.0 network to Samba3 (with
close to 1k clients). What I really want from samba3 was it able to
replace NT4 domain without needing to go to each client and re-join to
the domain again.
Is this possible with samba 2.2?
Also I note that support for ldap was verygood on samba3, any advice?
Tks.
--beast
Matt D.
I almost have one finished. I also had the problem of migrating the
machine accounts using net rpc vampire. It turns out that samba was
attempting to add the machine to the /etc/passwd file as MACHINE$. My
version of linux does not support capital letters in the username. So
instead, I created a perl script called machineadd:
#!/usr/bin/perl -w
$machine = $ARGV[0];
$machine = lc($machine);
system("useradd $machine");
Then added the line into smb.conf:
add machine script = /path/to/machineadd '%u'
This adds the account as machine$ (not MACHINE$) to /etc/passwd and then
uploads to the LDAP server just great!! I'm sure this will also work on
other backends.
Mike