Kaseya Community

Machine Rename post agent install

  • We've run into issues a few times where workstation names have been changed after agent install. So the machine name the agent reflects is no longer correct.

    The issue first popped up while a tech was speaking with a user and was asking for the computer name. The name the user saw in the system properties was not one reflected by any of the agents listed in the machine group for that client.

    Is there a way to autoupdate agent names? Or how would we deal with this?

    Legacy Forum Name: Machine Rename post agent install,
    Legacy Posted By Username: TNITG
  • Under the system tab go to 'naming policy'. From there you can 'Force machine ID to always be computer name'.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: GDRBrian
  • Or, you can also go to the Agent tab->Install Agents section->Rename, and rename the account.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: lwolf
  • If you use auto-naming, Macintosh agents will "drop out" and become invisible within the group.

    Macs have a mandatory ".local" attached to their name, specifically the part of the name that Kaseya picks up on. So what happens is Kaseya parses that as part of the groupid, and not part of the machineid.

    Before auto-name:
    mac.groupid - select "groupid" and you see "mac" underneath it.
    After auto-name:
    mac.local.groupid - select "groupid" and you don't see it! You have to select and find it, because the kserver parses it as a member of the non-existent group "local.groupid" - since it's non-existent you can't select it or anything, you will only find the agent with selected.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: Matthew Bartels
  • Matthew Bartels
    If you use auto-naming, Macintosh agents will "drop out" and become invisible within the group.

    Macs have a mandatory ".local" attached to their name, specifically the part of the name that Kaseya picks up on. So what happens is Kaseya parses that as part of the groupid, and not part of the machineid.

    Before auto-name:
    mac.groupid - select "groupid" and you see "mac" underneath it.
    After auto-name:
    mac.local.groupid - select "groupid" and you don't see it! You have to select and find it, because the kserver parses it as a member of the non-existent group "local.groupid" - since it's non-existent you can't select it or anything, you will only find the agent with selected.


    Sounds like a K bug to me. Wink

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: sequoya