Importing customers

Currently, DET does not support the export of user group permissions that are associated with customers, except in cases when the customer name being exported has the same name as a customer in the target mesh (the mesh you are importing the customer into).

For example, let’s say that in your source mesh, you had a software application node named iPlanet, and that software application node iPlanet was accessible for reading and writing to all groups associated with a customer named Computing Machines. One of these groups associated with the customer Computing Machines was named groupA.

Next, you export a software application node iPlanet from the source mesh, and then import that node into a new mesh — and this mesh does not have a customer named Computing Machines. The result would be that any users in groupA would not be able to see software application node iPlanet in the target mesh.

However, if the mesh you imported the customer Computing Machines into already has a customer with exactly the same name, then all permissions are untouched in the new mesh and all users groupA would be able to access the software application node named iPlanet — in other words, all permissions associated with the Computing Machines customer (the ability to read and write the software node iPlanet) will remain in tact.

Workaround

If a user group loses permissions to access objects (such as servers associated with a customer), then use the SA Client to re-assign the permissions. Until doing so, only users who are administrators will see these customers and their associated objects.