Follow

Why do Kaseya Mac Agents get .local or whatever FQDN text added to the machine name when "Force machine ID to always be computer name" is selected under System > Function List > Machine Groups > Naming Policy or during a fresh Mac Agent

QUESTION

Why do Kaseya Mac Agents get .local or whatever FQDN text added to the machine name when "Force machine ID to always be computer name" is selected under System > Function List > Machine Groups > Naming Policyor during a fresh Mac Agent installation?

ANSWER

The cause of this can be twofold:

1) An older KServer build (ie.: v5.1.0.0) that has since been updated to address and fix this.

2) An older Mac Agent version that has since been updated to address and fix this.

The first thing to do in this case is to update the KServer build. First, raise a support request for a link to the latest KServer build. Then, when this is received, here is what to do from here:

Note & Warning: When doing this, you will sever connections from your Kaseya Server to your Agents. Plan an appropriate time to do this.

1) On your Kaseya Server machine, download this file and unzip it.

2) Then, pull up an IE Web Browser window and log into your VSA with an account that can access the System Configure page. When there, visit the System > Server Management > Configure page.

3) On this page, press the "Stop Service" button found here towards the mid-right section of this page. This will stop the Kaseya Service.

After this is done, you will see red 'KServer Stopped' text in the top Index page of the Kaseya VSA, indicating that this server has been stopped.

4) After this, then visit this directory on your Kaseya Server:

C:\Kaseya\KServer\

Note: Replace 'C:\' as necessary.

5) Then, rename the current 'KServer.exe' in this directory to something like 'KServer.exe.old' for example.

6) Then move the newer downloaded KServer.exe into this same directory.

7) After this, in your VSA again, visit the System > Server Management > Configure page and press the 'Start Service' button that used to be the 'Stop Service' button. This will restart the Kaseya Service and launch the new KServer.exe.

After this, we recommend that all current Mac Agents exhibiting this issue are updated to Kaseya Mac Agent version 5.1.0.8 or higher and then renamed to get rid of the .local reference. If you do not have Kaseya Mac Agent version 5.1.0.8 or higher, then raise a support request that requests this.

MORE INFORMATION

"What if I cannot view an already .local appended machine ID due to grouping issues?"

Amongst certain ways to do this (ie.: using a machineID.local.parentGroup method, etc...), the simplest way around this is to create a custom View in which the OS Type is set to show only Mac OS X-based machine ID's. Select this view with the Machine ID filed blank or with "*" only, and leave the Group filter item to '' and you will be able to see the .local-named agents.

APPLIES TO

Kaseya 2008 Server 
Kaseya Mac Agents

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.