I had to remove the application from the Login Items list and rely on the Screen Saver lock above. For some reason, it would not receive external network connections if the login prompt was displayed on the Mac screen. ![]() Additional Note: One of the Mac's is running Windows Server 2012 R2 in its virtual machine, which has bridged networking.I found that it didn't work on a headless Mac, unless I fooled the Mac into thinking that a display was attached.I converted the shell script above into a Mac application, and added it to the ServerUser Login Items list.See: Terminally Geeky: use automatic login more securely Create a small application that locks the screen and displays the OS X login prompt.Better solution for experts: In addition to the above, you can configure your Mac to display the login prompt immediately after startup, even though the ServerUser account is logged in and the virtual machine is running.Set the System Preferences, Security & Privacy, General tab, Require password "immediately" after sleep or screen saver begins. System Preferences, Desktop & Screen Saver, Screen Saver tab, Start after (pulldown menu). Set the ScreenSaver in the ServerUser account to start after 1 minute.(That is one reason why you do not use your admin account for automatic login.) You can mitigate some of the risks by: It will be logged in to your ServerUser account. ![]() If someone steals your Mac, they can connect a keyboard, mouse, and monitor to it and then boot it. Security Risk: Your Mac is configured to login automatically at startup.That is because you cannot enable FileVault if you want the virtual machine to launch automatically. If someone can get physical access to your Mac itself, they could gain access to any file on your Mac, including the virtual machine itself, the ServerUser password file, etc. The password is encoded, but not really encrypted. Security Risk: If you configure automatic login on your Mac, the password is stored in a file that only root can access.Automatic restart on power failure won't work if you have FileVault enabled.You may want to run a power failure test to verify that the virtual machine launches automatically after a power failure.It should automatically login to the ServerUser account, launch VMware Fusion, and then VMware Fusion will automatically start the virtual machine. Enable the desired virtual machine to "Start automatically when VMware launches" in the chosen virtual machine's VMware Settings, General. Launch VMware Fusion in the ServerUser account.Login to the Mac under the ServerUser account.You will probably want to configure some type of remote access so that you can control your Mac from another system. If you will be running your Mac as a headless machine with no keyboard or mouse (like my Mac mini computers), disable "Open Bluetooth Setup Assistant at startup if no keyboard is detected" and disable "Open Bluetooth Setup Assistant at startup if no mouse or trackpad is detected".You will be prompted for the ServerUser account password. Go to System Preferences, Users & Groups, Login Options, and select the ServerUser account from the pulldown menu. Set the ServerUser account to login automatically.In this procedure, let us call the account, "ServerUser" On my Macs, I named the automatic login account "Server". I create the same set of accounts in the same order on all of my Macs, so that Unix user IDs match. Create an account for automatic login at startup. ![]() Set the Mac so that it automatically restarts if there is a power failure. ![]()
0 Comments
Leave a Reply. |