Changing local user to network user on the sever?

I moved a local user's home folder off a client computer to the server and made them a network user. The user can log in to the network numerous computers fine, as expected. However, the original computer where the user was a local user will not allow him to log in. It seems the original computer still thinks he is a local user and not attempting to log in to the server. Other network users can log in using the same original computer in question, only this user can not. Is there some way to check and remove the the local user? Local client computer is Leopard, server is Snow Leopard. There use to be an app called Netinfo Manager which I thought would allow something like this, but seems to have been removed with Leopard. I know I can give the user a new name and that would get around the problem, but it does not solve the problem. Any ideas, anyone? Thanks.

I recreated the user, then used dscl to delete the user. But, alas, did not solve the problem. Dug a little deeper into some other commands and found "id" which indicates that said user is part of many groups
:~ id username
uid=1025(username) gid=20(staff)
groups=20(staff),215(com.apple.loginwindow.netaccounts),1025(us),102(com.apple. sharepoint.group.2)
it seems that uid 1025 is the network user id, as well 1025(us) is a group on the server; don't know where 102 come from.
It seems the client still is not looking on the server, because it immediately shakes off login.
Any more thoughts?
Thanks.

Similar Messages

  • How can i change a password for network users?

    Good day. I have a problem with changing passwords on server Yosemite. As i understand there is no way to change password for the network users remotely. I mean, when for example someone will change his password and then will forgot it how can i change it? When i open a server manage program and go to the "Users" and than open a setting for the user - "Change Password..." is not clickable.

    Hi Dcp24,
    If you are having issues resetting a user's account password on your server, you may find the information in the following article helpful (article is aimed at Mavericks, but the steps should be similar in Yosemite):
    Mavericks Server Admin: Reset a user’s password
    Regards,
    - Brenden

  • Local copy of Network User files

    With the latest OS X Server, I see how you can use a Network User account to log onto the server or any "bound" client machine on the home network.  However, when leaving home with a "client" machine (e.g. MacAir with Mountain Lion), is their someway to have a local copy of the Network User files on the client?  Hopefully you can see the objective of this question: while at home, use any machine to work with the files, but when you leave the network, how can you have a synchronized copy of the files on a Mac laptop?  If needed I can dedicate a client machine for each user, so maybe there's a way to designate the files of a Network User on another, non-server, client machine like a Mac laptop?

    I have the same question, cause I do not have more space on iCloud for more backups, and I really want to save an older backup from my iPhone, that speceific backup was the last one before my iPhone was stoled. if anyone know if it is posible to locate that file on "iCloud" and save it, I use iCloud instead of iTunes, and I do not know where to look for it...
    thanks

  • Migrating local users to network users

    Hi - I have seen answers for past versions of the server, but none seem to work.
    I have 5 macs, 4 users.  I want them to be able to log in from any mac and have their home screen/files appear as if it was on their (former) local machine. Also want to set up group folders that can be accessed as well.  The latter part is no problem setting up, but how can i migrate the local home folders to the network easily.
    I have set up user accounts, bound local machines to the server, tried mobility settings but can't get it to work.
    I read somewhere that if the shortname is the same on the local machine as the server that may cause problems.
    Also - is there any advantage to setting up machines vs users in workgroup manager?
    Thanks

    Hello,
    if you want your users to be able to login from any machine on the network, then your users must exist in the OD on the server and the client machines must be bound to to the server. Client machines must be set to use network accounts.
    If the client machines are not portable (MB, MBP, Air etc), set you users as _plain_ network users, otherwise use Mobile accounts. The difference is that in case of mobile account are user credentials cached on the client, so they are able to login even when they are on another network (so the server is not available to authenticate).
    Next you need to set up network home for network your users. Start up Server Admin, select a sharepoint and enable automount as User home folder.
    Next, in the workgroup manager select your users, and assign them new home folder paths. As a last step copy contents of local homes to the new network location.

  • Upgrade Local User to Network User for PHD

    I have a normal local user on a workstation. The home directory has quite a bit of stuff. I would like to create a Portable Home Directory for that user. If possible I would like to keep everything on the workstation as it is.
    I know it's easy to create a network user, and then sync the PHD on the local machine. But how do I do it the other way around?
    If I create a network user with the same name, I can only login on the workstation as the original local user, and no syncing is done.
    Is there a less drastic way than
    1) "ditto" the local home directory onto the network user home directory
    2) delete the local user
    3) log into the workstation as network user (with the same name) and sync the PHD ?
    Thanks!

    Hi Xiao Di Di I followed this http://www.afp548.com/articles/Panther/mcx2.html article when converting a local account to an AD network account and all went well. I did have the luxury of creating a 'test' mobile account of the users as the local users were all named 'staff_user'. I know the article is written for Panther, but did what I needed it to do.
    Cheers

  • Can I have a network user with the same name as a local user?!

    I have just set up Mac OS X 10.8 SErver with Open Directory.  I have about 20 machines that I will be setting up, some which have mainly been used localy and just used to tap into Shared Files, [historically], but am wanting to use network users for better backup and support.
    However some of the legacy accounts were not used on off the server...  What I have is the following :-
    a)    [Person A]  - They are a network user with Password [Password A]
    b)    The computer is [Person A], they have a Password [Password Old] (so it is different)
    I have Network Account Users turned on, with a green dot! (have domain all set up)
    However How do I connect using either a or b.  depending on what i feel like that day!
    ? Help any ideas.
    Ultimately I will have set up all my client machines with a client admin user and standard password... but I am not there yet!

    Moving from local (legacy) users to network users takes a one-time hassle of moving the contents of their local home folder contents up to the server. Using a finder copy never worked for me. What I finally found worked reliably was using rsync to copy the entire users local folder up to the server. Once on the server, move the files into place (if you didn't rsync them there directly. Finally, Chown all the files (on the server) to associate them with the correct userID on the server. If everything looks right on the server, you can test by trying to login as this user from another local Mac (but now as a network account), and hopefully their home folder looks like they expected.
    Note you will need admin access in the local machine and the server to rsync their home folder. You don't want to be logged into their account while trying to copy their files up to the server.
    If rsync is not your bag, a portable hard disk and/or disk image of their home folder is another way to move their stuff.
    Once you've verified that their network account got to the server ok, then REMOVE the local account.

  • 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

  • Can not make network user accounts

    After upgrading from 10.6.8 Server to 10.8 and installing server tools, I can not make network user accounts.  All of my old network user accounts migrated to the new OS and work properly, I just can not seem to make new accounts under 10.8.
    Under 10.6.8 I would log into Workgroup Manager as diradmin and I could pretty easily make new users.
    Under 10.8.2 I launch the server app and click on "users".  The addition (+) symbol in greed out for making new users.  I can make local users via System Preferences, but I can not see any way to change local users to network users via either System Preferences or the Server app.
    I have logged into the server app using a local administrator account, the diradmin account, and the root account.  None of the accounts allow access to create new network users (addition symbol is greed out).
    Is there a trick to making network users in 10.8 that I am missing?
    (as an aside, I have noticed I can log into Directory Utility as diradmin and can view the node with all my network accounts.  It seems like I might be able to manually create a user account this way, but I'm not quite sure how to make the user record)

    Open Directory service is started and functional for all the pre-existing network user accounts that were made under 10.6.8 and earlier.  I just can not seem to create new netowork user accounts.
    I followed the steps on this page and managed to make a user record that appeared as a network user in the Server app, but I still can not seem to log in under the user I made in this fashion (dscl command via terminal).
    http://www.deadmarshes.com/Blog/20111105010130.html

  • Problem setting up Network User

    I am running Mac OS X 10.5 Server with clients running 10.5 also. Currently, there are several users on the server, but in Workgroup Manager, their home directory is set to null. The users have local accounts on certain 10.5 clients which are linked to their accounts on the server. So when they log in to the client, they are authenticated against their account on the server, and various settings (Mail, iCal) are picked up from the server.
    I now need to allow users to log in to any client machine without setting up a local account (and linking it to the server account) first. So I have gone through the procedures specified in the 'User Management v10.5' documentation, specifically the 'Administering Share Points' and 'Administering Home Folders -> Creating a Network Home Folder' sections. I have used the second set of procedures to create a network home folder for a single test user. I assume that this makes the test user a 'Network User', though how to create a 'Network User' is not explicitly specified anywhere.
    The problem is that on a client machine (that does not have a local account for the test user), the test user's network account is not listed on the login screen (though the login settings indicate it should be), and I also cannot log in as the test user by clicking on 'Other...' and supplying the requisite credentials. I should note that the client Mac is 'attached' to the server (eg. through Directory Utility).
    Can anyone provide advice as to what's going wrong? Is there some other (secret?!) step that is needed to create a Network User so that clients see the user and allow the user to login?
    Many, many thanks,
    Jolin

    Hi Leif,
    Many thanks for your reply.
    Leif Carlsson wrote:
    The only way of "linking" a "local" account on a computer to a OpenDirectory account that I know of is to create the "network" account homefolder on the local/client machine HD when the user is logging in to the OD server for the first time.
    Actually, it is possible to not have a network account or home folder, and link a local user to a user account on the server. When a client computer is bound to the OpenDirectory server, in the 'Accounts' preference pane of the client computer, there is a field called 'Server Account:' with a 'Set…' button. Clicking the 'Set…' button allows one to link the local account to the server account. Even though there is no home directory on the server, when the user logs in to the client Mac, the password and any managed preferences for that account are taken from the server account.
    The client machine has to be bound to OD first and the account should preferably be setup as a mobile account (so the account can be used even if the computer isn't connected to the network - logins are cached locally).
    I have bound the client machine to the OD server, but I have not yet set up the account as a mobile account. I plan to do this eventually, but wanted to get the 'basic' network user account working first.
    For a "true network home" folder residing only on a server volume/share, the OD account should use a share(point) setup in Server Admin for an automount AFP (or NFS) "User home folders" share.
    I have done this. The server has a sharepoint called 'Homes' which is set to automount over AFP, with the setting 'Use for: User home folders and group folders'. This seems to be working, because on the client Mac, the 'Homes' sharepoint automatically appears when browsing the available network volumes.
    Then in the OD the user should be setup to use the automatically created path (afp://<server FQDN>/<shared folder>) as it's homefolder path.
    I believe I've done this as well, using Workgroup Manager. When viewing the 'Basic' tab of the user, the 'Home:' is given as 'afp://<server FQDN>/Homes/jwarren'. That looks right to me, but I cannot login as the user 'jwarren' from the client Mac's login screen (Network Users are enabled on the client Mac). When I log in as a different user on the client Mac, I can browse the network, and the above afp path is automatically mounted.
    Is there some other setting needed so that the client Mac will 'see' the network user I have set up? As I say, the autmount sharepoint is set up, and the user is set up in OpenDirectory (on the server) to have a home folder on the automount. But when I'm at the login screen on the client Mac, the network user does not appear in the list, and if I try to login by typing the username and password manually, the login window just shakes as it does when one enters the incorrect password.
    Any further help much appreciated!

  • Adobe Reader and Firefox incompatible with network users

    We have 17 workstations running OSX 10.7.3, all users log in to OD "Home Accounts". The problem seems to be when making Adobe Reader v 10.1.3 default reader, logging out then logging in causes, Preview app to become default reader. This issue also happens with Firefox and Safari. Set Firefox to be default browser, log out, then back in Safari is now default. These issues don't seem to be an issue when running as local user, only network user. A side note, is the default setting stays in effect until you log out.
    I seem to recall in earlier days, certain local apps had problems connecting daemons to external servers.
    We can't possiblly be the only users with this issue.
    TIA
    Steve
    LA Studios

    I have 10.7.4 and have the same issues that everytime I log out, my browser goes back to Safari and pdfs open with Preview!  Grrrr!!  I cannot get my preferences to retain these 2 things - very frustrating!  And this is only since I moved over to Lion .....

  • How do I prevent other Mac users from changing my Airport Extreme Network Name and Password within the Airport Utility?

    How do I prevent other Mac users from changing my Airport Extreme Network Name and Password within the Airport Utility?  My company is using an Airport Extreme in our office now and I want to prevent other employees from messing with the network/settings.  Is there a way to place a password on the settings to allow only the admin to access the network name and password? 

    Hi - you have will have to change the device passwords on all the base stations and then don't give them to anyone except the administrators and tell them not to save them on their computers that use the older versions of the Airport Utility - for the newer versions like the mobile apps, as soon as you enter the pasword it is saved and is visible in the advanced pane along with the network password - so if anyone gets a hold of your iPad or iPhone, they can edit the whole network - I have this same issue with my networks in the office and it is inconvenient but doable - I hope this helps

  • How do I change system settings so that users are not required to enter the mac's admin pw in order to join a wifi network?

    how do I change system settings so that users are not required to enter the mac's admin pw in order to join a wifi network?
    Right now my macbook pro requires an admin password before connecting to a new wifi network. In other words when a user that is not an admin tries to connect to a new wifi network the pop up displays indicating that it is locked and an admin password is required.
    Is there a way to remove this restriction so that a non admin can connect to wifi without the mac's admin password.

    You can enable / disable this option in System Preferences:
    System Preferences > Network > Wi-Fi > Advanced > Wi-Fi tab > Require administrator authorization to: Change networks

  • How to Change Date Format according to the Locale/Country of Portal User

    Hi,
    In a webdynpro applicaiton, how to chage the  Date Format according to the Locale/Country of Portal User.
    Consider for INDIA: mm/dd/yyyy
    Consider for UK: yyyy/mm/dd
    So when i select the date from the Date Picker[input ui element bound to date context variable], the date format should be displayed accroding the portal users country/locale.
    Creating a simple type for every date format in the dictionary would not be the right solution.
    Please help.
    Thanks,
    Regards,
    Aditya Metukul

    Hi Aditya,
    Check out the following post in SDN and refer the
    Bertram's reply on the same topic.
    date format
    Regards,
    Shubham

  • Giving an OD Network User/Group local admin rights.

    Is there a way to manage workstation admin rights from the server?
    I ran into a problem with Lightroom that requires admin privileges to change the program preferences. We have alot of graphic art students with roaming profiles, spread out across 5 labs, that need to make this change. I would like to be able to add a group or all network users to the local admin group, for a few days, so the students can make the changes.

    This works on 10.5, not sure about 10.6.
    As root on the client.
    Upgrading legacy group for local admin group - this is from 10.4 days, not sure if you still need to do it.
    dseditgroup -o edit -f n -t group -n /Local/Default admin
    Nest OD group in local admin group
    dseditgroup -o edit -a DirectoryAdminGroup -t group -n /Local/Default admin
    Gen

  • Can't create Local Network Users in Yosemite

    I can't create Local Network Users (or change passwords)
    Logged on to /LDAPv3/127.0.0.1 as directory administrator
    When I try to create a new user (press the [+], fill in the form), it brings up the message:
    existing connection is not authenticated or secure: password change denied
    I suspect this is emblematic of other issues. I can authenticate for Mail and SMB, but not for AFP or Xcode

    So I had this problem last night as well when I upgraded my 10.9.5 OD master to 10.10.
    Two obvious problems after that upgrade:
    1)  Could not add a new Local Network User
    2)  Existing users could not connect via AFP (but could via SMB)
    Through a series of trial and error (and with two Apple Support people...), we found that the following actions seemed to help fix some (but not all) of the problems.:
    Problem #2 seemed to initially be fixed by archiving the OD Master, destroying the OD Master and then reimporting from the archive.  I archived from the upgraded 10.10, but should probably have tried restoring my 10.9.5 archive (which may end up being why I still have some problems...)
    Problem #1 seemed to be solved when I used WorkGroup Manager to reset the password on the Directory Administrator account I use  (I also blew out all references to that account from the Keychain, so everything reprompted me to add that password
    However, we think the root cause of this might have been that in /var/db/openldap/migration, the following "dot" files were still present after the upgrade
    fs:migration root# ls -la
    total 6308816
    drwx------  10 root  wheel         340 Oct 30 18:59 .
    drwxr-xr-x   6 root  wheel         204 Oct 30 18:57 ..
    -rw-------   1 root  wheel           0 Oct 30 18:59 .autossl
    -rw-------   1 root  wheel           0 Oct 30 18:59 .enableODProxyd
    -rw-------   1 root  wheel           0 Oct 30 18:59 .rekerberize
    -rw-------   1 root  wheel           0 Oct 30 18:59 .updateLocales
    -rw-r--r--   1 root  wheel      333436 Oct 30 18:57 authbackup.ldif
    -rw-r--r--@  1 root  wheel      617453 Oct 30 18:57 backup.ldif
    -rw-r--r--   1 root  wheel      617453 Oct 30 18:57 backup.ldif.backup
    -rw-r--r--   1 root  wheel  3228537344 Oct 30 18:59 oldsystem.tar
    Those 4 .dot files were *not* present in that directory on the two other test OD Master servers that I upgraded without issue.
    So we removed them and after having done all the above as well -- I can now add users to the server.   The OD engineer I talked to thought that the presence of those .dot files may have been triggering something to rerun every time PasswordService launched.
    When all was said and done, I was then able to "kinit <mydiradminaccount>" correctly and get a "klist" without issue.
    ALL THAT SAID:  As of this morning, *some* (most?  I don't know yet) of my existing OD user accounts are able to successfully log into the server.   A couple of them (so far) are reporting that their account is "disabled" (which is different from the "shaking"/can't-log-in behavior) -- but they can still log in via SMB -- so I think there was still a problem migrating OD accounts in the upgrade process.
    AND -- I noticed that -- in Server 4.0 -- "change password" is greyed out, so I have to use WorkGroup Manager to change server account passwords. 
    Whee...

Maybe you are looking for