When VSA syncs to BMS, the hardware assets end up under both root.locke and under locke.root.
(The following steps are part of a verification process. They may not exclusively lead to a solution.)
- Go to https://<server name>.kaseya.net/api/v1.0/swagger/ui/index.
- Go to endpoint Auth > Get/auth.
- Input username and password and then click Execute. You will get a token.
- Go to endpoint Asset > Get/assetmgmt/assets/assetId.
- Enter the assetId in the respective field.
To get the assetId, go to BMS > Asset Management page. Press F12 (or fn+F12 on a laptop) on your keyboard. A panel opens to the right and reveals the code.
- Run a search and find the assetId from the code. The assetId is a long number with many digits. (For example, 751329453359976.)
- Copy the assetId from the code and paste it in the assetId field.
- In the Authorization field, enter the token that you got from the Auth endpoint.
- Click Execute. Check if the machine group is appearing in reverse order or in correct order. If it is still appearing in the reverse order, then the data of this asset on the VSA side might be broken. This is a VSA issue as per the VSA API logs. VSA asset is sending the org name in reverse. It is not a BMS issue. BMS is just the receiver. Contact VSA Support team for further investigation.
If there is an IT Glue integration, that might be a contributing cause.