Deploying Mac KAgent
We have very little luck provisioning KAgent on both mac and pc, so we are deploying the agent on the mac through ARD (Apple Remote Desktop). We install the .pkg file, then send the unix commands to stop the kbox agent, set the kbox to the right server and then start back up the service. Starting back up the service always tells us that the service is already running, but the unix command just hangs at this point and never finishes. Is there a better way to deploy this agent, or a way to integrate the name of our kbox into the .pkg file?
Here is the messages we get with ARD when it runs the commands (manually or through ARD):
waiting for 1028..... done.
could not load config. loading default.
SMMPAgent is already running (1056).
Here is the messages we get with ARD when it runs the commands (manually or through ARD):
waiting for 1028..... done.
could not load config. loading default.
SMMPAgent is already running (1056).
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
mlathrop
14 years ago
I can offer some insights on deploying the agent to Macs using KBOX. I am not using ARD.
With the KBOX two things are crtical; a common local Administrator account password and enabling Remote Login on all the Macs
Once you have enabled Remote Login and have a common Administrator password, the KBOX should be able to push the agent to each Mac. Use advanced provisioning and create a job for your IP ranges, I create a separate one for each subnet so I can stagger the schedule. I run provisioning once per day on each and they all get provisoned very quickly and any new machines get provisioned soon after they are on the network.
Use the Administrator account and password in the provisoning job.
With the KBOX two things are crtical; a common local Administrator account password and enabling Remote Login on all the Macs
Once you have enabled Remote Login and have a common Administrator password, the KBOX should be able to push the agent to each Mac. Use advanced provisioning and create a job for your IP ranges, I create a separate one for each subnet so I can stagger the schedule. I run provisioning once per day on each and they all get provisoned very quickly and any new machines get provisioned soon after they are on the network.
Use the Administrator account and password in the provisoning job.
Posted by:
serrinca
14 years ago
We have many subnets, and though we have our kbox name in DNS, things get confused since the default name is just kbox. What if your 1000 box has a different name, or you want the fully qualified domain name? According to Kace documentation this is done through terminal (Unix commands), this is what has slowed us down in the deployment of the KAgent for our Mac computers.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.