similar to: Migrate SAMBA 3.0 domain to Windows 2003 AD

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

Hello, I'm finding migration Windows 2003 AD to Samba + LDAP solution. I seen there can use pwdump2 to dump all accounts information in Windows 2003. I tried it but only can dump local account not AD accounts, cound anyone share some experience to me ? Thanks _________________________________________________________________ Discover the new Windows Vista

Hello, We are thinking about migrate our AD to samba 4. I found a thread at this list [1] where the steps are: 1. Join samba4 with samba-tool domain join ... 2. ensure that the directory is replicated 3. copy the sysvol share from win2k3 to samba4 4. run samba-tool ntacl sysvolreset on the samba4 box 5.-1000. Test test test 1001. If you are satisfied with how samba4 is working you can launch

Hi, I would have to join 7 computers (a mix of win 8, 8.1, 10 WKSs) to samba 4.7 AD DC. After I will have joined those workstations to samba AD DC I would like the users to experience a minimal disruption of their Desktops and profiles. The computers have never been registered to any domain before. Can their existing local user names be mirrored on the ADDC (samba)? Can their user profiles be

We have been directed to move off a SAMBA domain to a server 2003R2 domain. We run roaming profiles with samba and would like to continue this on 2003R2. After bringing all the XPSP3 desktops into the 2003R2 domain, roaming profiles wont work. I'm not even trying to use the SAMBA generated profiles. The error I get when logging on is: *Windows cannot locate the server copy of your

In the comming months we will be setting up a few new machines to replace our PDC and BDC that are currently running Fedora 11 with Samba 3.4.7 and OpenLDAP 2.4.15. We will be upgrading to the latest Fedora with samba/ldap. With this we will be recreating our domain fresh to get rid of alot of old junk not needed and add in new features. We do use roaming profiles also. My main concern is this:

We are currently setting up a new domain with samba 3.5.10 and openldap 2.4.23 (based off of Centos 6.3). The current domain is running older versions, 3.4.7 and 2.4.15 respectively. We are changing domain names also. There is alot of layout changes and the way it works. One change we are implementing is combining all the BDC's/home servers into one and moving them to the PDC. On the old

Migrating Users Profiles When Changing Domain Affiliation: A Primer I. Introduction NOTE: This applies to Windows NT-based systems with locally-stored user profiles. Windows 9x and Me do not manage user profiles in the same way. Quite often we find the need to change a workstation's affiliation, either from a workgroup (that is, the workstation is not in a domain environment) to a domain,

Hello, I am wondering if this is preferred at this iteration in development. If so, what would be the best way to continue? To build a VM server and have that do file serving, then migrate file serving from the old ad, then join the new VM to the ad server? Vice versa? My reasoning; running sernet (Version 4.0.12-SerNet-Ubuntu-8.precise) with Ubuntu 12.0.2 and since deployment in three different

On 11/06/15 14:12, joseph-andre Guaragna wrote: > I look at your article, and it did not change my view about profile. > As we did not use any roaming/mandatory profile, nor we have any > redirection. > > the only roaming we have is dedicated to few users and we use NFS as > they are under linux, and way more simpler to set up. Strangely we do > not have problems with those

Hi, I've to migrate transparently a NT4 PDC to a SAMBA-LDAP-PDC with 1000 users. Each user has a roaming profile on the NT server. Of course, I want to migrate all the roaming profiles automaticaly on the Samba server without any intervention on clients ! How can do that ? How to preserve the ownership of each profile ? Thank you, -- Rapha?l Berghmans <rberghmans@arafox.com>

Yes that is exactly the point and why we implemented the AD in the first place. But still every person connecting to any workstation gets a home directory created whether it is on Linux or windows. And if I understood well, if no roaming profile in place on each machine the domain.user is created. Thus leading to blank home directory every time your user connect for the first time to a

Hi, I've reinstalled the server that I use as my Samba PDC, and run into a few problems: the old server (which is still available for fossicking through) was running a prerelease Samba 3.0 (3.0.alpha23) the new server is running 3.0final I have a couple of Windows 2000 workstations using it as a PDC in NT4 domain mode, and I'm using roaming profiles. The few problems I've run

Hi! I have an Windows 2003 with Active Directory providing authentication to the network, and a SUSE box providing file services (currently hosting the users' homes). Now I want to migrate the roaming profiles from the Windows 2003 box to the SUSE box, but it is proving difficult. I copied a profile folder for a test user to the SUSE box and changed its permissions to give ownership

I have quite a few samba installations, and I've had problems with roaming profiles when upgrading from Samba 2.2 to 3.0. My servers run Debian stable, which uses Samba 2.2.3, with security patches. At some point Debian will release a new stable version with a recent Samba 3.0 release. Right now I'm testing a few servers with a samba 3.0.10 backport to make sure the transition will go

Hi Everyone, Does anybody use roaming profiles in domain level? I'm looking for helps for setting up Samba as a NT4 domain member to support roaming profiles for sharing during domain logon of Windows clients. I ran into the problems. log files couldn't show specified messages, except for BUFFER_TOO_SMALL. If a profile share directory is mounted on a Windows NT DC or a Windows domain

Grettings, all I have a bizarre problem on a laptop in my Samba 3.3.4 domain. This domain includes a mixture of XP Pro and Vista Ultimate clients. I had just completed a migration to this new domain (from a Samba 2.2.8a domain), and all seemed happy and well - machines had rebooted and were still active in the domain, users were logging in with no problem, shares were working perfectly - all

Hello, I wan't to migrate accounts, roaming profiles and other shares from Samba 2.2 (Slackware) to Samba 3.0.23 (Debian). It should be transparent for clients. I migrated linux user accounts, smbpasswd file, smb.conf and domain SID. I can join new client to the new domain and it works, but when I'm trying to substitute old server with new one (only for test clients of course, without

Hello, I wan't to migrate accounts, roaming profiles and other shares from Samba 2.2 (Slackware) to Samba 3.0.23 (Debian). It should be transparent for clients. I migrated linux user accounts, smbpasswd file, smb.conf and domain SID. I can join new client to the new domain and it works, but when I'm trying to substitute old server with new one (only for test clients of course, without

I'm running Samba 4.7.0 on FreeNAS 11.1-U2. It's configured as an Active Directory Domain Controller, and I'm trying to configure roaming profiles. I've created a profile dataset in ZFS that uses Windows permissions. I've configured the share and file system permissions as described in the "Using Windows ACLs" section of: