Automount Home Directories from LDAP

I have a Red Hat Linux LDAP/kerberos Server (IPA Server) that i beside authentication also use as a NFS Server sharing users Home Directories.
All information for Solaris machine is provided from a custom DUAProfile in LDAP.
Relevant autofs information in DUAProfile:
serviceSearchDescriptor: automount:cn=default,cn=automount,dc=example,dc=org
serviceSearchDescriptor:auto_master:automountMapName=auto.master,cn=default,cn=automount,dc=example,dc=org
All users on the network have their home directories under /home
I have a auto.home map on the server with key:
* -rw,soft ipaserver.example.org:/home/&
This setup works perfect for our Linux clients but not for Solaris.
In Solaris, autofs seems to look for local users home directories too in the LDAP tree and thus making them unavailable when logging in.
Even though +auto_home is after the local usermappings.
t4 LOOKUP REQUEST: Tue Dec 25 22:08:36 2012
t4 name=localuser[] map=auto.home opts= path=/home direct=0
t4 LOOKUP REPLY : status=2
Removing autofs entries in DUAProfile and specifying every user directly in /etc/auto_home works with a delay in mount.
This is however a less than satisfactory solution.
I thought about just removing local user mounts to /home from /export/home but that does not seem to be a good idea.
How could i make this work the way i want with wildcards?
Regards,
Johan.

I have now tried with a different share and mountpoint (/nethome) on a different test server.
Verified that i can mount it through krb5 and automount works for Red Hat Linux clients.
ssh, su and console login works on Solaris 11 except for finding home directory through automount.
root@solaris2:~# ldapclient list
NS_LDAP_FILE_VERSION= 2.0
NS_LDAP_BINDDN= uid=solaris,cn=sysaccounts,cn=etc,dc=example,dc=org
NS_LDAP_BINDPASSWD= {XXX}XXXXXXXXXXXXXX
NS_LDAP_SERVERS= server.example.org
NS_LDAP_SEARCH_BASEDN= dc=example,dc=org
NS_LDAP_AUTH= tls:simple
NS_LDAP_SEARCH_REF= TRUE
NS_LDAP_SEARCH_SCOPE= one
NS_LDAP_SEARCH_TIME= 10
NS_LDAP_CACHETTL= 6000
NS_LDAP_PROFILE= solaris_authssl1
NS_LDAP_CREDENTIAL_LEVEL= proxy
NS_LDAP_SERVICE_SEARCH_DESC= passwd:cn=users,cn=accounts,dc=example,dc=org
NS_LDAP_SERVICE_SEARCH_DESC= group:cn=groups,cn=compat,dc=example,dc=org
NS_LDAP_SERVICE_SEARCH_DESC= netgroup:cn=ng,cn=compat,dc=example,dc=org
NS_LDAP_SERVICE_SEARCH_DESC= ethers:cn=computers,cn=accounts,dc=example,dc=org
NS_LDAP_SERVICE_SEARCH_DESC= automount:cn=default,cn=automount,dc=example,dc=org
NS_LDAP_SERVICE_SEARCH_DESC= auto_master:automountMapName=auto.master,cn=default,cn=automount,dc=example,dc=org
NS_LDAP_SERVICE_SEARCH_DESC= aliases:ou=aliases,ou=test,dc=example,dc=org
NS_LDAP_SERVICE_SEARCH_DESC= printers:ou=printers,ou=test,dc=example,dc=org
NS_LDAP_BIND_TIME= 5
NS_LDAP_OBJECTCLASSMAP= shadow:shadowAccount=posixAccount
NS_LDAP_OBJECTCLASSMAP= printers:sunPrinter=printerService
root@solaris2:~# sharectl get autofs
timeout=600
automount_verbose=true
automountd_verbose=true
nobrowse=false
trace=2
environment=
From /var/svc/log/system-filesystem-autofs\:default.log:
t4 LOOKUP REQUEST: Wed Dec 26 12:28:43 2012
t4 name=user02[] map=auto.nethome opts= path=/nethome direct=0
t4 getmapent_ldap called
t4 getmapent_ldap: key=[ user02 ]
t4 ldap_match called
t4 ldap_match: key =[ user02 ]
t4 ldap_match: ldapkey =[ user02 ]
t4 ldap_match: Requesting list for (&(objectClass=automount)(automountKey=user02)) in auto.nethome
t4 ldap_match: __ns_ldap_list FAILED (2)
t4 ldap_match: no entries found
t4 ldap_match called
t4 ldap_match: key =[ \2a ]
t4 ldap_match: ldapkey =[ \2a ]
t4 ldap_match: Requesting list for (&(objectClass=automount)(automountKey=\2a)) in auto.nethome
t4 ldap_match: __ns_ldap_list FAILED (2)
t4 ldap_match: no entries found
t4 getmapent_ldap: exiting ...
t4 do_lookup1: action=2 wildcard=FALSE error=2
t4 LOOKUP REPLY : status=2
The automount map is called auto.nethome
key is: * -rw,soft server.example.org:/nethome/&
Is it that Solaris automount dont like asterisk(*) in a automount key?
At least now the local users home directories work when i am not trying to autofs mount to /home.
Anyone know what is wrong here?
Thank you for your help.
Regards,
Johan.

Similar Messages

Automounting home directories from Redhat Linux OpenLDAP server

We have an existing, functioning autofs environment here. At least the linux boxes have no problem automounting user home directories.
I am looking for a more comprehensive solution to getting our macs integrated into this environment.
What should the ldap entries contain?
What should the attribute mappings be set to.
I have ldap authentication working - the only thing left is automounting.
Also - is there a way to get the nfs client to work over secure ports by default? Or is this a BSD thing?
Thanks

http://rajeev.name/blog/2007/12/09/integrating-leopard-autofs-with-ldap/
There's some additional LDAP schema stuff that has to be done; Apple seems to have gone with the most absolutely bleeding edge RFC for automounts - and then removed all legacy support.
This covers most of the issues, however, there is one that I'm still unable to resolve:
typically, a linux box does autofs using an entry like
"* -fstype=nfs foo:/home/&"
LDAP uses a slighty different entry, but it works.
I haven't for the life of me been able to get auto.home mounting from LDAP as easily as if it is defined in the file.
The frustrating part is that the post gives a really good example LDIF; but it still doesn't seem to work.
So while I have other automounts working wonderfully, the wildcarded home directories are still a bust.
So if you're willing to forgo using LDAP for autofs mounting home, then hard-coding /etc/auto_home will fit the bill.
But since the link seems to imply that it works, I'm wondering what's gong on...
Message was edited by: pariah0
Trying to get the asterisk...

Automount home directories from another computer

Hello,
after 2 days of work, I write here to find some help.
I have a well configured Leopard Server 10.5.8 which serves users accounts through Open Directory: network users can log to all my Mac OS X clients, home directories are well automounted in /Network/Servers/myserver.com/Users/user1. myserver.com is the server of user1 Home directory.
Now, I want that (let's say) host1 (Leopard Workstation) becomes the Home directory server of user1. So, I created a local account on host1 with network credentials (uid, gid and passwd) and configure /etc/exports to export his home on the network with NFS.
How to put in LDAP server that his home directory is not located on myserver.com but on host1 ? That is when user1 logs on host2, host2 automount host1:/Users/user1 on /Network/Servers/host1/Users/user1 or elsewhere.
Note: I already test manually the configuration and it works!
1. In WGW, I put /path/user1 as user1's default Home Directory
2. On the client (host2), I manually mount host1:/Users/user1 to /path/user1
3. user1 logs into host2, it works fine.
But I cannot do it for each clients and for each new such user! This is why I want to put this information (for each such user) in LDAP to automatically distribute the information to clients.
Thank you for your help,
Joan

Hello,
after 2 days of work, I write here to find some help.
I have a well configured Leopard Server 10.5.8 which serves users accounts through Open Directory: network users can log to all my Mac OS X clients, home directories are well automounted in /Network/Servers/myserver.com/Users/user1. myserver.com is the server of user1 Home directory.
Now, I want that (let's say) host1 (Leopard Workstation) becomes the Home directory server of user1. So, I created a local account on host1 with network credentials (uid, gid and passwd) and configure /etc/exports to export his home on the network with NFS.
How to put in LDAP server that his home directory is not located on myserver.com but on host1 ? That is when user1 logs on host2, host2 automount host1:/Users/user1 on /Network/Servers/host1/Users/user1 or elsewhere.
Note: I already test manually the configuration and it works!
1. In WGW, I put /path/user1 as user1's default Home Directory
2. On the client (host2), I manually mount host1:/Users/user1 to /path/user1
3. user1 logs into host2, it works fine.
But I cannot do it for each clients and for each new such user! This is why I want to put this information (for each such user) in LDAP to automatically distribute the information to clients.
Thank you for your help,
Joan

Home directories from GUI work but not from command line

I'm having trouble accessing home directories through SSH. After significant trouble, I reinstalled OS 10.4.6 Server on each of my 24 XServes. This is a HPC with an XServe RAID providing the storage space. I promoted the first XServe to an Open Directory master and created 2 test users. I created a two sharepoints from the XServe RAID--one for general data and one for home directories. I enabled AFP on both, granted R/W access to the default group "staff" (of which my two test users are members) and set the home directory sharepoint ("HomeDir") to automount using AFP for users' home directories through WGM. If I use Remote Desktop to login to one of the cluster nodes, the home directory seems to mount correctly. However, if I try to access the same user account through the command line--the home directory cannot be found.
I can cd to /Network/Servers/headnode.domain.com/Volumes/HomeDir; but I cannot see any of the folders listed there. On the head node, I can verify that the user's home directory has been created--it seems to be fully populated. I've checked permissions, and they seem to be correct; but the fact that I cannot access it from the command line seems to suggest that there's a greater permissions issue.
I've tried doing the identical setup using an NFS automount instead of AFP with no success. I can't find any answers for command line/SSH access to this problem. Any help would be appreciated.
Thanks,
CF

I've discovered something else in the course of troubleshooting this problem. If I login as a test user through remote desktop to, say, node1.domain.com; the home directory mounts correctly; and, as long as I do not reboot either headnode.domain.com or node1.domain.com, I can login via SSH and access my home directory.
Of course, if I do reboot--access no longer works. I've browsed through dozens of other posts and tried to follow other users' suggestions. I've manually created a hosts file, which I've uploaded to /etc/hosts on each node. I've double and triple checked DNS and DHCP--I have LDAP propagated through autodiscovery on DHCP; I have each node statically assigned; and I have DNS entries for each node. I also have computer entries in WGM; and I've used the FQDN of each node (node#.domain.com) for everything across the board.
I'm also hitting the "authentication error" when I try to access my other AFP sharepoint. I can't figure this out.

Moving Portable Home Directories from one server to another

I am in the process of migrating users from an older xserve running 10.3 with open directory to a new xserve running 10.5. So far, everything is looking good with the migration, the only major issue I'm running into in my testing is with Portable Home Directories. Presently, the portable home directory on the computer still points to the old server for existing user accounts after they are moved to the new open directory server. On the 10.3 server, the home directories are all mounted under /Volumes/Home, where on Leopard it appears it wants to create the shares under /Volumes/ServerName/Folder. Granted, at present the original server's Home Folders are on a fiber attached raid and in testing I don't have this available. Any suggestions on a way to test easily without moving the raid? Also, is there an easy way to do a mass change on user machines where if I move my raid over to the new server, I can make sure that users data is being backed up to the proper location?
Sorry for the lengthy post, just trying to make sure I'm covering all my bases, heh.

Antonio, thanks for the response. I do have one more question regarding this. On the client side, the mirrors.plist file references the old server FQDN and share name. Because this will be being moved over to the new server, is there an easy method to update the clients mirror plist without breaking the PHD mirror? My big concern here is that either the users will not be able to synchronize phd's or we will have to re-establish all the phd's from the client machines to the server. My thought here is simply using a cname to direct any traffic still trying to hit the old server name to the new server name.

Automounting home directories

I really like how Solaris keeps home directories at /export/home/<username> and then mounts them at /home/<username> upon login. I tried to get this same functionality with OL63 but couldn't get the automounter to work.
My setup is:
/etc/auto.master contains
/home /etc/auto.homeAnd /etc/auto.home contains
* :/export/home/&I restarted the services but when any user logs in the system complains about not having a home directory. What am I missing?

I have not configured autofs recently, but have the following example in my notes:
<pre>
# cat auto.master
/nfs-photon01 /etc/auto.photon01 vers=3,rw,hard,proto=tcp,intr
# cat auto.photon01
* photon01.example.com:/&
# mkdir /nfs-photon01
# service autofs reload
</pre>
Does your /etc/auto.home file specify the NFS server?
By the way, NFS4 is default in OL6, which requires that you export all NFS directories under one virtual home. For instance, if /ext/nfs is the NFS root (fsid=0), everything else that you want to be shared over NFS4 must be accessible under /ext/nfs. Check your /etc/export file. There are examples on the web, you should be able to find it searching for "NFS4 fsid-0".

Migration Assistant does not see Home Directories from AD Users

We use AD as authentication domain but home directories are stored local at the client computer. Hence they are backed up via Time Machine. AD Users can use Time Machine like any local user. But now one machine crashed and we wanted to restore the full computer via Migration Assistent. Unfortunally AD Users home directories are not restored to the computer although the home directories are on the backup set. Is there a way to restore the whole Computer from the Backup Set inclusive all Users directories (including these from the AD Users, which had been stored locally)?

So, finally after fourten hours of unattended "migration," I let it continue overnight and in the morning found that the time remaining had not moved a minute. I canceled MA and found that not one iota of data had transferred.
As far as I'm concerned, Migration Assistant ranks lower on the Apple success list than Open Doc, Newton, Pink and Taligent.
Now I have to manually install software I want to use on the MBA, apply licenses, and all the other stuff I would expect from Windows.
NOT happy.

Automount Home Directories Failed

Hi There,
i have solaris 10 server that is running zfs filesystem.
after patching this server, the clients running sol 10 are not mounting the home directories anymore.
i see that /etc/dfs/dfstab file has the word "Error: Syntax" infront of the line where home directories are getting shared.
also the autofs svcs is up, while the nfs/server svc is offline*.
any thoughts, what should i check.
any help will be greatly appreciated.
thanks
wasim.

Thanks alot for the reply, here is what you need.
svcs -xv nfs/server
svc:/network/nfs/server:default (NFS server)
State: offline since Tue Feb 22 09:56:10 2011
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: man -M /usr/share/man -s 1M nfsd
See: /var/svc/log/network-nfs-server:default.log
Impact: This service is not running.
bash-3.00# dfshares
nfs dfshares:edison: RPC: Program not registered
bash-3.00# vi dfs/dfstab
"dfs/dfstab" 16 lines, 629 characters
# Do not modify this file directly.
# Use the sharemgr(1m) command for all share management
# This file is reconstructed and only maintained for backward
# compatibility. Configuration lines could be lost.
# Place share(1M) commands here for automatic execution
# on entering init state 3.
# Issue the command 'svcadm enable network/nfs/server' to
# run the NFS daemon processes and the share commands, after adding
# the very first entry to this file.
# share [-F fstype] [ -o options] [-d "<text>"] <pathname> [resource]
# .e.g,
# Error: Syntax share -F nfs -o rw -d "home directory" /tank/home
# Error: Syntax share -F nfs -o ro -d "local" /tank/local
bash-3.00# zfs get sharenfs tank/home
NAME PROPERTY VALUE SOURCE
tank/home sharenfs rw=soemgr,rw=soelab113 local
well i did try to correct the dfstab file but did not work. i dont know what was being used to share the home directories, but i do recall that dfstab file was not like the one above.
any thoughts,
wasim
a

Migrate home directories from NW6.5/NSS to OES2/NSS

Hi
Is there a way to migrate the user home directory from NW65 to OES2/Linux in the same tree and copy trusties and change the users home directory setting in the user object?
I've looked at the migration tool in OES2 but I can only copy data, and not trusties and change home directory...
/Jonas

I use a utility called HOMES...by HBware...slick!
I have also used a utility called (I think) Mass volume changer...that was slick too. HOMES is the more powerful, though. Both are freeware.
--El
Originally Posted by jonhol
My mistake... Trustees are copied. Just my luck that when I tested I randomly selected a homdir and that one had no trustees as someone deleted the user object without deleting the directory...
Tried wit another homedir and it worked just fine.
Just the problem with changing the home directory in the user object left to solve...
/Jonas

NFS and LDAP on different servers: Problems with location of home director

Dear Apple Experts.
We are using LDAP server for user authentification
and NFS server for home directories.
Both are decictaed servers on differnt machines.
on the NFS server there are directories
/home/urpi
for staff's home directories
and
/home/students
for student's home directories
both are mounted to the Mac minis in
/Users directory
so
/Users/urpi
contains home directories for staff
/Users/students
contains home directories for students
Authentification works well andpermission are set as needed
but OS X shows missing home directories for LDAP authentificated users
and terminal shows missing home directory
for me it is
/home/urpi/fodrek
I was tried to mount NFS to /home, but it is not allowed
Would I ask if there is any setting to add directories, where home directories are placed,please?
I look forward hearing form you.
Yours faithfully
Peter Fodrek

So none of these machines are Snow Leopard servers?
What exactly do you mean when you say you tried to mount the NFS share to home? Can you copy and paste the command and error?
It sounds as though you don't actually have the NFS shares mounted. Assuming this is so, you might want to investigate how the automount command works so that your MacMinis mount the NFS shares on boot.
If your NFS/LDAP server is an OS X 10.6 server, set the shares to be automounted as user/group directories. Make sure your LDAP server is providing correct information on the home directory location. If it is local, I think the home directories need to be in /Users. If your mounts are indeed working but you cannot login, you might consider making links from /Users to /home/urpi or /home/students on an account-by-account basis (could be done with a quick shell script).

NFS Network Home Directories

Hi,
I am able to authenticate the iMAC through an LDAP directory on a Linux machine but the home directories do not get mounted - can someone help me to get the NFS home directories from the server to mount dynamically on boot? There are around 300+ users and putting each user into a seperate line is not an option.
Thank you in advance!

This page came up in Google:
http://coewww.rutgers.edu/www1/linuxclass2005/lessons/lesson5/sec_10.html
I believe that the automount daemon is normally running on Mac OS X, so you don't need to start it, but I think you do need to define the master mapping. You also need to create a mount point directory such as /mnt or /home as an empty directory.

AD Nested Group & Network Home Directories

Hi,
I have nested an AD group into my newly created OD master. Authentication is successful with home directories set to local startup disk.
I'd like to be able to run all user (~ 200 students) home directories from OS X server and WGM.
I know of 2 ways to direct user profiles to the correct network home
1. use the homedirectory attribute in AD
2. amend the AD schema to recognise OS X attributes
The AD admin is understandably anxious about adjusting the schema at this point. If I provide a case that highlights what's involved, he may consider it.
Has anyone tried this? Does anyone know a good source for info on the subject? I have a feeling number 2 is the best option.
Is there an alternate method of configuring home directories other than above?
Any advice greatly appreciated!

Well, I answered my own question. I found that in order to have my network home directory automount at login I had to use my AD account login as my initial login. I had been trying to log in using Fast User Switching from my old local account and even though I could log in, the directory would not mount.
This has probably been discussed somewhere before. I just hadn't found it yet!

Home Directories Remote Access

Hi,
As a school we are looking to give students access to their home directories from anywhere (preferably with easy access from tablet devices). We have an on-premise SharePoint Server (2013), and also students have access to Office 365 which could give
them 25GB areas on OneDrive for Business.
The three possibilities I can think of so far (without spending anymore money as budgets are tight, and I am a great believer in using the in-built capabilities of Microsoft Products before outsourcing to 3rd Parties).
Students have user areas on OneDrive for Business in Office 365
This would be great in a way because the files are stored off site freeing space up on our SAN. But with no ability to make our own backups (can get around this using versioning), our main issue would be the 500MB-1GB art/music files our students generate,
opening and saving these across the Internet would be painful, and although chances are they won't need these at home, I don't want to confuse matters by giving them multiple areas to save things. Although it's great that it also integrates with office
when they sign in at home or in school, I find it annoying that it creates a SharePoint folder alongside the already existing OneDrive area (very confusing for end users). When you click this and then on the OneDrive @ Company Name it gives you
access to Style Library and other config folders as well as Documents (just looks messy to me). It also means students would have to use web pages to open anything other than office files, I have mapped network drives to OneDrive
before and it works but is glitchy when clicking through folder structures. I also don't want to have to sync their files to every workstation they log onto to make the OneDrive for Business shortcut appear in file explorer.
Students have user areas on OneDrive for Business on-premise
This solves the speed problem with large files to an extent although saving large files into SharePoint inevitably takes longer. We would still have the messy menu with opening office files (explained above) and the issue with opening other
files via web pages.
Students keep user areas in a directory on our server, using Work Folders to access remotely
After the issues when looking at OneDrive, Work Folders was a ray of light I was hoping would solve the issues. Keep the existing folder structure but give access from anywhere (with the promised apps for IOS, android and windows devices). I
set it up and looked good, until I realised you HAVE to sync all of your files to every device you use them with. So if they're at home on an 16GB iPad for example, their user area is 3GB and they only have 1GB left, they can't access their documents
at all. Sync would be great as an option, but there is no way for them to simply access their directory at home (even via web page).
Please someone tell me there is a way! (Without spending more money).
Thanks,
Andy

Hi Andy,
Thanks for contacting Microsoft.
From you description, I learnt that the issue you are experiencing is that you want to give students access to their home directories from anywhere without spending more money.
If I misunderstand anything, please feel free to contact me.
I have read all the three possibilities. For the first two possibilities, you had better post them to SharePoint forum. For the third possibilities, you are right, syncing up is really an issue.
So for this issue, I need to discuss it with our discussion team. I will update you on this as soon as we can.
Best regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Portable home directories + Lightweight network setup

I have a simple home network with a couple of macs running tiger and an airport extreme connected to my cable modem and serving dhcp addresses to the wired and wireless machines.
I was hoping that it would be possible to:
set up a spare mini with tiger server
give it a static ip and set it up as a open directory master
share the home directories from the server
create a network account for myself and then have a synchronised home on all my machines inc. possibly setting up vpn on the server too and syncing from work occassionally.
From my initial experiments and from reading the posts on this forum I'm coming to the conclusion that is unlikely to work. I don't need a server for anything other than this so I'm reluctant to set up more services on it (dhcp, dns etc.), when I'm perfectly happy with the airport extreme providing dhcp and just using bonjour to connect to my local machines when i want to.
I'm very happy with the way OS X works with minimal network infrastructure: the fact you can just plug a cable between two machines and it just works, bonjour is also really cool.
Is it the case that server is never used in this kind of situation and if I am to use it then i must administer the traditional networking services myself as the server software is somehow hardwired to work in this situation.

Hi
Not sure why you have posted this and not closed this off. I guess what you need to ask yourself is: Do I need a server. If you cant find a compelling reason to have a server then leave things as they are.
HTH

Migrating Local Users to Network/Mobile Home Directories

Hey Everyone!
A Happy Holiday's to you all! I'm in the midst of building a new system for my new clients. They had nothing but static IP numbers and no actual servers in a 50+ Mac environment. MacBook Pros, G5's and PowerBook G4s up the yang.
What I'm looking to do is migrate as seamlessly as possible, all of the existing local users to network users and then some of those network users will become mobile accounts. I have Open Directory authenticating properly so...
Here's my plan:
1) Finish creating new builds for the MacBook Pro's, the G5s, and the PowerBook G4s.
2) Create the users in OD and assign them to groups for permissions.
3) Drag and drop entire home directory from each computer to a shared folder on my OD Server.
From here I want to run chown, I'm guessing, to change the user:group for the home folders I copied over so that they match the ID's created by OD. I figure when I do that, then I can simply replace the OD created home folders in my server's Users folder with the copied and permission modified home directories from each local user.
My guess is that would be the fastest way to migrate the users to the network.
My question is are the terminal commands I need to run on each folder in order to make this as seamless as possible?
chown -R username:newgroupname /~path to copied local home directory
Is that syntax right?

The command is correct!!!
But my quess is if you use ACL's to set the permissions you won't need to run the command on every folder
Best Regards

Automount Home Directories from LDAP

Similar Messages

Maybe you are looking for