Mac OS X Lion Server :: Disable Sleep Button At Login Screen?
May 1, 2012
Is there a way to disable or hide the sleep button at the login screen? I am trying to send updates and/or commands from ARD.... But the end users are putting the computers to sleep by pressing the sleep button. This is causing the ARD updates/commands to fail. The computers and severs are all Lion OSX. If I can disable the sleep button at login then I can send the updates/commands. I normally only do the updates/commands when there is no user logged in.So I am not concerned with the case where the user is already logged in and puts the computer to sleep. I have already setup an MCX in WGM for the Energy Saver.
Have latest Lion on new MBPro. Only one user defined - an Admin. Prefs set to automatically log in - yet whenever I wake it from sleep it shows me the login dialogue. Allow user to admin computer is checked - but gray, auto login is set to the same and only admin user account. I repaired prefsÂ
I have auto login on my profile and disable auto on the security page but still need to login every time I log out or shut down.I have also noticed that the general page of the security and privacy in Syste Prefs is different on my wife Macbook air and my pro....
This is the first time I've encountered this. Upon cold booting the machine it went directly to the legacy Mac OS X Server login screen from before the upgrade to Mavericks. It would not let me login with current credentials. I had no choice but to hard power off. It returned to normal operation on restart.
I'm trying to diagnose our new intel servers and VNC.They're of varying configurations in terms of memory, disks, etc, but all are the new xserve model.
Here's what happens.
When connecting to VNC either through ARD's built in software or chicken of the vnc we can see the login screen perfectly, but as soon as we login it suddenly "scrambles." The second a monitor is plugged in the remote display "clears" and again becomes usable.
Here's what's been done so far; Rebooted the server (VNC broken) Ran software update (VNC broken) Booted the server with a monitor attached (VNC works) Unplug the monitor after reboot + login + monitor plugged in. (VNC continues to work.)
Here's the problem. When I reboot the server I don't need to go through a song and dance to login remotely after a reboot.
I installed the 10.7.3 Server Combo update today, and now when I try to use Server.app to administer my server, it just shakes to tell me they are invalid (even though I'm logged in to the server with that username/password).
Info: Mac mini, Mac OS X (10.7.2), Server | 2.53 ghz | 4GB | (2) 500GB
I want to be able to disable Mission Control for client computers. We are a school with a 1:1 computer setup and it is too easy for the kids to swipe their desktop away when a teacher walks by. I know I could manually disable the gesture, but I can't disable to my knowledge by permissions and I would rather disable the whole thing all together.
I need to disable any external device like hdd usb or hdd firewire and usb key as well. Is there a way to do it in osx lion server ? I've heard that deleting some extension could do that job but which one ?
Info:Mac mini, Mac OS X (10.7.4), LION SERVER 10.7.4
In tiger you could easily disable safe sleep and remove the sleep image file but in Leopard this seems to have changed. Yes you can disable safe sleep & remove sleep image files but only temporarily. As soon as you restart or change energy settings back to default, leopard automatically reverts the safe sleep settings to default and starts creating an image file again
Is there no way to permanently disable/remove these?
I have a Mac Mini Lion Server which is running open directory. I have several users which I created a while ago and they are able to login to the server from both Lion and SL clients. I created a new user account today and for some reason I am unable to login using the new user account from a SL computer. I've been able to login using a lion client, but SL, no dice. Â
I would like to move my service data to the newly acquired Promise Pegasus. Server.app -> Server Name: Settings: "Edit" button next to "Service Data" is greyed out.
Info: Mac OS X (10.7.4), 8GB, 2,93 GHz Intel Core 2 Duo
I have a Mini Server, 10.7.3. 8GB, SSD 256, use it for FCPX mostly. Just moved all datafiles to external disks and re-installed Lion, but now I cannot access my user account. When I started up the system after it had installed, it asked me for company name and email address, but then I cannot access my user account any more.
Do I need to re-install the system again, or how can I solve this? I don't remember what email address I used originally when I got the server and registered it, whether it was my personal or the business address, which I gave this time. Â
I do remember the login name and password that I have always used, but these don't work anymore and I have too many jobs pending this week.
Info: Mac mini, Mac OS X (10.7.3), Server 2.0Gz 8GB SSD256
Here again dealing with how OS X deals with .local domains I think.Was previously bound and all was working fine. Have just updated to 10.7.4 When trying to login using the "Other User" the button stays red and says Network accounts unavailable. I can ping domain server by name and IP.Permissions have been rebuilt.
Have rebound. Had a problem at first unbinding inside the Open Directory Utility as it said it could not connect with the domain and an unused account would be left if a forced unbind was done. Tried again by using the minus button instead of the Unbind button and it worked without any message.
So then binded to the domain and all looked good. Green button next to Network Account Server in the Users and Groups.
Info:iMac (27-inch Mid 2011), Mac OS X (10.7.3), VM Ware with XP Pro
I'm not sure - but for some reason I am no longer able to login to my wikiserver via Safari. I can with firefox, chrome, IE, etc but not in Safari. Username doesn't matter. (either total admin or just a user).
I have 3 servers in my office. I have plan to configure these three together in my office. My plan is one server just only for login purpose and other two to keep the home folders and shared folders.the function is when one network user log in to one client machine, it just login(by using first server)and disconnect from first server and connect to the either two (means direct to the homefolder i created either of two server). Means first server as login server and other two are file servers.
I have a brand new iMac running 10.7.4 bound to AD with mobile accounts to be created at login. We've had dozens of users log into this Mac with their AD credentials with no problems. Login proceeds as expected, home folders are created, etc. One user cannot log in. The login window will freeze (spinning beach ball) after he enters his credentials and the computer has to be manually shut down. After a restart you can see that his home directory has been created, with proper permissions, but he still cannot log in (spinning beach ball). However, he CAN log onto other AD bound Macs, just not this one. And he CAN log onto a bound Windows machine, so apparently there's nothing wrong with his account. There is no OD server in the mix. The computer is bound to our AD domain only. The system log shows the proper UID but indicates that the user name can't be found. But then the user folder (with the correct name) is created anyway. Later there is an entrry that the UID can't be found.
I have a problem with Network Users defined on my Lion Server accessing the server through VPN or Profile Manager (via Safari) ... I keep on getting authentication errors. Is this because they are network users or am I missing something else?
This works: when I logon to my Lion Server with either local or network users everything seems to be OK including home directory synchronisation.
I tried the following for VPN:my local server account can logon to the server (ie my secret key, user account/password combination are OK ("chap peer authentication succeeded for ...")when I try the same with two of my network accounts I keep on getting authentication errors (VPN) but I'm sure I use the same userid/password combinations as above ("chap peer authentication failed for ...")
I get similar results when I access the Profile Manager (url..)my local server account can logon on to the Profile Manager and sees as all the informationwhen I try this with one of my network accounts (which has devices assigned) I keep on getting 'incorrect user name or password
I have an OSX Lion 10.7.4 Server set up with Profile Manager and it is joined to AD.Â
I am able to see AD groups in the Profile Manager groups section. I can also see and add AD users and groups using the server app.Â
I have enabled the "Can Enable Remote Management" check box for Domain Users through Profile Manager. I have also added Domain Admins to the Workgroup group in the Server app. I'm not sure that I want or need either of these options, but they were suggestions to try. I am not able to log on to the Profile Manager or My Devices pages with AD logins.Â
I found these directions about nested groups in Workgroup Manager [URL] but I don't have a [URL] local group or any groups like are shown in the picture.Â
I'm running OS X Lion Server on a Mac Mini 2ghz Core 2 Duo and every time it wakes from sleep I get a message saying "There is already a computer on the network named MacServer, renaming to MacServer (2)".Â
It only happens when waking from sleep. If I reboot or use the mini for hours without sleeping it's fine, but once it's gone to sleep it renames on wake. When it sleeps overnight it's named MacServer (5) by the morning, as it wakes up every two hours or so to re-register itself on the network and each time it renames itself.Â
I don't have any other compters on the network with the same name. The only other computer is a MBP and has a completly different name. Here's my setup; My Mac Mini is wired via ethernet to a Time Capsule. AirPort is turned off (I've tried on and off).My Mac Mini has a static IP address (x.x.x.40) with DHCP for everything else (DNS, etc.)The Time Capsule is wired to an ADSL router via ethernet. The ADSL router manages DHCP and NAT, with IP pool x.x.x.2 through x.x.x.30. DHCP and NAT are turned off on the Time Capsule (bridged mode). Wireless is turned off on the ADSL router.Time Capsule is handling wireless.Â
I've tried resetting the ADSL router. I've tried resetting the Time Capsule (to factory defaults).Â
The problem seems to be with mDNSResponder, as the log seems to suggest that it is this daemon that thinks there's a duplicate computer name. I've even looked at the source code for mDNSResponder and the last mod-log entry suggests that a fix was put in for this issue in 2009. It doesn't look like it's fixed it, though.Â
I've tried doing a fresh install of OS Server several times now and, after the last install, it started happening before I got a chance to restore from a Time Machine backup. i.e. on a completly fresh install and assigning a completely new computer name.Â
Info: Mac mini, Mac OS X (10.7.3), 2ghz Core 2 Duo, 8Gb Ram, 500Gb HDD
I installed Lion Server on a MacMini to run a shared Wiki calendar, and all is quite well, I got the Wiki calendar page up and running and the iCal clients have successfully subscribed to it.The problem: external users can'tl log in from the internet.On our LAN they can reach the Wiki Home page at http://10.x.y.z/wiki but how do they log in from the internet ?We have a DynDNS host name, but [url] brings up an empty page.I forwarded port 8080 to our server. I did checkip -checkhostname and it looked alright to me. The server has a FQDN ourserver.name.private. that points to 10.x.y.z and the reverse lookup points to the server name.Â
I have a macbook pro 13" early 2011 and I'm se as shown in the pictures (since i upgraded to os x yosemite) . It happens after display sleep or computer sleep on login not on boot up .I've noticed that i run out of ram when the problem appears (only 15MB RAM available out of 4GB), though i doesn't happen every time . I've talked to service and told me its either motherboard replacement or because the ram isn't enough (gpu shares with main ram) so maybe i should try upgrading ram. URL....
