/build/static/layout/Breadcrumb_cap_w.png

Agent Single Provioning MAC

Hello,
Been trolling around looking for a work around for installing the agent on a MAC without physically going to the machine and opening port 22. We are trying to stay away from our MAC users mostly because of their bad attitudes and lack of cooperating : p . Has anyone been down this road and find anything worthwhile ?

0 Comments   [ + ] Show comments

Answers (5)

Posted by: dchristian 13 years ago
Red Belt
0
LOL!

Unfortunately we will need port 22 open to be able to provision.

After the agent is installed you can manage them from a safe distance!
Posted by: jmlucien 13 years ago
Yellow Belt
0
This solution is not a great one because many of our users are remote and not technologically savvy. We are not a MAC shop but all of our Sales people have MACs (close to 50 ppl) around the world.

Anyone know how to open port 22 on a MAC so I can get it working on the MACs I CAN get to?

Thanks!
Posted by: dchristian 13 years ago
Red Belt
0
This was the first article when i googled "enabling ssh on mac"

[link]http://www.bluishcoder.co.nz/articles/mac-ssh.html[/link]
Posted by: jmlucien 13 years ago
Yellow Belt
0
Here is what I have so far.

To open port 22 on a MAC.
- On each Mac go to System Preferences
- Click Sharing
- Select “Remote Login” to enable SSH (port 22)
- Check “Only These Users” under the “Allow access for:” section.
- Hit the + sign and choose “Administrators”
- We must use the Administrator pw in mac provisioning.

I will test and get back to you.

Thanks for the link, I will look at it.
Posted by: smaug_ca 12 years ago
Senior Yellow Belt
0
You could try putting the KACE agent up on your kbox portal. Then the users could log in, download the agent themselves and install it. The agent will then open the ports (silently) for you. Nothing shows up in, and users do not have to mess with the sharing control panel.
You would have to provision the portal with a way for your clients to log in. In an AD environment that is pretty easy. The only other catch is that the Mac users have to be able to install software on their machines (ie. administrators on their boxes). That would go for them changing SSH settings in the System Preferences as well.
You would also need to have them type in the variable for the kbox server name.
We do this for stand alone Macs and PC's "In the wild" that we need to manage.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ