Network accounts doesn't create

Hi.
When I create a network account in server.app and set its permissions to services it all looks fine. When I look into Workgroup Mgr I can see the account. When I go to the location of my home folder, the account doesn't show up. I have created network accounts before, so I do have some that works, but now I can't create new ones and be able to login with them. Not even from the server computer directly.
I've tried to delete the Library for the server, destroyed the OD Master and the result is still the same.
Any ideas?
Thanks.

Similar Messages

New open directory account doesn't create mail account

Hi All
I have a Mac Mini with lion server, Fresh out of the box i messed with it a few times to learn and then i did a clean (internet) install and started with the settings i wanted (hostname, etc) with no mistakes. (It seems Lion doesn't like applhying most changes)
When i set it up i created one local admin user that won't be in the open directory.
Anyway, I've set up the following :
* Address Book
* File Sharing
* iCal
* Mail
* Profile Manager
* and VPN
The first open directory user i added was myself and that user managed to get assigned an email account.
Susiquent users i've added have not been registered with the mail subsystem.
I've checked this using the "Server Admin" additional download management tool. (Mail service on the left, Maintenance up the top and then accounts uder that)
There is only one mail account and thats the first one i've added.
I havn't played with the settings so other than switching things on it should "just work" but it doesn't.
I've prevously setup vmail servers using mysql to store the accounts with postfix and courioer imap but that was in some ways simpler as nothing was under the covers. I havn't dug too much into the dovecot config files, etc as i believe there is an all knowing server configuration engine at work here that isn't doing its job (which i havn't dug into)
Has anyone had this issue of the mail accounts not being created?
Or can anyone point me to a fix?

It seems to have something to do with profile manager.
I get stack traces in the "system messages" logs for the "Server" application, grrrr.
I'll get that info and attempt to submit a but report tonight.

Lion Server Network Account loses all created files after logout

Hi,
I am new to Server, I got Lion Server working on a Mac Mini and everything was alright until I added users from existing client machines. I created new Users on the Server App with the same name and passwords as on the existing client machines, logged in as root on the Server and copied the client user home folder contents from an external HD into the User home directory on the Server. After that I ran Batchmod on all the User folders on the server and everything seemed to be working alright, now the only problem is, if you create a file or folder on the desktop it is not there anymore the next time I log back in. The accounts are setup as Network Accounts, and they are available from any computer in the office, they just don't save any settings that have been changed or any files and folders.
I have found the "Convert a local Home into a Network Home" post to late, http://www.afp548.com/article.php?story=20050331212133607&query=migrate%2B
does this sound like a permissions issue, and if so, can I still repair it or is it better to start fresh?
Thank you

I think your problem has a rather simple solution, since all files in a directory aren't modified unless you tell the OS or a program you've installed to.
To keep the external hard drive mounted even when nobody is logged into your server, enter the following into terminal:
sudo defaults write /Library/Preferences/SystemConfiguration/autodiskmount \
AutomountDisksWithoutUserLogin -bool YES
I think your server is looking for the external Hard Drive, but can' tfind it and thus defaults back to the internal HD.

CS3 Serial Number doesn't hold (network accounts)

I work for a school and we recently purchased Photoshop CS3 (w/ a 30-user site license) for our students to use in the computer graphics (CG) lab (all intel macbooks). We created an image with PS on it (along with the serial number, done as an admin) and applied the image to all CG computers. We also use a file-management system called Filewave to push out updates en masse instead of applying updates to individual machines.
When the students first started using the program it worked fine, no problems. They logged into their network accounts and PS ran great. However, and I'm not sure about this, but when the 10.0.1 update came through, it knocked out the serial number. Now, every time a student wants to use PS, he/she has to enter the serial number (the teacher has it in big letters up on the chalkboard, permanently).
Since that happened, I've seen it happen on two other machines (another macbook and a brand new iMac) but they are both on network (mobile) accounts. I've got CS3 on my machine and my principal has it on his (macbook pros, neither are networked) and we haven't had any problems.
I've been working on one of the CG macbooks through an admin account to try to figure out what the problem is. I did a clean uninstall (I think...the Adobe Uninstaller tool has never worked -- I get a JavaScript Alert - installer database invalid -- so I used the mac CS3Clean tool provided by adobe and deleted anything related to adobe - a mistake??). When I reinstalled the software, it installed without any errors and it took the site serial number. I restarted the machine and shut it down, and was able to get into PS without a problem. As soon as I apply the 10.0.1 update and restart, I get the prompt for a serial number again. I did another clean uninstall and reinstall, and now even without the update I get prompted for the serial number every time ( I haven't even logged into a network account yet).
So now I come to you! Has anyone ever come across this problem? Is there a bug in the 10.0.1 update that won't let the serial number "stick?" Any ideas on this one? Is there a problem using this on network accounts? Any help is welcome!
Thank you.

Got it! After spending around 3-4 hours on the phone with Adobe, we found out that the file that holds the serial number info (cache.db) was being replaced by our FileWave software. So when you enter the serial number into the adobe SN prompt, it modifies the cache.db file and allows a user to keep using PS. After a restart however, our file-maintenance software sees that there is a change to that file and promptly replaces it with an older version, thus eliminating the PS serial number.
At first this seemed kind of strange since we did not set FileWave to touch any PS files. Then we found out that Adobe Reader uses the exact same file to store its information in (which FileWave was set to maintain). So, we turned off all maintenance on Adobe products and now we are having no serial number issues. The chalk can now be erased from the proverbial blackboard. In retrospect, it looks like the 10.0.1 update had nothing to do with anything, it just turned out to be coincidental timing.
Thanks for all of your help!

Mountain lion server network accounts are not mounting network home directory, rather its creating a blank local directory

I have set up a scratch mountain lion server with open directory. copied over old user account directories and added my users that match the directory ids. Currently if a networked user logs into a networked computer, instead of mounting the network home directory, its creating a local home directory. suggestions?
thanks,
Dave

Additional info: it appears that certificates are not working either: setting up ical: "the certificate for this server was signed by an unknown certifying authority."...

Is there a way to merge/migrate my local home folder to a network account

My family has a number of Macbooks and a couple of iMacs and we've been thinking we'd like centralized storage for our media collection and other files and I'd like an easier way to deal with these machines to keep them updated, etc. Also we swap laptops and desktops depending on who needs to do what at a particular moment. Is there a way to migrate an existing home folder on a macbook to an account on the server. What I would like to be able to do is to be able to log into any computer in my home and have it look like "my" computer, with files, settings etc... Since I am new to the server world I am confused by the terminology re: network accounts and mobile accounts. Is there a good guide someone could recommend to get me started. Thanks.

Hi Yodalogger,
I hope you have yourself sorted. I've been through alot of pain with lion server, it's very buggy at best.
Your best bet is SolidWood's suggestion of network accounts if you are constantly on the same network. I use this at home and it works very well. For simplicity, you can use WorkGroup Manager for this as it's more intuitive!
If, you need a mobile account, this is what I did.
I migrated local macbook accounts to server machine (migration assistant).
I renamed the /User home folders on macbook to _backup. For safety.
I deleted local accounts from macbook. Keep your _backup home folders! Also, you will need to have a local Admin account in place. Make sure you do not delete it.
On Server. You will have local accounts created for all your migrated macbook accounts. Just remove the accounts in system preferences but ensure you leave the /User home folders in place when prompted.
On server. I created the new users (old mackbook accounts) and groups in the server app. This doesn't create or overwrite your existing home folders. So go ahead and name them exactly the same as before and make sure the accounts match your home folder's names.
On server, using profile manager, I set up mobility etc., for the device. That is, you need to enroll your macbook with the server and configure services for it in profile manager. You can add a placeholder for this in profile manager to configure stuff.
A handy tip to alleviate all the automatic push settings pain and heartache is to set the general payload to manual. You can then wip up the profile manager from your macbook to install the profiles manually. (easily done).
On Macbook, login with local admin account.
On Macbook, go to system prefs and accounts, set up your open directory stuff in the login options.
On Macbook, log out of admin. Back at the login screen, you should see your admin account and 'Other.' Give it a few minutes or so to figure this out. It needs to contact the server etc. for info.
Once you have 'Other' click on it and login with one of your new network accounts. This will log you in as a network account - you should see all your usual settings that previously existed on your macbook when it was a local account.
At this point, you whip up profile manager. http://yourserver.local/profilemanager Change yourserver to the name of your server.
Login to profile manager with your admin account. I do this as I will be downloading a few profiles that only admin has access to.
So, you need to download a trust profile, your device profile, and a profile for remote management if you have set this up. You may have seen various download buttons knocking around the the interface. In downloads double click these to install (if it doesn't do this automatically).
Log out of everything.
Log back in with one of your network accounts. This time you should be prompted to create a mobile account. Say yes and let it sync your home folders from server to macbook.
Once each mobile account is created, you can then further define user/group settings in profile manager. You download these by logging into http://yourserver.local/mydevices as the user and download the appropriate settings.
I think thats it. Sorry, if its not detailed enough - I'm presuming you know yourself around a mac! I have to say the process is straightforward but Lion Server is not. I do not get consistent results with it and I'm still trying to tame it...
By far the easiest option is network accounts. Mobile accounts need more attention.
I hope this helps (and anybody else!)
Paul.

Mobile account doesn't complete initial creation and sync process

I'm trying to setup a mobile account for a network account but it won't complete the sync process on the client MacBook Pro. Both the server and the MacBook Pro are running 10.5.5.
When I login to client it prompts me to create a Mobile account and proceeds with the sync to create the account, but when the sync is complete it just logs in with the default account setup. None of the user files or settings (desktop image, preferences, etc) appear. The sync process says "Checking..." for all the files that supposedly get copied to the client, but it looks like it doesn't complete.
Is there a way of knowing what the problem is? Is there an issue with the user's home directory, some file that prevents the sync and mobile home creation from completing?
Thanks.

I solved this myself. The user ended up have a folder on his desktop that contained a backup home folder from an old powerbook that he was trying to save. It was a complete home folder, Documents, Library, etc and I thought it might be interfering with the sync of the normal home folder. So I created a folder called Bad Stuff in the home folder and copied the old powerbook home folder into it. Then opened up the Sync Settings and excluded the Bad Stuff folder from the sync. And it worked, the sync when fine and is resyncing fine.
Hope that helps with other people with a similar problem.

How do I block a network account in 10.6.8?

TL;DR - I have a local account with the same credentials as a network account. The network account logs in, but doesn't work the way I want. How can I get the login window to not ask me to pick between the two and default to the local account? Not allowing network logins under "Accounts" doesn't work.
I have about 15 iMacs running 10.6.8 that I am having an issue with. I am in a middle school and we're going to begin testing students soon. Our plan is to have a unique user account that students login to that will automatically launch the test in order to minimize potential problems. All of these computers are part of our Windows domain to manage printing, and the account we're using is a network account. I've set up 120 other computers without an issue - they login with the network account, hold all the settings and perform exactly as expected. The exception being three machines that for whatever reason refuse to login to the network account, though everything is identical to working machines. As a workaround, I created a local user with the exact same username and password. The idea is that staff won't have two sets of credentials when they want to start the test.
These 15 computers do not hold any settings for the network account. I've modified the dock, changed settings, and every time I log out it's all lost. I log back in, expecting to see my changes, and it's as if it's creating a new default account each time. So as a workaround, I created the local user with the same username and password as in the cases above. Now when I attempt to login, the login window shows me two options - the network account, and the local account. I've disabled logging in with a network account and it doesn't make a difference. I'm assuming that this is happening because the network account did/does successfully login, even if it's not holding settings, while the machines that never did login don't have this problem, thus no screen asking me to pick between logins.
This is going to confuse my users and cause problems that I may not be available to address within an approriate timeframe. Once a network account has successfully logged in, is there any way prevent it from trying to login again, defaulting to the local account instead? I know OS X is supposed to check against local users first, but I've never seen it ask me to pick between local and network like this before. Thanks in advance for your help!

Hi Rob,
Safe Boot , (holding Shift key down at bootup), use Disk Utility from there to Repair Permissions, test if things work OK in Safe Mode.
Then move these files to the Desktop...
/Users/YourUserName/Library/Preferences/com.apple.finder.plist
/Users/YourUserName/Library/Preferences/com.apple.systempreferences.plist
/Users/YourUserName/Library/Preferences/com.apple.sidebarlists.plist
/Users/YourUserName/Library/Preferences/com.apple.desktop.plist
/Users/YourUserName/Library/Preferences/com.apple.recentitems.plist
Reboot & test.
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.

Network users doesn't show up on snow leopard client

Hello,
I am having a weird problem with my snow leopard client that won't show a list of the network users.
The server is a open directory server and other snow leopard client can show the list of the network users on login screen except one. I've tried different connections via ethernet or via wireless. (I have 2 client set up at the moment, they are exactly the same clone, client #1 show the list of network user but not client #2).
client #2 will immediately recognize the network accounts are available upon start-up but won't show the list. The computers are added to workgroup manager's computer list and is managed but if the network list doesn't show up on the client that makes the client un-managed.
Could anyone kindly give me advise please?
Thanks!
Sumomo

Hi
+". . . they are exactly the same clone . . ."+
This might be where your problem begins and ends? If you joined client # 1 to OD and then cloned this to create client # 2 then you're probably going to have the problems you're seeing?
If you want all your workstations to be the same it's best to remove any references to any LDAP Server as well as any TGTs. It's also a good idea to give each client workstation unique names prior to joining an LDAP Directory after they've been imaged. You can create a NetBoot Image with an associated workflow that will define unique names as well as join an LDAP Directory as Post Install actions.
The above assumes you actually meant to post in the appropriate Snow Leopard Forum rather than the 10.4 one? Perhaps you should have posted here:
http://discussions.apple.com/forum.jspa?forumID=1349
HTH?
Tony

Use Migration Assistant to migrate network accounts

My company currently uses Centrify for AD auth onto our macs. Accounts are created on the machine but adding the computer to AD and then logging in as the user. No settings are stored/pulled from the network. All settings/files are stored on the local drive in a home directory created on first login.
I wanted to use Migration assistant to move a user from one computer to another but when I run MA, MA doesn't see the local home folder for the network account. Is there a way to migrate the user to a new machine easily?

If the 2 computers can 'see' each other on the network, try going to System Preferences/Sharing/File Sharing and check File Sharing. Then add the User folder you want to move (+ sign) to the window "Shared Folders". That should allow the files to be copied from one computer to the other. Mount the computer in Finder and copy.

Cannot login with Network account.

Hi,
I am an experimented Mac user, but quite new with Snow Leopard Server.
I've just purchased the brand new MacMini Server.
I have configured my server with the name server.local and installed OpenDirectory as Master.
I wanted to try the network login, so I created a Test1 account in Open Directory. Then from my iMac I joined my server.local through System Preferences/Accounts/Options/... then I log off and try to use the newly created account test1.... I asked the system to change the password from first loggin... which works, but then I receive a message saying that I cannot log in for the moment... I tried everything but I just can't use the network account.
Any hints?
Cheers.

You should avoid .local at all costs when configuring an OS X Server.
.local is reserved for zeroconfig/Bonjour, and will cause conflicts.
There's an excellent tutorial for new users here
http://www.wazmac.com/serversnetwork/fileservers/osxserver_setup/osxserver106setup.htm
Jeff

Cannot login to network account (leopard client and server)

Up until now, I have used local accounts on my leopard server. I want to start experimenting with OD prior to implementing. I created a new user account in the /LDAPv3/127.0.0.1 domain, and have bound my leopard client to the server using directory utility. On the login screen, "Network Accounts Available" has a green button to the left of it. When I try and login to the server account, the login window just shakes. At first, I could enter the password and then it would prompt me for a new password. Trying to enter a new password would not allow me to login. I went back to server admin and disabled the "require new password" setting, (as well as the other good security policies)...
I have also reset the password in WGM, and made sure to disable all the security stuff there too...
Lastly, I have deleted the server in directory utility, rebooted, then added it back in, and rebooted again...
I still cannot login to the server account, the login screen just shakes
Does anyone have an idea of what settings and or logs I can check to try and narrow down what is going on?
Thanks in advance....

to close out the thread, I have working dns on my network, but I did not have dns enabled on my server. I enabled the dns service and entered just the info for my server, then assigned my server and client to use the server's ip addy as the primary dns server. Next, I created the home directory.
Once both steps were done, I was able to log in from my client to my server based account...
FYI-I found a document on afp548.com called "leopard server: advanced setup, rsync backup and automated reporting" that walks you right thru the process...Here is the link, it's a very useful doc....
http://www.afp548.com/filemgmt_data/files/Leopard%20Server%20Quickstart%20Guide. pdf
thanks again boomboom_uk and woVi, your suggestions were spot on....

Cannot login to network accounts from client computer

Hi. I'm setting up my first OS X Server setup for home use...I'm not creating a very complicated setup, but I've been working through the setup one step at a time.
Right now, I'm just running the DNS, File Sharing, and Open Directory services. I setup a couple of Network User accounts, and I wanted to try using one of the accounts to log in to a Mac client (running Mountain Lion) on the network. When the machine first comes up, I get a message that says 'Network Accounts Unavailable,' and if I try to log in, I get the error message saying 'You are unable to log in to the user account "xxxxx" at this time. Logging in to the account failed because an error occurred.'
If I stop and restart the Open Directory service, I get the following messages in the Open Directory Log:
2013-02-15 09:11:01.017801 EST - Unregistered node with name '/LDAPv3/127.0.0.1'
2013-02-15 09:16:19.139744 EST - Registered subnode with name '/LDAPv3/127.0.0.1'
Not sure if this is the source of the problem, but these are the only messages that are coming up if I turn the Open Directory off and then on again.
If anyone has any experience with this, or any suggestions, I'd greatly appreciate it!
Thanks!
If it helps:
Running OS X Mountain Lion (10.8.2) with Server (v2.2.1)
Client Machine is a VMWare Fusion VM Running Mountain Lion (10.8.2)

On your client machine login screen, type in ">console" (without quotes) in the username field and hit enter. Try and login with your network account username and password. What error messages do you get in console?
Taylor

Can't Login With Network Account After Upgrade To Yosemite Server 4

I've been putting off this troubleshooting for a while now, and after trying everything I could find, decided to post.
- After upgrading my server to Yosemite with Server 4, and my MacBook to Yosemite, I can no longer login with any network accounts.
- I was on clean installs of Mavericks before the upgrade.
- I'm using SSL for the OD, with a GoDaddy cert, the same one that was working on Mavericks.
- I've tried removing the laptop's binding using the Users and Groups preferences dialog, which does not remove the laptop's entry from Open Directory, so I manually deleted the record on the server.
- I then choose to Join again, and it looks as though everything goes through, but I still cannot login with a network account. Also, when rejoining, it does not create a binding on the server.
- If I use the Directory Utility->Services->LDAPv3, and add it that way, entering the FQDN and checking Encrypt..., Use for auth and Use for contacts, it asks me for the directory admin username and password, and does in fact create the binding on the server, but I still cannot login. What's strange about that method, is that it forces the use of the IP address of the server, rather than the FQDN, like I entered it, which would of course have problems, because the certificate's common name is the server's FQDN. It does not allow me to change from using the IP address, graying out that field.
- I've also tried destroying the OD and restoring from archive to no avail.
It looks like many users have hit dead ends with this, with some having success by completely formatting and setting up a new iteration of the server, but I will not be doing that. However, I'll be happy to try any other suggestions.
Thanks for your time,
   -- Mike

     Okay, I've finally resolved the issue, thanks to the Apple Enterprise tech support team. I'm thinking they wouldn't mind if I share this information, but I can't guarantee that this will work on your system or, worse yet, degrade your system further. However, that's fairly unlikely, just make sure you have plenty of backups before you begin any troubleshooting session.
     So I was told to perform the following instructions, which I did, line for line. The part about closing Server.app seems a given, but I'm not sure why they want you to open Server.app at the the end (maybe taken out of context from some other instructions?). I did it anyway, but you should be able to begin testing, on a client workstation, right after rekerberizing is complete. I did, however, need to reboot my client, login as local admin, and then binding would proceed, and network users are able to login again. The engineer also let me know to expect an error, something like the following: "2015-03-11 21:58:38 +0000 Error synchronizing removal of attribute draft-krbPrincipalACL from record 72519e4c-7ac7-15e4-bd42-10adb1944cbc: 77013 result: 16 No such attribute" - this is apparently normal, and did in fact happen in my experience.
So here's the fix:
- Quit Server.app (don’t just close the window)
- On the Open Directory Server, execute these Terminal commands:
- sudo mkdir /var/db/openldap/migration/
- sudo touch /var/db/openldap/migration/.rekerberize
- sudo slapconfig -firstboot
- Open Server.app
And that's it. I did nothing else on my OD server, just logged out. Immediately tried binding on my MacBook client, it failed, I rebooted, tried again, it worked quickly, and I'm able to login with network user accounts again.

Cant login multiple network accounts on the same client?

Setup:
I have created a simple Lion Server on a new i7 Mac Mini. I have configured Open Directory in Master mode and have setup 4 user accounts. I have enabled the File Sharing service and checked the "Make available for home directories" option on the "Users" file share. I have configured each of the 4 user accounts to use this location as the home folder. I have connected my client machines (all OSX Lion) to the Network Account Server.
Problem:
I can log one user into the client machine, but when using "Fast User Switching" and logging on as the second user I get the following error:
"You are unable to log in to the user account "guestaccount" at this time. Loggin to the account failed because an error occured"
In the console if I search for that user account the related error message is:
11-07-31 12:30:54.993 PM authorizationhost: ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] | PremountHomeDirectoryWithAuthentication( url=afp://inntaserver01.local/Users, homedir=/Network/Servers/inntaserver01.local/Users/guestaccount, name=guestaccount ) returned 16
Any thoughts as to why the Home Folder "mounter" failed in this scenario?

Historically you have never been allowed to use Fast User Switching to log in multiple network logins on the same client machine. This certainly applied with Tiger, Leopard, and Snow Leopard. I have not yet personally tried this with Lion.
I believe that the underlying reason for this not being allowed is down to how AFP volumes are mounted. The AFP mount becomes 'owned' by the user that triggers the login. With a network login the first user becomes the owner and this means subsequent attempted network logins are denied access to that share and hence cannot access their home directories.
With Tiger, Leopard, and Snow Leopard servers, one could configure network home directories to be shared via NFS instead of AFP. NFS gets treated a lot different in terms of mounting, and is done more at a system level than a user level. While again I have not personally tried Fast User Switching with NFS shared home directories, this approach is specifically recommended by the authors of AquaConnect (a Macintosh Terminal Server solution) in order to allow multiple logins on the same Terminal Server. This seems to be for the same underlying reason. Using NFS does certainly work for use with AquaConnect and also works for the competing iRAPP Terminal Server product as well.
Unfortunately, Lion Server while it can be made to run an NFS server, will not let you configure using NFS for sharing home directories. I have actually reported this as a 'bug' in Lion server.
Neither the authors of AquaConnect or iRAPP have actually tested this scenario with Lion server yet, but AquaConnect do plan to investigate it. It could make it considerably more difficult to use their products.
So in summary, using NFS to share network home directories in theory would avoid the problem and can be done with a Tiger/Leopard/Snow Leopard server, but cannot be done with a Lion server. It is possible however to mix Lion with older server versions. This might for some people be a possible workaround.
PS. A bonus side-effect of using NFS shared home directories was that this allowed badly written software like Adobe's applications which are otherwise notorious for having major issues with network logins and home directories to work without errors. As an example Adobe Acrobat Pro introduced a bug in version 7.0 which prevented it being able to print-to-PDF (one of the major reasons to buy Acrobat Pro). It tooks two years for them to eventually fix this in Acrobat Pro 8.1 (I know because I spent that two years nagging them to fix it and was a beta tester). Unfortunately they then reintroduced the bug in Acrobat Pro 9.0. Fortunately I discovered this side-effect got round the issue although a clunkier workaround was also possible for Snow Leopard clients by redirecting certain folder paths.

Network accounts doesn't create

Similar Messages

Maybe you are looking for