On 27/08/12 02:54, Muhammad Yousuf Khan wrote:
any help please?
On Sat, Aug 25, 2012 at 1:33 PM, Muhammad Yousuf Khan<sir...@gmail.com> wrote:
i wanted to migrate Windows 2003 AD to Samba For DC with out rejoining
the clients and down time.Such as Additional Domain Controller
actually, i am Planning migrating my microsoft infrastructure to linux
gradually.
i successfully migrated Fileserver, Virtualization, Proxy. now my
goal is to replace my domain controller holding 2003 server.
i have a mix client (33 nodes) infrastructure including, WindowXP,
2003 Memeber server and Windows 7 while all are memeber of domain with
default GPO, though i wanted to use GPOs in future via samba4,
here is the detail of my domain controller,
1. 2003 Active directory
2. active directory integrated DNS with DNS forwarder.
3. DHCP.
so my questions are.
As per my understanding with DC . i can use ADC for failover.
- is it possible to install samba DC as an ADC and later promoted to DC?
- is there any one has migrated windows DC to SAMBA DC. what was
his/her strategy/experience (any suggestions would be appreciated).
- can anyone please tell me about the stability of SAMBA4. with his
personal experience , since it is in beta stage?
because my 2003 DC server is in production and i don't have a clue
that beta is a better way to go in production or not.
my requirement with samba4 after migration are.
1. DC
2. Integrated DNS so that when ever host join's. DNS records and other
updates in AD should be done by it self. (same ad windows AD)
3. DHCP
4. Group policy implementation.
BTW, i am using 2.7 SAMBA as file sharing server integrated with 2003 AD.
so is it going to effect the migration or not? or samba 2.7 with
consider SAMBA4 machine as an old DC.
Thanks,
Hello:
I'm also interested in deploying samba4. My plan is to build a testing
environment and then proceed with a possible migration.
Searching I found that samba4 from debian packages contains some
differences with the official samba distribution. Originally samba4's
team developed a replacement of the file server of samba3 called ntvfs.
But later they decided to continue to use samba3 file server (smbd).
But Debian don't ship samba4 with samba3 fileserver (smbd) because this
conflicts with smbd of samba3 package. Samba developers recommends to
reactivate ntvfs[1].
For now this is the only issue that I found with samba4 on Wheezy.
Greetings
Federico
[1]http://www.spinics.net/lists/samba/msg103250.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679678#32
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/503b767f.2050...@uncu.edu.ar
