Mountain Lion Server: add network user to remote management

Hi,
So recently I have upgraded from Lion Server to ML Server. A little disappointing, but whatever, I've moved on and got everything almost back to where I had it with Lion.
My last few issues I believe are related but can't quite figure it out. In Lion I have an admin profile and then a network user profile that I used on my MBP bound with AD. I'm at the stage where my nre network user can log in on the server machine but I can't log in as the network user via screen sharing. I can't add a network user to Remote Management, and with Remote Management enabled Screen Sharing is greyed out. I'd really like this to work.
My second problem is that I can't bind my MBP to the server but even when bound the network user account can't log in.
Any body have any ideas?
Thanks!

I had this problem on a clean install.
The solution was incredibly simple for me, but only after I saw Ross.M's note about opening the Users & Groups settings panel (in the OS System Prefs, not in server) and rebinding to OD server under Login Options.
That was not the solution for me, but under Login Options I discovered a previously unnoticed pref for "Allow network users to login at login window." I had this option set (apparently by default) to "Only these network users:" but with an empty list. Adding my users to the list made it work perfectly.
Talk about KISS

Similar Messages

Mountain Lion Server with Network User

I have a Mountain Lion Server with a network user. The whole system has been redone from Lion Server and on top of that I moved location, ISP, hardware and a few other things. The way I used the setup on Lion was to bind my MBP to the server and login from the MBP login window with the network account. If for whatever reason I wanted to look at the network account on the server, I could fast user swtich and everything that was open ie Safari, Mail, etc would be the same as it was on the MBP.
Now if I'm logged into the network user on the MBP and then go to the server, it logs in as if I've just booted. They share the home folder and any new files/folders created on one shows on the other. But if Mail is open on the MBP it won't be open on the server.
Does anyone have any ideas or suggestions?

Thanks for your reply.
I believe I got it to work, but,... How do you get the network account users to show up on the login window of the client computer? The login window shows the name of the client computer and the local accounts on the client computer. When I select Other in the login list I can login using a network account user id and it logs in. The network account user names do not show up on the login window

Lion Server: All network users have disappeared

Hi,
A search through the forums and kbase didn't give me anything that mapped well to my problem. Here's the situation:
Specs:
Mac Pro (2008) 6GB RAM, SSD boot with space available, OS X Lion (latest) with Server.app
Services:
File Sharing
Users: less than 15—accounts only used for file server access.
This is the only server on the local network, all network routing is taken care of by a Meraki router.
I went to add a new user to our fileserver, and was unable to connect to the server over Apple Remote Desktop. At the time, file sharing from the server (I *believe*) was still working. I logged in with the file server's local admin account via SSH and tried to use Kickstart to get ARD running again—something I'm well versed in. The script ran as usual, but ARD could still not connect. So, as everyone was in a meeting, I tried to use `shutdown` to reboot the fileserver from the CLI, something I've also done in the past (but not frequently). Usually that takes about a minute to work, and then my shell disconnects—but after 5 minutes, the Mac had not rebooted.
At that point, I decided to walk to the server and manually force it down by holding the power button in. That powered off the Mac, and 30 seconds later, I booted it up.
Back on my Mac via ARD, I was able to remotely control it and got to the Fileserver's log in screen, which featured a red dot in the use field I'd never seen before. It's tool tip read "network users are currently unavailable" (paraphrased, perhaps). I logged in with the Fileserver's local admin user (as usual) and launched the Server.app, only to find that in the `Users` section, there were no users listed, and the plus and minus buttons were greyed out.
I tried rebooting but got the same results. I then repaired permissions and verified the boot drive. Lots of permissions repairs (as usual) but nothing improved. Another reboot after the permission repair and disk repair, just for safety's sakes… and as you can guess by me posting here… no improvement.
I'm not heavily versed in Server. I'm not even sure if those users are stored in a database, and where that DB would live. Does server make dumps or backups of the users on its own? Should I have been? Is this LDAP? Anyone have some next steps I can try? What info would be useful?
My first goal would be to recover a damaged DB. I only have just under 15 users, so re-creation isn't difficult. But, under the department of "I don't know a ton about Lion Server" I don't know if network users act like OS X users… where you could create a new user with the same username, but if their UID is different, then they won't have access to their owned files on the fileserver… is Server that exacting? Does it care who owns the file?
Thanks in advance for any ideas, or resources you can point me to!

It gets far weirder……
Now no one, myself included can log in.
Checking the logs, which I'll try to attach a small sample of here (Dropbox link below since you can only attach images here), I see repeated instance of both `opendirectoryd` crashing and respawning, and of server manager unable to authenticate:
1/19/15 4:57:06.658 PM com.apple.opendirectoryd: Assertion failed: (0 == (connection->flags & eODConnectionFlagSocketValid)), function __odconnection_connect_block_invoke_2, file /SourceCache/opendirectoryd/opendirectoryd-172.17/src/odconnection.c, line 988.
1/19/15 4:57:07.641 PM com.apple.launchd: (com.apple.opendirectoryd[13760]) Job appears to have crashed: Abort trap: 6
1/19/15 4:57:07.641 PM com.apple.launchd: (com.apple.opendirectoryd) Throttling respawn: Will start in 9 seconds
1/19/15 4:57:07.761 PM ReportCrash: Saved crash report for opendirectoryd[13760] version ??? (???) to /Library/Logs/DiagnosticReports/opendirectoryd_2015-01-19-165707_localhost.cras h
1/19/15 4:57:17.276 PM PasswordService: -[AuthDBFile getPasswordRec:putItHere:unObfuscate:]: user with slot 4873a20f-0cc0-f7c3-0000-000a0000000a not found. Result: 80 Other (e.g., implementation specific) error
1/19/15 4:57:17.277 PM AppleFileServer: _Assert: /SourceCache/afpserver/afpserver-585.7/afpserver/AgentSession.cpp, 856 (4294952813)
1/19/15 4:57:32.703 PM servermgrd: servermgr_accounts: got error 2100 trying to auth to local LDAP node
https://dl.dropboxusercontent.com/u/1344045/server-sample.log.txt

Unable to add/remove users in Mountain Lion Server (Options are greyed out)

For some reason, im unable to add/remove users in Mountain Lion server. The + and - are greyed out. It seems like something is wrong with the permissons because it looks like it cant write the the Ldav3 file (although that may be speculation). Does anyone have any advice for me? I URGENTLY need to add users.
Maybe theres a way to restore default permssions for the boot drive (if that in fact is the issue). Hopefully there is a way that I can fix this while leaving all users, groups, their permissions and shares intact.

Anything interesting and relevent in the server logs?
Anything interesting in the server alerts?
Since it's far and away the most common cause of problems with OS X Server and with distributed authentication (Open Directory is entirely based on network encryption and digital certificates and on responses from your local DNS server(s)), verify your local DNS configuration is working and requires no changes with the following Terminal.app (Applications > Utilities) harmless, diagnostic command:
sudo changeip -checkhostname
sudo requires an administrative password. You might get a one-time warning about the sudo, and that can safely be ignored. The command will display some details, and indicate whether the local configuration appears valid and no changes are required, or further diagnostics for (most) common errors that can arise.

Sharing a Calendar from Mountain Lion server with Snow Leopard users on local network

Hello.
I have a new Mac Mini Server running Mountain Lion Server and I want to create a shared calender for a mix of Lion, Mountain Lion and Snow Leopard users on our local network. Does anyone have any info on how to do this? I have tried using the Server App and Calender Help within the applications, but the content isn't available. I have managed to create a Shared Calender from the Mini's Calendar App where I've added users and I can see a 'wireless' transmit icon to the right of the Calendar name - but I cant get any of the users' iCal or Calendar apps to recognise the Calendar on the local network. I've also created a Location in the Server App under Calendar and still can't see anything on the local network. Am I missing something really obvious?
Thanks in advance!

Sorry, I hadn't explained everything fully. I don't want to open up my VPN to friends and family. I do have the router assigning the NAS a fixed IP, so that when I connect over the VPN I can use the local IP address to connect, as you have mentioned.
What I would like is for my friends or family to connect to my server over AFP or SMB using the public IP of my network, which my router then forwards onto my server, and display the available sharepoints configured using Mountain Lion server. However, the NAS drive is not an available option this way as it has a separate IP to the server.
As the NAS alllows guest access, I also don't want to configure the router to forward a specific port to it, as this way it will be open to the internet. I wanted to try and use my server as an authentication point, with profiles set using Mountain Lion server, and limited to file sharing services only.
Hope this makes sense.

Mountain Lion Server - Folder names intermittently change between Upper and Lowercase names on some user's iMacs

Hi,
Sorry if I'm posting in the wrong group, but I couldn't find a Mountain Lion server specific group.
I have a new Mac Mini Server running 10.5.8 that serves Mac only users. The Mac Mini has a 4tb Promise Pegasus RAID attached via thunderbolt. Today, some of the users on the network reported that a folder on the RAID was quickly alternating displaying it's sub-folders as all capital letters then upper and lowercase - I witnessed this and it happened 2-3 times a second. I have run a propogate permissions fix on the folder, then the whole volume from within Server App and also copied the contents of this folder to my Mac, then I deleted the original from the server and created a brand new folder with the correct name and copied the contents back.
The problem still persists. Server App does not report any issues and other folders don't exhibit this behaviour. I've looked to see if there are any weird characters in folder names that would do this. The volume is shared via AFP only (SMB and WEBdav are off).
Any ideas as to what could be going on?
Thanks in advance!

Hi.
I solved this problem. I fixed permissions on the Mac's that the users were using to access the server and this has fixed the problem. The server folder giving the problems had many nested folders totalling over 5000 items inside and this seemed to corrupt the permissions on the user's macs.
Hope this helps anyone with similar issues.

Additional email address for user in mountain lion server

I have a new installation of OS X Mountain Lion server (10.8.2) that I am wanting to deploy. The problem that I am running into now is that there is no way that I have found to add a second email address.
I have multiple domains so, i need to have "[email protected]" and "[email protected]" for the same user.
Has anyone seen a way around this?

matneyc wrote:
Wow - just after I answer back, I found a download for the Workgroup Manager at http://support.apple.com/kb/DL1567. I probably need more sleep.
Yes, it is just Server Admin that is no more, Workgroup Manager is still at the moment available.
For your information another less pleasant means would be to directly modify the Open Directory record using either the command line or the Directory Editor launched from Open Directory Utility which in turn is launched from the Login Options "Join..." button.

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

Server App can't connect to a Mountain Lion server

Hi,
I installed OS X Mountain Lion Server (2.2.1) on a 2012 Mac Mini running OS X 10.8.4. I am able to access all the options using the Server.app on the Mini. Then I installed the Server.app (2.2.1) on a 2010 MacBook Pro running 10.8.4. On trying to configure the Server options on the Mac Mini from the MacBook Pro by providing the correct Mac Mini admin credentials, the password is not validated correctly. This happens when both the systems are on the same network or on different networks.
I am certain that the username / password provided is correct, since using the same credentials I can successfully remote into the Mac Mini using Apple Remote Desktop (3.6.1) when both the systems are on the same network or on different networks.
My situation supersedes the resolution provided in http://support.apple.com/kb/TS3960?locale=en_US. Note that the command sudo launchctl list | grep -q com.apple.servermgrd && echo loaded || echo not loaded returns loaded on the Mac Mini.
Please help!

I am having exactly the same setup and exactly the same problem - nevertheless I would like to add some more information in order to hopefully find / get help from other readers in here.
I am using DynDNS - not a dedicated domain. I do not utilize an AirPort Extreme for port forwarding and else. All the necessary port forwardings were triple checked!
- First of all "Apple Remote Desktop" is able to connect to my server over the internet (screen sharing) and locally in my LAN. No troubles here.
- My iOS devices can connect using various VNC clients without any troubles.
- VNC connections started within Safari (MacBook Pro) do work very well, too.
- All kinds of WebDAV connections are working like a charme.
- When connecting with "Server.app" from my MacBook Pro it asks if I would like to trust the self-signed certificate before I can enter name and password. After trusting that certificate it doesn't matter which account information I am entering: none is accepted. It does not make any difference if I am using a local user account or a user network account (both configured as being allowed to administer that server). "Server.app" does not accept any information provided.
I've been following the KB advice, too that c xavier mentioned. "servermgrd" is loaded!
For some odd yet unknown reason neither WAN nor LAN FTP login does work, too. It just gives me a time out, as already mentioned WebDAV is working fine.
Sorry I could not help You, c xavier! I just thought that some additional information could help...

OSX Mountain Lion Server - how do you uninstall this including services

Hi All,
Sorry if the question has been asked before.
I have Mountain Lion 10.8.5 and installed OSX Mountain Lion Server (2.2.2) and run into a couple of issues after installed successfully.
* I no longer can add users and groups.
* Open Directory fails to connect.
So I read some forums and uninstalled the server by trashing it, deleting /Libaray/Server, empty trash and reboot. But when I reinstalled the server it renabled all the services that I had previously and still not able to add users and groups. Open Directory fails to connect "not able to load replica" So I try to create a new OD and get an error the server is already a Network Server.
So basicaly I want to start from scratch and need some assistance how to get rid of OSX Server.
Thanks
Sahid

Wipe the disk, and reinstall OS X. (Not fun, of course. I just created a bootable USB disk for this purpose, and nuked an errant server configuration. A "target practice" server used for testing purposes had gone awry, and needed to be wholly reset. So I know what you're going through. Visit here or here for some instructions.)
FWIW, usual trigger for problems with OS X Server on a NAT'd network is bad DNS. That step gets skipped, or folks think they can refer to ISP or off-LAN DNS servers, and problems ensue. OS X Server needs LAN-local DNS when NAT is in use.

I'm trying to use Mountain Lion Server so my family can have separate logins via Screen Share to their iTunes.

Using Mountain Lion Server so my family can have separate logins and connect via Screen Share.
Works great, each has their own home directory and permissions are perfect.
Now setting up iTunes for each with their own Library (not shared), thus keeping multiple Libraries.
I get this;
This Computer is already associated with an Apple ID.
If you download past purchases with your Apple ID, you
cannot auto-download past purchases with a different
Apple ID for 90 days.
What!
So what it is on the same computer, they are completely separate Libraries never to be mixed.
If this works, I only need to keep one computer up and running, instead of three.
Each can do their syncing/backup and connect to the various Airplay/AppleTVs I have around the house.
How do I fix this.
Thanks

Bottom line is you can't - easily.
You need to make sure that you log out of the server each time otherwise the ID is running. To explain, if you had a laptop with different people using it, your solution works fine. Each time someone logs in, the iTunes ID is different so it works as you can only have one person using the laptop at any one time.
Now, turning your problem inside-out, you want people to be able to log into iTunes concurrently to use their own version of the program with their own library. This does not seem to work and you get the conflicted ID error message. Even though iTunes is running under their own login ident, I have never been able to get this working reliably and was told that iTunes is NOT a network-aware application as it is designed to be single user.
The way I got around this was to login as XYZ and to make sure that the ID was changed in iTunes accordingly. However, it did not always work so I gave up with the whole thing.

Configuring postfix on Mountain Lion Server

I'm trying to upgrade from Snow Leopard Server to Mountain Lion Server and did an install of Mountain Lion Server on top of a working instance of Snow Leopard Server. The "crippled" GUI on Mountain Lion Server is forcing me into using terminal to configure Postfix to handle incoming email.
I would like to configure Postfix to only accept email that is forwarded from a gmail business account. The public email address is [email protected] which is received by Google Mail, goes through their spam filters and then is auto-forwarded to [email protected]
The server WAN domain is nonpublic.com The ip address is 96.231.165.126
The server LAN is nonpublic.local The ip address is 10.6.18.201
The server is a MacMini running Mountain Lion Server 10.6.8 hostname server so the FQDN is server.public.com.
The network on the MacMini is configured to handle both LAN and WAN traffic through the 1GB physical ethernet port which plugs into a CISCO 3750 switch. The external traffic to the WAN flows through the switch as tagged packets. The LAN traffic is not tagged. The VLAN connection is running 802.1q
When an email is sent through the WAN to [email protected] the Postfix SMTP log shows:
Jun 7 19:29:22 server.public.com postfix/smtpd[42181]: connect from cisco.public.com[96.231.165.123]
Jun 7 19:29:22 server.public.com postfix/smtpd[42181]: disconnect from cisco.public.com[96.231.165.123]
I can send emails from a client on the LAN through this server with no problems. The incoming mail server can connect to the machine via the Cisco router/switch but Postfix just shows "cisco" as the connection (that's the router's DNS name) and provides no more info. I suspect Postfix possibly doesn't like the 802.1q connection and drops the SMTP request to connect on port 25.
I have turned on "debug" logging in Postfix, but that is all that appears in the SMTP log file
I've spent most of the week reading through everything I can find on how to install and configure postfix on Mountain Lion Server and work around the cripled GUI in the "server" application. I'm barely OK using Terminal and not familiar at all with configuring Postfix directling editing the config file.
What is the best approach to configure Postfix to allow SMTP connections from the outside to deliver incoming email that is forwarded from gmail.com?
I did find an "aliases" file in /etc/postfix/aliases but I'm not sure how to add the aliases and if adding aliases with a text editor is going to cause the "server" app problems and if the changes will be lost when the machine is restarted.
Any help would be appreciated.

MrHoffman, thank you for your response to my challenge to get the new test server working. This is a migration from Snow Leopard Server to Mountain Lion Server.
Here is the "checkhostname" test results:
blue:~ admin$ sudo changeip -checkhostname
Password:
Primary address     = 96.231.165.211
Current HostName    = blue.pderby.com
DNS HostName        = blue.pderby.com
The names match. There is nothing to change.
dirserv:success = "success"
blue:~ admin$
Here is the response from postconf -n
blue:~ admin$ postconf -n
biff = no
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5
dovecot_destination_recipient_limit = 1
html_directory = /usr/share/doc/postfix/html
imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
inet_interfaces = loopback-only
inet_protocols = all
mail_owner = _postfix
mailbox_size_limit = 0
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
message_size_limit = 10485760
mydomain_fallback = localhost
newaliases_path = /usr/bin/newaliases
queue_directory = /Library/Server/Mail/Data/spool
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpd_tls_ciphers = medium
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
use_sacl_cache = yes
blue:~ admin$
I agree that I should change the LAN domain from .local to something like .internal or whatever.   I've been running with .local for 5 years on snow leopard server and never had any problems so that was a low priority.
I hope I'm just not seeing some obvious setting in main.cf

Complications migrating from Snow Leopard Server to Mountain Lion Server.

I'm migrating from Snow Leopard Server to Mountain Lion Server. The article "OS X Server: Upgrade and migration" (http://support.apple.com/kb/HT5381) says
"Make sure that any DNS or DHCP servers on which your server depends remain running during the upgrade"
This advice is reinforced by the details of the article "OS X Server: Steps to take before upgrading or migrating the Open Directory database" (http://support.apple.com/kb/HT5300).
As the server I'm migrating from provides these services it will need to be running during the migration process. This would seem to limit my options to doing the migration from a Time Machine backup (or, making a seperate clone of the server's drive and connecting it externally to the new box)
My main concern is the seemingly inevitable clash that is going to occur on the network as the new server takes on the roles of the old one - while it is still running.
What are my options here ?
This is my second attempt as on my first try I did the migration from the TM backup with the network down - and none of my local network users or their home directories were migrated, although the settings for the mount points were, but there were no actual directories where they pointed to!
Clear directions on how to procede would be VERY MUCH appreciated
Thank you.

Moving from Snow Leopard to Mountain Lion means first installing the client (non-Server) version of Mountain Lion and then install Server.app this means that for at least part of the process you will not be running DNS, DHCP or Open Directory.
If you are going to end up using the same DNS name and IP address after the change then an approach you could follow would be as follows.
Destroy any Open Directory replicas
Archive your Open Directory Master (to make a backup)
Note down your DNS records in case they get messed up
Export via Workgroup Manager your users, and groups (you might not need this but better safe than sorry), make sure you do not include the diradmin account
Keep a full back of the server (you should always have backups)
Note down your DHCP server settings in case they get messed up
Note down any other service settings
Install Mountain Lion
Install Server.app
Install Workgroup Manager (extra free download)
Run Server.app
Make sure settings for services are as much as possible the same as before
If your lucky that may be all you need to do, otherwise...
Restore Open Directory archive, if your lucky that will be all you need to do, otherwise...
Make new Open Directory Master
Run Workgroup Manager
Import users and groups you previously exported
You will then have to set passwords for each user as these are not preserved via Workgroup Manager export
When I did this, I was also being forced to change all my IP addresses so I had no choice but to use Workgroup Manager to export and import accounts.

How do I share a folder over the internet with Mountain Lion server?

I am new to using formal servers. In Snow Leopard I was able to use web sharing to serve a small website and if I wanted to share a folder with someone I would just provide the person I wanted to share a file with the path to the file inside the sites directory. With Mountain Lion this functionality was removed from the sharing section of system preferences.
I purchased mountain lion server and was able to restore the website serving ability, but I haven't been able to figure out how to share a folder. I am still looking over what documentation I can find, but for the most part it just tells me to set up the services without telling me how. Any assistance would be helpful. Networking is not my area of expertise.
Best Regards,
David Finell

I purchased server to assist with this as I am unfamiliar with the command line protocols for using apache. Because of the UNIX architechture of OSX and I presume apache, I am uncomfortable using the command line for fear of causing serious problems.
Unfortunately, the documentation that I have seen for mountain lion server is wanting in either its completeness or layout/functionability. To summarize the server instructions as I understand them. It just says to configure it and my system to meet my requirements without telling me how.
I am confident that both the apache command line and server are capable of accomplishing what I was able to do before under snow leopard. I just haven't figured out how.
I was able to provide a link to family and clients like http://ipaddress/~user/folder
This no longer works.

HT5678 What the important thing we need before we can setup The Mountain Lion Server application

I want to set up mountain lion server application on my mac osx 10.83 , may i have some suggestion before i set up it to my macBook .

I'd ask what requirements you're looking to fulfill by using OS X Server on a MacBook system, as that's not a typical hardware configuration for a server.
OS X Server and most other server operating systems expect static IP addresses and full-time availability, where a MacBook tends to be mobile and to thus have a variety of dynamic DHCP IP addresses and networks, and MacBook systems also tend to be closed and hibernating at random times.
It's certainly possible to use this hardware as a server (and it can be useful when you're learning how to manage a server and have a "scratch" MacBook available), but the hardware is not necessarily a good fit.
As you add services, you'll want to have DNS services established and verified, and — on a typical NAT'd local area network with no other LAN-local DNS services — that involves configuring DNS services on OS X Server itself. DNS is a prerequisite for various other OS X Server services.
But yes, do have a disk backup, either Time Machine, or as an external disk backup, or however you preserve your data. Skimming the OS X Server manuals can help save some time figuring out the platform, too.

Mountain Lion Server: add network user to remote management

Similar Messages

Maybe you are looking for