Okay, I have machines imaging and a few deployed but now I have run into a new problem: I cannot connect via ARD or VNC. I have exactly the same configuration as my Snow Leopard machines Remote Management is enabled and a VNC password is enabled. The Sharing pane shows the green light and Management: On.

Tight VNC reports that the host actively refused the connection and Dameware's VNC client states that the machine is shut down or settings are wrong. ARD reports connection Failed and suggests making sure that the above settings are enabled. The system is 10.8.2 and ARD is 3.6.1, as is my mac server which I am VNC'd into right now. Reporting in ARD is active and appears to function okay. Also, FWIW, Lanschool is installed and I can view/control that way, although it's entirely too slow to be useful for anything but monitoring.

Johnny1600 wrote: under sharing in system preferences, you have Remote Management checked? Make sure you have a local Admin account and then do the allow access for: Only these Users, and select your local admin account. Then when you connect to that machine again in ARD, Control click it and put in the local admin username and password. Remote management is definitely checked. The systems are clones of our existing systems with the only exception being that we migrated the apps and settings to Mountain Lion. There are two admin accounts (plus root) that are available to manage the system. Also, VNC used to work flawlessly and now actively refuses the connection.

Before you can use Screen Sharing or VNC client to access a Mac, you must allow incoming connections on the targeted Mac. To do so, on the targeted Mac go to “System Preferences > Sharing”, here click the “Screen Sharing” check box. A connected VNC Viewer user cannot automatically wake a Mac computer from deep sleep. A VNC Viewer user may be able to wake a Mac computer from display sleep (the lower of the two options in the System Preferences > Energy Saver pane).

This is why I suspect something more than a simple configuration error. 1.Open Terminal and ssh to the system in question: ssh. Enter the admin password, and if prompted to accept the certificate, type YES then press Enter. 2.Type cd /Library/Prefrences and press Enter. 3. Type mv com.apple.ARDagent.plist com.apple.ARDagent.plist_bad and press Enter.

Repeat this command with com.apple.RemoteDesktop.plist and com.apple.RemoteManagement.plist -- remember to add _bad to the end of each filename when moving it. 4.Type cd /Users/username/Library/Prefrences; replace username with the affected user's short username. 5.Type mv com.apple.internetconfig.plist com.apple.internetconfig.plist_bad. Repeat this step for com.apple.internetconfigpriv.plist and com.apple.remotedesktop.plist if they are present (remember to add the _bad bit to the filename). 6.If the end user is logged in, pick up the phone and call them, ask them in your nice admin voice to save their work and go get a cup of coffee. You will be force restarting the computer.

Tap “Airplay Mirroring”, and choose the computer’s name beginning with “Apowersoft”. Mirror iOS Device to Other Mobile Devices After you have installed ApowerMirror app on both mobile devices, please follow the instruction below to mirror iOS screen to another phone. • For iOS 10, open the Control Center on your iPhone or iPad. Iphone app to control mac mini. Then your iOS device will be mirrored to PC.

7.Once the user has saved his/her work, type sudo shutdown -r now and press Enter. Supply the password as needed for the admin account. Wait two minutes for the remote system to restart, go back into Apple Remote Desktop, and rescan the IP address for the affected system. If you are still unable to remote control the system, go to the next, less secure method for correction. Johnny1600 wrote: If you ping them with the -a command from a pc do they come back with the correct name/ip address?

Just to verify there isn't a DNS problem. Are you managing these machines through Open Directory?

Sorry Yes I ment Static IP No problem with DNS. We actually use Active Directory as the macs are only a tiny percentage of the installed computer base.

I cannot VNC to the computer via IP address and I was able to add a computer to ARD via ip address, but not control it, although I can pull reports. The iMac I re-imaged as a test, that one I can remote control. Johnny1600 wrote: You could always move the ard agent on the client and name it.bad, then run update and it will re install the agent.