Mounting AD Home Directories

I kind have this working by typing smb://cp-file-home/home$ into the connect to server winto but the problem i am having is that after it logs in the home directory has nothing in it other then my admin and user folders and i can not seem to modify those folders. They should each contain a few folders and it seems that i do not have rights to read or write despite the fact that the get info windows says i can do both. Anyone seen this before?

So basically you plan to affect mobile home directories which resides on each laptop, with a copy synchronised on an afp server, with the authentication done by AD.
So you magic triangle need first to be correctly set, meaning that your server is first bound to the AD then promoted as a Open Directory without kerberos realm - as it is the AD one which need to be used. Then bound your clients to OD first, AD second, in this order.
Try first with a regular account to be shure that your kerberos ticked is granted - "regular" means that you don't care about the home directory which is by default in the /users/ of the local (client) machine. Then once you shure that AD allow you to access and create an account, (in terminal type klist to see the ticked AD-issued) you'll play with the various option of the home dir.
Regards,
Antoine.

Similar Messages

  • Problem mounting NFS home directories of NIS users.

    Only on one of client (rest on all clients working fine), the Local directories under /home is getting mounted instead of NFS shared home directories of NIS users. Able to manually mount the NFS shared directories but they also get automatically unmount after some ideal time. Want that the NFS shared directories gets automatically mount when the NIS user gets login as it is happening on all other clients.
    Scenario:_
    NIS user: user1
    NFS Shared home directory: /export/home/user1 (which should get mount as /home/user1 when user1 gets login)
    Local directory: /home/user1 (which is getting mounted when user1 is getting login)
    [CLIENT]/--->ps -ef | grep automount
    root 23369 1 0 Mar 19 ? 1:58 /usr/lib/autofs/automountd
    [CLIENT]/--->cat /etc/auto_master
    /xfn -xfn
    /net -hosts -nosuid,nobrowse
    /- auto_direct -intr
    /- auto_home -intr
    [CLIENT]/--->ypcat -k auto.home
    /home/user1 NFS_SERVER:/export/home/user1
    /home/user2 NFS_SERVER:/export/home/user2
    [NFS_SERVER]-->cat /etc/dfs/dfstab
    share -F nfs -d "user home dir" /export/home
    [NIS_SERVER]--->cat /etc/auto_master
    /xfn -xfn
    /net -hosts -nosuid,nobrowse
    /- auto_direct -intr
    /- auto_home -intr
    Please let me know if any other information is required.

    add this entry as the first non-comment line in /etc/auto_master on the client:
    +auto_master                                                                                                                                                                                       

  • Mounting Users home directories on a replica

    I have two Xservers. One is the master and the other a replica. The replica gets all it's info from the master. If I'm on it and finger a user it knows the users and correctly says where the users home is...
    /Network/servers/master-servers-name/Users/user-name
    But the users home is not mounted on the replica and I can't logon as the users. Can someone tell me what needs to be done on the master and replica to get the home directories mounted?
    Thanks.
    Pat.

    Hi, Thanks for the info. I did find an old IP in the replica section under inspector. I've cleaned it up and will restart the system tonight and clean up the replica in the morning also.
    While I was in the inspector I looked at some of the other sections. Under "SharePoints" there is nothing? I have set up the /Users sharepoint. So should it be listed here in inspector?
    Also to answer some of your questions about how I log in:
    I try to ssh to the replica and I get in but I get the messages
    "Could not chdir to home directory /Network/Servers/system.company.com/Users/pat: No such file or directory"
    If I'm on the system and "su to pat I also get the
    "No such file or directory" message.
    If I use ARD to login it all works fine?? The sharepoint is mounted and
    I'm in my home directory (st this stage I can ssh in as pat and the directory is there. But if I log off ARD the the ssh session looses the directory mount)
    Thanks for the help

  • Home Directory on External Disk has stopped being mounted as Home Director

    Title says it all....
    Set up external RAID mirror to be used as Home Directory for User "David". The Home Directory used to mount as Home drive but doesn't anymore. When I turn on I need to first login with root user then:
    1. Open Disk Manager and Unmount disk (/Volumes/David on RAID mirror as a safety precaution for step 2)
    2. Open Terminal:
    cd /Volumes
    rm -rf David (this deletes /Volumes/David which is created on startup disk)
    3. Re-mount RAID mirror
    4. Log out and Login as David
    If I do not take this action when I want to login a freshly created /Volumes/David is created on the startup drive.
    Advice on resolving please

    I have already checked the RAID volume and it looks healthy.
    I have had a look in the system.log and the following appears to be relevant to the problem however I would not know how to make a full diagnosis and resolve:
    Dec 22 00:34:56 kutching SystemStarter[44]: The following StartupItems failed to start properly:
    Dec 22 00:34:56 kutching SystemStarter[44]: /Library/StartupItems/tap
    Dec 22 00:34:56 kutching SystemStarter[44]: - execution of Startup script failed
    Dec 22 00:34:56 kutching SystemStarter[44]: /Library/StartupItems/tun
    Dec 22 00:34:56 kutching SystemStarter[44]: - execution of Startup script failed
    Dec 22 00:34:56 kutching system_profiler[205]: CFPreferences: user home directory at file://localhost/Volumes/David/ is unavailable. User domains will be volatile.
    Going to try what is suggested here:
    http://www.tonymacx86.com/viewtopic.php?f=7&t=7175&start=0
    to correct home perms.
    Any other suggestions ?

  • 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

  • Home directories on NIS clients show "NOBODY" for group and owner

    Hi,
    I recently changed 10 clients from an old NIS server (running Solaris 7!) to a new one (running Solaris 10).
    All my clients log on through NIS and mount their home directories OK, but when you do a ls -l it shows all files as having the owner and group as "nobody".
    I am guessing this has to do with the NIS maps, or auto_home or something, but I keep going around in circles.
    FROM CLIENT:
    $ ls -l
    total 14
    drwxr-xr-x 2 nobody nobody 4 Sep 11 14:46 Desktop/
    drwxr-xr-x 2 nobody nobody 2 Sep 11 14:46 Documents/
    -rw-r--r-- 1 nobody nobody 136 Sep 11 13:07 local.cshrc
    -rw-r--r-- 1 nobody nobody 157 Sep 11 13:07 local.login
    -rw-r--r-- 1 nobody nobody 174 Sep 11 13:07 local.profile
    -rw-r--r-- 1 nobody nobody 33 Sep 11 14:51 test
    FROM SERVER
    nisserver # ypcat auto.home
    nisserver # ypcat auto.master
    auto.home -nobrowse
    -hosts -nosuid,nobrowse
    nisserver # ypcat -x
    Use "passwd" for map "passwd.byname"
    Use "group" for map "group.byname"
    Use "project" for map "project.byname"
    Use "networks" for map "networks.byaddr"
    Use "hosts" for map "hosts.byname"
    Use "ipnodes" for map "ipnodes.byname"
    Use "protocols" for map "protocols.bynumber"
    Use "services" for map "services.byname"
    Use "aliases" for map "mail.aliases"
    Use "ethers" for map "ethers.byname"

    Darren,
    Yes. The clients are Solaris 10 as well. And the domain is the same on both server and clients.
    The files should be owned by real users.
    If a user ssh's into the server directly, the permissions display properly. But on the clients it is nobody. Other than the permission displaying wrong, I haven't noticed any permission-related restrictions on the clients.
    -Jim
    Edited by: cr8rface on Sep 22, 2008 10:30 AM

  • NFS Home Directories not acquiring permissions

    Hi there. We have recently upgraded our labs to 10.5.4 from 10.4.11. We mount user home directories via NFS and have for some time without an issue. Now, though, I can create the mount using either fstab or Directory Services and it works, however when a new user logs in who does not have a home directory, the profile gets copied to the NFS server but does not acquire the correct permissions. THe home directory is owned by root and not the logged in user. Have any of you seen this? Are there any solutions or something that I might have done wrong? Any help would be appreciated and if this is the wrong section, point me to where I can post and I'll repost there.
    Thanks
    Jason

    The NFS mounts are being shared off of a NetApp. We didn't have any issues with this in the past, only with Leopard.

  • Home Directories not mounting

    I'm setting up an OS X network for the first time.
    I've got Open Directory based network logins working, but I can't get the home directories to mount over the network. When logging in, a dialog box says that an error occurred and that the home direcotry is mounted via SMB or AFP.
    So I log in as a local user on the client machine to poke around. I don't see the server listed in /Network/Servers, but I can manually do a Connect To Server and put in afp://server.dom.ain/Users/usename and it's fine. This afp:// URL is the same as is specified as the user's home directory.
    I have verified that /Users is exported on the server.
    Do I need to go in to every client and create an automount map for this or is there something else I've forgotten?
    Thanks...
    various   Mac OS X (10.4.9)   10.4.9 server and clients

    The first thing to do when you're having any kind of login problem is to ssh in to the client machine and tail -f /var/log/system.log, then log in to the client machine and watch for clues.
    Step by step:
    1. make sure Remote Login is enabled in the Sharing preferences on the client machine (you can turn it off when you're done if you're paranoid)
    2. on any other mac (or ssh equipped PC) run Terminal (in /Applications/Utilities) and type "ssh username@IP-of-client-machine" obviously replacing "username" and "IP-of-client" with your values, and no quotes of course. Note that "username" needs to be an administrative user. If you haven't logged in with Terminal before, keep in mind that it does not echo back characters when you type in the password. Just type it and press enter. You may have to type "yes" after that to set up the initial trust relationship between the two computers.
    3. Once you're logged in to the client machine, type "tail -f /var/log/system.log" (again, no quotes) and leave it like that. You now have one computer watching another computer's logs in "real time" -- VERY handy when you're troubleshooting a reproducible error.
    4. Go back to the client computer and log in with the problematic account. The other computer will show you everything being logged in system.log. Watch for clues that something is wrong. (something couldn't be found, access denied, anything that doesn't sound too friendly)
    5. Figure out what they mean or copy/paste 'em here! The part that counts is anything that came up on the watching computer's screen from the moment you clicked "Log In" on the client computer to the moment you are at your regular (deficient) desktop, confident it's not gonna do anything else.

  • Word 2008 for Mac and NFS mounted home directories "Save File" issues

    Greetings everyone,
    (Long time lurker, first time poster here)
    I admin a small network (under 20 workstaitons) with a centralized NFS server, with user home directories mounted via NFS upon login.  Users are authenticated via LDAP.  This is all working fine, there is no problem here.  The problem lies when my users use Microsoft Word 2008 for Mac.  When they attempt to save a file to thier Desktop (or Documents or any folder under thier home dir) they are met with the following message:
    (dialog box popup)
    "Word cannot save or create this file.  The disk maybe be full or write-protected.  Try one or more of the following: * Free more memory. * Make sure the disk you want to save the file on is not full, write-protected or damaged. (document-name.ext)"
    This happens regardless of file format (Doc, Docx, Txt) and regardless of saved location under the network mounted dir.  I've noticed that when saving Word creates a .tmp file in the target directory, which only further confuses me to the underlying cause of the issue.
    When users logon to a local machine account and attempt the save, there is no issue.
    I have found many posts in other commuity forums, including this one, indicating that the issue is a .TempoaryItems folder in the root of the mounted directory.  This folder already exists and is populated with entries such as "folder.2112" (where 2112 is the uid of the LDAP user).  I find other posts indicating that this is an issue with Word:2008 and OSX10.8, with finger pointing in either direction, but no real solution.
    I have installed all Office for Mac updates from Microsoft (latest version 12.3.6).
    I have verified permissions of the user's home dir.
    I have also ensured that this issue effects ONLY Microsoft Office 2008 for Mac apps, LibreOffice and other applications have no issue.
    Does *ANYONE* have a solution or workaround for this issue?  While we're trying to phase Microsoft products out, getting users to ditch Word and Excel is difficult without removing them from systems completely.  So any pointers or help would be greatly appreciated.
    Thanks.
    ~k

    I can't tell you how to fix bugs in an obsolete version of Office, but a possible workaround is to use mobile home directories under OS X Server. The home directories are hosted locally and synced with the server.

  • Multiple simutaneously logged in users accessing AFP home directories?

    Hi,
    Many of our problems are described in this guy's blog:
    http://alblue.blogspot.com/2006/08/rantmac-migrating-from-afp-to-nfs.html
    The basic capability we want is to have multiple simultaneously logged in users to have access to their AFP mounted home directory, which is configured in a sane, out-of-the box setup using WGM and Server Admin.
    Multiple user access could take the form of FUS (fast user switching), or simply allowing a user to SSH into a machine that another user is already logged into and expect to be able to manipulate the contents of her home directory.
    From my extensive searches, I have no reason to believe this is currently possible with 10.4 Server and AFP.
    (here's the official word from apple: http://docs.info.apple.com/article.html?artnum=25581)
    I've read that using NFS home directories will work, though.
    I want to believe that Apple has a solution for this by now (it's been almost a year since we first had difficulty), or at least a sanctioned workaround. If Apple doesn't have one, maybe someone else has come up with something clever. I find it hard to believe that more people haven't wanted this capability! (not being able to easily search the discussion boards doesn't help, though...)
    Thanks for your help!
    Adam

    Parallels Issue. Track at http://forum.parallels.com/showthread.php?p=135585

  • How to configure Airport Extreme AFP disk sharing to host multiple users' home-directories (Lion, using autofs)

    I have this working, but only by completely bypassing access control, using guest access with read+write permissions.
    Do I need to buy Lion Server, to do this. All my past unix/linux experience says Lion Server should _not_ be necessary.
    This seems like a simple & obvious setup objective, but it is proving to be harder than I would imagine.
    Setup:
    multiple users, sharing two mac mini's running OSX Lion
    connected to an Airport Extreme (4th gen) with a USB disk shared (either via disk password, AEBS password, or using AEBS user's passwords).
    After much experimentation and web research, I finally have managed to get the mini's to auto mount the Airport Extreme's AFP shared USB disk. Well almost... It only works if, on the Airport, I set the guest access permissions to read+write and select the "Secure Shared Disks" method to "With disk password" or "with Airport Extreme password".  In other words, it only works if I essentially bypass/disable access control by using the guest authentication mechanism to the AFP shared disk.
    On the Lion side of this, I am automounting the users directories via "autofs". The config files for this are
    /etc/auto_master:
    # Automounter master map
    +auto_master            # Use directory service
    /net                    -hosts          -nobrowse,hidefromfinder,nosuid
    /home                   auto_home       -nobrowse,hidefromfinder
    /Network/Servers        -fstab
    /-                      -static
    /-                      auto_afp
    /etc/auto_afp:
    # Automounter AFP master map
    # https://discussions.apple.com/thread/3336384?start=0&tstart=0
    /afp/users -fstype=afp afp://;AUTH=No%20User%[email protected]/Users/
    Then, after rebooting and verifying read+write access to the /afp/users directories, I change each user's home directory: In System Preferences > System > Users & Groups, I right-click over the users to access the Advanced Options, changing the Home directory field to point at the AFP-mounted /afp/users/Users/* home directories.
    I experimented with alternate UAM specifications, as well as both OSX and AESB users & passwords. Using guest access is the only thing that has worked.
    Any pointers would be appreciated...

    Based on lots more experimentation which confirms the information in a parallel discussion (cf. Automount share as non ROOT or SYSTEM user! https://discussions.apple.com/thread/3221944), I have concluded that the Lion 10.7.2 implementation of AutoFS mechanism is broken. I submitted a bug report via apple.com/feedback.
    Work arounds..?
    Earlier I wondered if installing Lion OSX Server was necessary.  The more I contemplate this, the more I am convinced it _should_not_ be necessary. The client-server architecture is clear: my mac's are the file-server client's and the Airport Extreme is supposed to act as the file server. The only thing instaling Lion Server would do (besides enriching Apple.com) is enable me to configure one of the mac's as the file server. This would require it to be "always on" (thus enriching my electric utility as wel).  Okay, an additional benefit would be configuring software RAID disks attached to the Lion server, but Time Machine has worked fine for me in the past, backing up to disks mounted on the Airport Extreme.
    One solution is to create a disk partition for each user and instruct each user to connect / authenticate to the Airport Extreme AFP share at login.  The multiplicity of partitions is necessary since the first user to mount the AFP share, takes ownership of it, blocking other users from accessing that disk partition.  A user can "steal" ownership by reconnecting, but this will leave the other user's applications & open files dangling.
    This disfunctional situation really *****.  Before instaling Lion, I put a 64 GB SSD (solid state disk) in each of our mac's. I did this expecting to easily configure the /Users/* data on external networked storage. I'm having a dejavu "Bill Gates"-ware moment; problems like this were why I abandoned Windoz.
    I will make a few more experiments using the depreciated /etc/fstab mechanism.  Maybe that will bypass the broken-ness of AutoFS...? Alternately, I guess I could also try to run Kerberos authentication to bypass whatever is broken in AutoFS, but that would require a running a Kerberos daemon somewhere.  Possibly I could configure a Kerberos service to run on both my mac's (without installing Apple's Lion Server)...?
    Stay tuned...

  • Home directories not being created

    Hi,
    I am having trouble creating home directories for users on my OSX Server Tiger 10.4.4 running on a mac mini.
    Home directoried do not seem to be created for users on my Open Directory.
    I have configured my server to be an Open Directory master. I have no other Open Directory replicas/Servers running.
    I have set up and configured DNS. It appearts to be working correctly and can resolve my server name to the local IP (10.1.1.X) and give me a fully qualified domain name.
    When accessing users on my OpenDirectory via the work group manager the directory name comease up as "LDAPv3/127.0.0.1" (local host possibly the problem).
    When I click on the "Create Home Now" button and hit save, the home dirs are not created.
    I have checked to make sure that the home directory is shared (owner root) and it seems okay.
    I have read some other threads on topics similar to this, but have had no luck. I would appreciate any help in trying to fix this problem.
    Please let me know if any further information s required.
    Cheers

    I had the same issues you've described in this thread. It turned out that I had named my server "morris", and when the client machines went to mount a user's home folder, they attempted to mount /Network/Servers/morris/Users/whoever. When I went to the Finder, I clicked on the Network icon, then the Servers icon, and listed under there was "morris.domain.com" (where domain.com is your own local domain), but not "morris". So it appeared that there was a name mismatch.
    The fix was easy. I started up Server Admin, clicked the machine I wanted to fix, clicked the Settings tab in the right pane, the Network tab up top, and changed the "Computer Name:" field from "morris" to "morris.domain.com". From that point on, my login problems went away.
    It seems that the Server Admin-set "Computer Name" has to match the machine's FQDN in DNS.

  • 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.

  • Multiple Home Directories

    I have a OD server running 10.5.2 and and 10.5.2 file server that is a member of the OD. I am curious if this is possible:
    I'd like local home directories for all of the computers (which i currently have set up in WGM by setting the home dirs to /Users. But what i'd also like is for them to have a network home directory that they can save files to for personal use. Right now i have the share set up so that there is a folder called /Users on the file server and i'd like any folder in there to be able to be mounted by doing afp://server/username
    are having both of these at the same time possible?

    This was my point. I wanted total separation.  In order to create that separation (when trying to use a network user) I had to temporarily move the existing Snow Leopard Users folder (on Partition 1) so that the Partition 2 OS (either Snow leopard or LION) will create it's own User directory structure.  This is only needed for network users (i.e. ones that authenticate via OSX server).
    Once the process of temporarily moving the Users folder, letting the new instance create it's own directories, and renaming back, everything works.  i.e. when I startup Snowleopard all operations are within Partition 1 then if I start LION all operations are within Partition 2. 
    When installing new versions of an O/S I like to have control and manage the change so that I know I have a totally working system.  Been doing the same with Linux for years, but Mac OS/X tries to be a bit too clever!

  • Key-based SSH Authentication and AFP Home Directories

    I'm setting up some users with AFP home directories (hosted on an Xserve, with a couple of G5 towers as Open Directory clients). When logging in on the console on a G5 tower, the home directories work fine. The users can SSH into the Xserve using SSH key authentication. However, the users can not SSH into the G5 towers using SSH key authentication, and are instead asked for passwords - presumably because the AFP home directory is mounted with guest access (and thus the keys are unreadable) before the password is entered.
    Is there a known workaround for this? A different way of setting up the home directory mounting? I don't particularly want to go the mobile home directory route, because (among other things), as far as I know, mobile home directories only sync when a user logs into the GUI. If that's not the case (that is, if they will sync when a user logs into the machine with SSH), then I guess that would be a reasonable solution.
    Thanks in advance for any suggestions!

    That was just speculation on my part; I'm not sure exactly what's happening. I do know that until the user authenticates, the entire automount is mounted with guest access... and that the user can't authenticate until the key file can be read. It may be the case that I was just encountering some transient failure or the like, however.

Maybe you are looking for