Table of Contents
In your IT environment, you can classify computers according to two criteria
Their geographical location: the place where they are used, for example the country, the agency, the floor, or other criteria.
Their function: how they are used, such as office automation, CAD, or other criteria.
The LRS makes very easy to represent this two-dimensional organization, through concepts of membership
A group for the geographical location.
A profile for the function.
The Profiles are used to group computers according to their function. Clients used in the same field will have the same profile.
A sample case is the deployment for a financial services company where the computers include a "Network management" profile, a "Branch manager" computer, "Advisers" computer and "Counter" computers.
It is recommended that computers belonging to the same profile should have a similar hardware configuration, to enhance hardware coherence.
The groups contain clients gathered in a same place. A concept of tree based structure of group is available in the LRS to group computers belonging to the same city, then to the same building, to the same floor and the same service.
The clients do not necessarily have to have the same configuration, the concept of group being intended more for administration purpose than for deployment purpose.
In the LRS, clients can be organized using a two-dimensional array:
By profile.
By group (with a tree notion).
Let's take the example of a computer named Computer1. Computer1 is used in accountancy, in the Acc01 department of the Agency05 agency of the Town02 town. The profile of Computer1 is "Accountancy," its group "Town02/Agency05/Acc01".
By convention in the LRS, one will indicate this client under the denomination "Accountancy:/Town02/Agency05/Acc01/Computer1".
More generally, the LRS client's name will be as should follow the notation:
PROFILE:/GROUP/SUBGROUP/SUBSUBGROUP/COMPUTER![[Warning]](/ucome.rvt/any/en/Produits/LRS/details/doc/img/warning.png) | |
To ensure compatibility with the previous LRS versions, the names of the clients must be unique, whatever their profile or group. Thus two clients member of profiles A and B must not have the same name. |
Please note that a client does not have to be member of a profile or a group:
A client without profile can be named for example
:/GROUP/SUBGROUP/SUBSUBGROUP/COMPUTER
or even
/GROUP/SUBGROUP/SUBSUBGROUP/COMPUTER
In the same way, a client which does not belong to a group:
PROFILE:/COMPUTER
or even
PROFILE:COMPUTER
For a computer not belonging to a group and without a profile:
:/COMPUTER
or
:COMPUTER
or
/COMPUTER
or quite simply
COMPUTER
When you declare a new client, during the PXE boot, or by using the "Add a Client" tab, it is possible to set it as a member of a particular group/profile by using the notation described in Section 10.1.3, “Final Organization and Notation”.
Here are the concepts to understand for the LRS's groups and profiles:
A group (or a profile) only exists if there are clients in that group.
A group (or a profile) without clients will be automatically removed.
Adding a client to a non existing group (or profile) will automatically create the group.
PROFILES AND GROUPS ARE DYNAMICALLY GENERATED.
In practice, a group/profile is defined only if computers are members of it, but in the event of "re-creation" (i.e. in the case of a group/profile is implicitly created, then removed by moving of all the computers composing it, then again creation by adding a computer), all original information will be restored.
In parallel, changing the name of a computer can have two consequences:
If the profile/group into which it is integrated already exists: the menu of the computer itself is not modified,
If the profile/group into which it is integrated does not exist yet: it is created according to the same principle as the client declaration. The client's boot menu is not modified.
![[Important]](/ucome.rvt/any/en/Produits/LRS/details/doc/img/important.png) | |
In no case the renaming of a computer does modify its menu. For example to move a client from a A profile to a B profile will not change the profile of the moved client. |
The modification of a menu for a profile or a group implicitly modifies the menu of all the member clients. The menu of all the clients is overwritten (including the possible shared images which could be attached), but local images are not suppressed: they simply do not appear in the menu anymore.
The modification of a client belonging to a profile/group is always possible, at the price of a possible loss of synchronization of the client's boot menu of the corresponding group or profile.
The modification of the menu of a group modifies all the computers automatically belonging to it.