Problems creating home directories

I'm having a lot of trouble trying to configure user home directories on a Windows 2012 R2 server running active directory.
What I've currently done is created a share on the drive called "home" and made it read/write accessible to "authenticated users".
In the user profile where I set up the user home directory, I select the drive letter (this case H:) and put in the path as "\\fs1\home\%username%".
On my windows 2008 server, after I hit apply, it would create a folder with the username in the home share that I created.  It doesn't do this on the 2012 server.  Am I doing something wrong?  I verified that \\fs1\home\ was accessible remotely,
and it is, but there are no user directories created in it.
Any ideas?  Thanks!

Hi,
More information for you:
Automatic creation of user folders for home, roaming profile and redirected folders
http://blogs.technet.com/b/askds/archive/2008/06/30/automatic-creation-of-user-folders-for-home-roaming-profile-and-redirected-folders.aspx
If these links couldn’t help you solve this issue, please post out related errors and warnings for troubleshooting.
Best Regards,
Amy Wang

Similar Messages

  • No longer able to create home directories

    I'm having a slight problem here. Recently after adding some new users, with PHD activated I have been having problems creating home directories on the server.
    If i am in local node I can create home directories, but once i switch over to LDAP/myserver home directories are no longer created ---> this leads to me no longer being able to sync homes or do anything.
    Does anyone have any advice for me? I've deleted the users directory, created new ones, turned the ldap service off, restarted, turned it back on, restarted, added new users tested tested tested to no avail.
    Any help would be appreciated.

    My Woes continue :
    So far I have reinstalled OSX server, re-set everything up for an OD master, dns ,afp ect. And I am still having issues with WGM to create home directories for my users. SO, i decided to create all my users and than type in terminal : createhomedir -s --> the end result no changes.
    Next I tried
    Createhomedir -b and voila I get all my home directories built. Fantastic. Or so I think. so i start to log all my PHD users in, everything seems good. Than i start a test, simply downloading a file to my desktop. I hit sync now. The sync window comes up, few conflicts but other than that everything looks great. I goto the users home directory on the server and no changes.
    So where are my PHD's syncing to?
    This is getting very frustrating because I am pretty sure nothing is being backed up anymore.
    any advice would be great.

  • Workgroup Manager won't create home directories; no error message

    This is quite frustrating. For the past 3 years or so I have used the same procedure to add new users to my LDAP directory:
    1) In Workgroup Manager, click the New User button
    2) Assign name and password under the basic tab
    3) Assign group memberships under the Groups tab
    4) Under the Home tab, select the right place (nfs://my.server.org/Volumes/Users), click Create Home Now
    5) Click Save
    Suddenly, when I try to do this yesterday, workgroup manager won't create home directories anymore. I could probably do it manually, but I'm not sure how to get all the right skeleton setup in there. But my main question is, why doesn't this work anymore? Why can't I at least get an error message instead of being silently ignored?
    I share admin duties with other people, so it's possible someone installed an update recently; all I can really say is that I'm running Leopard Server 10.5.8 right now, and can find out whatever else is relevant.
    Any ideas?
    Thanks!
    ~Ben

    Thanks for the pointer to createhomedir - that did indeed do the trick. (How on earth do people find these little nuggets).
    I hesitate to mark this as solved however - it's a functioning workaround, but does nothing to explain why on earth the GUI suddenly stopped functioning.
    But in the (likely) event that that question never gets answered, thanks again for letting me get on with working!

  • Creating Home Directories

    Hi,
    I'm still fairly new to Mac Servers (come across from a Windows background), and am having trouble creating the home directories for the users I've created.
    Initially I created the user (just bog standard users - no mail, no calendars etc), bound the client machine to the server in Directory Utility (all working ok so far), even added the client machine to workgroup manager.
    However, the user was unable to logon - just a shaking screen after each logon attempt. Confirmed the password etc, all ok.
    Deduced (after looking on here) that it may be because the client has no home folder (a prerequisite for 10.5, even though it doesn't tell you that). However, coming from a Windows background, am unfamiliar with the syntax of network paths for Mac/Linux.
    The home folder location I've created is on the server: Server HD/Users/Shared/ and it is shared in Server manager as a Share Point. Actual folder permissions include Users: Read and Write, and share permissions are the same. AFP is on.
    In Workgroup manager, the syntax for the three fields I currently have is:
    Share point URL: afp://servername.domain.co.uk/Users/Shared
    Path to Home folder: username
    Full Path: /Network/Servers/servername.domain.co.uk/Users/Shared/username
    I click OK, then click on Create Home now, then Save and it returns the error: Unable to create Home Directory. The home directory could not be created because an error occurred.

    Hi
    +". . . The home folder location I've created is on the server: Server HD/Users/Shared . . ."+
    This is possibly where the problem lies? By default OSX Server, after installation, creates Users, Groups and Public as default share points. You only have to enable AFP and those shares are instantly available once users have been created to access them.
    Don't be tempted to delete the default Users and Groups folders as the Server will complain. There is already a default Shared folder that the Public folder resides in. Don't be tempted to delete these either.
    There is no need to create another shared directory within the top level User Directory as that is already being shared. Once you promote to OD Master and populate the node with users all you have to do is set the default Users folder to be auto-mounting for users Home folders. There is no further need to share it or define permissions. These are correctly set when the folder was initially created.
    In Workgroup Manager you should see the path as afp://fqdnofyourserver/Users. That's all you need. Simply select it and click Create Now and Save. Navigate to the Users folder and you should see the home directory has been created. There is no need either to tinker with permissions for individual users' home folders as these are correctly set at the time of creation. The default permissions model used for users' home folders is standard POSIX.
    For clients to access networked home folders correctly it's a good idea if the server's IP address is used to resolve DNS queries. Assuming the service is placed with the server?
    Unlike Microsoft, Apple don't tinker with Open Source OpenLDAP as much. They still modify it to suit their purposes but it's more standards based. If you don't want to use the default Users directory on the boot volume then simply un-share and un-automount and define a similar directory on another volume (a RAID for example) instead. Define it as a Share in Server Admin and set it for auto-mounting home directories. It will show in WGM with the correct path. Avoid long names and spaces if you can. You could stick with Users as it works.
    There is no need to resort to the command line in any of this as all the tools you need are there in the interface. Provided DNS is correctly configured on both pointers and you have not used .local as the basis for DNS it does work as it's supposed to and it works well.
    Tony

  • Workgroup Manager doesn't create home directories for OD accounts

    I'm having an issue where home directories aren't created for OD accounts. My setup is as follows, the home directories are stored on the OD Master (the only Apple/OD/AD server on the network), and the home directory paths are filled as afp://192.168.1.254/Customers, fakeuser, /Users/Customers/fakeuser
    This same pathing scheme works fine for local accounts, however for OD, clicking Create Home Directory and saving the account does nothing (no errors, nor folders created). If I ftp into said account, I wind up being directed to /Users (definitely not the expected behaviour)
    I am deploying a web based upload system that I want to authenticate against OD users so as to share home folders and permissions with the ftp server, once I have this figured out I will be migrating a bunch of accounts to OD from local.

    In addition to potential DNS issues, it sounds like you may be using the wrong procedure to define the users' home directories. You should never have to specify the paths manually; instead, define the share point ("Customers" in your case) to be automounted, and then it should automatically show up in the list of available home folder locations, with all the necessary paths predefined. Here's the full procedure:
    1. Run Server Admin, and select: the server name in the sidebar -> File Sharing in the toolbar -> Volumes & Browse under that -> navigate to the /Customers folder in the column view.
    2. Make sure the folder is being shared (with it selected, you should see an "Unshare" button near the top right of the window); if not share it with the Share Button (then Save the change).
    3. Select the Share Point tab under the file browser (NOT the one above it), and select the Enable Automount checkbox. A dialog will open asking for the automount details; make sure the Directory is set to /LADPv3/127.0.0.1, Protocol to AFP, and Use for is User home folders and group folders. OK the dialog, and be sure to click Save to make the change take effect.
    4. Run Workgroup Manager, and select Accounts in the toolbar -> Users (single person icon) tab under that -> some user account(s) you want to configure under that -> Home tab on the right.
    5. Select (None) from the location list and click Save (this wipes out any current setting, so we can rebuild it correctly).
    6. The Customers share point should be in the list of available locations (due to being configured for automount); select it, then click Create Home Now, and finally Save.

  • Problem with home directories NOT in Users and Workgroup manager

    I am setting up a Leopard server (10.5.3) with the users directories in /h1. This is mounted as /Volumes/h1.
    It is exported under AFP as /h1.
    When I try to get Workgroup manager to create a home directory, I can enter the home directory as:
    afp://quattro.innocon.com/h1
    path is 'user'
    Full path is:
    /Network/Servers/quattro.innocon.com/Volumes/h1
    However, when I try to log in as this this user, it says that the directory /Network/Servers/quattro.innocon.com/h1/username does not exist.
    I cannot seem to figure out why the 'Volumes' part of the full path is being lost.
    Any ideas on how to get this right?

    have you checked to see if /Network/Servers/quattro.innocon.com exists?
    I'm having ALOT of issues with automount not picking up on the mount-maps set by Open Directory.. If anyone has any solutions on this it would be great.

  • Create Home Directories on an Xserve for AD clients 2

    Is it possible for an os x client bound by OD/AD who normally gets it's AD network mount home from the win2k server to get the network mount home from the os x server's hard drive instead. But, also having the ability for that AD user to go back and login to a PC pointing them to their AD win2k server's mounted network home and not the os x server's MNH.
    Should I be editing the “Augment Attribute List” adding <string>dsAttrTypeStandard:HomeDirectory</string>
    as described in the Leveraging AD pdf?

    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

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

  • Active Directory plugin not correctly creating users home directories

    Is there a trick to getting the Active Directory plugin in 10.4.7 to correctly create home directories for AD users? It is creating them with the root owning everything in it, and this is unacceptable.
    Our setup: We have a Active Directory network (Windows Server 2003 SP1 as DCs), and are trying to integrate some of our Mac clients to user AD single-sign logins. We are not using OS X Server at all.
    We do not user any sort of network home directories, as our users always use the same computers.
    We just want a user to have a local home directory created when they log on for the first time. Unfortunately, the directories are being created with the wrong permissions.
    One thing that may be the problem: the UID that are assigned to the AD users on the Mac clients are very high (> 60000000000). There is an error in the log that a UID that high cannot be added to the lastlog db, so that may be another symptom of the problem.
    Is there a way to fix this wihout changing anything on the domain?

    Is there a trick to getting the Active Directory plugin in 10.4.7 to correctly create home directories for AD users? It is creating them with the root owning everything in it, and this is unacceptable.
    Our setup: We have a Active Directory network (Windows Server 2003 SP1 as DCs), and are trying to integrate some of our Mac clients to user AD single-sign logins. We are not using OS X Server at all.
    We do not user any sort of network home directories, as our users always use the same computers.
    We just want a user to have a local home directory created when they log on for the first time. Unfortunately, the directories are being created with the wrong permissions.
    One thing that may be the problem: the UID that are assigned to the AD users on the Mac clients are very high (> 60000000000). There is an error in the log that a UID that high cannot be added to the lastlog db, so that may be another symptom of the problem.
    Is there a way to fix this wihout changing anything on the domain?

  • Create Home Now, Doesn't Work

    Hello all. I am trying to create home directories for users in a "Golden Triangle" setup.
    On my OD Master I'm trying click the "Create Home Now" button and no home is created. The home directories are hosted on a share that lives on a Promise RAID. I setup the folder "Users" and made it a sharepoint. I enabled the option to "Use as home folders". From a client machine I have found /Network/Servers/myserver.my.com/ with an alias named "Users". I've also tried using the createhomedir command in Terminal. That didn't work either.
    Currently I do have a home folder that is on the share and that works perfectly as a Portable Home Directory, but I created this folder manually because I was migrating a user from a windows file share. I'm trying not to have to go in and change permissions and all that.
    I've read a couple of other posts about the subject so I apologize for any reposting. Can anyone help???

    Hi Tony
    Thanks for the reply. You are correct. The environment is your run of the mill AD-OD integrated setup.
    I am giving users defined in AD the ability to use home folders shared on my OS X servers. This has been successful and I have been able to move my home data from a windows file share to the OS X User sharepoint that I've established and am using Portable Home Directories.
    My problem arise when I am trying to do create home now for a user account. To test this I have setup a few test account in OD to try and generate homes. I would think that this would work. Maybe it won't. I'm also assuming that for all of the AD users I will have to manually generate atleast the root home directory folder (e.g. wsmith home directory within the Users directory). I need to do further testing but will the underlying folder structure be generated upon the user's login (i.e. Document, Public, Music, etc.)? I don't think it will.
    I'm really just trying to find the most efficient way to get AD users migrated over to having Network or Portable Home Directories on the OS X sharepoint. I have it working with the UNC path and all. I'm just trying to make sure to see whether creating the folder manually is the best way because I've have go in and apply the correct permissions for the folders underlying a user's home folder.
    Thanks for the help.

  • Crearting Home Directories for AD clients

    I am trying to create Home Directories on an Xserve for AD clients. We get a permissions error when the PC server attempts to create the folder.Am I missing a step ?

    Three steps actually. >=)
    1: Yell loudly
    2: Push the PC server off the desk
    3: Kick it across the floor.
    Okay okay... Just kidding.
    It's an issue with the PC server trying to use it's own permissions to create the folder. Make sure the directory that the PC's trying to place in has the "everyone" posix permissions set to read and write.
    After you're done creating folders, set it back to read only.
    -Graham

  • Flash with OS X Home Directories

    Hello
    I work in education and am having problems when I try to use
    the Publish Settings or Publish Preview command with OS X 10.4 and
    network home directories. Basically, when I try to publish a
    website or goto Publish Settings, I get an error saying "No valid
    HTML templates are available to complete this operation". The HTML
    templates are actually in the users home directory but seems to
    have trouble finding them. When I try this as a local user it
    works, just a problem with home directories.
    Hope somene can please help.
    Thanks.
    Regards.

    Yes. This is the current version: Adobe Flash Player 15.0.0.199.

  • ARD 3.2, network home directories and two admin workstations = problems

    Hello:
    I've got a situation where I've got two ARD admin workstations in two separate classrooms where the instructors have network home directories. If an instructor switches from one machine to another after setting up ARD on the first (i.e. entering a password, making computer lists, etc.), they are asked to enter their ARD password and they are not allowed in no matter what password they enter. It seems that there is some machine specific information in the ~/Library/Preferences/com.apple.RemoteDesktop.plist file because the only way around the problem that I've found is to delete this file and re-enter a password. This creates a new plist file, but the problem comes back as soon as the user uses ARD on the other admin workstation. Each machine has a separate (licensed) copy of ARD on it.
    What's the right way to use ARD with admins that have network home directories?

    Hi,
    You mentioned the machines are all from a single image. I realize you are an experienced ARD user. However, there are quirks in this app at any stage of development. I'm sure you already applied a unique name to the shared network name and have no DHCP conflicts as well as checked that all the accounts, not just the admin account that permissions are checked. Although you may have all the correct ports addressed and configured, there is no accurate accounting for the gremlins. These play havoc across the network. Sometimes the only thing you can do is go to the machine and walk through the settings as if it was the first time. I can't tell you how many times a problem has resolved itself after just logging into the admin and redoing the settings. I mean the exact settings that are already selected. Sometimes the settings were actually wrong, even ones that came from an identical image. Like forgetting to select the observe and control selections in the sharing options for all the users. Other times it was simply deselecting and reselecting the options and restarting that snapped the machine out of the funk.
    Aside from the occasional discovery of admin setup issues, I live by the motto "the simplest solutions are usually the best, and should be tried first". Glitches do happen though. Sometimes running the scanner and reselecting and dragging the same machine into your user lists can refresh a connection that is not acting properly. I have detected countless quirks that cause strange side effects. Do a get info on the specific machine and delete the IP, then make sure you have the "name".local in the DNS name field. Re-enter the admin or try a user account name in this experiment and test this. This has given me clues to setup issues before having to go to the machine. I know this stuff sounds simplistic but it has solved most of my issues.
    Good Luck

  • Problem changing the location of multiple users home directories...

    I've just set up a new entry level model iMac for my Mum. Without getting into a discussion about the benefits or otherwise of doing so, I partitioned the hard disk into two with the first partition for the system and the second a scratch disk for files etc. I set up two users, one for my Mum and one for my younger brother. I then copied the users folder across to the scratch disk and in advanced options in the users list set each account's home folder to the relevant user on the scratch disk. This is the same set up as I have on my own system and with which I have no problems and which runs well and cleanly. I have only one account on my system. However on the iMac, the second user (my brother) is unable to write to the new home directory. Downloads don't work and preferences including right click for magic mouse, dock etc are forgotten instantly. It seems there's a permissions issue.
    I've set the machine up this way in order to keep all their files separate from the system after their last Mac got very bogged down. I expected it to work in exactly the same way as my own. Does anyone know how to successfuly set up both user accounts in this way?
    Any advice would be much appreciated...
    Message was edited by: Jimmy Hat
    Message was edited by: Jimmy Hat

    Jimmy Hat wrote:
    I've just set up a new entry level model iMac for my Mum. Without getting into a discussion about the benefits or otherwise of doing so,
    still not advisable though IMO.
    I partitioned the hard disk into two with the first partition for the system and the second a scratch disk for files etc. I set up two users, one for my Mum and one for my younger brother. I then copied the users folder across to the scratch disk and in advanced options in the users list set each account's home folder to the relevant user on the scratch disk. This is the same set up as I have on my own system and with which I have no problems and which runs well and cleanly. I have only one account on my system. However on the iMac, the second user (my brother) is unable to write to the new home directory. Downloads don't work and preferences including right click for magic mouse, dock etc are forgotten instantly. It seems there's a permissions issue.
    how exactly did you copy the home directories? did you do it using drag and drop in finder from one account? then the copied home directories both are owned by that account and the permissions need to be changed. please clarify if that's what you did.
    I've set the machine up this way in order to keep all their files separate from the system after their last Mac got very bogged down. I expected it to work in exactly the same way as my own. Does anyone know how to successfuly set up both user accounts in this way?
    Any advice would be much appreciated...
    Message was edited by: Jimmy Hat
    Message was edited by: Jimmy Hat

  • Portable Home Directories and iphoto - problems

    Hi
    We have recently set up the 'mobility' funtion for our staff via our 10.4 server - thuse creating Portable Home Directories. This all seems to be working fine and documents sync perfectly. What is not behaving is iphoto - we keep getting synchronization conflicts based around iphoto files - not the images themselves but files such as:
    Library6.iphoto
    iphoto.ipspot
    Dir.data
    Albumdata.xml
    .lpoptions (not sure if this one relates to iphoto but is recurring on numerous acccounts)
    Anyone have any clues on this. Iphoto does not seem to be syncing the images at all........and I can't resolve the conflict.
    Chris

    iPhoto works fine with my users so I can't offer much assistance there, but .lpoptions is where the default printer is stored, and that's typically not something you'd want to synchronize. I personally exclude it.

Maybe you are looking for