We started on this path several years ago when an IT consolidation happened across all the
divisions which had previously done their own thing in IT. We had multiple NIS domains and
recognised it was getting a bit old as a technology. The main project driver was file
server consolidation, and the NIS part of the project was not funded initially. Because
the NIS domains had historically grown independently we had overlapping user name space as
well as overlaps in uid and gid. The first part of the work consisted of making those 3
spaces unique as it was a pre-requisite for file server consolidation. I don't think
we had overlap in group names, but it was a while ago now.
We decided on an HR identifier as the userid as it was unique and it was already being
used on Windows (which had come along well after Unix) and was already set up as a single
domain across the entire organisation. In the uid and gid space we decided on renumbering
all existing users and groups to a range above all those currently in use, and chose above
2^32.
Userids were renamed first. Unix groups were added into AD as security groups. The
numbering scheme was a formula based on the Windows SID for both group and user. All files
on fileservers were renumbered before fileserver consolidation. We were not really happy
with any of the existing replacements for NIS around 6 years ago so did some NIS
consolidation as required. We did not populate AD with uidNumber or gidNumber at that
time, but did experiment a bit with it on a few users and groups with vanilla ldap. NIS
servers were setup to nightly look up a global passwd and group file which was generated
from Windows AD using the formula based uids and gids. Account changes in AD would then be
reflected as updates in NIS. This was of course batch only. This was made hourly
eventually to handle group membership changes which could happen through the day. HR
processes generally happened only nightly.
A few years later we updated our HR processes to populate and maintain the extra AD
attributes, like uidNumber, gidNumber, shell, unixhomedir, gecos. Just recently we have
added some extra processes to manage the gidNumber, so now have all the pieces in place to
use AD as our single source of information.
sssd will now likely be the final piece that lets us get rid of NIS. It will probably be a
gradual shift as older Linux hosts drop off and new ones replace them. We will be running
both schemes for a while in parallel and since they have the same information it won't
be a problem.
The one thing we have yet to really address is automount maps and I suspect we will have
to turn on NIS in AD to get that part to work properly, or use something like puppet to
manage flat file versions of automount maps.
Hope this helps.
Greg
-----Original Message-----
From: sssd-users-bounces(a)lists.fedorahosted.org [mailto:sssd-users-
bounces(a)lists.fedorahosted.org] On Behalf Of Longina Przybyszewska
Sent: Wednesday, 13 February 2013 9:28 PM
To: End-user discussions about the System Security Services Daemon
(sssd-users(a)lists.fedorahosted.org)
Subject: [SSSD-users] migrating from NIS to AD+kerberos
As a continuation of sssd evaluatin we plan migration from NIS to
Active Directory+Kerberos.
Now again the question - what is the best approach and practice to
migrate users ?
AD administrators enabled SFU, and we got extended schema with POSIX
attributes.
I guess there might be some free or commercial tools for extracting
data from NIS and loading into AD -ldap objects.
Our Linux users are dispersed in separated NIS domains, and all have
AD account beside the entry in NIS.
Home directories are NFS-mounted with autofs from Linux storage
server but some users access MSWin storage with smbclient.
Can you share experiences on assigning POSTFIX attributes in SSSD
context, best practice etc..?
We would not like activate NIS services on AD server for migration.
Longina
_______________________________________________
sssd-users mailing list
sssd-users(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sssd-users