similar to: Re: Please help me with migration to MS Windows 2003

Hi all, I need some help with the following problem: I need to migrate a bunch of user accounts to another domain on a Windows 2003 server (eventually to 2008R2, but that step seemed to big to do in one go). To keep all access rights etc. correct, I need to get the SID history set correctly as well. From what I've researched so far, I'm aware of

Hi Rowland! On 26.11.18 19:37, Rowland Penny via samba wrote: > [..] > adminuser at ubutestdc:~$ ls -la /var/lib/samba/private/ldapi > srwxrwxrwx 1 root root 0 Nov 25 17:13 /var/lib/samba/private/ldapi Also strange: # dpkg-query -l *samba* Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/         

Mr. Gowda, Please review the following prior posts: "HOW TO: Migrating users' locally-stored profiles from one domain or workgroup to a new domain" http://lists.samba.org/archive/samba/2005-December/115326.html http://lists.samba.org/archive/samba/2005-December/115413.html Note that I have only performed this migration where the users had locally-stored profiles. If you are

I presently have a Samba server (3.0.21b) set up as a member server in an NT4 domain (with a real Windows NT4 PDC). We are migrating to an Active Directory domain (with a real Windows 2003 domain controller). We have set up a two-way trust between the old NT4 domain "CLUNKY" and the new ADS domain "SLEEK" (aka sleek.local). The Samba server is a member of the CLUNKY domain

Hi to all, I know that a few posts treat this subject, but I can't found the good answer to my problem. I actually have a Samba domain based on a smbpasswd backend. I must migrate to an AD 2003 and all is working correctly if I don't select the SID history migration. If I select this 'SID history migration' option, I received a message 'Could not verify Auditing

I'm attempting to migrate a Samba 3.x / NT domain to Active Directory. I have a Windows 2003 SE host and ADMT. I've established trusts between the Samba 3 domain and the Windows 2003 AD domain. I can use "User Account Migration Wizard" up to the "Account Transition Options". Then of I check the option to Migrate SIDs it fails with - "Could not verify auditing

This might be a stupid question, but I ask only because I can't think of a good reason... Why do so many vendors' builds of Samba not include libnss_wins, the WINS/NetBIOS name resolution library? I find that it is very helpful for my Linux/Samba servers to be able to resolve hostnames by WINS. It also seems to improve domain browsing performance dramatically to have the library present

It appears that you cannot include groups from trusted domains in the 'valid users =' directive on a share. Here is the scenario as I experienced it (names have been changed to protect the innocent): Configuration: - Samba 3.0.21b as a member server in a real NT4 domain (security = domain) called 'NTDOMAIN' - NTDOMAIN has a two-way trust with Windows 2003 Active Directory

Hi, I think there are some files missing (regarding auth mech-external): compile error (did fresh autogen.sh): gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-auth -I../../src/lib-sql -I../../src/lib-settings -I../../src/lib-ntlm -I../../src/lib-otp -I../../src/lib-master -DAUTH_MODULE_DIR=\""/opt/dovecot-2.0/lib/dovecot/auth"\"

Here's the situation. We've got an old NT4 domain (not a Samba domain in NT 4 mode) which we'll call CRUSTY. There is of course an NT4 PDC and several NT4 BDCs. We have some Linux/Samba file servers (Samba 3.0.1) that are member servers (security = domain) of the NT4 domain. We also have several NT4 BDCs and about 200 workstations of varying vintage (2000, XP) in several

The man page for rsync(1) states: --password-file This option allows you to provide a password in a file for accessing a remote rsync server. Note that this option is only useful when accessing an rsync server using the built in trans- port, not when using a remote shell as the transport. The file must not be world readable. It should contain just the password as a single line.

Does anyone know of a place where I can find sample scripts for use with Samba? Looking thru smb.conf we have these options: add user script delete user script add group script delete group script add user to group script delete user from group script set primary group script add machine script shutdown script abort shutdown script logon script There are probably others that I'm

I have a Samba 3.0.4 server configured as a PDC. NetBIOS name of the server is "SERVER"; name of the workgroup is "AEC". Problem is that there's now a phantom workgroup called "SERVER" when I try to browse the network. Since there's no clients configured in this workgroup, any attempts to browse this workgroup fail. When I attempt to use User Manager for

I'll start off with my question: how do you change a user's SID? When I issue the command: [root@server root]# pdbedit -u testuser -U \ S-1-5-21-4000410194-515421893-615041212-2006 I see testuser:516:Test User [root@server root]# Then, I do "pdbedit -Lv testuser" and it still shows the old SID. Now, I'll give you a little background. Previously, this server (NetBIOS

You can see by the subject I've got an ugly problem. Even though I don't have a Samba server anywhere near the network in question, nobody understands browsing as well as the folks on the Samba team. :-) Here's the situation: I've got two workgroups, FLINTSTONE and RUBBLE which are on physically separate networks. FLINTSTONE has a Windows 2003 Active Directory domain

Having a little trouble with SWAT in Samba 3.0.3. When an option in smb.conf contains quotes, for example: add group script = /path/to/addgroupscript "%g" SWAT will, upon parsing smb.conf, display add group script = /path/to/addgroupscript and committing it causes the quoted portion to be dropped in smb.conf. Note that anything in double quotes (or, rather, after the first double

I've got a Samba 3.0.4 server running on RedHat 8.0 as a PDC. It's the only domain controller on the network, and the only WINS server on the network. The problem is, when I browse the network neighborhood, I see the NetBIOS name of the server ("SERVER") appear as a workgroup/domain (though there are no hosts listed in this phantom domain). It also appears as a computer under

Ben S. wrote: >Hi Jonathan, > >I saw your post in the linux.samba newsgroups with the above topic heading. >Looking through the posts I could not see any replies. > >We also have a customer with the exact same requirements, and I though that >I would quickly ping you to see if you had any luck with migration. > >Any experiences of suggestion are appreciated in advance,

I've decided to share my experiences with the list in hopes that it will help someone else doing something similar avoid the problems I experienced, and hopefully, have a better experience. Here's the scope of my project: Original installation: - Samba 2.2.x series server - Workgroup security (read: local security, not domain security) - no domain controller - password database is

First of all, let me say "I know it's been fixed in Samba 3." That's for those of you who think I'm talking about the requiresignorseal registry hack in Windows XP. I'm not. I ran into an issue when using Windows 95 clients with a Windows 2003 server. (Why not Samba? The customer needs terminal services for some windows-only programs.) Because Windows 2003, by policy,