mmartinjust on the .root part after speaking to kaseya this can be removed so you only have machinegroup instead of machinegroup.root
6. If you are upgrading from v5.1 you will have to decide how organizations will be created for existing machine groups...
Create a Single Organization:
Use this option if most of your existing machine groups belong to the same organization.
 All machine groups are added to a single myOrg organization, representing your own
 The myOrg organization can be renamed after the update.
rbjseaAgree, would love to know how to change/move the "root" I don't think we'll be able to remove it entirely, since this is where your machines live (it's the root group for the ORG).
Ideally I'd love to be able to move/convert the existing groups into subgroups. That would probably solve the problem for most of us. Tho I have a feeling we'll just need to create new Orgs/groups and move every agent into the new ones.
BTW, looking at it, wouldn't scopes be a better place to put SLA's?
thirteentwentyThe .root group can be renamed or deleted
rbjseaBut only if you've moved the agents to an actual group. Many of us have probably used a client name for a group, thus when moving to k2 they all show up with 2 entries.
It took me a moment to figure out that the initial "group" you see in the drop down list is not a group but the org, and the .root "group" is necessary if your machines only belong to an org and not a group within an org. A bit confusing initially, which is why I think so many questions on it. Doubly so if you do a migration you don't get the group/org options.
Probably it might have been better to give us a drop-down for "org" just like they do with a group. I can see what they're doing here and it's cool, but there probably was a better way to implement it. Once we all get through some migration pain it will be better.